Accessibility statement

Accessible.org, LLC wants StrongPrivacy to be usable by everyone, including people who rely on a keyboard, a screen reader, magnification, voice control or reduced motion. A consent tool has a particular duty here: if a visitor cannot operate the consent choice, they cannot make it.

This statement covers the StrongPrivacy website, dashboard and documentation at strongprivacy.com, and the consent banner and preference center that StrongPrivacy renders on customer sites.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. StrongPrivacy is currently partially conformant. We have not completed a full representative audit, so we do not claim a percentage of pages or that unlisted components conform. The known limitations and current test scope are described below.

• The shared page layouts use a primary heading, landmarks, labelled navigation and a skip link.
• Reviewed form components use visible labels and text errors; complete coverage still needs page-by-page verification.
• Shared interactive components define visible focus styles; keyboard order and visibility still need verification in every complete flow.
• Reviewed status components pair colour with text or an icon, and reviewed data tables use table markup with headers.
• Shared decorative icons are intended to be hidden from assistive technology; bespoke pages remain in the audit scope.
• Reviewed dashboard charts provide a text summary or underlying values; chart-by-chart parity remains to be audited.
• Light and dark themes, layouts that reflow on small screens, and reduced motion honoured where the interface animates.

• A complete manual screen-reader matrix has not yet been performed across the public site, dashboard, consent banner and preference centre.
• Long code samples in the documentation scroll sideways inside their blocks rather than wrapping.
• Wide comparison tables scroll sideways on small screens, which is harder to follow with magnification.
• How the consent banner looks on a customer site depends partly on that site's own styles. Customers should check it with their theme, their language and a keyboard before publishing.

Accessibility is checked as part of building the product, not afterwards:

• Automated source and component checks for selected headings, labels, roles, accessible names and common structural defects. The current review date is 19 September 2026.
• Keyboard spot checks of shared navigation, forms and dialogs; this is not yet a complete end-to-end keyboard audit.
• Visual spot checks in both themes and at narrow widths.
• Code review of markup and ARIA use.
• No external conformance audit has yet been completed. We will name the auditor, scope, date and method here if one is completed.

StrongPrivacy is designed for current versions of Chrome, Edge, Firefox and Safari using standard HTML and ARIA. A formal browser and assistive- technology compatibility matrix has not yet been completed, so this statement does not promise support for every browser/screen-reader pair. Internet Explorer is not supported.

If something in StrongPrivacy is hard or impossible for you to use, email info@accessible.org with the page address, what you were trying to do, and the browser and assistive technology you use. We aim to respond within two business days.

If the barrier is in a consent banner on another company's website, that company is responsible for its site; you can still tell us, and we will pass it on to them if it comes from StrongPrivacy.

Implementation documentation explains how customers can test their own banner.