What is an accessibility statement?

An accessibility statement is a public declaration of your website's commitment to accessibility. It describes conformance levels, accessibility features, known limitations, and how users can report issues. It demonstrates transparency and good-faith efforts to comply with accessibility laws.

Is an accessibility statement legally required?

While not always legally mandated, accessibility statements are strongly recommended and often expected under ADA (Americans with Disabilities Act), Section 508, and European accessibility directives. They demonstrate due diligence and commitment to accessibility.

What is WCAG and which level should I target?

WCAG (Web Content Accessibility Guidelines) has three levels: A (minimum), AA (recommended standard), and AAA (highest). Most legal requirements and best practices target WCAG 2.1 Level AA. WCAG 2.2 (latest version) adds new criteria for mobile and cognitive accessibility.

What's the difference between WCAG 2.0, 2.1, and 2.2?

WCAG 2.1 (2018) adds mobile, low vision, and cognitive accessibility criteria to 2.0. WCAG 2.2 (2023) adds criteria for mobile interactions, authentication, and cognitive support. Each version is backward compatible - meeting 2.2 means you meet 2.1 and 2.0.

What does ADA compliance mean for websites?

The ADA (Americans with Disabilities Act) requires places of public accommodation to be accessible. Courts have ruled this includes websites. While ADA doesn't specify technical standards, most organizations follow WCAG 2.1 Level AA as the de facto standard for ADA compliance.

How do I test my website's accessibility?

Use automated tools (WAVE, axe DevTools, Lighthouse), manual keyboard testing, screen reader testing (NVDA, JAWS, VoiceOver), and ideally user testing with people with disabilities. Automated tools catch only 30-50% of issues - manual testing is essential.

What should I do if my site isn't fully accessible yet?

Be honest in your accessibility statement. State 'Partial conformance' or 'Working toward' and list known issues with planned remediation timelines. Provide alternative contact methods. Transparency and ongoing improvement show good faith.

What are common accessibility features I should implement?

Essential features include keyboard navigation, screen reader compatibility, alt text for images, sufficient color contrast, resizable text, clear focus indicators, skip navigation links, descriptive link text, and ARIA landmarks for complex interfaces.

Do I need to provide alternative formats like large print or Braille?

For digital content, web accessibility (WCAG conformance) usually suffices. However, if requested, you may need to provide alternative formats. Your accessibility statement should explain how users can request alternatives and your process for providing them.

How often should I update my accessibility statement?

Update your accessibility statement whenever you make significant accessibility improvements, discover new barriers, change conformance levels, or after accessibility audits. Review it at least annually to ensure accuracy.

Accessibility Statement Generator - ADA & WCAG Compliant

Organization Information

Organization Name *

Website URL *

Contact Email *

Accessibility Contact Phone

Conformance Level

WCAG Conformance *

Assessment Method

Last Assessment Date

Known Limitations

Known Accessibility Issues (if any) Be transparent about known issues and describe your plans to address them.

Feedback Mechanism

How can users report accessibility barriers?

Email contact

Online feedback form

Phone support

Expected Response Time