Reputation
22,183
Next tag badge:
147/100 score
19/20 answers
Badges
9 77 118
Newest
 Nice Answer
Impact
~664k people reached

11h
comment Is the folder structure dying?
I have removed the comments here. This is not the place for extended discussions. Please use the User Experience Chat if you wish to continue.
14h
comment morae (multiple cameras)
I'm voting to close this question as off-topic because it is about product / software recommendations; it isn't a User Experience question that needs solving. Although it may be used by User Experience practitioners, that doesn't necessarily mean it is a UX question.
15h
comment Best mobile landing pages
We can't really help with things like this I'm afraid. 'Best' is very subjective, there is no 'best' UI. You're probably best looking for some pattern libraries that cover off content items you're looking for.
1d
comment Improving google ranking for city specific pages
I'm voting to close this question as off-topic because it is about search engine optimisation, it is not a User Experience question needing a solution.
1d
answered Does the hover functionality on Netflix's website break UI best practice?
2d
awarded  Nice Answer
2d
comment How do you make a range input / slider accessible to screen readers for blind UX
@DA01 yup. We just did some usability testing and found just that too.
Jul
3
comment How to display a family tree structure with both parents and multiple interconnections using SVG or HTML?
We can't help with how to implement something. Besides, you've posted this to StackOverflow already so you should only post a question to one site, not cross-posting elsewhere. A question is rarely a fit for multiple sites at the same time.
Jul
3
awarded  accessibility
Jul
2
awarded  Nice Question
Jul
2
comment Do disabled buttons still need to be contrast compliant for accessibility?
@JonasDralle I'm not suggesting having a colourblind inaccessible site as a whole, my concern is with inactive buttons only and whether their colour contrast could be considered an accessibility fail. We're not serving up less content to colourblind users - there is messaging on the page to inform them of missing functionality - and to make disabled buttons more accessibly in contrast may mean that fully sighted users (which make up the majority) do not realise the option is disabled, therefore being a worse experience for more users.
Jul
2
comment Controlling movement direction in isometric view
@NathanRabe True. That's why FPS games have in-game options screen where you can flip with Y axis controls. Something similar should be added to this game too.
Jul
2
comment Controlling movement direction in isometric view
Yeah, maybe my wording is a bit clunky (and I went with Camel Case too for some crazy reason) but perhaps just "Use the cursor keys to move towards the mcguffin" would work too.
Jul
2
comment Help on placing controls
Can you elaborate a bit on this? It's a bit low on details - when you say 'controls' I assume you mean the Insert / Clear buttons? and what is it about them that you don't think is working?
Jul
2
revised Help on placing controls
deleted 165 characters in body; edited tags
Jul
2
answered Controlling movement direction in isometric view
Jul
2
comment Do disabled buttons still need to be contrast compliant for accessibility?
You make a good point though. Just because something officially / legally ticks all the boxes, that isn't going to help those individuals who get into difficulty as a result of a design decision. They won't care the site is 100% AA compliant if they can't do something they wanted to.
Jul
2
accepted Do disabled buttons still need to be contrast compliant for accessibility?
Jul
2
comment Do disabled buttons still need to be contrast compliant for accessibility?
Ah bingo! Not sure how I missed that in the WCAG guidelines, but it does support my opinion, so I'm happy!
Jul
2
comment Do disabled buttons still need to be contrast compliant for accessibility?
@RogerAttrill there is still messaging on the screen to give feedback to users of this. I am concerned that we may end up with a button that isn't so clearly disabled just so that it passes DDA / WCAG, but to the detriment of the majority of users (sighted ones) who will be less able to clearly tell that the feature is unavailable.