> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/accessibility-widget.md).
# Accessibility Widget
Add an AI-powered accessibility widget to improve usability and support WCAG-aligned customer journeys.
{% hint style="info" %}
The Accessibility Widget is available for Echo sites. It is not available for landing pages.
{% endhint %}
The Accessibility Widget is an AI-powered accessibility layer for customer-facing Echo sites. It continuously scans for common accessibility issues and provides visitor controls for a more accessible browsing experience.
It supports WCAG-aligned web accessibility efforts without a separate manual remediation project. See the [Bolt-ons catalog](/customizations-and-bolt-ons/bolt-ons-catalog.md) for the request process.
### Best suited for
Use this bolt-on for client sites and portals with evolving content or code. It can support WCAG, ADA, and Section 508 accessibility requirements.
It is particularly useful for:
* Storefronts with frequent plan, promotion, or device updates.
* Customer account and checkout journeys.
* Support portals used by customers with different access needs.
### What you get
| Capability | Description |
| ------------------------- | --------------------------------------------------------------------------------------------------- |
| **Automated remediation** | AI scans and remediates common issues, including missing alt text, ARIA labels, and keyboard traps. |
| **Visitor controls** | Visitors can use accessibility profiles or adjust contrast, text size, and motion. |
| **Continuous scanning** | The widget rescans every 24 hours after installation. |
| **Standards alignment** | It supports WCAG 2.1 AA, ADA, Section 508, and international standards, including the EAA. |
| **Simple deployment** | Reach installs one script on the Echo site. Existing pages need no redevelopment. |
### Accessibility profiles and controls
Visitors can select a profile or customize individual settings.
| Option | Supports |
| ----------------------------------- | ------------------------------------------------------------------------- |
| Screen reader and keyboard profiles | Screen reader optimization and keyboard-only navigation. |
| Cognitive and seizure-safe profiles | Reduced distractions and controls for cognitive or seizure-related needs. |
| Display controls | Contrast, text size, and motion preferences. |
### Business use cases
* **Reduce accessibility gaps:** Identify and address common issues as the site changes.
* **Improve customer access:** Keep account, checkout, and support journeys easier to use.
* **Support procurement reviews:** Address common accessibility criteria in enterprise and public-sector reviews.
### Scope
{% columns %}
{% column %}
### In scope
* Widget installation and configuration on an Echo site.
* Automated scanning and remediation of common accessibility issues.
* Continuous 24-hour rescans.
* Visitor profiles and individual adjustment controls.
* Multi-language interface support.
{% endcolumn %}
{% column %}
### Out of scope
* Deployment on marketing landing pages.
* Manual code remediation for complex custom components.
* Formal VPAT documentation or legal compliance certification.
* Litigation defense.
{% endcolumn %}
{% endcolumns %}
{% hint style="warning" %}
The widget supports accessibility efforts. It does not provide legal certification or guarantee compliance.
{% endhint %}
### How it works
{% stepper %}
{% step %}
#### Install and configure
Reach installs and configures the widget on the Echo site.
{% endstep %}
{% step %}
#### Audit and remediate
The widget audits the site and applies automated fixes. Initial remediation typically completes within 48 hours.
{% endstep %}
{% step %}
#### Rescan every 24 hours
The widget rescans and re-remediates after content and code changes.
{% endstep %}
{% step %}
#### Enable visitor adjustments
Visitors select a profile or customize settings for their needs.
{% endstep %}
{% step %}
#### Monitor the integration
Reach monitors the integration as part of ongoing platform support.
{% endstep %}
{% endstepper %}
### Pricing
Tiered annual pricing based on site scale and support level. Contact your Account Manager for a proposal.
### Frequently asked questions
Is the Accessibility Widget available on landing pages?
No. The widget is available on Echo sites only.
How quickly does the initial audit complete?
Initial remediation typically completes within 48 hours of installation.
Does the widget replace manual accessibility remediation?
No. Complex custom components may need manual code-level remediation.
### Support information
{% hint style="info" %}
Questions or need clarification? Reach out to your respective Account Manager or email us at for assistance and support.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.reachplatform.com/customizations-and-bolt-ons/accessibility-widget.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.