Content MUST be robust so that a variety of user agents and devices can interpret it. This includes assistive tech.
Again, a quick refresher on the levels:
- A, AA, AAA
- Many entities try to maintain a level AA compliance because it is achievable as well as meaningful. Maintaining just a level AA compliance is still falling short in being accessible and inclusive.
- Every guideline success criterion is necessary to at least some users with disabilities, so don't ignore level AAA compliance.
Compatability must be at the forefront of planning so that current and future user agents will be compatible. This includes assistive tech.
Following these standards:
- Content must be implemented in markup languages
- Elements must have complete start and end tags.
- Element must be nested to their specifications
- Elements don't include duplicated attributes
- Id's assigned to elements must be unique
- Only where specs allow
For all UI components:
- Name & Role programmatically determined
- States, Properties, and Values that can be set by users can be programmatically set.
- Changes allow for notifications to the user agents.
This particular success criterion is primarily for web authors, who build custom controls
Content that is implemented by using markup languages, a status message, or messages can be programmatically determined through role or props such that they can be present to the user through assistive tech without receiving focus.
Oh... My... Glob! We've made it! We have covered the POUR Principles of the WCAG 2.0 & 2.1 Guidelines. That is so exciting! I'm hoping that this is just the beginning of your journey into exploring accessibility and wish you the best as you continue to study to make software and the web a better place for all.