Skip to main content

Editing Your Accessibility Statement

Customize your auto-generated accessibility statement to include organization-specific information, known limitations, and your unique accessibility c

Written by Frank

Editing Your Accessibility Statement

Overview

Customize your accessibility statement to include organization-specific information, known limitations, and your unique accessibility commitments. This guide walks you through using AllAccessible's rich-text editor.

Who This Is For

  • Paid AllAccessible users (Starter and above)

  • Website owners customizing their statement

  • Compliance officers managing accessibility documentation

What You'll Learn

  • How to access the statement editor

  • How to customize statement content

  • How to preview your changes

  • How updates appear on your website

Accessing the Statement Editor

Step 1: Navigate to Accessibility Statement

  1. Log in to your AllAccessible dashboard

  2. Select your website from your list of sites

  3. Open the Accessibility Statement tab

Step 2: Understanding the Editor Interface

You'll see three main sections:

1. Statement Information Cards

  • Compliance Standard: Your target level (typically WCAG 2.2 AA)

  • Last Updated: The date shown for your statement

  • Testing Method: How accessibility is assessed

2. Rich Text Editor

  • Full WYSIWYG editor (What You See Is What You Get)

  • Formatting toolbar for text styling

  • Drag-and-drop editing

3. Action Buttons

  • Preview: See how your statement will look to users

  • Save Statement: Publish your changes

Using the Rich Text Editor

Basic Formatting

The editor includes standard formatting tools:

Text Styling:

  • Bold and Italic text

  • Underline and strikethrough

  • Text color and highlighting

  • Font size and heading levels

Lists:

  • Bulleted lists

  • Numbered lists

  • Nested lists

  • Indent and outdent

Alignment:

  • Left, center, right, justify

  • Text direction

Links:

  • Insert hyperlinks

  • Link to email addresses

  • Link to other pages

Adding Content Sections

Recommended Sections to Include:

1. Organization-Specific Commitment

Example:
"At [Your Company], accessibility is a core value. Our dedicated
accessibility team reviews all new content and features to ensure
they meet or exceed WCAG 2.2 Level AA standards."

2. Known Limitations

Example:
"Current Known Issues:
• Some PDF documents uploaded before 2023 may not be fully tagged
  for screen readers. We are systematically reviewing and updating
  these documents.
• Certain third-party embedded content (social media feeds) may not
  be fully accessible. We are working with vendors to address this.
• Expected Resolution: Q2 2026"

3. Specific Contact Information

Example:
"For accessibility-related questions or to request accommodations:Email: [email protected]
Phone: (555) 123-4567
Accessibility Coordinator: Jane Smith
Response Time: Within 2 business days"

4. Alternative Formats

Example:
"Alternative Formats Available:Upon request, we can provide this website's content in alternative
formats including:
• Large print
• Audio format
• Simplified language
• Braille (via certified transcription service)Contact us at [email protected] to request alternative formats."

Previewing Your Changes

Step 1: Click Preview Button

  1. Make your edits in the editor

  2. Click the Preview button (eye icon)

  3. A modal window opens showing how your statement will appear

Step 2: Review Appearance

Check for:

  • Formatting looks correct

  • Links work properly

  • Contact information is accurate

  • No typos or grammatical errors

  • Proper heading structure

Step 3: Make Additional Edits

  • Close preview (click X or press Escape)

  • Make any needed changes

  • Preview again to verify

Tip: Preview multiple times to ensure everything looks perfect!

Saving Your Changes

Step 1: Click Save Statement

  1. After editing and previewing

  2. Click the Save Statement button (green button)

  3. You'll see a success message: "Accessibility statement updated successfully!"

Step 2: Understand Update Propagation

Important: Changes take up to 1 hour to appear on your live website due to performance caching.

Caching Timeline:

  • Dashboard: Changes saved immediately

  • Server Cache: Updates within 5-60 minutes

  • Browser Cache: Updates within 24 hours for repeat visitors

Why We Cache:

  • Faster widget loading (sub-100ms)

  • Reduced server load

  • Better performance worldwide

  • Improved user experience

Step 3: Verify on Your Website

After 60 minutes:

  1. Visit your website

  2. Open the AllAccessible widget

  3. Scroll to widget footer

  4. Click "Accessibility Statement"

  5. Verify your changes appear

If changes don't appear:

  • Clear your browser cache (Ctrl+Shift+R or Cmd+Shift+R)

  • Try incognito/private browsing mode

  • Wait another 30 minutes for cache expiration

Best Practices for Editing

1. Keep It Clear and Concise

Good:

"We test accessibility using automated scans and manual evaluation with screen readers."

Too Vague:

"We make sure our website is accessible."

2. Be Honest About Limitations

Good:

"Some legacy PDF files may not be fully accessible. We're updating these on a rolling basis, with completion expected by June 2026."

Bad:

"Our website is 100% accessible." (Almost never true!)

3. Use Plain Language

Good:

"Screen reader compatible - works with JAWS, NVDA, and VoiceOver"

