Skip to content
A11Y Cheat Sheet

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.

Known limitations and roadmap
Area or feature
Screen readers
The problem
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.
What you can do instead
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.
When we expect to fix it
Not yet scheduled
The label card's video
The problem
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.
What you can do instead
Read the corrected transcript under the video.
When we expect to fix it
Not yet scheduled
Subscribe and Feedback forms
The problem
The name and email fields don't tell your browser what they're for, so autofill may not offer your details.
What you can do instead
Type them in. Nothing else on the forms depends on autofill.
When we expect to fix it
Not yet scheduled
Score gauges on this report
The problem
The rings around the scores keep turning, with no button to stop them.
What you can do instead
Turn on Reduce motion in your device settings and they stay still.
When we expect to fix it
Not yet scheduled
PDF exports
The problem
PDFs come from your browser's Print window. Chrome's are tagged for screen readers; other browsers' haven't been checked.
What you can do instead
Print from Chrome, or export the report as JSON or plain text instead.
When we expect to fix it
Not yet scheduled
Colour contrast
The problem
Contrast has only been measured automatically, in one theme, so some text may be hard to read in others.
What you can do instead
Tell us where text is hard to read and we'll look at it first.
When we expect to fix it
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.

100 out of 100

Accessibility

Automated Checks

28/28 Checks passed • Last tested 5 Nov 2026

Understanding Severity Levels

Automated tests catch some accessibility problems, not all of them, so a clean run doesn’t prove a page is accessible.

Severity is how badly a problem stops someone with a disability finishing a task. Here, each check’s level comes from the weight Lighthouse gives it in the score.

Critical

They can’t finish the task, and there’s no way around it. For example, a Pay button a keyboard or screen reader can’t reach.

Serious

The task is very hard to finish. There may be a workaround, but many people will give up. For example, a menu that keyboard focus skips, or an infographic with no alt text.

Moderate

It’s annoying, or it breaks a WCAG rule, but people can still finish the task. For example, a decorative icon with no empty alt, so a screen reader reads out its file name.

28 checks

Filter by category

Filter by user impact

Automated checks: 28 shown
CheckStatus

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.

View Card: An ARIA attribute is used where it isn't allowed

ARIA · Critical

Pass

The whole page is hidden from screen readers

With aria-hidden="true" on the body, screen readers find nothing on the page, so blind visitors can't read or use any of it.

View Card: The whole page is hidden from screen readers

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.

View Card: A role is missing an ARIA attribute it needs

ARIA · Critical

Pass

A role attribute uses a value that doesn't exist

When role is misspelt, made up or abstract, screen readers ignore it — so people can't tell what the element is or how to use it.

View Card: A role attribute uses a value that doesn't exist

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.

View Card: An ARIA attribute has a value that isn't allowed

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.

View Card: An ARIA attribute name is misspelled or made up

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.

View Card: A button has no name a screen reader can say

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.

View Card: An image has no text alternative

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.

View Card: A form field has no label

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.

View Card: The page stops people from zooming in

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.

View Card: An ARIA attribute breaks the rules for this element

ARIA · Serious

Pass

Hidden content can still receive keyboard focus

Something is hidden from screen readers but can still be reached with Tab, so focus lands on a control that says nothing at all.

View Card: Hidden content can still receive keyboard focus

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.

View Card: An ARIA label is on an element that can't have one

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.

View Card: Text colour is too close to its background colour

Contrast · Serious

Pass

A definition list contains the wrong elements

When a <dl> holds stray elements or terms in the wrong order, screen readers may miss which description belongs to which term.

View Card: A definition list contains the wrong elements

Tables · Serious

Pass

Term and description items sit outside a description list

When <dt> or <dd> items aren't inside a <dl>, screen readers can't tell which description belongs to which term, or how many pairs there are.

View Card: Term and description items sit outside a description list

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.

View Card: The page has no title

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.

View Card: The page doesn't say what language it's in

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.

View Card: The page's language code is not a real language

Language · 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.

View Card: A list contains something other than list items

Tables · Serious

Pass

A list item sits outside a list

When an <li> isn't inside a <ul> or <ol>, screen readers may not announce it as a list, so people lose the count and grouping.

View Card: A list item sits outside a list

Tables · Serious

Pass

An element has a tabindex greater than zero

A positive tabindex forces that element to the front of the Tab order, so keyboard users jump around the page in a confusing order.

View Card: An element has a tabindex greater than zero

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.

View Card: A button or link is too small to tap easily

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.

