The CMS Design System strives to work for as many people as possible, including people with disabilities.
What we do to help meet and exceed standards
- Embed accessibility and inclusive design practices into our workflow.
- Provide accessibility as a checkpoint in new components created in the design system.
- Add accessibility as a key aspect to much of the component documentation.
- Conduct regular accessibility reviews of new and existing features and documentation for the design system.
- Use Axe libraries for automated accessibility testing in our end to end testing.
We test with these assistive technology pairings
| Operating system | Browser | Screen reader |
|---|---|---|
| OS X 13.2.1 (Ventura) | Safari (latest version) | VoiceOver |
| Windows 10 | Chrome (latest version) | NVDA (latest version) |
| Windows 10 | Edge (latest version) | JAWS 2021 |
| iOS (latest version) | Safari (latest version) | N/A |
What level we meet currently
The CMS Design System currently meets or exceeds WCAG 2.0 AA and Section 508 standards, which requires information and communications technology developed, procured, maintained, or used by the federal government be accessible to both employees and members of the public with disabilities.
Additionally, each component page has its own component maturity checklist which includes a summary of the efforts made toward accessibility. For more information about how we tested and validated our work for each checklist item, read our component maturity documentation.
More information on Section 508 can be found at:
Current browser/technology support
The current browser support for the design system can be viewed here.
How to provide feedback
If you cannot access any content or use any features on this website due to a disability, please reach out and include the URL and/or other identifying information.
- Contact the CMS Design System team
- File a GitHub issue.
- Contact the CMS Section 508 Team via email at 508Feedback@cms.hhs.gov.