You’re a developer who has just been handed a complex design spec. You know the designs support accessibility because your UX team read a…
in Section 508 contains one very sage suggestion. It states that,
“… sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology.”
Originally written for software, these words are even more relevant today given the prevalence of web based applications. They describe the type of information users with disabilities need in order to successfully complete a task. This could be a blind user with a screen reader, a voice input user with a physical disability, or any number of other types of users with a variety of assistive technologies.
The basic fundamentals of making any interaction accessible with both the keyboard and for screen reader users comes down to providing three basic pieces of information: identity, operation, and state.
Users interacting with an element as basic as a checkbox, or as complex as drag and drop experience, have to consider these three questions:
Curated by (Lifekludger)
Read full article at Source: How to Describe Complex Designs for Users with Disabilities – Salesforce UX – Medium