Robust

Users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible).

Information and user interface components must be presentable to users in ways they can perceive. This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses).

Provide text alternatives for non-text content.
Provide captions and other alternatives for multimedia.
Create content that can be presented in different ways , including by assistive technologies, without losing meaning.
Make it easier for users to see and hear content.

Is your Content Robust?

The questions below are designed to assist you in determining if your website, application, and/or content is robust to people with disabilities. Each question is linked to in-depth information, resources, and examples on how to apply the guidelines to our products.

Parsing - To ensure proper parsing, is website/application code complete, according to specifications, nested correctly, free of duplicate attributes, and are all IDs unique? (Success Criterion - 4.1.1 - Level A)
Name, Role, Value - In your platform/content, are there any interface components that have been developed or scripted internally that may not provide name, role, and value appropriately? (Success Criterion - 4.1.2 - Level A)
Status Messages - Still need questions (Success Criterion - 4.1.3 - Level AA)