This site is our first piece of evidence.
We sell accessible delivery to public-sector buyers. It would be difficult to argue for that credibly on a site that did not meet the standard itself, so this one does — and where it does not yet, this page says so.
Conformance
Target: WCAG 2.2, Level AA.
We design and build to the Web Content Accessibility Guidelines 2.2 at Level AA, which is the level referenced by Section 508 in the United States, EN 301 549 in Europe, and the accessibility requirements applying to federally regulated organisations in Canada.
This is a self-assessment. No independent auditor has reviewed this site. We will name the assessor and the date here when one has.
- Standard
- WCAG 2.2 Level AA
- Also designed to
- Section 508 · EN 301 549
- Assessment
- Self-assessed
- Last reviewed
- August 2026
What we did
Specific measures, not a policy statement.
| Area | What was done |
|---|---|
| Colour and contrast | Every foreground/background pair in the design system was measured before it was written into the stylesheet. Body and heading text meets or exceeds 4.5:1; interface borders and focus indicators meet 3:1. Both light and dark themes were measured independently rather than one being derived from the other. |
| Keyboard operation | All interactive controls are reachable and operable by keyboard. Navigation menus use a disclosure pattern with real buttons, aria-expanded and Escape-to-close, rather than hover-only reveals. Scrollable data tables carry a focusable region so they can be scrolled without a pointer. |
| Focus visibility | A 2px focus outline with offset is applied to every focusable element and is never removed. Focus is moved deliberately after form submission so keyboard users are taken to the outcome. |
| Semantics and structure | One main landmark per page, a skip link to it, a single h1, and headings in order. Data tables use th with scope. Breadcrumbs use an ordered list with aria-current. |
| Forms | Every control has a persistent visible label. Errors are announced through a role=alert summary, associated to their field with aria-describedby, marked with aria-invalid, and carry a text glyph so the state is never signalled by colour alone. |
| Motion | Motion is restrained by design — no parallax, no autoplaying carousels, no scroll-jacking. prefers-reduced-motion removes animation and transition duration site-wide. |
| Content | Sentence-case headings rather than uppercase, which screen readers can misread as initialisms. Link text is meaningful out of context. Decorative images carry empty alt text. |
| Zoom and reflow | Layouts use relative units and reflow to 320px without horizontal scrolling. Wide tables scroll within their own region rather than forcing the page to scroll. |
Known gaps
Where we are not there yet.
An accessibility statement that lists only successes is a marketing document. These are the gaps we know about, which is also the list we are working through.
Third-party assessment
Not startedNo independent accessibility audit has been carried out. Until one has, everything on this page is a self-assessment and is described as such.
Assistive technology testing
In progressAutomated checks and keyboard testing are run against every page. Structured screen-reader testing across NVDA, JAWS and VoiceOver is being formalised rather than done ad hoc.
Legacy content pages
In progressA small number of older article and listing pages predate this design system. They are being migrated; until then they may not meet the standard described above.
Report a barrier
Tell us and we will fix it.
If any part of this site prevented you from doing something, we want to know — including if you are not sure whether it is a bug or a barrier.
Email accessibility@round.digital with the page address and what happened. We aim to acknowledge within two business days and to tell you what we are going to do about it and when.
If you need information from this site in another format, ask and we will provide it. That includes the capability statement in an alternative format for procurement purposes.
Buying accessible digital services?
Accessibility is a scored evaluation factor on most public-sector digital work. We deliver to WCAG 2.2 AA and can evidence how — starting with this site.