Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not all of accessibility is for those who cannot see (well). WCAG also has a bunch of guidelines for loss of dexterity and other ailments:

• keyboard support (being able to navigate to all controls as needed, not being stuck in a navigation island from which there is no escape with the keyboard, etc.)

• pointing device considerations (not requiring drag unless absolutely essential, no action on mouse-down, etc.)

• not requiring the simultaneous use of mouse and keyboard (e.g. via modifier keys)

• sufficient size for buttons and other pointer targets

• the ability to suppress animations, flashing images, etc.

• the ability to control colors and contrast of things on the screen

...

Of course, something like Photoshop, Illustrator, or the visual part of Google Maps is hard to use when you cannot see, but there are so many different disabilities that some or even most accessibility guidelines can apply to pretty much any software.



Oh is that why modern American software is almost unusable? Give me back my modifier keys and compact UIs


No action on mouse down? So we need to develop applications that you can't click? Is that really part of accessibility requirements these days?


There's a difference between mouse down and mouse up. A click needs both.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: