Accessibility Statement Best Practices
Overview
Learn how to create an effective, legally sound accessibility statement that demonstrates your commitment to inclusion while protecting your organization from potential legal risks.
Who This Is For
Compliance officers
Legal and HR departments
Website owners managing risk
Organizations serious about accessibility
What You'll Learn
Legal best practices for statements
What to include and what to avoid
How to demonstrate good faith
Industry standards and recommendations
The Golden Rules
1. Be Honest, Not Perfect
DON'T:
❌ Claim 100% compliance unless professionally audited
❌ Say "fully accessible" without evidence
❌ Overclaim your conformance level
DO:
✅ "We strive to conform to WCAG 2.2 Level AA"
✅ "We are continually improving accessibility"
✅ "We acknowledge some areas need improvement"
Why: Honesty demonstrates good faith and is legally safer than false claims.
2. Be Specific, Not Vague
DON'T:
❌ "We care about accessibility"
❌ "Our site works with assistive technologies"
❌ "We follow best practices"
DO:
✅ "Our website supports JAWS, NVDA, and VoiceOver screen readers"
✅ "All interactive elements are keyboard accessible"
✅ "We maintain a minimum 4.5:1 contrast ratio for all text"
Why: Specific claims are more useful to users and show deeper understanding.
3. Acknowledge Limitations
DON'T:
❌ Hide known accessibility issues
❌ Ignore reported problems
❌ Claim there are no barriers
DO:
✅ List known issues with remediation timeline
✅ Invite user feedback
✅ Show active work on improvements
Why: Transparency builds trust and demonstrates ongoing effort.
What to Include
Essential Components
1. Organizational Commitment (Required)
Format:
[Organization Name] is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.
Customize With:
When accessibility became a priority
Who in organization is responsible
Specific policies or initiatives
Example:
Since 2023, AllAccessible has made accessibility a core company value. Our dedicated Accessibility Team, led by our Chief Accessibility Officer, reviews all new features and content for WCAG 2.2 AA compliance before launch.
2. Conformance Status (Required)
Format:
We aim to conform to [Standard] [Level]. We regularly test our website to ensure we meet these standards.
Common Standards:
WCAG 2.2 Level AA (most common)
WCAG 2.2 Level AAA (higher standard)
Section 508 (US Federal)
EN 301 549 (EU)
Example:
Conformance Status: Partial WCAG 2.2 Level AAWe aim for WCAG 2.2 Level AA conformance. As of our most recent audit (October 2025), we meet approximately 85% of applicable success criteria. We are actively addressing the remaining 15%.
3. Accessibility Features (Required)
List Specific Features:
Our website provides:Visual Accessibility: • Text resizing up to 200% • High contrast modes (dark and light) • Color blindness adjustments • Increased line and letter spacingNavigation: • Full keyboard navigation • Skip links to main content • Visible focus indicators • Logical heading structureAssistive Technology: • Screen reader compatible (JAWS, NVDA, VoiceOver) • Alternative text for images • ARIA labels for interactive elements • Text-to-speech functionality
4. Known Limitations (Recommended)
Be Transparent:
Good Example:
Known Accessibility Barriers:1. Legacy PDF Documents Status: 47 PDF files lack proper tagging Timeline: Updating 5 files per week Expected Resolution: March 20262. Third-Party Embedded Content Status: Some social media embeds lack full accessibility Mitigation: Providing text alternatives Working With: Twitter/Facebook to improve their embeds3. Complex Data Visualizations Status: Some charts lack text equivalents Timeline: Adding data tables for all charts by Q1 2026
Why This Works:
Shows awareness
Demonstrates active work
Provides timeline
Manages expectations
5. Feedback Mechanism (Required)
Provide Clear Contact Info:
Accessibility Feedback:If you experience accessibility barriers on our website:Email: [email protected] Phone: (555) 123-4567 ext. 8 Online Form: yourcompany.com/accessibility-feedbackResponse Time: We respond within 2 business daysAccessibility Coordinator: Jane Smith Department: Digital Accessibility Team
Must Include:
Specific contact method (not generic support)
Response timeline
Person/department responsible
6. Assessment Information (Required)
Document Your Testing:
Assessment and Testing:This statement was created: October 1, 2025 Last reviewed: October 1, 2025 Next scheduled review: April 1, 2026Testing Methods: • Automated testing: AllAccessible compliance scans (weekly) • Manual testing: Screen reader evaluation (quarterly) • User testing: Feedback from assistive technology users • Third-party audit: Annual WCAG audit by [Auditor Name]Tools Used: • AllAccessible automated scanning • WAVE browser extension • axe DevTools • Manual testing with NVDA and JAWS screen readers
Legal Considerations
Good Faith Effort
Courts look favorably on organizations that demonstrate good faith effort:
Evidence of Good Faith:
✅ Published accessibility statement
✅ Regular testing and audits
✅ Remediation timeline for known issues
✅ Responsive to user complaints
✅ Budget allocated to accessibility
Not Good Faith:
❌ Ignoring accessibility entirely
❌ Statement exists but no actual work
❌ No response to user reports
❌ False claims of full compliance
What NOT to Say
❌ Absolute Claims
Avoid:
"Our website is 100% accessible"
"We are fully compliant with all standards"
"Zero accessibility barriers exist"
Why: Almost impossible to prove, and sets you up for liability.
❌ Disclaimers of Responsibility
Avoid:
"We are not responsible for accessibility issues"
"Use of this site assumes acceptance of limited accessibility"
"Accessibility compliance is not guaranteed"
Why: These statements can be seen as violations of disability rights laws.
❌ Excuses
Avoid:
"Accessibility is too expensive to implement"
"Very few of our users need accessibility features"
"Older technology doesn't support accessibility"
Why: Courts generally don't accept these as valid reasons.
Industry Standards and Recommendations
W3C WAI Guidelines
The W3C (Web Consortium) recommends accessibility statements include:
Basic Information:
Standard to which you conform (WCAG 2.2)
Conformance level (A, AA, or AAA)
Additional information about your site
Optional but Recommended:
4. Status (full, partial, non-conformance)
5. Non-accessible content explanation
6. Limitations and alternatives
7. Feedback mechanism
8. Formal complaints procedure
DOJ (Department of Justice) Guidance
The US DOJ recommends:
Clear statement of commitment
Specific contact for accessibility issues
Description of available accessibility features
Information on how to request accommodations
Regular review and updates
Accessibility Professional Recommendations
Best Practices from Experts:
Include Positive Examples
Don't just list problems
Highlight what works well
Show accomplishments
Provide Context
Explain why some issues can't be fixed immediately
Show the process for prioritization
Demonstrate resource allocation
Link to Supporting Documents
VPAT reports
Audit results
Accessibility roadmap
Policy documents
Template: Professional Accessibility Statement
Accessibility Statement for [Organization Name]Last Updated: [Auto-Date]---1. COMMITMENT TO ACCESSIBILITY[Organization Name] is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.---2. CONFORMANCE STATUSWe aim to conform with WCAG 2.2 Level AA standards. These guidelines help make web content more accessible for people with disabilities and improve usability for everyone.Current Status: Partial Conformance Most Recent Audit: [Date] Conformance Level: Approximately [X]% of WCAG 2.2 AA criteria met---3. ACCESSIBILITY FEATURESOur website provides the following accessibility features:Visual Adjustments: • Text sizing and spacing controls • Color contrast modes including dark mode • Color blindness filters (protanopia, deuteranopia, tritanopia) • High contrast and inverted color optionsNavigation Assistance: • Full keyboard navigation support • Skip links to main content • Reading guides and focus indicators • Logical heading structureAssistive Technology Support: • Screen reader compatibility (JAWS, NVDA, VoiceOver) • Alternative text for meaningful images • ARIA labels for interactive elements • Text-to-speech functionality • Keyboard shortcutsThese features are provided through the AllAccessible widget, available on every page via the accessibility button.---4. KNOWN LIMITATIONSDespite our efforts, some areas may have accessibility barriers:[List specific known issues with timelines]We welcome reports of any accessibility barriers not listed here.---5. FEEDBACK AND CONTACTWe welcome feedback on the accessibility of [Website Name].If you encounter an accessibility barrier:Email: accessibility@[domain].com Phone: [(XXX) XXX-XXXX] Response Time: Within 2 business daysAccessibility Coordinator: [Name] Department: [Department Name]---6. ACCOMMODATION REQUESTSIf you need content in an alternative format or require specific accommodations to access our website:• Email your request to accessibility@[domain].com • Describe the barrier you encountered • Specify the alternative format needed • We will provide accommodations within 5 business days---7. ASSESSMENT AND TESTINGTesting Methods: • Automated testing: Weekly scans with AllAccessible • Manual testing: Quarterly evaluation with assistive technologies • User feedback: Ongoing collection and responseTools and Technologies: • AllAccessible automated compliance scanning • Manual screen reader testing (NVDA, JAWS) • Keyboard navigation testing • Color contrast analyzersNext Scheduled Review: [Date + 6 months]---8. FORMAL COMPLAINTSIf you are not satisfied with our response to your accessibility concern:[Include government enforcement agency contact, if applicable]• US: File complaint with Department of Justice (ADA) • UK: Equality Advisory and Support Service • EU: National enforcement body • Canada: Canadian Human Rights Commission---9. TECHNICAL SPECIFICATIONSThis website is designed to work with:Browsers: • Chrome, Firefox, Safari, Edge (current and previous version) • Mobile browsers (iOS Safari, Chrome Mobile)Assistive Technologies: • Screen readers (JAWS 2020+, NVDA 2020+, VoiceOver) • Speech recognition software • Browser accessibility extensionsThe website uses: • Responsive design • Semantic HTML5 • WAI-ARIA where appropriate • AllAccessible widget for enhanced accessibility---10. THIRD-PARTY CONTENTOur website may include content from third parties (social media embeds, videos, etc.). We cannot guarantee the accessibility of third-party content but are working with vendors to ensure accessibility where possible.---Powered by AllAccessible - Professional Web Accessibility Platform
Reviewing Your Statement
Self-Review Checklist
Before publishing, verify your statement includes:
Content:
Organization name and commitment
Specific conformance standard (WCAG 2.2 AA)
List of accessibility features
Known limitations with timelines
Clear contact information with response time
Assessment and testing information
Last updated date
Legal:
Honest, accurate claims
No false compliance statements
No disclaimers of responsibility
Specific to your actual site
Accessibility:
Proper heading structure
Links work correctly
Contact info is accessible
Easy to read and understand
Statement Maintenance Schedule
Quarterly Review (Every 3 Months)
Quick Check:
Contact information still accurate?
Any new known issues to add?
Old issues resolved?
Features added/removed?
Time Required: 15 minutes
Semi-Annual Review (Every 6 Months)
Comprehensive Review:
Run new accessibility audit
Update conformance percentage
Review all listed issues
Update timelines
Get legal review
Time Required: 1-2 hours
Annual Review (Every 12 Months)
Complete Overhaul:
Full accessibility audit
Update all content
Review against new WCAG versions
Update contact information
Consider third-party professional audit
Time Required: 2-4 hours
Getting Legal Review
When You Need Legal Review
Recommended For:
High-risk industries (healthcare, finance, education)
Organizations with 500+ employees
Government contractors
Companies that have received complaints
Websites with high traffic (100k+ monthly visitors)
What to Ask Your Lawyer
Does our statement meet ADA/WCAG requirements for our industry?
Are our known limitations disclosed appropriately?
Is our feedback mechanism sufficient?
Should we include additional disclaimers?
Are we at risk based on current conformance level?
Typical Cost: $200-500 for statement review
Common Questions
Q: Can a well-written statement protect me from lawsuits?
A: A statement alone doesn't provide legal immunity, but demonstrates good faith effort which courts consider favorably.
Q: Should I mention specific lawsuits or complaints?
A: Generally no, unless required by settlement. Focus on forward-looking improvements.
Q: How detailed should known limitations be?
A: Be specific enough to be useful, but don't overwhelm users. List major issues with timelines.
Q: Can I link to my VPAT report?
A: Yes! This adds credibility and provides detailed technical information.
Q: Should I include a "last updated" date?
A: Absolutely. It shows active maintenance and regular review.
Q: What if I haven't done any testing yet?
A: Be honest: "Initial accessibility statement. Comprehensive testing scheduled for [Date]"
Related Articles
What is an Accessibility Statement? - Purpose and importance
Creating and Publishing Your Accessibility Statement - Getting started
Editing Your Statement - Customization guide
Updating Your Statement - Maintenance guide
External Resources
Legal and Compliance:
Examples and Templates:
Last Updated: October 2025
Legal Disclaimer: This guide provides general best practices, not legal advice. Consult an accessibility attorney for specific legal guidance.