View Card: A lang attribute on part of the page has an invalid value

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.

View Card: Heading levels skip a step, like jumping from h2 to h4

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.

View Card: The page has no main content area marked up

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.

View Card: An outdated ARIA role is used

ARIA · Moderate

Pass

53 out of 100

Accessibility

Manual Checks

33/47 Checks completed • Last tested 9 Nov 2026

Understanding Manual Checks

Lighthouse can’t test everything. Some checks need a person: using the page with only a keyboard, listening to it with a screen reader, following the focus order, and reading the words for clarity.

Each check is tested by hand against the WCAG 2.2 criteria in its Coverage column, and has one of four statuses:

  • Not started: nobody has tested it here yet, so it counts as failed.
  • Pass: a person tested it and it meets the criteria.
  • Fail: a person tested it and found a problem.
  • Not applicable: the site has nothing this check covers, so it’s left out of the score.

The score is the share of checks that passed, so it climbs as they’re tested.

User Impact is who gets stopped if a check fails, in the same levels as Severity on the automated checks. Effort is roughly how long it takes to test: Low is 1 to 5 minutes, Medium is 5 to 15, and High is over 15 minutes or needs something set up first, like a phone or a screen reader. Start with the quick wins near the top of the list.

58 checks

Manual checks: 47 shown, sorted by User Impact, descending
Check / Coverage / Evaluator Notes
Online forms: labels, instructions, errors, and recovery

Critical · Medium effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Online forms: labels, instructions, errors, and recovery

Critical · Medium effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Real-device checks in mobile Safari with VoiceOver

Critical · High effort

Manual iOS and VoiceOver verification
Not started
Real-device checks in mobile Safari with VoiceOver

Critical · High effort

Manual iOS and VoiceOver verification
Not started
Real-device checks on Android with TalkBack

Critical · High effort

Manual Android and TalkBack verification
Not started
Real-device checks on Android with TalkBack

Critical · High effort

Manual Android and TalkBack verification
Not started
Desktop screen reader checks: NVDA with Chrome and Firefox, VoiceOver with Safari

Critical · High effort

Manual assistive tech verification across browsers
Not started
Desktop screen reader checks: NVDA with Chrome and Firefox, VoiceOver with Safari

Critical · High effort

Manual assistive tech verification across browsers
Not started
Keyboard tabbing reaches all controls with no keyboard traps

Critical · High effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Keyboard tabbing reaches all controls with no keyboard traps

Critical · High effort

Zaid Al-Dabbagh (opens in a new tab) 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.)

Pass
Videos include captions, and audio/video has a transcript or alternative

Serious · Low effort

Not started
Videos include captions, and audio/video has a transcript or alternative

Serious · Low effort

Zaid Al-Dabbagh (opens in a new tab) 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".

Pass
Focus indicators are visible and not obscured

Serious · Medium effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Fail
Focus outlines, borders and icons reach 3:1 against what's next to them

Serious · Medium effort

WCAG 1.4.11
Zaid Al-Dabbagh (opens in a new tab) 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.

Fail
Gestures have a single-pointer alternative, and a press can be cancelled

Serious · Medium effort

WCAG 2.5.1, WCAG 2.5.2
Zaid Al-Dabbagh (opens in a new tab) 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.

Fail
Moving or updating content can be paused, stopped or hidden

Serious · Medium effort

WCAG 2.2.2
Zaid Al-Dabbagh (opens in a new tab) 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.

Fail
Focus outlines, borders and icons reach 3:1 against what's next to them

Serious · Medium effort

WCAG 1.4.11
Not started
Focus indicators are visible and not obscured

Serious · Medium effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Zoom and reflow at 200% without content loss

Serious · Medium effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Zoom and reflow at 200% without content loss

Serious · Medium effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Responsive layouts and touch targets across breakpoints

Serious · Medium effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Responsive layouts and touch targets across breakpoints

Serious · Medium effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Text stays readable with spacing overridden: line, paragraph, letter and word

Serious · Medium effort

WCAG 1.4.12
Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Text stays readable with spacing overridden: line, paragraph, letter and word

Serious · Medium effort

WCAG 1.4.12
Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Active filters, errors and tags don't rely on colour alone

Serious · Medium effort

WCAG 1.4.1
Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Active filters, errors and tags don't rely on colour alone

Serious · Medium effort

WCAG 1.4.1
Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Visible labels are part of each control's accessible name

Serious · Medium effort

WCAG 2.5.3
Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Visible labels are part of each control's accessible name