Too Technical:

"ARIA-compliant semantic markup with proper landmark regions and role attributes"

4. Provide Specific Contact Info

Good:

"Email [email protected] (response within 2 business days)"

Too Generic:

"Contact us if you have issues"

5. Include Action Items

Good:

"We review our accessibility statement quarterly and conduct full audits semi-annually."

Passive:

"We care about accessibility."

Advanced Editing Tips

Using Headings Properly

Structure your statement with proper headings:

  • H2: Main sections (Our Commitment, Conformance Status)

  • H3: Subsections (Contact Information, Known Issues)

  • H4: Minor subsections if needed

Why: Screen readers use headings for navigation!

Adding Links

Link to Supporting Documents:

  • Full WCAG compliance report

  • VPAT/ACR documents

  • Accessibility policy PDF

  • Third-party audit results

Example:

View our full <a href="/wcag-compliance-report.pdf">WCAG Compliance Report</a>

Formatting Lists

Use lists for easy scanning:

Features List:

  • Keyboard navigation support

  • Screen reader compatibility

  • Text resizing up to 200%

  • High contrast modes

  • Focus indicators

Contact Options:

  1. Email: [email protected]

  2. Phone: (555) 123-4567

  3. Mail: 123 Main St, City, State, ZIP

AI-Assisted Drafting (Coming Soon)

We're developing an AllAccessible AI feature to help you draft and refine your statement:

Planned:

  • ✦ Help drafting statement content

  • Suggestions for improving clarity and completeness

  • Prompts for information you may have missed

Status: In development. For now, the editor is fully manual — you write and edit every word yourself, and the starter template gives you a solid head start.

Common Editing Scenarios

Scenario 1: Adding Your Accessibility Team

Our Accessibility Team:Accessibility Coordinator: Jane Smith
Email: [email protected]
Phone: (555) 123-4567The accessibility team:
• Reviews all new content for compliance
• Responds to accommodation requests
• Conducts quarterly audits
• Manages remediation priorities

Scenario 2: Documenting Known Issues with Timeline

Known Accessibility Barriers and Resolution Timeline:1. PDF Accessibility (In Progress)
   Issue: 127 PDF documents lack proper tagging
   Impact: Screen readers may not read content correctly
   Timeline: Updating 10 documents weekly
   Expected Resolution: March 20262. Video Captions (Planned)
   Issue: 15 product videos lack closed captions
   Impact: Deaf users cannot access audio content
   Timeline: Starting January 2026
   Expected Resolution: April 2026

Scenario 3: Adding Accommodation Request Process

Requesting Accessibility Accommodations:If you require content in an alternative format or need specific
accessibility accommodations, please submit a request:• Email: [email protected]
• Phone: (555) 123-4567 ext. 8
• Online Form: www.company.com/accessibility-requestWe will respond within 2 business days and provide requested
accommodations within 5 business days when possible.

What NOT to Include

❌ False Claims

Don't claim compliance levels you haven't verified:

  • "Our site is 100% compliant" (almost never true)

  • "We meet AAA standards" (unless professionally audited)

  • "Zero accessibility issues" (every site has some)

❌ Legal Jargon

Avoid legalese that confuses users:

  • "Pursuant to 42 U.S.C. §12101 et seq..."

  • Complex legal disclaimers

  • Liability waivers

Keep it user-friendly!

❌ Excuses

Don't make excuses for accessibility barriers:

  • "Accessibility is too expensive to implement"

  • "We don't have many disabled users"

  • "Older browsers aren't supported"

Instead: Acknowledge issues and provide timeline for fixes.

Saving and Publishing Workflow

Recommended Process:

  1. Draft Your Edits

    • Make all changes in editor

    • Don't save yet

  2. Preview Multiple Times

    • Check desktop view

    • Imagine mobile view

    • Read as if you're a user

  3. Get Internal Review (Optional)

    • Share preview with team

    • Get legal review if needed

    • Collect feedback

  4. Save and Publish

    • Click Save Statement

    • Note the time (for cache tracking)

  5. Verify After 1 Hour

    • Check live site

    • Test on different devices

    • Confirm changes appear correctly

Frequently Asked Questions

Q: Can multiple team members edit the statement?
A: Yes, anyone with access to your AllAccessible account can edit. Last save wins, so coordinate with your team.

Q: Is there a character limit?
A: No hard limit, but keep it concise (500-1000 words recommended).

Q: Can I include images in my statement?
A: Currently, the editor supports text and HTML only. Images not recommended for accessibility reasons.

Q: What happens if I accidentally delete everything?
A: Click the "Generate with AI" button to restore a default statement, or contact support to restore your previous version.

Q: Can I see a history of changes?
A: Not currently. We recommend copying your statement to a document before making major changes.

Need Help?

Stuck with editing?

Related Articles

Last Updated: October 2025
​Editor: TinyMCE Rich Text Editor
​Cache Time: Up to 1 hour for updates to propagate

Related Articles
Did this answer your question?