Skip to main content
AuditAble
Free Scan
Back to Home

Accessibility Statement

Last reviewed: March 2026

Our Commitment

As an accessibility company, we hold ourselves to the highest standard. We believe that if we ask our customers to make their digital services accessible, our own platform must lead by example. Accessibility is not a feature we bolt on at the end. It is a core design principle that informs every decision we make, from architecture to implementation to testing.

We are committed to ensuring that AuditAble is usable by everyone, including people who use screen readers, keyboard-only navigation, voice control, magnification software, and other assistive technologies.

Conformance Target

AuditAble targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. WCAG 2.1 Level AA is the standard referenced by the DOJ Final Rule (28 CFR Part 35) for state and local government web content and the standard we help our customers work toward.

What We Have Done

We have taken the following concrete steps to make our platform accessible:

  • Semantic HTML: All pages use proper heading hierarchy, landmark regions, lists, and other semantic elements so assistive technologies can accurately convey page structure.
  • Keyboard Navigation: Every interactive element on our platform is fully operable with a keyboard alone. Tab order follows a logical sequence, and no keyboard traps exist.
  • Screen Reader Testing: We regularly test our platform with NVDA (Windows) and VoiceOver (macOS/iOS) to verify that all content is properly announced and that interactive workflows are understandable without visual context.
  • Color Contrast: All text and interactive elements meet or exceed WCAG 2.1 AA contrast ratios (4.5:1 for normal text, 3:1 for large text and UI components).
  • Focus Indicators: All focusable elements display visible focus indicators that meet contrast requirements, ensuring keyboard users always know where they are on the page.
  • Alternative Text: All meaningful images include descriptive alternative text. Decorative images are properly marked so screen readers skip them.
  • ARIA: We use ARIA attributes where native HTML semantics are insufficient, following the ARIA Authoring Practices Guide to ensure correct implementation of complex widgets.
  • Responsive Design: Our platform adapts to different screen sizes and supports text resizing up to 200% without loss of content or functionality.

Known Limitations

We are committed to transparency about areas where we are still improving:

  • Complex Data Visualizations: Some charts and data visualizations in our scan reports may not be fully accessible to screen reader users. We provide equivalent data tables alongside all visualizations, but we are actively working to improve the interactive chart experience with better ARIA labels and keyboard controls. Target resolution: Q3 2026.
  • PDF Reports: While our PDF reports include tagged structure and alternative text, the accessibility of PDF output is being improved to fully conform with PDF/UA standards. HTML versions of all reports are available as a fully accessible alternative. Target resolution: Q2 2026.

Testing Methods

Our accessibility testing process includes:

  • Automated scanning with axe-core on every code change
  • Manual keyboard navigation testing of all interactive workflows
  • Screen reader testing with NVDA and VoiceOver
  • Color contrast verification using our own contrast calculator tool
  • Periodic third-party accessibility audits
  • User testing with people who use assistive technologies

Feedback

We welcome your feedback on the accessibility of AuditAble. If you encounter any accessibility barriers or have suggestions for improvement, please contact us:

We take accessibility feedback seriously and aim to respond within 2 business days. For critical accessibility issues that prevent you from using our platform, we will prioritize a fix and provide a workaround within 24 hours when possible.

Third-Party Content

Our platform may display content from third-party services (such as embedded payment forms from Stripe). While we select third-party providers that prioritize accessibility, we cannot certify that all third-party content meets WCAG 2.1 AA standards. If you encounter an accessibility issue with third-party content on our platform, please let us know and we will work with the provider to address it.

Legal References

AuditAble's accessibility efforts are guided by the following standards and regulations:

  • Section 508 of the Rehabilitation Act: Federal accessibility requirements for information and communication technology
  • ADA Title II: Requires state and local governments to make their services, programs, and activities accessible to people with disabilities
  • DOJ Final Rule (28 CFR Part 35): Establishes WCAG 2.1 Level AA as the technical standard for state and local government web content, with compliance deadlines of April 26, 2027 (entities serving 50,000+ population) and April 26, 2028 (all others)