Skip to main content
Accessibility
Purpose of These DocsThese docs are meant as a starting point for using Anvil2 accessibly. While the contents can contribute to building accessible interfaces from scratch, that is not the main goal.
Not just as engineers or designers, but as humans, we should strive to ensure our product is built with accessibility for all users in mind. Anvil2 has a baseline of meeting WCAG 2.2 AA standards built-in, but there are still certain things that the implementing teams need to be mindful of to ensure they are continuing with this approach. This guide focuses on practical implementation patterns that teams can apply when using Anvil2 components. While the design system provides the technical foundation for accessibility, implementing teams are responsible for content-level accessibility, proper labeling, and ensuring that their specific use cases meet accessibility requirements. Each section provides clear guidance on what Anvil2 handles automatically versus what teams need to implement themselves. Please reach out on slack in #ask-designsystem or #accessibility-champions for further guidance, help, and information.
Most countries in the world have some form of law on the books stating that digital applications must meet a level of WCAG to be compliant. In the United States, the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act require digital accessibility compliance, with courts and regulations increasingly referencing WCAG 2.1 AA as the standard. The European Union’s Web Accessibility Directive mandates EN 301 549 compliance (based on WCAG 2.1 AA) for public sector websites and applications. Canada, Australia, and many other countries have similar requirements. Beyond legal compliance, building accessible products is simply the right thing to do. It ensures that all users, regardless of their abilities, can access and use our applications effectively. This includes users with visual, auditory, motor, cognitive, and other disabilities who rely on assistive technologies like screen readers, voice recognition software, or alternative input devices. Want to learn more about a11y laws and their impact for not just our product but also our clients?

​
Business Impact

Accessibility compliance isn’t just about avoiding legal risk—it’s about creating better products for everyone. Accessible design often improves usability for all users, enhances SEO performance, and expands your potential user base to include the global population who have disabilities. By embracing the social model over the medical model of disability, we recognize that barriers are often created by design, not by individual limitations. Therefore, designing for accessibility not only removes these barriers for people with disabilities but also enhances usability and improves the experience for all users by providing flexible and adaptable interfaces for any scenario one might find themselves in.
Last modified on January 23, 2026