Serious · Medium effort

WCAG 2.5.3
Zaid Al-Dabbagh (opens in a new tab) 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").

Pass
Images, including older content, have meaningful text alternatives

Serious · High effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Fail
Every interactive element meets the 24 by 24 pixel target size or its spacing exception

Serious · High effort

WCAG 2.5.8
Zaid Al-Dabbagh (opens in a new tab) 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.

Fail
Real-device checks in mobile Chrome

Serious · High effort

Manual interaction and assistive tech verification
Not started
Real-device checks in mobile Chrome

Serious · High effort

Manual interaction and assistive tech verification
Not started
PDFs and other documents are tagged, navigable, and screen-reader compatible

Serious · High effort

Not started
Images, including older content, have meaningful text alternatives

Serious · High effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Every interactive element meets the 24 by 24 pixel target size or its spacing exception

Serious · High effort

WCAG 2.5.8
Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Print stylesheet preserves core content readability

Moderate · Low effort

Print accessibility checks
Zaid Al-Dabbagh (opens in a new tab) 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.

Fail
Skip links appear early and move focus to main content

Moderate · Low effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Skip links appear early and move focus to main content

Moderate · Low effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Print stylesheet preserves core content readability

Moderate · Low effort

Print accessibility checks
Zaid Al-Dabbagh (opens in a new tab) 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.

Pass
Technical content is written in plain language or offers a simpler summary

Moderate · Medium effort

Not started
Technical content is written in plain language or offers a simpler summary

Moderate · Medium effort

Zaid Al-Dabbagh (opens in a new tab) 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.

Pass

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
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

WCAG criteria: 55 listed, sorted by Criterion, ascending
1.1.1 Non-text ContentA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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.

Supports

Under review: Images, including older content, have meaningful text alternatives failed

1.2.1 Audio-only and Video-only (Prerecorded)A
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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)A
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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)A
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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)AA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 RelationshipsA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 SequenceA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 CharacteristicsA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it.

Not Evaluated

1.3.4 OrientationAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 PurposeAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 ColorA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 ControlA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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)AA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 TextAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 TextAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it. Release note screenshots contain text.

Not Evaluated

1.4.10 ReflowAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 ContrastAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

A manual check for this is required and hasn't been started.

Not Evaluated

1.4.12 Text SpacingAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 FocusAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it. The product has hover labels and hints.

Not Evaluated

2.1.1 KeyboardA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 TrapA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 ShortcutsA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 AdjustableA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it.

Not Evaluated

2.2.2 Pause, Stop, HideA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 ThresholdA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 BlocksA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 TitledA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 OrderA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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)A
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 WaysAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 LabelsAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 VisibleAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

Every 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

2.4.11 Focus Not Obscured (Minimum)AA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

The 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

2.5.1 Pointer GesturesA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 CancellationA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 NameA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 ActuationA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it.

Not Evaluated

2.5.7 Dragging MovementsAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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)AA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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.

Supports

Under review: Every interactive element meets the 24 by 24 pixel target size or its spacing exception failed

3.1.1 Language of PageA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

Lighthouse's html-has-lang and html-lang-valid rules passed.

Supports

3.1.2 Language of PartsAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 LevelAAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 FocusA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it.

Not Evaluated

3.2.2 On InputA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it.

Not Evaluated

3.2.3 Consistent NavigationAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it.

Not Evaluated

3.2.4 Consistent IdentificationAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it.

Not Evaluated

3.2.5 Change on RequestAAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 HelpA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

No manual check covers this yet, and no automated rule settles it.

Not Evaluated

3.3.1 Error IdentificationA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

Subscribe and Feedback: each error says what's wrong, sits under its field and takes focus there.

Supports

3.3.2 Labels or InstructionsA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

Subscribe and Feedback have a label on every field.

Supports

3.3.3 Error SuggestionAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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)AA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 EntryA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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, ValueA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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 MessagesAA
Zaid Al-Dabbagh (opens in a new tab) 10 Nov

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

Powered by

Powered byA11y Universityv1.1.0Built withSanity

Feedback on the A11Y Cheat Sheet

A problem, an idea, a card that could be clearer — tell us.

Issue Details Form

An image (PNG, JPEG, GIF, WebP) or a video (MP4, MOV), up to 4 MB.

Subscribe to the A11Y Cheat Sheet

New cards and what's changed in the A11Y Cheat Sheet. Leave any time from a link in every email.

© 2026 Panda UX Studio Pty Ltd