accessWidget is accessiBe’s Layer 1 product, the runtime accessibility layer of the three-layer platform. It operates on the live site, in the visitor’s browser session, scanning the rendered DOM and applying programmatic corrections to accessibility barriers it can reliably detect and address.
What accessWidget does
1. Background remediation:
An AI-powered engine continuously scans a website’s DOM and applies corrections to WCAG-related barriers with objectively verifiable properties. That includes color contrast and decorative image markup. It also corrects ARIA attributes that are missing, and handles unlabeled form fields and keyboard navigation patterns automatically. The engine runs on a recurring scan cycle, adapting as site content changes.
2. Accessibility interface:
A customizable widget that appears on the site and gives visitors control over how content is presented. Website visitors can activate disability profiles designed for common accessibility needs, or make individual adjustments to font size, contrast level, text spacing, cursor behavior, and other display parameters. Adjustments are session-based and affect only that visitor’s experience.
What accessWidget is not
accessWidget is a runtime accessibility layer, not a code rewrite. It applies corrections to the rendered page, but does not modify the underlying source code. Source code issues that accessWidget addresses at runtime remain in the codebase. For organizations focused on sustainable accessibility, addressing root causes in code – accessFlow – is an important complement.
accessWidget also does not produce the documentation required for procurement or litigation. That includes VPAT documents, Accessibility Conformance Reports, and manual audit deliverables. These require human expertise and are provided through accessServices.
How accessWidget fits in the platform
accessWidget is designed to work within accessiBe’s three-layer platform. Organizations that deploy only accessWidget are addressing Layer 1. Adding accessFlow gains development-time testing. Adding accessServices provides audit documentation, user testing, and program management.
The layers compound: accessWidget monitors surface issues for developer review; accessFlow reduces what accessWidget needs to address at runtime; accessServices validates and documents the whole.
