Bill Explainer now conforms to WCAG 2.1 AA accessibility standards across the Explainer microsite. This enhancement improves usability for all consumers and helps clients meet global accessibility and compliance requirements. It establishes a strong accessibility baseline by removing critical barriers that previously impacted users with visual, auditory, cognitive, or motor impairments.
By embedding accessibility into core microsite interactions, Bill Explainer delivers a more inclusive, reliable, and enterprise‑ready self‑service experience. WCAG 2.1 AA conformance covers the Explainer consumer microsite.
The Studio admin module is not covered by this release; Studio accessibility is planned for a future release
Use Cases
Inclusive Consumer Self‑Service
Consumers using assistive technologies such as screen readers or keyboard navigation can access bill explanations, understand changes, and complete actions independently.
Client Compliance Requirements
Clients with regulatory or contractual accessibility obligations can confidently deploy Bill Explainer knowing it meets WCAG 2.1 AA standards.
Enterprise Go‑to‑Market Readiness
Accessibility compliance removes potential blockers during procurement, legal review, and rollout, especially for accessibility‑sensitive markets.
The Solution
The Explainer microsite has been enhanced across multiple accessibility dimensions to meet WCAG 2.1 AA requirements. Key improvements include:
Full keyboard navigation with visible focus indicators
Screen reader‑friendly labels, alt text, and status messages
Improved color contrast and visual clarity
Accessible form validation and error messaging
Correct HTML structure and language semantics
Automated accessibility checks are built into the CI pipeline
Together, these changes ensure consistent and standards‑compliant accessibility across core consumer interactions.
Key Benefits
Compliance: Meets WCAG 2.1 AA accessibility standards
Usability: Improves ease of use for all users
Accessibility: Supports keyboard, screen reader, and low‑vision users
Consistency: Provides a uniform, accessible experience across the microsite
How It Works
Accessibility support is built directly into the Explainer microsite experience.
Users can navigate all interactive elements using a keyboard, with logical tab order and visible focus states.
Screen readers announce images, controls, errors, and confirmation messages using programmatic labels and ARIA support.
Text, icons, and UI components meet WCAG contrast thresholds for readability.
Forms provide clear, descriptive error messages that are visible and announced to assistive technologies.
Automated accessibility checks run during builds to catch critical issues early, while manual testing validates contextual usability.
These mechanisms work together to ensure that accessibility is maintained throughout the product's evolution.
Common Issues and Troubleshooting
Pages are difficult to navigate using a keyboard
Ensure all interactive elements remain reachable via standard tab navigation, and no custom styling removes focus visibility. Automated and manual QA checks help prevent this regression.
Screen readers do not announce errors or updates
Verify that status messages are exposed programmatically and not obscured by invalid ARIA attributes. Ensure error feedback includes descriptive text.
Text or buttons are hard to read
Check contrast ratios against WCAG standards. Validate that design tokens or styling changes have not reduced contrast below acceptable levels.
Accessibility regressions in new releases
Automated accessibility checks in the CI pipeline block builds when critical WCAG 2.1 AA violations are detected, preventing regressions from reaching production.
Compliance Documentation & Roadmap
A formal VPAT (Voluntary Product Accessibility Template) and Deque-certified audit are available on a per-client basis when contractually requested.
WCAG 2.2 alignment is on the future roadmap.