Copilotly

Legal

Accessibility

The standard we build to, what is in place, and where we currently fall short. The last part is the one worth reading.

Effective · Last updated

The standard we build to

We aim for WCAG 2.2 Level AA across this site and the product. That is the level most legislation references, including the ADA in US practice, the Equality Act in the UK, and the European Accessibility Act.

Aiming is not the same as achieving, and this page says where we fall short rather than only where we succeed.

What is in place

  • Keyboard navigation throughout, with a visible focus indicator and a skip-to-content link on every page.
  • Semantic structure - real headings in order, landmarks, and lists that are lists. Screen readers depend on this more than on any ARIA attribute.
  • Colour contrast meeting AA for body text and interface components. The palette was checked at design time rather than retrofitted.
  • Text alternatives on every non-decorative image, with decorative images explicitly marked as such so they are skipped rather than announced.
  • Reduced motion - all animation respects the prefers-reduced-motion setting.
  • Resizable text - the layout holds at 200% zoom without horizontal scrolling.
  • No colour-only meaning - anything indicated by colour is also indicated by text or shape.

Where we know we fall short

Being specific is more useful than a general commitment, so:

  • Some migrated long-form content contains tables that are harder to navigate with a screen reader than they should be. We are working through them.
  • The third-party chat widget is not under our control and does not fully meet AA. We are evaluating alternatives.
  • Complex charts embedded in some guides have text alternatives that summarise rather than fully describe the data.

None of these is acceptable as a permanent state. They are listed because a page claiming full conformance while these exist would be false.

If something does not work

Tell us. Email [email protected] with what you were trying to do, what happened, and what you were using - browser, screen reader, or assistive technology.

We treat accessibility reports as bugs rather than as feature requests, and we will tell you what we are doing about it rather than closing the thread.

If you need information from this site in a different format, ask and we will provide it.