3 ms·
I think this comment makes a pretty clear case for it: https://news.ycombinator.com/item?id=25168303 https://news.ycombinator.com/item?id=25168303 For me pers
by forgotmypw17 6y ago
I think this comment makes a pretty clear case for it:
https://news.ycombinator.com/item?id=25168303 https://news.ycombinator.com/item?id=25168303
For me personally, the accessibility issues would be with elements used out of their usual role.
For example: When I, blessed with being sighted at this time, but without a mouse, ask my browser to identify the clickable/actionable elements on the page, it mis-identifies both unclickable elements as clickable, and clickable elements as unclickable.
I would call that a serious usability issue. And if I was not sighted, using a screen-reader, I would be very confused indeed by this landing page.
I agree that whether this qualifies as a "huge" usability issue is indeed a matter of opinion. I would certainly argue that it is a huge usability issue.
- ehnto 6y agoUsing the software you've got, would using role attributes be a sufficient workaround?