Accessibility
This page tracks the current accessibility posture of the A11Y Cheat Sheet. Here you’ll find our active conformance statement, live testing data from our automated and manual audits, and our formal VPAT® 2.5 Conformance Report detailing known exceptions and workarounds.
Our commitment
We want the A11Y Cheat Sheet to work for everyone, including people who use screen readers, keyboard-only navigation or screen magnification. Rather than make a claim and leave it, we check it automatically, test it by hand, and list below what we know doesn't work yet.
Verification and current status
- Target standard
- WCAG 2.1 & 2.2 Level A / AA
- Current status
- Partially conforming, with the known exceptions listed below
- Last automated scan
- 5 November 2026
- Last manual audit
- 16 November 2026
- Testing environment
- Automated: Google Lighthouse 13.6.0 with axe-core 4.14.0, on desktop
- Keyboard only, with DOM and CSS inspection
- Phone, tablet and desktop widths, in an emulated browser
- Screen readers: VoiceOver on macOS started; NVDA, VoiceOver on iPhone and TalkBack not yet
Known limitations and roadmap
We'd rather you knew before you start. These are the barriers we know about, and what you can do instead.
| Area or feature | |||
|---|---|---|---|
Screen readers
| We haven't yet tested the cheat sheet from start to finish with a screen reader, so there may be barriers we don't know about. | Use Report issue next to any check, or Feedback at the bottom of the page, and tell us what you were using. We'll help. | Not yet scheduled |
The label card's video
| Its captions are YouTube's automatic ones and haven't been checked, so some words are wrong ("four" for the for attribute). It has no audio description. | Read the corrected transcript under the video. | Not yet scheduled |
Subscribe and Feedback forms
| The name and email fields don't tell your browser what they're for, so autofill may not offer your details. | Type them in. Nothing else on the forms depends on autofill. | Not yet scheduled |
Score gauges on this report
| The rings around the scores keep turning, with no button to stop them. | Turn on Reduce motion in your device settings and they stay still. | Not yet scheduled |
PDF exports
| PDFs come from your browser's Print window. Chrome's are tagged for screen readers; other browsers' haven't been checked. | Print from Chrome, or export the report as JSON or plain text instead. | Not yet scheduled |
Colour contrast
| Contrast has only been measured automatically, in one theme, so some text may be hard to read in others. | Tell us where text is hard to read and we'll look at it first. | Not yet scheduled |
Need help or have feedback?
If something on the cheat sheet gets in your way, or you need it in another format, tell us. Use Report issue next to any check in this report, or Feedback at the bottom of every page.
Accessibility
Automated Checks
28/28 Checks passed • Last tested 5 Nov 2026
28 checks
Filter by category
Filter by user impact
| Check | Coverage | Category | User impact | Status |
|---|---|---|---|---|
An ARIA attribute is used where it isn't allowed Each role allows only certain ARIA attributes, and screen readers ignore any other — so people miss what it was meant to say. ARIA · Critical | Rule ID: Ruleset: | ARIA | Critical | Pass |
A role is missing an ARIA attribute it needs Some roles need a state, like checked or expanded. Without it, screen reader users can't tell whether a control is on, off, open or closed. ARIA · Critical | Rule ID: Ruleset: | ARIA | Critical | Pass |
A role attribute uses a value that doesn't exist When ARIA · Critical | Rule ID: Ruleset: | ARIA | Critical | Pass |
An ARIA attribute has a value that isn't allowed When an ARIA attribute holds a wrong or misspelled value, screen readers ignore it or guess — so people miss whether something is open, checked or current. ARIA · Critical | Rule ID: Ruleset: | ARIA | Critical | Pass |
An ARIA attribute name is misspelled or made up Screen readers ignore any ARIA attribute with a wrong name, so a label, hint or hidden setting silently never reaches the person. ARIA · Critical | Rule ID: Ruleset: | ARIA | Critical | Pass |
A button has no name a screen reader can say A screen reader announces just "button", so people can't tell what it does — close, search, delete or buy. Names · Critical | Rule ID: Ruleset: | Names | Critical | Pass |
An image has no text alternative Screen readers can't describe an image with no text alternative, so people miss what it shows, or hear a meaningless file name instead. Names · Critical | Rule ID: Ruleset: | Names | Critical | Pass |
A form field has no label Screen readers can't say what a field is for, so people don't know what to type or choose. Names · Critical | Rule ID: Ruleset: | Names | Critical | Pass |
The page stops people from zooming in The page's settings block pinch-zoom on phones, so people who need bigger text can't make it bigger and may not be able to read it. Best practices · Critical | Rule ID: Ruleset: | Best practices | Critical | Pass |
An ARIA attribute breaks the rules for this element Some ARIA attributes only work in certain situations, and when misused, screen readers announce the wrong state or nothing at all. ARIA · Serious | Rule ID: Ruleset: | ARIA | Serious | Pass |
An ARIA label is on an element that can't have one Some elements aren't allowed a hidden label, so screen readers may skip it — and people miss the words you meant them to hear. ARIA · Serious | Rule ID: Ruleset: | ARIA | Serious | Pass |
Text colour is too close to its background colour When text and background are too similar, many people can't read the words — especially in sunlight, on cheap screens, or with ageing or low vision. Contrast · Serious | Rule ID: Ruleset: | Contrast | Serious | Pass |
A definition list contains the wrong elements When a Tables · Serious | Rule ID: Ruleset: | Tables | Serious | Pass |
Term and description items sit outside a description list When Tables · Serious | Rule ID: Ruleset: | Tables | Serious | Pass |
The page has no title Without a page title, people can't tell which page or tab they're on, and screen readers announce only the web address or nothing useful. Names · Serious | Rule ID: Ruleset: | Names | Serious | Pass |
The page doesn't say what language it's in Without a language set on the page, screen readers may read the words with the wrong accent and rules, making them hard or impossible to understand. Language · Serious | Rule ID: Ruleset: | Language | Serious | Pass |
The page's language code is not a real language The page says it's written in a language that doesn't exist, so screen readers guess the voice and accent — and often read the words wrongly. Language · Serious | Rule ID: Ruleset: | Language | Serious | Pass |
A link has no text a screen reader can read When a link has no readable name, screen reader users hear only "link" or a messy web address, and can't tell where it goes. Names · Serious | Rule ID: Ruleset: | Names | Serious | Pass |
A list contains something other than list items When a list holds items that aren't marked as list items, screen readers may miscount it or skip things — so people lose track of what's in it. Tables · Serious | Rule ID: Ruleset: | Tables | Serious | Pass |
A list item sits outside a list When an Tables · Serious | Rule ID: Ruleset: | Tables | Serious | Pass |
An element has a tabindex greater than zero A positive Navigation · Serious | Rule ID: Ruleset: | Navigation | Serious | Pass |
A button or link is too small to tap easily Tiny or tightly packed buttons and links are hard to hit, so people tap the wrong thing or give up. Best practices · Serious | Rule ID: Ruleset: | Best practices | Serious | Pass |
A lang attribute on part of the page has an invalid value When a passage is marked with a language code that doesn't exist, screen readers can't switch voice, so foreign words come out garbled or mispronounced. Language · Serious | Rule ID: Ruleset: | Language | Serious | Pass |
Heading levels skip a step, like jumping from h2 to h4 When heading levels skip, screen reader users may think they missed a section, and the page outline stops making sense. Navigation · Moderate | Rule ID: Ruleset: | Navigation | Moderate | Pass |
The page has no main content area marked up Screen reader users can't jump straight to the page's main content, so they must wade through the header and menus on every page. Best practices · Moderate | Rule ID: Ruleset: | Best practices | Moderate | Pass |
An outdated ARIA role is used The page uses a role that has been retired from ARIA, so screen readers may ignore it or handle it differently, and people can't tell what the content is. ARIA · Moderate | Rule ID: Ruleset: | ARIA | Moderate | Pass |
Accessibility
Manual Checks
33/47 Checks completed • Last tested 9 Nov 2026
58 checks
| Check / Coverage / Evaluator Notes | Coverage | Evaluator Notes | |||
|---|---|---|---|---|---|
Online forms: labels, instructions, errors, and recovery Critical · Medium effort WCAG 1.3.1 (opens in a new tab), WCAG 3.3.1 (opens in a new tab), WCAG 3.3.2 (opens in a new tab), WCAG 3.3.3 (opens in a new tab), WCAG 3.3.4 (opens in a new tab) Subscribe and Feedback have a label on every field. Each error says what to do, sits under its field and takes focus there, and what you typed stays. A failed send is announced. WCAG 3.3.4 doesn't apply: neither form is legal or financial. | WCAG 1.3.1 (opens in a new tab), WCAG 3.3.1 (opens in a new tab), WCAG 3.3.2 (opens in a new tab), WCAG 3.3.3 (opens in a new tab), WCAG 3.3.4 (opens in a new tab) | Critical | Medium | Subscribe and Feedback have a label on every field. Each error says what to do, sits under its field and takes focus there, and what you typed stays. A failed send is announced. WCAG 3.3.4 doesn't apply: neither form is legal or financial. | Pass |
Online forms: labels, instructions, errors, and recovery Critical · Medium effort WCAG 1.3.1 (opens in a new tab), WCAG 3.3.1 (opens in a new tab), WCAG 3.3.2 (opens in a new tab), WCAG 3.3.3 (opens in a new tab), WCAG 3.3.4 (opens in a new tab) The contact form's fields each have a label, and required ones are marked. Sent empty, it moves focus to the first field missing, marks each one invalid, and says what's needed under it, tied to the field. The hidden spam-trap field is out of the Tab order and hidden from screen readers. The newsletter form's field is labelled too. | WCAG 1.3.1 (opens in a new tab), WCAG 3.3.1 (opens in a new tab), WCAG 3.3.2 (opens in a new tab), WCAG 3.3.3 (opens in a new tab), WCAG 3.3.4 (opens in a new tab) | Critical | Medium | The contact form's fields each have a label, and required ones are marked. Sent empty, it moves focus to the first field missing, marks each one invalid, and says what's needed under it, tied to the field. The hidden spam-trap field is out of the Tab order and hidden from screen readers. The newsletter form's field is labelled too. | Pass |
Screen reader flow is logical (headings, links, forms, states) Critical · High effort | WCAG 1.3.2 (opens in a new tab), WCAG 2.4.4 (opens in a new tab), WCAG 4.1.2 (opens in a new tab) | Critical | High | Not started | |
Screen reader flow is logical (headings, links, forms, states) Critical · High effort | WCAG 1.3.2 (opens in a new tab), WCAG 2.4.4 (opens in a new tab), WCAG 4.1.2 (opens in a new tab) | Critical | High | Not started | |
Real-device checks in mobile Safari with VoiceOver Critical · High effort Manual iOS and VoiceOver verification | Manual iOS and VoiceOver verification | Critical | High | Not started | |
Real-device checks in mobile Safari with VoiceOver Critical · High effort Manual iOS and VoiceOver verification | Manual iOS and VoiceOver verification | Critical | High | Not started | |
Real-device checks on Android with TalkBack Critical · High effort Manual Android and TalkBack verification | Manual Android and TalkBack verification | Critical | High | Not started | |
Real-device checks on Android with TalkBack Critical · High effort Manual Android and TalkBack verification | Manual Android and TalkBack verification | Critical | High | Not started | |
Desktop screen reader checks: NVDA with Chrome and Firefox, VoiceOver with Safari Critical · High effort Manual assistive tech verification across browsers | Manual assistive tech verification across browsers | Critical | High | Not started | |
Desktop screen reader checks: NVDA with Chrome and Firefox, VoiceOver with Safari Critical · High effort Manual assistive tech verification across browsers | Manual assistive tech verification across browsers | Critical | High | Not started | |
Keyboard tabbing reaches all controls with no keyboard traps Critical · High effort WCAG 2.1.1 (opens in a new tab), WCAG 2.1.2 (opens in a new tab), WCAG 2.4.3 (opens in a new tab), WCAG 2.4.7 (opens in a new tab) Tab reaches every control, in order, and nothing traps you. A filter panel and a folded card are one stop each: Enter goes in, and Escape or tabbing past the end comes back out. Filters take Enter or Space, and Skip to cards jumps past them. | WCAG 2.1.1 (opens in a new tab), WCAG 2.1.2 (opens in a new tab), WCAG 2.4.3 (opens in a new tab), WCAG 2.4.7 (opens in a new tab) | Critical | High | Tab reaches every control, in order, and nothing traps you. A filter panel and a folded card are one stop each: Enter goes in, and Escape or tabbing past the end comes back out. Filters take Enter or Space, and Skip to cards jumps past them. | Pass |
Keyboard tabbing reaches all controls with no keyboard traps Critical · High effort WCAG 2.1.1 (opens in a new tab), WCAG 2.1.2 (opens in a new tab), WCAG 2.4.3 (opens in a new tab), WCAG 2.4.7 (opens in a new tab) Tab reaches every link and button in the header, the page and the footer, with no traps. The FDRS video player's controls take focus in turn and let it go. The Today strip under the header is a stop too: Tab opens it, then moves through Keep Today open, the soundtrack player, full screen and the weather toggle, and on to the page. In full screen, Tab goes round its links and buttons. (Fixed 16 Nov 2026: Tab used to pass over Today.) | WCAG 2.1.1 (opens in a new tab), WCAG 2.1.2 (opens in a new tab), WCAG 2.4.3 (opens in a new tab), WCAG 2.4.7 (opens in a new tab) | Critical | High | Tab reaches every link and button in the header, the page and the footer, with no traps. The FDRS video player's controls take focus in turn and let it go. The Today strip under the header is a stop too: Tab opens it, then moves through Keep Today open, the soundtrack player, full screen and the weather toggle, and on to the page. In full screen, Tab goes round its links and buttons. (Fixed 16 Nov 2026: Tab used to pass over Today.) | Pass |
Non-HTML links include file type, size, and open behaviour Serious · Low effort No page tested links to a file. But many links open a new tab without saying so: the footer's social links and office addresses, "View live" on a work entry, and links in articles. Only some say "(opens in a new tab)". | WCAG 2.4.4 (opens in a new tab), WCAG 3.2.5 (opens in a new tab) | Serious | Low | No page tested links to a file. But many links open a new tab without saying so: the footer's social links and office addresses, "View live" on a work entry, and links in articles. Only some say "(opens in a new tab)". | Fail |
Videos include captions, and audio/video has a transcript or alternative Serious · Low effort | WCAG 1.2.1 (opens in a new tab), WCAG 1.2.2 (opens in a new tab), WCAG 1.2.3 (opens in a new tab) | Serious | Low | Not started | |
Non-HTML links include file type, size, and open behaviour Serious · Low effort No link here goes straight to a file. The only format is PDF, and those links say so, with its size: about 500 KB a card, from a saved sample. Each one says it opens the print dialogue in a new tab. | WCAG 2.4.4 (opens in a new tab), WCAG 3.2.5 (opens in a new tab) | Serious | Low | No link here goes straight to a file. The only format is PDF, and those links say so, with its size: about 500 KB a card, from a saved sample. Each one says it opens the print dialogue in a new tab. | Pass |
Videos include captions, and audio/video has a transcript or alternative Serious · Low effort One card has a video: label. It has a corrected transcript under it. Its captions are YouTube's automatic ones and haven't been reviewed line by line, and they spell the for attribute as "four". | WCAG 1.2.1 (opens in a new tab), WCAG 1.2.2 (opens in a new tab), WCAG 1.2.3 (opens in a new tab) | Serious | Low | One card has a video: label. It has a corrected transcript under it. Its captions are YouTube's automatic ones and haven't been reviewed line by line, and they spell the for attribute as "four". | Pass |
Focus indicators are visible and not obscured Serious · Medium effort Every control shows a focus indicator. Until the cookie banner is answered, though, it covers links near the bottom of the screen as Tab reaches them — footer links, "Learn more", the scorecards — so the focused link can be fully hidden. With the banner closed, nothing focused was covered. | WCAG 2.4.7 (opens in a new tab), WCAG 2.4.11 (opens in a new tab) | Serious | Medium | Every control shows a focus indicator. Until the cookie banner is answered, though, it covers links near the bottom of the screen as Tab reaches them — footer links, "Learn more", the scorecards — so the focused link can be fully hidden. With the banner closed, nothing focused was covered. | Fail |
Focus outlines, borders and icons reach 3:1 against what's next to them Serious · Medium effort WCAG 1.4.11 The usual focus ring — on the header's menus, its buttons and most links — is a dashed grey line at half strength, about 1.6:1 against the cream page. It needs 3:1. The blue dashed ring on cards and the report's buttons is about 3:1 or better. | WCAG 1.4.11 | Serious | Medium | The usual focus ring — on the header's menus, its buttons and most links — is a dashed grey line at half strength, about 1.6:1 against the cream page. It needs 3:1. The blue dashed ring on cards and the report's buttons is about 3:1 or better. | Fail |
Gestures have a single-pointer alternative, and a press can be cancelled Serious · Medium effort WCAG 2.5.1, WCAG 2.5.2 The testimonials and work galleries have Previous and Next buttons. On a phone, the key highlights carousel can only be moved by swiping, with no buttons. Presses act on release, so they can be cancelled. | WCAG 2.5.1, WCAG 2.5.2 | Serious | Medium | The testimonials and work galleries have Previous and Next buttons. On a phone, the key highlights carousel can only be moved by swiping, with no buttons. Presses act on release, so they can be cancelled. | Fail |
Focus outlines, borders and icons reach 3:1 against what's next to them Serious · Medium effort WCAG 1.4.11 | WCAG 1.4.11 | Serious | Medium | Not started | |
Focus indicators are visible and not obscured Serious · Medium effort Every control shows a dashed blue outline on keyboard focus. A folded card and a filter panel show it around the whole thing, so it's clear what you're on, and the sticky footer doesn't hide it. | WCAG 2.4.7 (opens in a new tab), WCAG 2.4.11 (opens in a new tab) | Serious | Medium | Every control shows a dashed blue outline on keyboard focus. A folded card and a filter panel show it around the whole thing, so it's clear what you're on, and the sticky footer doesn't hide it. | Pass |
Zoom and reflow at 200% without content loss Serious · Medium effort At 200% (640px wide) every page reflows into one column with nothing lost and no sideways scrolling. The header's text size control also takes text to 125% and beyond. | WCAG 1.4.4 (opens in a new tab), WCAG 1.4.10 (opens in a new tab) | Serious | Medium | At 200% (640px wide) every page reflows into one column with nothing lost and no sideways scrolling. The header's text size control also takes text to 125% and beyond. | Pass |
Zoom and reflow at 200% without content loss Serious · Medium effort At 200%, by hand and measured at 640px wide, and measured at 320px, on the cheat sheet, the report and a rule page, with a card and the filters open. Nothing is lost and the page doesn't scroll sideways. An open card is taller than the window at 200%, so you scroll down it. Two tables on a rule page scroll sideways inside themselves at 320px, and keys can scroll them. The report's View Card modal wasn't tested. | WCAG 1.4.4 (opens in a new tab), WCAG 1.4.10 (opens in a new tab) | Serious | Medium | At 200%, by hand and measured at 640px wide, and measured at 320px, on the cheat sheet, the report and a rule page, with a card and the filters open. Nothing is lost and the page doesn't scroll sideways. An open card is taller than the window at 200%, so you scroll down it. Two tables on a rule page scroll sideways inside themselves at 320px, and keys can scroll them. The report's View Card modal wasn't tested. | Pass |
Responsive layouts and touch targets across breakpoints Serious · Medium effort On the cheat sheet, the report and a rule page, as a phone (390px, both ways round), a tablet (768px) and a desktop (1280px), with touch on for all but the desktop. Every control is at least 24 by 24px or spaced so a 24px circle round it touches no other, and nothing scrolls sideways. A list row's copy link is left off below 1024px, where the open card has its own. Checked in an emulated browser, not on a real device. | WCAG 1.3.4 (opens in a new tab), WCAG 1.4.10 (opens in a new tab) | Serious | Medium | On the cheat sheet, the report and a rule page, as a phone (390px, both ways round), a tablet (768px) and a desktop (1280px), with touch on for all but the desktop. Every control is at least 24 by 24px or spaced so a 24px circle round it touches no other, and nothing scrolls sideways. A list row's copy link is left off below 1024px, where the open card has its own. Checked in an emulated browser, not on a real device. | Pass |
Responsive layouts and touch targets across breakpoints Serious · Medium effort At 320, 640, 768 and 1024px wide, and in landscape at 640 by 360, no page scrolls sideways, and nothing is cut off. Carousels scroll within themselves, as they should. | WCAG 1.3.4 (opens in a new tab), WCAG 1.4.10 (opens in a new tab) | Serious | Medium | At 320, 640, 768 and 1024px wide, and in landscape at 640 by 360, no page scrolls sideways, and nothing is cut off. Carousels scroll within themselves, as they should. | Pass |
Text stays readable with spacing overridden: line, paragraph, letter and word Serious · Medium effort WCAG 1.4.12 WCAG's spacing (line 1.5, paragraphs 2, letters 0.12, words 0.16) on every kind of page at 390px and 1280px: nothing is lost. The report's tables outgrew their panels on a phone and cut off Status, fixed on 9 Nov. Rule IDs on cards are cut short sooner, as they are anyway, and show whole on hover or focus. | WCAG 1.4.12 | Serious | Medium | WCAG's spacing (line 1.5, paragraphs 2, letters 0.12, words 0.16) on every kind of page at 390px and 1280px: nothing is lost. The report's tables outgrew their panels on a phone and cut off Status, fixed on 9 Nov. Rule IDs on cards are cut short sooner, as they are anyway, and show whole on hover or focus. | Pass |
Text stays readable with spacing overridden: line, paragraph, letter and word Serious · Medium effort WCAG 1.4.12 With line height 1.5, paragraph spacing 2em, letter spacing 0.12em and word spacing 0.16em applied to everything, no text is cut off or overlaps. The Today strip grows to fit. | WCAG 1.4.12 | Serious | Medium | With line height 1.5, paragraph spacing 2em, letter spacing 0.12em and word spacing 0.16em applied to everything, no text is cut off or overlaps. The Today strip grows to fit. | Pass |
Active filters, errors and tags don't rely on colour alone Serious · Medium effort WCAG 1.4.1 Checked on the cheat sheet, the report and the Feedback form. Tags pair colour with an icon and words: severity a dot and its name, themes and features an icon and a name, statuses an icon and a word. Errors are written under each field ("Enter your name."), not only a red border. Filters ticked in both states, grey or blue, so only colour told them apart: fixed on 9 Nov, an empty ring until chosen, then a tick. | WCAG 1.4.1 | Serious | Medium | Checked on the cheat sheet, the report and the Feedback form. Tags pair colour with an icon and words: severity a dot and its name, themes and features an icon and a name, statuses an icon and a word. Errors are written under each field ("Enter your name."), not only a red border. Filters ticked in both states, grey or blue, so only colour told them apart: fixed on 9 Nov, an empty ring until chosen, then a tick. | Pass |
Active filters, errors and tags don't rely on colour alone Serious · Medium effort WCAG 1.4.1 Links in text are underlined. The contact form's errors are written out ("Enter your name.") as well as shown in red, and tags carry their words. | WCAG 1.4.1 | Serious | Medium | Links in text are underlined. The contact form's errors are written out ("Enter your name.") as well as shown in red, and tags carry their words. | Pass |
Visible labels are part of each control's accessible name Serious · Medium effort WCAG 2.5.3 axe-core's label-content-name-mismatch rule on every kind of page, at desktop and phone widths: no failures. A card's button said its rule ID in the reader's spelling ("colour-contrast" for "color-contrast"), fixed on 9 Nov. Built with Sanity's diagram buttons are flagged because the diagram's words sit inside them, but those words aren't the button's label, so they're not a failure. | WCAG 2.5.3 | Serious | Medium | axe-core's label-content-name-mismatch rule on every kind of page, at desktop and phone widths: no failures. A card's button said its rule ID in the reader's spelling ("colour-contrast" for "color-contrast"), fixed on 9 Nov. Built with Sanity's diagram buttons are flagged because the diagram's words sit inside them, but those words aren't the button's label, so they're not a failure. | Pass |
Visible labels are part of each control's accessible name Serious · Medium effort WCAG 2.5.3 Where a control has a name of its own, it includes the words shown: "100%" is in "Text size 100% — press for 125%", and each hour in the forecast reads as shown ("Now: overcast, 12°C"). | WCAG 2.5.3 | Serious | Medium | Where a control has a name of its own, it includes the words shown: "100%" is in "Text size 100% — press for 125%", and each hour in the forecast reads as shown ("Now: overcast, 12°C"). | Pass |
Images, including older content, have meaningful text alternatives Serious · High effort Most images have good alt text: client logos say the client, badges say what they mean. Some don't: insight images say "Test", "Important for SEO and accessibility.", "Humans" or "Bricks"; work images say "stream", "Food" or "Crowds"; a service image says "dev"; /sanity's background says "Sanity bg". These need real descriptions, or empty alt where they're decoration. | WCAG 1.1.1 (opens in a new tab) | Serious | High | Most images have good alt text: client logos say the client, badges say what they mean. Some don't: insight images say "Test", "Important for SEO and accessibility.", "Humans" or "Bricks"; work images say "stream", "Food" or "Crowds"; a service image says "dev"; /sanity's background says "Sanity bg". These need real descriptions, or empty alt where they're decoration. | Fail |
Every interactive element meets the 24 by 24 pixel target size or its spacing exception Serious · High effort WCAG 2.5.8 Almost every target is 24px or more, or spaced well apart. The footer scorecard's "0/29 passed, full report" link is 16px tall and sits 10px from the "Conformance report" link under it, closer than the spacing allows. | WCAG 2.5.8 | Serious | High | Almost every target is 24px or more, or spaced well apart. The footer scorecard's "0/29 passed, full report" link is 16px tall and sits 10px from the "Conformance report" link under it, closer than the spacing allows. | Fail |
Real-device checks in mobile Chrome Serious · High effort Manual interaction and assistive tech verification | Manual interaction and assistive tech verification | Serious | High | Not started | |
Real-device checks in mobile Chrome Serious · High effort Manual interaction and assistive tech verification | Manual interaction and assistive tech verification | Serious | High | Not started | |
PDFs and other documents are tagged, navigable, and screen-reader compatible Serious · High effort | WCAG 1.3.1 (opens in a new tab), WCAG 1.3.2 (opens in a new tab), WCAG 2.4.1 (opens in a new tab), WCAG 4.1.2 (opens in a new tab) | Serious | High | Not started | |
Images, including older content, have meaningful text alternatives Serious · High effort Every image on the cheat sheet, its report, Built with Sanity and the release notes says what it shows, back to v1.0.0's screenshots. Cards hold no images. The video thumbnail's alt is empty because its play button names it, and each diagram has a transcript. A11y University's other pages weren't part of this. | WCAG 1.1.1 (opens in a new tab) | Serious | High | Every image on the cheat sheet, its report, Built with Sanity and the release notes says what it shows, back to v1.0.0's screenshots. Cards hold no images. The video thumbnail's alt is empty because its play button names it, and each diagram has a transcript. A11y University's other pages weren't part of this. | Pass |
Every interactive element meets the 24 by 24 pixel target size or its spacing exception Serious · High effort WCAG 2.5.8 axe-core's target-size rule on every kind of page at desktop and phone widths, and with Feedback, Subscribe, Sort and Export open: nothing under 24 by 24px without enough space round it. | WCAG 2.5.8 | Serious | High | axe-core's target-size rule on every kind of page at desktop and phone widths, and with Feedback, Subscribe, Sort and Export open: nothing under 24 by 24px without enough space round it. | Pass |
Print stylesheet preserves core content readability Moderate · Low effort Print accessibility checks Printed (About, A4), the words come through, but the page title "About" disappears with its banner, and the header prints at the top of every page over the first lines of text. The Today strip and the assistant button print too. | Print accessibility checks | Moderate | Low | Printed (About, A4), the words come through, but the page title "About" disappears with its banner, and the header prints at the top of every page over the first lines of text. The Today strip and the assistant button print too. | Fail |
Skip links appear early and move focus to main content Moderate · Low effort Skip to cards comes straight after the search box. It's unseen until you tab to it, sits inside the search box, and moves focus to the first card, past every filter. | WCAG 2.4.1 (opens in a new tab) | Moderate | Low | Skip to cards comes straight after the search box. It's unseen until you tab to it, sits inside the search box, and moves focus to the first card, past every filter. | Pass |
Skip links appear early and move focus to main content Moderate · Low effort Pressing "Skip to content" opens the page's contents and moves focus to its first section, one Tab from the main content. Checked on all 13 pages tested. | WCAG 2.4.1 (opens in a new tab) | Moderate | Low | Pressing "Skip to content" opens the page's contents and moves focus to its first section, one Tab from the main content. Checked on all 13 pages tested. | Pass |
Print stylesheet preserves core content readability Moderate · Low effort Print accessibility checks A card prints on A4 with its headings and words intact, nothing cut off at the sides. A video prints as its link, written out, and the footer stops following the page. | Print accessibility checks | Moderate | Low | A card prints on A4 with its headings and words intact, nothing cut off at the sides. A video prints as its link, written out, and the footer stops following the page. | Pass |
A skip link is one of the first things Tab reaches on every page Moderate · Low effort Checked on every kind of page: the cheat sheet, the report, a rule page, Built with Sanity, Updates, Changes, a change and a newsletter. Skip to content (or Skip to cards on the cheat sheet, after the logo and search) is in the first three Tab stops, shows when reached, and Enter moves focus to the content, so the next Tab carries on from there. Five pages had none and were given one on 9 Nov. | WCAG 2.4.1 (opens in a new tab) | Moderate | Low | Checked on every kind of page: the cheat sheet, the report, a rule page, Built with Sanity, Updates, Changes, a change and a newsletter. Skip to content (or Skip to cards on the cheat sheet, after the logo and search) is in the first three Tab stops, shows when reached, and Enter moves focus to the content, so the next Tab carries on from there. Five pages had none and were given one on 9 Nov. | Pass |
A skip link is one of the first things Tab reaches on every page Moderate · Low effort The first Tab on every page reaches "Skip to content", and it shows when focused. Tested on the home page, About, Services, a service (Product Design), Products, Work, a work entry (FDRS), Insights, an article, Contact, Accessibility, the privacy policy and /sanity, in Chrome at 1280px wide. | WCAG 2.4.1 (opens in a new tab) | Moderate | Low | The first Tab on every page reaches "Skip to content", and it shows when focused. Tested on the home page, About, Services, a service (Product Design), Products, Work, a work entry (FDRS), Insights, an article, Contact, Accessibility, the privacy policy and /sanity, in Chrome at 1280px wide. | Pass |
Technical content is written in plain language or offers a simpler summary Moderate · Medium effort | WCAG 3.1.5 (opens in a new tab) | Moderate | Medium | Not started | |
Technical content is written in plain language or offers a simpler summary Moderate · Medium effort All 99 cards open with a plain headline and a one-sentence summary, before any code. Those summaries read at about Year 9 or 10 on a rough Flesch-Kincaid count, a little above WCAG 3.1.5's lower-secondary bar. Words like ARIA and tabindex push that up, and they stay because they're what the reader has to learn. | WCAG 3.1.5 (opens in a new tab) | Moderate | Medium | All 99 cards open with a plain headline and a one-sentence summary, before any code. Those summaries read at about Year 9 or 10 on a rough Flesch-Kincaid count, a little above WCAG 3.1.5's lower-secondary bar. Words like ARIA and tabindex push that up, and they stay because they're what the reader has to learn. | Pass |
Sign-in, if there is any, needs no memory test or puzzle without an alternative Serious · Low effort WCAG 3.3.8 Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | WCAG 3.3.8 | Serious | Low | Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | Not applicable |
Sign-in, if there is any, needs no memory test or puzzle without an alternative Serious · Low effort WCAG 3.3.8 | WCAG 3.3.8 | Serious | Low | The public website has no sign-in. | Not applicable |
Gestures have a single-pointer alternative, and a press can be cancelled Serious · Medium effort WCAG 2.5.1, WCAG 2.5.2 Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | WCAG 2.5.1, WCAG 2.5.2 | Serious | Medium | Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | Not applicable |
PDFs and other documents are tagged, navigable, and screen-reader compatible Serious · High effort | WCAG 1.3.1 (opens in a new tab), WCAG 1.3.2 (opens in a new tab), WCAG 2.4.1 (opens in a new tab), WCAG 4.1.2 (opens in a new tab) | Serious | High | The pages tested link to no PDFs or other documents. | Not applicable |
Maps and interactive embeds provide an accessible text alternative Moderate · Low effort The cheat sheet has no maps or interactive embeds. Its one video is covered by the video check. | WCAG 1.1.1 (opens in a new tab), WCAG 1.3.1 (opens in a new tab) | Moderate | Low | The cheat sheet has no maps or interactive embeds. Its one video is covered by the video check. | Not applicable |
Maps and interactive embeds provide an accessible text alternative Moderate · Low effort No page embeds a map or an interactive widget. Office addresses are text, linking to Google Maps. | WCAG 1.1.1 (opens in a new tab), WCAG 1.3.1 (opens in a new tab) | Moderate | Low | No page embeds a map or an interactive widget. Office addresses are text, linking to Google Maps. | Not applicable |
Forms don't ask again for what a person has already entered Moderate · Low effort WCAG 3.3.7 Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | WCAG 3.3.7 | Moderate | Low | Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | Not applicable |
Forms don't ask again for what a person has already entered Moderate · Low effort WCAG 3.3.7 The site's forms — contact and newsletter — are one step each, so nothing is asked twice. | WCAG 3.3.7 | Moderate | Low | The site's forms — contact and newsletter — are one step each, so nothing is asked twice. | Not applicable |
Single-key shortcuts can be turned off, remapped or work only on focus Moderate · Low effort WCAG 2.1.4 Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | WCAG 2.1.4 | Moderate | Low | Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | Not applicable |
Single-key shortcuts can be turned off, remapped or work only on focus Moderate · Low effort WCAG 2.1.4 | WCAG 2.1.4 | Moderate | Low | The website has no single-key shortcuts. | Not applicable |
This report is pending a review. It's from 10 November 2026, and the test results it's based on changed on 16 Nov.
About this Report
Status: Draft Accessibility Conformance Report (Work in Progress)
This draft report utilizes the VPAT® 2.5 framework to assess the A11Y Cheat Sheet against WCAG 2.2 Levels A and AA, as well as two selected Level AAA criteria.
Please note:
- This document is an unfinalised Working Draft and does not constitute a formal claim of conformance.
- While official VPAT® guidelines restrict the term “Not Evaluated” exclusively to Level AAA criteria, it is used provisionally throughout this draft across Levels A and AA to indicate items where testing is currently underway. A status of “Not Evaluated” does not indicate failure or non-conformance.
Report Summary
- Product
- A11Y Cheat Sheet (v1.0+)
- Evaluation Date
- 10 November 2026
- Evaluator(s)
- Automated testing
- Google Lighthouse 13.6.0 (axe-core 4.14.0)
- Manual inspection
- Keyboard-only traversal, DOM & CSS inspection
- Assistive Technology (AT) testing
- VoiceOver (macOS) started; VoiceOver (iOS) and NVDA (Windows) planned
- Status
- Interim Assessment (In Progress)
Evaluation Scope & Coverage
- Target Standard
- WCAG 2.1 & 2.2 Level A / AA
- Audit Progress
- 46% Complete (27 of 58 criteria evaluated; 31 pending manual/assistive tech review)
Known gaps
- This is an interim report, not a claim of WCAG conformance. Most Level A and AA criteria are still Not Evaluated.
- The automated score covers one page: a saved Lighthouse run of the main page, on desktop, on 5 Nov 2026. It isn't a daily or CI run, and 100 means the 28 rules that applied passed, not that the page is accessible.
- Screen reader flow isn't tested from start to finish. That check and the mobile Safari VoiceOver check haven't been started, and the NVDA and Android TalkBack checks are required but not started. That leaves 1.3.2, 2.4.4 and 4.1.2 Not Evaluated.
- Zoom and reflow passed on the cheat sheet, the report and a rule page on 7 Nov 2026, and responsive layouts and touch targets on 9 Nov 2026. The report's View Card modal wasn't tested.
- Responsive layouts and touch targets were checked in an emulated browser, not on a real device: no mobile Chrome, and no mobile Safari with VoiceOver. 2.5.8's own check, which looks at every control, passed on 9 Nov 2026.
- PDF tagging isn't verified. The report's export relies on the browser's Print window. Chromium's output is tagged, other browsers are unchecked, and a card PDF scored 84/100 on a PDF/UA-2 checker on 15 Oct 2026.
- Captions on the label card's video are YouTube's automatic ones and unreviewed (1.2.2), and nobody has checked that its transcript covers what's shown (1.2.3).
- The report's score gauges keep turning with no pause control (2.2.2).
- The form component behind Subscribe and Feedback sets no autocomplete values on personal fields (1.3.5).
- The manual keyboard and focus checks are dated 5 Nov 2026 and predate the report's pins, heading sort and Export menus. Those new controls have story tests but no manual retest.
- Contrast is measured automatically in one theme only (1.4.3).
- A11y University's pages outside the cheat sheet, and the dashboard, aren't in scope.
- 13 manual checks were added on 6 Nov 2026 to close gaps. On 9 Nov 2026, 8 of them were made required and count in the manual score of 70: 5 have passed, and the NVDA, TalkBack and non-text contrast checks haven't been started. The other 5 are set aside as Not applicable for now. That label means not yet tested here, not that they don't apply, so they're left out of the score.
Criteria Conformance Summary
58 criteria
| Evaluator Notes | |||
|---|---|---|---|
1.1.1 Non-text ContentALighthouse's image-alt rule passed. A person went through every image on the cheat sheet, its report, Built with Sanity and the release notes, back to v1.0.0's screenshots, and each says what it shows. Cards hold no images. The video thumbnail's alt is empty because its play button names it, and each diagram has a transcript. A11y University's other pages weren't part of this. Supports Under review: Images, including older content, have meaningful text alternatives failed | A | Lighthouse's image-alt rule passed. A person went through every image on the cheat sheet, its report, Built with Sanity and the release notes, back to v1.0.0's screenshots, and each says what it shows. Cards hold no images. The video thumbnail's alt is empty because its play button names it, and each diagram has a transcript. A11y University's other pages weren't part of this. | SupportsUnder review: Images, including older content, have meaningful text alternatives failed |
1.2.1 Audio-only and Video-only (Prerecorded)AThe one card video, on the label card, has sound and a corrected transcript. The A11y University promo's background video wasn't assessed as video-only content. Partially Supports | A | The one card video, on the label card, has sound and a corrected transcript. The A11y University promo's background video wasn't assessed as video-only content. | Partially Supports |
1.2.2 Captions (Prerecorded)AThe label card's video has captions, but they're YouTube's automatic ones and haven't been reviewed line by line. They spell the for attribute as "four". The transcript under the video is the corrected text. Partially Supports | A | The label card's video has captions, but they're YouTube's automatic ones and haven't been reviewed line by line. They spell the for attribute as "four". The transcript under the video is the corrected text. | Partially Supports |
1.2.3 Audio Description or Media Alternative (Prerecorded)AThe video has a corrected transcript, but nobody has checked that it covers what's shown on screen as well as what's said. Partially Supports | A | The video has a corrected transcript, but nobody has checked that it covers what's shown on screen as well as what's said. | Partially Supports |
1.2.5 Audio Description (Prerecorded)AAThe video has no audio description track, and nobody has checked whether its soundtrack already says everything shown. Not Evaluated | AA | The video has no audio description track, and nobody has checked whether its soundtrack already says everything shown. | Not Evaluated |
1.3.1 Info and RelationshipsAPassed so far: form labels and errors in the forms check, and Lighthouse's list, definition list, heading order and label rules. The PDF check hasn't been started. Not Evaluated | A | Passed so far: form labels and errors in the forms check, and Lighthouse's list, definition list, heading order and label rules. The PDF check hasn't been started. | Not Evaluated |
1.3.2 Meaningful SequenceAThe screen reader flow check hasn't been started, so this can't be claimed yet. The PDF check hasn't been started. Not Evaluated | A | The screen reader flow check hasn't been started, so this can't be claimed yet. The PDF check hasn't been started. | Not Evaluated |
1.3.3 Sensory CharacteristicsANo manual check covers this yet, and no automated rule settles it. Not Evaluated | A | No manual check covers this yet, and no automated rule settles it. | Not Evaluated |
1.3.4 OrientationAAThe responsive layouts check passed on 9 Nov 2026: the cheat sheet, the report and a rule page work as a phone both ways round, a tablet and a desktop, in an emulated browser. Nothing is locked to one orientation. Supports | AA | The responsive layouts check passed on 9 Nov 2026: the cheat sheet, the report and a rule page work as a phone both ways round, a tablet and a desktop, in an emulated browser. Nothing is locked to one orientation. | Supports |
1.3.5 Identify Input PurposeAAFrom a code review: the form component behind Subscribe and Feedback sets no autocomplete values on the fields that ask for a person's own details. The only autocomplete in it is on a hidden anti-spam field. Does Not Support | AA | From a code review: the form component behind Subscribe and Feedback sets no autocomplete values on the fields that ask for a person's own details. The only autocomplete in it is on a hidden anti-spam field. | Does Not Support |
1.4.1 Use of ColorAThe colour check passed on 9 Nov 2026: tags pair colour with an icon and words, errors are written under their fields, and filters show a tick once chosen, an empty ring before, fixed that day. Supports | A | The colour check passed on 9 Nov 2026: tags pair colour with an icon and words, errors are written under their fields, and filters show a tick once chosen, an empty ring before, fixed that day. | Supports |
1.4.2 Audio ControlAThe video plays only when pressed. Read aloud and the promo's background video haven't been assessed. Not Evaluated | A | The video plays only when pressed. Read aloud and the promo's background video haven't been assessed. | Not Evaluated |
1.4.3 Contrast (Minimum)AALighthouse's colour-contrast rule passed on the main page, in one theme, on desktop. Contrast hasn't been measured across themes or on the other pages. Not Evaluated | AA | Lighthouse's colour-contrast rule passed on the main page, in one theme, on desktop. Contrast hasn't been measured across themes or on the other pages. | Not Evaluated |
1.4.4 Resize TextAAThe zoom and reflow check passed at 200% on 7 Nov 2026 on the cheat sheet, the report and a rule page, with a card and the filters open. The report's View Card modal wasn't tested. Supports | AA | The zoom and reflow check passed at 200% on 7 Nov 2026 on the cheat sheet, the report and a rule page, with a card and the filters open. The report's View Card modal wasn't tested. | Supports |
1.4.5 Images of TextAANo manual check covers this yet, and no automated rule settles it. Release note screenshots contain text. Not Evaluated | AA | No manual check covers this yet, and no automated rule settles it. Release note screenshots contain text. | Not Evaluated |
1.4.10 ReflowAAThe zoom and reflow check passed on 7 Nov 2026 at 320px on the cheat sheet, the report and a rule page, after two overflows were fixed, and the responsive layouts check on 9 Nov 2026. On 9 Nov 2026 the report's Automated and Manual Checks tables were found 40px and 3px wider than their panels at 320px, cutting off Status, which the earlier check missed; they were fixed that day. The report's View Card modal wasn't tested. Supports | AA | The zoom and reflow check passed on 7 Nov 2026 at 320px on the cheat sheet, the report and a rule page, after two overflows were fixed, and the responsive layouts check on 9 Nov 2026. On 9 Nov 2026 the report's Automated and Manual Checks tables were found 40px and 3px wider than their panels at 320px, cutting off Status, which the earlier check missed; they were fixed that day. The report's View Card modal wasn't tested. | Supports |
1.4.11 Non-text ContrastAAA manual check for this is required and hasn't been started. Not Evaluated | AA | A manual check for this is required and hasn't been started. | Not Evaluated |
1.4.12 Text SpacingAAThe text spacing check passed on 9 Nov 2026 on every kind of page at 390px and 1280px, after the report's tables were made to fit their panels. Rule IDs on cards are cut short and show whole on hover or focus. Supports | AA | The text spacing check passed on 9 Nov 2026 on every kind of page at 390px and 1280px, after the report's tables were made to fit their panels. Rule IDs on cards are cut short and show whole on hover or focus. | Supports |
1.4.13 Content on Hover or FocusAANo manual check covers this yet, and no automated rule settles it. The product has hover labels and hints. Not Evaluated | AA | No manual check covers this yet, and no automated rule settles it. The product has hover labels and hints. | Not Evaluated |
2.1.1 KeyboardAA person tabbed through the cheat sheet: every control can be reached and used, and filters take Enter or Space. Tested 5 Nov 2026, before the report's pins, heading sort and Export menus were added. Those haven't had a manual keyboard pass. Supports | A | A person tabbed through the cheat sheet: every control can be reached and used, and filters take Enter or Space. Tested 5 Nov 2026, before the report's pins, heading sort and Export menus were added. Those haven't had a manual keyboard pass. | Supports |
2.1.2 No Keyboard TrapANothing traps focus. A filter panel and a folded card are one stop each: Enter goes in, and Escape or tabbing past the end comes out. Supports | A | Nothing traps focus. A filter panel and a folded card are one stop each: Enter goes in, and Escape or tabbing past the end comes out. | Supports |
2.1.4 Character Key ShortcutsAA manual check for this has been added, but it's set aside for now and hasn't been done. The one global shortcut found, Command or Control K for search, uses a modifier key, but a full review hasn't been done. Not Evaluated | A | A manual check for this has been added, but it's set aside for now and hasn't been done. The one global shortcut found, Command or Control K for search, uses a modifier key, but a full review hasn't been done. | Not Evaluated |
2.2.1 Timing AdjustableANo manual check covers this yet, and no automated rule settles it. Not Evaluated | A | No manual check covers this yet, and no automated rule settles it. | Not Evaluated |
2.2.2 Pause, Stop, HideAThe report's score gauges turn for as long as the page is open, with no way to pause them. They stay still with reduced motion on, but that's not a control on the page. Other moving content hasn't been reviewed. A manual check for this has been added, but it's set aside for now. Partially Supports | A | The report's score gauges turn for as long as the page is open, with no way to pause them. They stay still with reduced motion on, but that's not a control on the page. Other moving content hasn't been reviewed. A manual check for this has been added, but it's set aside for now. | Partially Supports |
2.3.1 Three Flashes or Below ThresholdANo manual check covers this yet, and no automated rule settles it. The gauges fire confetti, which hasn't been assessed. Not Evaluated | A | No manual check covers this yet, and no automated rule settles it. The gauges fire confetti, which hasn't been assessed. | Not Evaluated |
2.4.1 Bypass BlocksAPassed so far: Skip to cards comes right after the search box and moves focus to the first card, and the report has Skip to content. The PDF check, which also covers this, hasn't been started. The check that a skip link comes first on every page passed on 9 Nov 2026, after five pages were given one. Not Evaluated | A | Passed so far: Skip to cards comes right after the search box and moves focus to the first card, and the report has Skip to content. The PDF check, which also covers this, hasn't been started. The check that a skip link comes first on every page passed on 9 Nov 2026, after five pages were given one. | Not Evaluated |
2.4.2 Page TitledALighthouse's document-title rule passed, and the main and report pages have titles that say what they are. Other pages weren't individually reviewed. Supports | A | Lighthouse's document-title rule passed, and the main and report pages have titles that say what they are. Other pages weren't individually reviewed. | Supports |
2.4.3 Focus OrderAFocus moves in a logical order in the keyboard check. One known mismatch on the report: a panel's Export Report comes after the panel's fold button in the Tab order, though it's drawn before the chevron. Supports | A | Focus moves in a logical order in the keyboard check. One known mismatch on the report: a panel's Export Report comes after the panel's fold button in the Tab order, though it's drawn before the chevron. | Supports |
2.4.4 Link Purpose (In Context)APassed so far: Lighthouse's link-name rule, and PDF links give their format, size and that they open in a new tab. The screen reader flow check hasn't been started, so this can't be claimed yet. Not Evaluated | A | Passed so far: Lighthouse's link-name rule, and PDF links give their format, size and that they open in a new tab. The screen reader flow check hasn't been started, so this can't be claimed yet. | Not Evaluated |
2.4.5 Multiple WaysAANo manual check covers this yet, and no automated rule settles it. The deck has search and filters. Not Evaluated | AA | No manual check covers this yet, and no automated rule settles it. The deck has search and filters. | Not Evaluated |
2.4.6 Headings and LabelsAALighthouse's heading-order rule passed, and forms have labels, but nobody has judged whether headings and labels describe their content. Not Evaluated | AA | Lighthouse's heading-order rule passed, and forms have labels, but nobody has judged whether headings and labels describe their content. | Not Evaluated |
2.4.7 Focus VisibleAAEvery control shows a dashed blue outline on keyboard focus. A folded card and a filter panel show it around the whole thing. Supports Under review: Focus indicators are visible and not obscured failed | AA | Every control shows a dashed blue outline on keyboard focus. A folded card and a filter panel show it around the whole thing. | SupportsUnder review: Focus indicators are visible and not obscured failed |
2.4.11 Focus Not Obscured (Minimum)AAThe sticky footer doesn't hide what has focus. This is Level AA in WCAG 2.2. Supports Under review: Focus indicators are visible and not obscured failed | AA | The sticky footer doesn't hide what has focus. This is Level AA in WCAG 2.2. | SupportsUnder review: Focus indicators are visible and not obscured failed |
2.5.1 Pointer GesturesAA manual check for this has been added, but it's set aside for now and hasn't been done. Not Evaluated | A | A manual check for this has been added, but it's set aside for now and hasn't been done. | Not Evaluated |
2.5.2 Pointer CancellationAA manual check for this has been added, but it's set aside for now and hasn't been done. Not Evaluated | A | A manual check for this has been added, but it's set aside for now and hasn't been done. | Not Evaluated |
2.5.3 Label in NameAThe visible labels check passed on 9 Nov 2026: no control on any kind of page has a name that leaves out its visible words, at desktop and phone widths. A card's name used to respell its rule ID, fixed that day. Supports | A | The visible labels check passed on 9 Nov 2026: no control on any kind of page has a name that leaves out its visible words, at desktop and phone widths. A card's name used to respell its rule ID, fixed that day. | Supports |
2.5.4 Motion ActuationANo manual check covers this yet, and no automated rule settles it. Not Evaluated | A | No manual check covers this yet, and no automated rule settles it. | Not Evaluated |
2.5.7 Dragging MovementsAANo manual check covers this yet, and no automated rule settles it. Filter panels have drag handles, and a single-pointer alternative hasn't been confirmed. Not Evaluated | AA | No manual check covers this yet, and no automated rule settles it. Filter panels have drag handles, and a single-pointer alternative hasn't been confirmed. | Not Evaluated |
2.5.8 Target Size (Minimum)AAThe target size check passed on 9 Nov 2026: no control on any kind of page, or in the Feedback, Subscribe, Sort or Export menus and dialogs, is under 24 by 24px without enough space round it, at desktop and phone widths. Supports Under review: Every interactive element meets the 24 by 24 pixel target size or its spacing exception failed | AA | The target size check passed on 9 Nov 2026: no control on any kind of page, or in the Feedback, Subscribe, Sort or Export menus and dialogs, is under 24 by 24px without enough space round it, at desktop and phone widths. | SupportsUnder review: Every interactive element meets the 24 by 24 pixel target size or its spacing exception failed |
3.1.1 Language of PageALighthouse's html-has-lang and html-lang-valid rules passed. Supports | A | Lighthouse's html-has-lang and html-lang-valid rules passed. | Supports |
3.1.2 Language of PartsAALighthouse's valid-lang rule passed, but that only checks language tags that exist, not passages that need one. Not Evaluated | AA | Lighthouse's valid-lang rule passed, but that only checks language tags that exist, not passages that need one. | Not Evaluated |
3.1.5 Reading LevelAAAMarked Pass in the manual check, but its own note falls short of the bar. All 99 cards open with a plain headline and a one-sentence summary before any code, and those read at about Year 9 or 10 on a rough Flesch-Kincaid count, a little above lower-secondary. Words like ARIA and tabindex push that up, and they stay because they're what the reader has to learn. Partially Supports | AAA | Marked Pass in the manual check, but its own note falls short of the bar. All 99 cards open with a plain headline and a one-sentence summary before any code, and those read at about Year 9 or 10 on a rough Flesch-Kincaid count, a little above lower-secondary. Words like ARIA and tabindex push that up, and they stay because they're what the reader has to learn. | Partially Supports |
3.2.1 On FocusANo manual check covers this yet, and no automated rule settles it. Not Evaluated | A | No manual check covers this yet, and no automated rule settles it. | Not Evaluated |
3.2.2 On InputANo manual check covers this yet, and no automated rule settles it. Not Evaluated | A | No manual check covers this yet, and no automated rule settles it. | Not Evaluated |
3.2.3 Consistent NavigationAANo manual check covers this yet, and no automated rule settles it. Not Evaluated | AA | No manual check covers this yet, and no automated rule settles it. | Not Evaluated |
3.2.4 Consistent IdentificationAANo manual check covers this yet, and no automated rule settles it. Not Evaluated | AA | No manual check covers this yet, and no automated rule settles it. | Not Evaluated |
3.2.5 Change on RequestAAAPassed so far: PDF links say they open a new tab and the print dialog. That covers links to files only, not every change of context. Not Evaluated | AAA | Passed so far: PDF links say they open a new tab and the print dialog. That covers links to files only, not every change of context. | Not Evaluated |
3.2.6 Consistent HelpANo manual check covers this yet, and no automated rule settles it. Not Evaluated | A | No manual check covers this yet, and no automated rule settles it. | Not Evaluated |
3.3.1 Error IdentificationASubscribe and Feedback: each error says what's wrong, sits under its field and takes focus there. Supports | A | Subscribe and Feedback: each error says what's wrong, sits under its field and takes focus there. | Supports |
3.3.2 Labels or InstructionsASupports | A | Subscribe and Feedback have a label on every field. | Supports |
3.3.3 Error SuggestionAAEach error says what to do, and what was typed stays. A failed send is announced. Supports | AA | Each error says what to do, and what was typed stays. A failed send is announced. | Supports |
3.3.4 Error Prevention (Legal, Financial, Data)AANeither form is legal or financial. Whether the Subscribe form's stored email counts as user data under this criterion hasn't been reviewed. Not Evaluated | AA | Neither form is legal or financial. Whether the Subscribe form's stored email counts as user data under this criterion hasn't been reviewed. | Not Evaluated |
3.3.7 Redundant EntryAA manual check for this has been added, but it's set aside for now and hasn't been done. Not Evaluated | A | A manual check for this has been added, but it's set aside for now and hasn't been done. | Not Evaluated |
4.1.2 Name, Role, ValueALighthouse's ARIA, button-name and link-name rules passed. The screen reader flow check hasn't been started, so this can't be claimed yet. Early VoiceOver testing found an open question: moving between a card's panels with the arrow keys gives no announcement. Not Evaluated | A | Lighthouse's ARIA, button-name and link-name rules passed. The screen reader flow check hasn't been started, so this can't be claimed yet. Early VoiceOver testing found an open question: moving between a card's panels with the arrow keys gives no announcement. | Not Evaluated |
4.1.3 Status MessagesAAPassed so far: a failed form send is announced, and Copy to Clipboard says so. Not reviewed across the product. Sorting the report says nothing as it happens, and a download isn't announced.. Not Evaluated | AA | Passed so far: a failed form send is announced, and Copy to Clipboard says so. Not reviewed across the product. Sorting the report says nothing as it happens, and a download isn't announced.. | Not Evaluated |
1.2.4 Captions (Live)AANot Applicable | AA | The cheat sheet has no live audio or video. | Not Applicable |
3.3.8 Accessible Authentication (Minimum)AANot Applicable | AA | The cheat sheet has no sign-in. | Not Applicable |
4.1.1 ParsingARemoved from WCAG 2.2 as obsolete. Kept here for WCAG 2.1 readers. Not Applicable | A | Removed from WCAG 2.2 as obsolete. Kept here for WCAG 2.1 readers. | Not Applicable |
https://a11yuniversity.org/a11y-cheat-sheet/accessibility
Accessibility Statement
Our commitment
We want the A11Y Cheat Sheet to work for everyone, including people who use screen readers, keyboard-only navigation or screen magnification. Rather than make a claim and leave it, we check it automatically, test it by hand, and list below what we know doesn't work yet.
Verification and current status
- Target standard
- WCAG 2.1 & 2.2 Level A / AA
- Current status
- Partially conforming, with the known exceptions listed below
- Last automated scan
- 5 November 2026
- Last manual audit
- 16 November 2026
- Testing environment
- Automated: Google Lighthouse 13.6.0 with axe-core 4.14.0, on desktop
- Keyboard only, with DOM and CSS inspection
- Phone, tablet and desktop widths, in an emulated browser
- Screen readers: VoiceOver on macOS started; NVDA, VoiceOver on iPhone and TalkBack not yet
Known limitations and roadmap
We'd rather you knew before you start. These are the barriers we know about, and what you can do instead.
| Area or feature | The problem | What you can do instead | When we expect to fix it |
|---|---|---|---|
| Screen readers | We haven't yet tested the cheat sheet from start to finish with a screen reader, so there may be barriers we don't know about. | Use Report issue next to any check, or Feedback at the bottom of the page, and tell us what you were using. We'll help. | Not yet scheduled |
| The label card's video | Its captions are YouTube's automatic ones and haven't been checked, so some words are wrong ("four" for the for attribute). It has no audio description. | Read the corrected transcript under the video. | Not yet scheduled |
| Subscribe and Feedback forms | The name and email fields don't tell your browser what they're for, so autofill may not offer your details. | Type them in. Nothing else on the forms depends on autofill. | Not yet scheduled |
| Score gauges on this report | The rings around the scores keep turning, with no button to stop them. | Turn on Reduce motion in your device settings and they stay still. | Not yet scheduled |
| PDF exports | PDFs come from your browser's Print window. Chrome's are tagged for screen readers; other browsers' haven't been checked. | Print from Chrome, or export the report as JSON or plain text instead. | Not yet scheduled |
| Colour contrast | Contrast has only been measured automatically, in one theme, so some text may be hard to read in others. | Tell us where text is hard to read and we'll look at it first. | Not yet scheduled |
Need help or have feedback?
If something on the cheat sheet gets in your way, or you need it in another format, tell us. Use Report issue next to any check in this report, or Feedback at the bottom of every page.
Automated Checks
100 out of 100. 28/28 checks passed. Last tested 5 Nov 2026. Lighthouse 13.6.0, axe-core 4.14.0, on https://a11yuniversity.org/a11y-cheat-sheet. 38 more didn’t apply.
| Check | Category | User impact | Status |
|---|---|---|---|
| An ARIA attribute is used where it isn't allowed Rule ID: aria-allowed-attr | ARIA | Critical | Pass |
| The whole page is hidden from screen readers Rule ID: aria-hidden-body | ARIA | Critical | Pass |
| A role is missing an ARIA attribute it needs Rule ID: aria-required-attr | ARIA | Critical | Pass |
| A role attribute uses a value that doesn't exist Rule ID: aria-roles | ARIA | Critical | Pass |
| An ARIA attribute has a value that isn't allowed Rule ID: aria-valid-attr-value | ARIA | Critical | Pass |
| An ARIA attribute name is misspelled or made up Rule ID: aria-valid-attr | ARIA | Critical | Pass |
| A button has no name a screen reader can say Rule ID: button-name | Names | Critical | Pass |
| An image has no text alternative Rule ID: image-alt | Names | Critical | Pass |
| A form field has no label Rule ID: label | Names | Critical | Pass |
| The page stops people from zooming in Rule ID: meta-viewport | Best practices | Critical | Pass |
| An ARIA attribute breaks the rules for this element Rule ID: aria-conditional-attr | ARIA | Serious | Pass |
| Hidden content can still receive keyboard focus Rule ID: aria-hidden-focus | ARIA | Serious | Pass |
| An ARIA label is on an element that can't have one Rule ID: aria-prohibited-attr | ARIA | Serious | Pass |
| Text colour is too close to its background colour Rule ID: color-contrast | Contrast | Serious | Pass |
| A definition list contains the wrong elements Rule ID: definition-list | Tables | Serious | Pass |
| Term and description items sit outside a description list Rule ID: dlitem | Tables | Serious | Pass |
| The page has no title Rule ID: document-title | Names | Serious | Pass |
| The page doesn't say what language it's in Rule ID: html-has-lang | Language | Serious | Pass |
| The page's language code is not a real language Rule ID: html-lang-valid | Language | Serious | Pass |
| A link has no text a screen reader can read Rule ID: link-name | Names | Serious | Pass |
| A list contains something other than list items Rule ID: list | Tables | Serious | Pass |
| A list item sits outside a list Rule ID: listitem | Tables | Serious | Pass |
| An element has a tabindex greater than zero Rule ID: tabindex | Navigation | Serious | Pass |
| A button or link is too small to tap easily Rule ID: target-size | Best practices | Serious | Pass |
| A lang attribute on part of the page has an invalid value Rule ID: valid-lang | Language | Serious | Pass |
| Heading levels skip a step, like jumping from h2 to h4 Rule ID: heading-order | Navigation | Moderate | Pass |
| The page has no main content area marked up Rule ID: landmark-one-main | Best practices | Moderate | Pass |
| An outdated ARIA role is used Rule ID: aria-deprecated-role | ARIA | Moderate | Pass |
Manual Checks
53 out of 100. 25/47 checks passed. Last tested 9 Nov 2026.
| Check | Coverage | User impact | Effort | Status |
|---|---|---|---|---|
| Online forms: labels, instructions, errors, and recovery Zaid Al-Dabbagh, 5 Nov Subscribe and Feedback have a label on every field. Each error says what to do, sits under its field and takes focus there, and what you typed stays. A failed send is announced. WCAG 3.3.4 doesn't apply: neither form is legal or financial. | WCAG 1.3.1, 3.3.1, 3.3.2, 3.3.3, 3.3.4 | Critical | Medium | Pass |
| Online forms: labels, instructions, errors, and recovery Zaid Al-Dabbagh, 16 Nov The contact form's fields each have a label, and required ones are marked. Sent empty, it moves focus to the first field missing, marks each one invalid, and says what's needed under it, tied to the field. The hidden spam-trap field is out of the Tab order and hidden from screen readers. The newsletter form's field is labelled too. | WCAG 1.3.1, 3.3.1, 3.3.2, 3.3.3, 3.3.4 | Critical | Medium | Pass |
| Screen reader flow is logical (headings, links, forms, states) | WCAG 1.3.2, 2.4.4, 4.1.2 | Critical | High | Not started |
| Screen reader flow is logical (headings, links, forms, states) | WCAG 1.3.2, 2.4.4, 4.1.2 | Critical | High | Not started |
| Real-device checks in mobile Safari with VoiceOver | Manual iOS and VoiceOver verification | Critical | High | Not started |
| Real-device checks in mobile Safari with VoiceOver | Manual iOS and VoiceOver verification | Critical | High | Not started |
| Real-device checks on Android with TalkBack | Manual Android and TalkBack verification | Critical | High | Not started |
| Real-device checks on Android with TalkBack | Manual Android and TalkBack verification | Critical | High | Not started |
| Desktop screen reader checks: NVDA with Chrome and Firefox, VoiceOver with Safari | Manual assistive tech verification across browsers | Critical | High | Not started |
| Desktop screen reader checks: NVDA with Chrome and Firefox, VoiceOver with Safari | Manual assistive tech verification across browsers | Critical | High | Not started |
| Keyboard tabbing reaches all controls with no keyboard traps Zaid Al-Dabbagh, 5 Nov Tab reaches every control, in order, and nothing traps you. A filter panel and a folded card are one stop each: Enter goes in, and Escape or tabbing past the end comes back out. Filters take Enter or Space, and Skip to cards jumps past them. | WCAG 2.1.1, 2.1.2, 2.4.3, 2.4.7 | Critical | High | Pass |
| Keyboard tabbing reaches all controls with no keyboard traps Zaid Al-Dabbagh, 16 Nov Tab reaches every link and button in the header, the page and the footer, with no traps. The FDRS video player's controls take focus in turn and let it go. The Today strip under the header is a stop too: Tab opens it, then moves through Keep Today open, the soundtrack player, full screen and the weather toggle, and on to the page. In full screen, Tab goes round its links and buttons. (Fixed 16 Nov 2026: Tab used to pass over Today.) | WCAG 2.1.1, 2.1.2, 2.4.3, 2.4.7 | Critical | High | Pass |
| Non-HTML links include file type, size, and open behaviour Zaid Al-Dabbagh, 16 Nov No page tested links to a file. But many links open a new tab without saying so: the footer's social links and office addresses, "View live" on a work entry, and links in articles. Only some say "(opens in a new tab)". | WCAG 2.4.4, 3.2.5 | Serious | Low | Fail |
| Videos include captions, and audio/video has a transcript or alternative | WCAG 1.2.1, 1.2.2, 1.2.3 | Serious | Low | Not started |
| Non-HTML links include file type, size, and open behaviour Zaid Al-Dabbagh, 5 Nov No link here goes straight to a file. The only format is PDF, and those links say so, with its size: about 500 KB a card, from a saved sample. Each one says it opens the print dialogue in a new tab. | WCAG 2.4.4, 3.2.5 | Serious | Low | Pass |
| Videos include captions, and audio/video has a transcript or alternative Zaid Al-Dabbagh, 6 Nov One card has a video: label. It has a corrected transcript under it. Its captions are YouTube's automatic ones and haven't been reviewed line by line, and they spell the for attribute as "four". | WCAG 1.2.1, 1.2.2, 1.2.3 | Serious | Low | Pass |
| Focus indicators are visible and not obscured Zaid Al-Dabbagh, 16 Nov Every control shows a focus indicator. Until the cookie banner is answered, though, it covers links near the bottom of the screen as Tab reaches them — footer links, "Learn more", the scorecards — so the focused link can be fully hidden. With the banner closed, nothing focused was covered. | WCAG 2.4.7, 2.4.11 | Serious | Medium | Fail |
| Focus outlines, borders and icons reach 3:1 against what's next to them Zaid Al-Dabbagh, 16 Nov The usual focus ring — on the header's menus, its buttons and most links — is a dashed grey line at half strength, about 1.6:1 against the cream page. It needs 3:1. The blue dashed ring on cards and the report's buttons is about 3:1 or better. | WCAG 1.4.11 | Serious | Medium | Fail |
| Gestures have a single-pointer alternative, and a press can be cancelled Zaid Al-Dabbagh, 16 Nov The testimonials and work galleries have Previous and Next buttons. On a phone, the key highlights carousel can only be moved by swiping, with no buttons. Presses act on release, so they can be cancelled. | WCAG 2.5.1, 2.5.2 | Serious | Medium | Fail |
| Moving or updating content can be paused, stopped or hidden Zaid Al-Dabbagh, 16 Nov The About page's video plays by itself, loops (46 seconds) and has no pause control, and keeps playing when reduced motion is asked for. On a phone, the key highlights carousel moves on by itself with no pause either. | WCAG 2.2.2 | Serious | Medium | Fail |
| Focus outlines, borders and icons reach 3:1 against what's next to them | WCAG 1.4.11 | Serious | Medium | Not started |
| Focus indicators are visible and not obscured Zaid Al-Dabbagh, 5 Nov Every control shows a dashed blue outline on keyboard focus. A folded card and a filter panel show it around the whole thing, so it's clear what you're on, and the sticky footer doesn't hide it. | WCAG 2.4.7, 2.4.11 | Serious | Medium | Pass |
| Zoom and reflow at 200% without content loss Zaid Al-Dabbagh, 16 Nov At 200% (640px wide) every page reflows into one column with nothing lost and no sideways scrolling. The header's text size control also takes text to 125% and beyond. | WCAG 1.4.4, 1.4.10 | Serious | Medium | Pass |
| Zoom and reflow at 200% without content loss Zaid Al-Dabbagh, 7 Nov At 200%, by hand and measured at 640px wide, and measured at 320px, on the cheat sheet, the report and a rule page, with a card and the filters open. Nothing is lost and the page doesn't scroll sideways. An open card is taller than the window at 200%, so you scroll down it. Two tables on a rule page scroll sideways inside themselves at 320px, and keys can scroll them. The report's View Card modal wasn't tested. | WCAG 1.4.4, 1.4.10 | Serious | Medium | Pass |
| Responsive layouts and touch targets across breakpoints Zaid Al-Dabbagh, 9 Nov On the cheat sheet, the report and a rule page, as a phone (390px, both ways round), a tablet (768px) and a desktop (1280px), with touch on for all but the desktop. Every control is at least 24 by 24px or spaced so a 24px circle round it touches no other, and nothing scrolls sideways. A list row's copy link is left off below 1024px, where the open card has its own. Checked in an emulated browser, not on a real device. | WCAG 1.3.4, 1.4.10 | Serious | Medium | Pass |
| Responsive layouts and touch targets across breakpoints Zaid Al-Dabbagh, 16 Nov At 320, 640, 768 and 1024px wide, and in landscape at 640 by 360, no page scrolls sideways, and nothing is cut off. Carousels scroll within themselves, as they should. | WCAG 1.3.4, 1.4.10 | Serious | Medium | Pass |
| Text stays readable with spacing overridden: line, paragraph, letter and word Zaid Al-Dabbagh, 9 Nov WCAG's spacing (line 1.5, paragraphs 2, letters 0.12, words 0.16) on every kind of page at 390px and 1280px: nothing is lost. The report's tables outgrew their panels on a phone and cut off Status, fixed on 9 Nov. Rule IDs on cards are cut short sooner, as they are anyway, and show whole on hover or focus. | WCAG 1.4.12 | Serious | Medium | Pass |
| Text stays readable with spacing overridden: line, paragraph, letter and word Zaid Al-Dabbagh, 16 Nov With line height 1.5, paragraph spacing 2em, letter spacing 0.12em and word spacing 0.16em applied to everything, no text is cut off or overlaps. The Today strip grows to fit. | WCAG 1.4.12 | Serious | Medium | Pass |
| Active filters, errors and tags don't rely on colour alone Zaid Al-Dabbagh, 9 Nov Checked on the cheat sheet, the report and the Feedback form. Tags pair colour with an icon and words: severity a dot and its name, themes and features an icon and a name, statuses an icon and a word. Errors are written under each field ("Enter your name."), not only a red border. Filters ticked in both states, grey or blue, so only colour told them apart: fixed on 9 Nov, an empty ring until chosen, then a tick. | WCAG 1.4.1 | Serious | Medium | Pass |
| Active filters, errors and tags don't rely on colour alone Zaid Al-Dabbagh, 16 Nov Links in text are underlined. The contact form's errors are written out ("Enter your name.") as well as shown in red, and tags carry their words. | WCAG 1.4.1 | Serious | Medium | Pass |
| Visible labels are part of each control's accessible name Zaid Al-Dabbagh, 9 Nov axe-core's label-content-name-mismatch rule on every kind of page, at desktop and phone widths: no failures. A card's button said its rule ID in the reader's spelling ("colour-contrast" for "color-contrast"), fixed on 9 Nov. Built with Sanity's diagram buttons are flagged because the diagram's words sit inside them, but those words aren't the button's label, so they're not a failure. | WCAG 2.5.3 | Serious | Medium | Pass |
| Visible labels are part of each control's accessible name Zaid Al-Dabbagh, 16 Nov Where a control has a name of its own, it includes the words shown: "100%" is in "Text size 100% — press for 125%", and each hour in the forecast reads as shown ("Now: overcast, 12°C"). | WCAG 2.5.3 | Serious | Medium | Pass |
| Images, including older content, have meaningful text alternatives Zaid Al-Dabbagh, 16 Nov Most images have good alt text: client logos say the client, badges say what they mean. Some don't: insight images say "Test", "Important for SEO and accessibility.", "Humans" or "Bricks"; work images say "stream", "Food" or "Crowds"; a service image says "dev"; /sanity's background says "Sanity bg". These need real descriptions, or empty alt where they're decoration. | WCAG 1.1.1 | Serious | High | Fail |
| Every interactive element meets the 24 by 24 pixel target size or its spacing exception Zaid Al-Dabbagh, 16 Nov Almost every target is 24px or more, or spaced well apart. The footer scorecard's "0/29 passed, full report" link is 16px tall and sits 10px from the "Conformance report" link under it, closer than the spacing allows. | WCAG 2.5.8 | Serious | High | Fail |
| Real-device checks in mobile Chrome | Manual interaction and assistive tech verification | Serious | High | Not started |
| Real-device checks in mobile Chrome | Manual interaction and assistive tech verification | Serious | High | Not started |
| PDFs and other documents are tagged, navigable, and screen-reader compatible | WCAG 1.3.1, 1.3.2, 2.4.1, 4.1.2 | Serious | High | Not started |
| Images, including older content, have meaningful text alternatives Zaid Al-Dabbagh, 6 Nov Every image on the cheat sheet, its report, Built with Sanity and the release notes says what it shows, back to v1.0.0's screenshots. Cards hold no images. The video thumbnail's alt is empty because its play button names it, and each diagram has a transcript. A11y University's other pages weren't part of this. | WCAG 1.1.1 | Serious | High | Pass |
| Every interactive element meets the 24 by 24 pixel target size or its spacing exception Zaid Al-Dabbagh, 9 Nov axe-core's target-size rule on every kind of page at desktop and phone widths, and with Feedback, Subscribe, Sort and Export open: nothing under 24 by 24px without enough space round it. | WCAG 2.5.8 | Serious | High | Pass |
| Print stylesheet preserves core content readability Zaid Al-Dabbagh, 16 Nov Printed (About, A4), the words come through, but the page title "About" disappears with its banner, and the header prints at the top of every page over the first lines of text. The Today strip and the assistant button print too. | Print accessibility checks | Moderate | Low | Fail |
| Skip links appear early and move focus to main content Zaid Al-Dabbagh, 5 Nov Skip to cards comes straight after the search box. It's unseen until you tab to it, sits inside the search box, and moves focus to the first card, past every filter. | WCAG 2.4.1 | Moderate | Low | Pass |
| Skip links appear early and move focus to main content Zaid Al-Dabbagh, 16 Nov Pressing "Skip to content" opens the page's contents and moves focus to its first section, one Tab from the main content. Checked on all 13 pages tested. | WCAG 2.4.1 | Moderate | Low | Pass |
| Print stylesheet preserves core content readability Zaid Al-Dabbagh, 6 Nov A card prints on A4 with its headings and words intact, nothing cut off at the sides. A video prints as its link, written out, and the footer stops following the page. | Print accessibility checks | Moderate | Low | Pass |
| A skip link is one of the first things Tab reaches on every page Zaid Al-Dabbagh, 9 Nov Checked on every kind of page: the cheat sheet, the report, a rule page, Built with Sanity, Updates, Changes, a change and a newsletter. Skip to content (or Skip to cards on the cheat sheet, after the logo and search) is in the first three Tab stops, shows when reached, and Enter moves focus to the content, so the next Tab carries on from there. Five pages had none and were given one on 9 Nov. | WCAG 2.4.1 | Moderate | Low | Pass |
| A skip link is one of the first things Tab reaches on every page Zaid Al-Dabbagh, 16 Nov The first Tab on every page reaches "Skip to content", and it shows when focused. Tested on the home page, About, Services, a service (Product Design), Products, Work, a work entry (FDRS), Insights, an article, Contact, Accessibility, the privacy policy and /sanity, in Chrome at 1280px wide. | WCAG 2.4.1 | Moderate | Low | Pass |
| Technical content is written in plain language or offers a simpler summary | WCAG 3.1.5 | Moderate | Medium | Not started |
| Technical content is written in plain language or offers a simpler summary Zaid Al-Dabbagh, 5 Nov All 99 cards open with a plain headline and a one-sentence summary, before any code. Those summaries read at about Year 9 or 10 on a rough Flesch-Kincaid count, a little above WCAG 3.1.5's lower-secondary bar. Words like ARIA and tabindex push that up, and they stay because they're what the reader has to learn. | WCAG 3.1.5 | Moderate | Medium | Pass |
| Sign-in, if there is any, needs no memory test or puzzle without an alternative Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | WCAG 3.3.8 | Serious | Low | Not applicable |
| Sign-in, if there is any, needs no memory test or puzzle without an alternative Zaid Al-Dabbagh, 16 Nov The public website has no sign-in. | WCAG 3.3.8 | Serious | Low | Not applicable |
| Gestures have a single-pointer alternative, and a press can be cancelled Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | WCAG 2.5.1, 2.5.2 | Serious | Medium | Not applicable |
| Moving or updating content can be paused, stopped or hidden Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | WCAG 2.2.2 | Serious | Medium | Not applicable |
| PDFs and other documents are tagged, navigable, and screen-reader compatible Zaid Al-Dabbagh, 16 Nov The pages tested link to no PDFs or other documents. | WCAG 1.3.1, 1.3.2, 2.4.1, 4.1.2 | Serious | High | Not applicable |
| Maps and interactive embeds provide an accessible text alternative Zaid Al-Dabbagh, 6 Nov The cheat sheet has no maps or interactive embeds. Its one video is covered by the video check. | WCAG 1.1.1, 1.3.1 | Moderate | Low | Not applicable |
| Maps and interactive embeds provide an accessible text alternative Zaid Al-Dabbagh, 16 Nov No page embeds a map or an interactive widget. Office addresses are text, linking to Google Maps. | WCAG 1.1.1, 1.3.1 | Moderate | Low | Not applicable |
| Forms don't ask again for what a person has already entered Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | WCAG 3.3.7 | Moderate | Low | Not applicable |
| Forms don't ask again for what a person has already entered Zaid Al-Dabbagh, 16 Nov The site's forms — contact and newsletter — are one step each, so nothing is asked twice. | WCAG 3.3.7 | Moderate | Low | Not applicable |
| Single-key shortcuts can be turned off, remapped or work only on focus Added on 6 Nov to close a gap in these checks. Set aside for now: it hasn't been tested, so it's not a finding. | WCAG 2.1.4 | Moderate | Low | Not applicable |
| Single-key shortcuts can be turned off, remapped or work only on focus Zaid Al-Dabbagh, 16 Nov The website has no single-key shortcuts. | WCAG 2.1.4 | Moderate | Low | Not applicable |
ACCESSIBILITY CONFORMANCE REPORT (VPAT® 2.5 WCAG Edition)
⚠️ This report is pending a review. It's from 10 November 2026, and the test results it's based on changed on 16 Nov.
Report Summary
- Product
- A11Y Cheat Sheet (v1.0+)
- Evaluation Date
- 10 November 2026
- Evaluator(s)
Zaid Al-Dabbagh- Evaluation Methods
- Automated testing: Google Lighthouse 13.6.0 (axe-core 4.14.0)
- Manual inspection: Keyboard-only traversal, DOM & CSS inspection
- Assistive Technology (AT) testing: VoiceOver (macOS) started; VoiceOver (iOS) and NVDA (Windows) planned
- Status
- Interim Assessment (In Progress)
Interim, not a claim of conformance.
Evaluation Scope & Coverage
- Target Standard
- WCAG 2.1 & 2.2 Level A / AA
- Audit Progress
- 46% Complete (27 of 58 criteria evaluated; 31 pending manual/assistive tech review)
Criteria Conformance Summary
- Supports
- 18
- Partially Supports
- 5
- Does Not Support
- 1
- Not Evaluated (Pending)
- 31
- Not Applicable
- 3
Known gaps
- This is an interim report, not a claim of WCAG conformance. Most Level A and AA criteria are still Not Evaluated.
- The automated score covers one page: a saved Lighthouse run of the main page, on desktop, on 5 Nov 2026. It isn't a daily or CI run, and 100 means the 28 rules that applied passed, not that the page is accessible.
- Screen reader flow isn't tested from start to finish. That check and the mobile Safari VoiceOver check haven't been started, and the NVDA and Android TalkBack checks are required but not started. That leaves 1.3.2, 2.4.4 and 4.1.2 Not Evaluated.
- Zoom and reflow passed on the cheat sheet, the report and a rule page on 7 Nov 2026, and responsive layouts and touch targets on 9 Nov 2026. The report's View Card modal wasn't tested.
- Responsive layouts and touch targets were checked in an emulated browser, not on a real device: no mobile Chrome, and no mobile Safari with VoiceOver. 2.5.8's own check, which looks at every control, passed on 9 Nov 2026.
- PDF tagging isn't verified. The report's export relies on the browser's Print window. Chromium's output is tagged, other browsers are unchecked, and a card PDF scored 84/100 on a PDF/UA-2 checker on 15 Oct 2026.
- Captions on the label card's video are YouTube's automatic ones and unreviewed (1.2.2), and nobody has checked that its transcript covers what's shown (1.2.3).
- The report's score gauges keep turning with no pause control (2.2.2).
- The form component behind Subscribe and Feedback sets no autocomplete values on personal fields (1.3.5).
- The manual keyboard and focus checks are dated 5 Nov 2026 and predate the report's pins, heading sort and Export menus. Those new controls have story tests but no manual retest.
- Contrast is measured automatically in one theme only (1.4.3).
- A11y University's pages outside the cheat sheet, and the dashboard, aren't in scope.
- 13 manual checks were added on 6 Nov 2026 to close gaps. On 9 Nov 2026, 8 of them were made required and count in the manual score of 70: 5 have passed, and the NVDA, TalkBack and non-text contrast checks haven't been started. The other 5 are set aside as Not applicable for now. That label means not yet tested here, not that they don't apply, so they're left out of the score.
| Criterion | Level | Status | Evaluator Notes |
|---|---|---|---|
| 1.1.1 Non-text Content | A | Supports⚠️ Under review: Images, including older content, have meaningful text alternatives failed | Lighthouse's image-alt rule passed. A person went through every image on the cheat sheet, its report, Built with Sanity and the release notes, back to v1.0.0's screenshots, and each says what it shows. Cards hold no images. The video thumbnail's alt is empty because its play button names it, and each diagram has a transcript. A11y University's other pages weren't part of this. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Partially Supports | The one card video, on the label card, has sound and a corrected transcript. The A11y University promo's background video wasn't assessed as video-only content. |
| 1.2.2 Captions (Prerecorded) | A | Partially Supports | The label card's video has captions, but they're YouTube's automatic ones and haven't been reviewed line by line. They spell the for attribute as "four". The transcript under the video is the corrected text. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Partially Supports | The video has a corrected transcript, but nobody has checked that it covers what's shown on screen as well as what's said. |
| 1.2.4 Captions (Live) | AA | Not Applicable | The cheat sheet has no live audio or video. |
| 1.2.5 Audio Description (Prerecorded) | AA | Not Evaluated | The video has no audio description track, and nobody has checked whether its soundtrack already says everything shown. |
| 1.3.1 Info and Relationships | A | Not Evaluated | Passed so far: form labels and errors in the forms check, and Lighthouse's list, definition list, heading order and label rules. The PDF check hasn't been started. |
| 1.3.2 Meaningful Sequence | A | Not Evaluated | The screen reader flow check hasn't been started, so this can't be claimed yet. The PDF check hasn't been started. |
| 1.3.3 Sensory Characteristics | A | Not Evaluated | No manual check covers this yet, and no automated rule settles it. |
| 1.3.4 Orientation | AA | Supports | The responsive layouts check passed on 9 Nov 2026: the cheat sheet, the report and a rule page work as a phone both ways round, a tablet and a desktop, in an emulated browser. Nothing is locked to one orientation. |
| 1.3.5 Identify Input Purpose | AA | Does Not Support | From a code review: the form component behind Subscribe and Feedback sets no autocomplete values on the fields that ask for a person's own details. The only autocomplete in it is on a hidden anti-spam field. |
| 1.4.1 Use of Color | A | Supports | The colour check passed on 9 Nov 2026: tags pair colour with an icon and words, errors are written under their fields, and filters show a tick once chosen, an empty ring before, fixed that day. |
| 1.4.2 Audio Control | A | Not Evaluated | The video plays only when pressed. Read aloud and the promo's background video haven't been assessed. |
| 1.4.3 Contrast (Minimum) | AA | Not Evaluated | Lighthouse's colour-contrast rule passed on the main page, in one theme, on desktop. Contrast hasn't been measured across themes or on the other pages. |
| 1.4.4 Resize Text | AA | Supports | The zoom and reflow check passed at 200% on 7 Nov 2026 on the cheat sheet, the report and a rule page, with a card and the filters open. The report's View Card modal wasn't tested. |
| 1.4.5 Images of Text | AA | Not Evaluated | No manual check covers this yet, and no automated rule settles it. Release note screenshots contain text. |
| 1.4.10 Reflow | AA | Supports | The zoom and reflow check passed on 7 Nov 2026 at 320px on the cheat sheet, the report and a rule page, after two overflows were fixed, and the responsive layouts check on 9 Nov 2026. On 9 Nov 2026 the report's Automated and Manual Checks tables were found 40px and 3px wider than their panels at 320px, cutting off Status, which the earlier check missed; they were fixed that day. The report's View Card modal wasn't tested. |
| 1.4.11 Non-text Contrast | AA | Not Evaluated | A manual check for this is required and hasn't been started. |
| 1.4.12 Text Spacing | AA | Supports | The text spacing check passed on 9 Nov 2026 on every kind of page at 390px and 1280px, after the report's tables were made to fit their panels. Rule IDs on cards are cut short and show whole on hover or focus. |
| 1.4.13 Content on Hover or Focus | AA | Not Evaluated | No manual check covers this yet, and no automated rule settles it. The product has hover labels and hints. |
| 2.1.1 Keyboard | A | Supports | A person tabbed through the cheat sheet: every control can be reached and used, and filters take Enter or Space. Tested 5 Nov 2026, before the report's pins, heading sort and Export menus were added. Those haven't had a manual keyboard pass. |
| 2.1.2 No Keyboard Trap | A | Supports | Nothing traps focus. A filter panel and a folded card are one stop each: Enter goes in, and Escape or tabbing past the end comes out. |
| 2.1.4 Character Key Shortcuts | A | Not Evaluated | A manual check for this has been added, but it's set aside for now and hasn't been done. The one global shortcut found, Command or Control K for search, uses a modifier key, but a full review hasn't been done. |
| 2.2.1 Timing Adjustable | A | Not Evaluated | No manual check covers this yet, and no automated rule settles it. |
| 2.2.2 Pause, Stop, Hide | A | Partially Supports | The report's score gauges turn for as long as the page is open, with no way to pause them. They stay still with reduced motion on, but that's not a control on the page. Other moving content hasn't been reviewed. A manual check for this has been added, but it's set aside for now. |
| 2.3.1 Three Flashes or Below Threshold | A | Not Evaluated | No manual check covers this yet, and no automated rule settles it. The gauges fire confetti, which hasn't been assessed. |
| 2.4.1 Bypass Blocks | A | Not Evaluated | Passed so far: Skip to cards comes right after the search box and moves focus to the first card, and the report has Skip to content. The PDF check, which also covers this, hasn't been started. The check that a skip link comes first on every page passed on 9 Nov 2026, after five pages were given one. |
| 2.4.2 Page Titled | A | Supports | Lighthouse's document-title rule passed, and the main and report pages have titles that say what they are. Other pages weren't individually reviewed. |
| 2.4.3 Focus Order | A | Supports | Focus moves in a logical order in the keyboard check. One known mismatch on the report: a panel's Export Report comes after the panel's fold button in the Tab order, though it's drawn before the chevron. |
| 2.4.4 Link Purpose (In Context) | A | Not Evaluated | Passed so far: Lighthouse's link-name rule, and PDF links give their format, size and that they open in a new tab. The screen reader flow check hasn't been started, so this can't be claimed yet. |
| 2.4.5 Multiple Ways | AA | Not Evaluated | No manual check covers this yet, and no automated rule settles it. The deck has search and filters. |
| 2.4.6 Headings and Labels | AA | Not Evaluated | Lighthouse's heading-order rule passed, and forms have labels, but nobody has judged whether headings and labels describe their content. |
| 2.4.7 Focus Visible | AA | Supports⚠️ Under review: Focus indicators are visible and not obscured failed | Every control shows a dashed blue outline on keyboard focus. A folded card and a filter panel show it around the whole thing. |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Supports⚠️ Under review: Focus indicators are visible and not obscured failed | The sticky footer doesn't hide what has focus. This is Level AA in WCAG 2.2. |
| 2.5.1 Pointer Gestures | A | Not Evaluated | A manual check for this has been added, but it's set aside for now and hasn't been done. |
| 2.5.2 Pointer Cancellation | A | Not Evaluated | A manual check for this has been added, but it's set aside for now and hasn't been done. |
| 2.5.3 Label in Name | A | Supports | The visible labels check passed on 9 Nov 2026: no control on any kind of page has a name that leaves out its visible words, at desktop and phone widths. A card's name used to respell its rule ID, fixed that day. |
| 2.5.4 Motion Actuation | A | Not Evaluated | No manual check covers this yet, and no automated rule settles it. |
| 2.5.7 Dragging Movements | AA | Not Evaluated | No manual check covers this yet, and no automated rule settles it. Filter panels have drag handles, and a single-pointer alternative hasn't been confirmed. |
| 2.5.8 Target Size (Minimum) | AA | Supports⚠️ Under review: Every interactive element meets the 24 by 24 pixel target size or its spacing exception failed | The target size check passed on 9 Nov 2026: no control on any kind of page, or in the Feedback, Subscribe, Sort or Export menus and dialogs, is under 24 by 24px without enough space round it, at desktop and phone widths. |
| 3.1.1 Language of Page | A | Supports | Lighthouse's html-has-lang and html-lang-valid rules passed. |
| 3.1.2 Language of Parts | AA | Not Evaluated | Lighthouse's valid-lang rule passed, but that only checks language tags that exist, not passages that need one. |
| 3.2.1 On Focus | A | Not Evaluated | No manual check covers this yet, and no automated rule settles it. |
| 3.2.2 On Input | A | Not Evaluated | No manual check covers this yet, and no automated rule settles it. |
| 3.2.3 Consistent Navigation | AA | Not Evaluated | No manual check covers this yet, and no automated rule settles it. |
| 3.2.4 Consistent Identification | AA | Not Evaluated | No manual check covers this yet, and no automated rule settles it. |
| 3.2.6 Consistent Help | A | Not Evaluated | No manual check covers this yet, and no automated rule settles it. |
| 3.3.1 Error Identification | A | Supports | Subscribe and Feedback: each error says what's wrong, sits under its field and takes focus there. |
| 3.3.2 Labels or Instructions | A | Supports | Subscribe and Feedback have a label on every field. |
| 3.3.3 Error Suggestion | AA | Supports | Each error says what to do, and what was typed stays. A failed send is announced. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Not Evaluated | Neither form is legal or financial. Whether the Subscribe form's stored email counts as user data under this criterion hasn't been reviewed. |
| 3.3.7 Redundant Entry | A | Not Evaluated | A manual check for this has been added, but it's set aside for now and hasn't been done. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Not Applicable | The cheat sheet has no sign-in. |
| 4.1.1 Parsing | A | Not Applicable | Removed from WCAG 2.2 as obsolete. Kept here for WCAG 2.1 readers. |
| 4.1.2 Name, Role, Value | A | Not Evaluated | Lighthouse's ARIA, button-name and link-name rules passed. The screen reader flow check hasn't been started, so this can't be claimed yet. Early VoiceOver testing found an open question: moving between a card's panels with the arrow keys gives no announcement. |
| 4.1.3 Status Messages | AA | Not Evaluated | Passed so far: a failed form send is announced, and Copy to Clipboard says so. Not reviewed across the product. Sorting the report says nothing as it happens, and a download isn't announced.. |
| 3.1.5 Reading Level | AAA | Partially Supports | Marked Pass in the manual check, but its own note falls short of the bar. All 99 cards open with a plain headline and a one-sentence summary before any code, and those read at about Year 9 or 10 on a rough Flesch-Kincaid count, a little above lower-secondary. Words like ARIA and tabindex push that up, and they stay because they're what the reader has to learn. |
| 3.2.5 Change on Request | AAA | Not Evaluated | Passed so far: PDF links say they open a new tab and the print dialog. That covers links to files only, not every change of context. |