Last updated: June 2, 2026
ComplianceOps is committed to making www.complianceops.ai usable for as many people as possible, including people who use assistive technologies. We design and build to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.
Conformance status
This statement reflects our self-assessment against WCAG 2.1 AA. We are partially conformant — meaning the site largely meets the standard, with the known limitations listed below. The site has not yet been independently audited by a third-party accessibility specialist; we plan to commission one before any major redesign.
What is implemented today
- Semantic HTML landmarks (
<header>,<main>,<footer>,<nav>,<section>,<article>,<aside>). - A “Skip to main content” link as the first interactive element on every page.
- Visible focus indicators (2 px brand-blue outline) on every interactive element.
- Brand colour contrast meeting WCAG AA on body text and primary actions.
- Reduced-motion support — animations are suppressed for visitors with the
prefers-reduced-motionsystem preference enabled. - Keyboard-operable navigation. Mobile menu opens via a native
<details>element — usable without JavaScript. - FAQ accordions also use
<details>, so they expand without JS and are exposed to assistive technologies. - Image alt text on the brand logo and other meaningful imagery. Decorative SVG banners are marked
aria-hidden="true"so screen readers skip them. - Page titles and meta descriptions distinct on every route.
- Responsive layout. Text remains readable when zoomed to 200%. No horizontal scroll at supported breakpoints.
- HTML lang attribute set on the document.
Known limitations
Specific areas we know need ongoing attention:
- Some decorative banners include text (for example, framework names). The same content is also present in the surrounding HTML so screen readers will encounter it; the banners themselves are marked as decorative.
- Forms are intentionally not used on the site at this stage. When introduced, they will be tested against the same standard, including label association, error handling, and focus management.
- No formal third-party audit has been completed. Visitors who encounter a barrier we have missed are invited to report it (below).
Report a barrier
If something on this site is hard to use with your assistive technology, or you would like content in an alternative format, email [email protected] with the page URL and a brief description of the barrier. We aim to acknowledge reports within five working days and to address the issue or provide an accessible alternative within thirty days, depending on complexity.
Compatibility
The site is tested with current versions of major browsers (Chrome, Edge, Safari, Firefox) and supports the latest two versions of macOS VoiceOver, JAWS, and NVDA on supported platforms.
Enforcement
If you have not received a satisfactory response, you may pursue applicable remedies in your jurisdiction — for example, under the Americans with Disabilities Act (ADA) in the United States, the European Accessibility Act in the EU, the Equality Act in the UK, or analogous legislation elsewhere.
This statement is drafted in good faith. Have your accessibility, UX, and legal teams review and update it after the first formal third-party audit and at any redesign milestone.