Component checks

What has been checked for each component, and what hasn't. Every result on this page is written by a script that works the real pages; nothing is typed in.

Beta

Why this page exists

A design system that says "accessible" asks to be believed. This one shows its working instead: for each component, what was tested, how, and when, and which checks nobody has done yet. A gap that is written down gets closed; one that isn't gets forgotten.

Results

Last run on against Somnia DS 1.89.0, in Chromium with axe-core 4.14.0.

ComponentAutomatedNarrow screenKeyboardOn paperScreen reader
ButtonPassedPassed9 of 9PassedNot yet
Chat buttonPassedPassed9 of 9PassedNot yet
LinkPassedPassed8 of 8PassedNot yet
Print buttonPassedPassed4 of 4PassedNot yet
Share barPassedPassed7 of 7PassedNot yet
Contact pagePassedPassed4 of 4PassedNot yet
Date fieldPassedPassed7 of 7PassedNot yet
Form fieldPassedPassed6 of 6PassedNot yet
Multi-choice drop-downPassedPassed7 of 7PassedNot yet
Newsletter sign-upPassedPassed5 of 5PassedNot yet
SearchPassedPassed7 of 7PassedNot yet
Segmented controlPassedPassed6 of 6PassedNot yet
SwitchPassedPassed6 of 6PassedNot yet
BreadcrumbPassedPassed7 of 7PassedNot yet
FooterPassedPassed4 of 4PassedNot yet
HeaderPassedPassed14 of 14PassedNot yet
Sections togglePassedPassed5 of 5PassedNot yet
AccordionPassedPassed8 of 8PassedNot yet
CardPassedPassed5 of 5PassedNot yet
Checklist offerPassedPassed6 of 6PassedNot yet
Code blockPassedPassed7 of 7PassedNot yet
Instagram stripPassedPassed9 of 9PassedNot yet
Page heroPassedPassed4 of 4PassedNot yet
Partner badgesPassedPassed5 of 5PassedNot yet
Read morePassedPassed5 of 5PassedNot yet
ReviewsPassedPassed7 of 7PassedNot yet
Stat gridPassedPassed4 of 4PassedNot yet
TablePassedPassed5 of 5PassedNot yet
TagPassedPassed3 of 3PassedNot yet
TestimonialsPassedPassed5 of 5PassedNot yet
AI suggestionsPassedPassed8 of 8PassedNot yet
CalloutPassedPassed4 of 4PassedNot yet
Cookie bannerPassedPassed11 of 11PassedNot yet
Empty statePassedPassed2 of 2PassedNot yet
Loading placeholdersPassedPassed7 of 7PassedNot yet
NoticePassedPassed7 of 7PassedNot yet
Progress barPassedPassed5 of 5PassedNot yet
Status indicatorPassedPassed5 of 5PassedNot yet
ToastPassedPassed9 of 9PassedNot yet
Tooltip and hintPassedPassed8 of 8PassedNot yet
CarouselPassedPassed12 of 12PassedNot yet
Lightbox and galleryPassedPassed15 of 15PassedNot yet
ModalPassedPassed11 of 11PassedNot yet
Video heroPassedPassed11 of 11PassedNot yet
Video playerPassedPassed16 of 16PassedNot yet

All 45 components have been through these checks and carry the full Accessibility and Evidence sections on their pages.

The checks

CheckWhat it doesWhat it can't tell you
Automatedaxe-core runs every WCAG 2.0, 2.1 and 2.2 rule at levels A and AA on the component's page, once in light and once in dark.Automated rules find a minority of real problems. Passing means nothing was found, not that nothing is wrong.
Narrow screenThe page is opened 320px wide, the width WCAG's Reflow criterion uses, and must not scroll sideways.Whether it is comfortable to use at that width, or at 400% zoom on a real device.
KeyboardA script presses real keys on the live example: Tab to reach it, Enter, Space and Escape to work it. After each it checks what changed, where the focus is, and the role, name and state the browser reports to assistive technology.Whether the order makes sense to a person, or how it feels with a switch device or voice control.
On paperThe page is printed to A4 as a reader would print it, and the result is searched for text over text, headings stranded at the foot of a sheet, controls left on the page and uneven spacing.How a saved PDF reads in a screen reader.
Screen readerA person listens to the component in VoiceOver and NVDA and writes down what is said.Not done yet for any component. Until it is, every page says so.

What the checks have found

The first full run, on 18 November 2026, found four faults that reading the code and looking at the pages had not:

  • Every docs page scrolled sideways at 320px. The menu's bar could not shrink below its words. Fixed in the layout, for every page.
  • A social link didn't say it opens a new tab. A label written for one site had replaced the one that did. The footer now adds it whatever the label.
  • One press of "Open all sections" opened and shut them. The script had bound twice where a page showed the example twice. Fixed in the component, and in Read more and See more.
  • The tooltip's bubble sat inside a list. A div where only list items may go. It is now added to the nearest element that may hold one.

The second, the same day, on the six Forms and input components, found five more (fixed in Somnia 1.81.0):

  • A contact form's error message wasn't tied to its field. It was placed under the field and nothing more. Each field now names its message, and focus goes to the first field with a problem.
  • A date field never said its date. Its button was named by its label alone. The name is now the label and the date showing.
  • Closing search on a phone lost your place. Focus fell to the top of the page. It goes back to Search.
  • A multi-choice option's row was 39px high where its page said 40. It is 40.
  • The Search page scrolled sideways at 320px. A file path in a sentence could not break. Long words in running text now do, on every page.

The third, on the four Actions components, found four more (fixed in Somnia 1.82.0):

  • The chat bubble moved for people who had asked for no movement. The rule that stops its bounce and pulse had been outranked since the choice of movement was added. Nothing moves now with reduced motion.
  • A button was disabled while its form sent, where the Button page said it should be busy. A disabled button can drop the keyboard's focus. It is now marked busy and keeps it.
  • Signing up to the newsletter lost your place. The field and button are taken away, and focus went with them. It goes to the thank-you line.
  • Copying a link twice was announced once. The share bar's announcement stayed in place. It is emptied with the words.

The fourth, on the header and the breadcrumb, found seven more (fixed in Somnia 1.83.0):

  • Escape in the settings menu lost your place. The menu closed and focus fell to the top of the page. It goes back to the button.
  • The settings menu ignored the arrow keys, which a menu promises. Down, Up, Home and End now move through it, and it takes the focus when it opens.
  • Tabbing past the settings menu left it open over the page. It closes.
  • The main menu had no name. A screen reader's list of landmarks said "navigation" for it and for a breadcrumb alike. It is "Main".
  • A breadcrumb's slashes were read out. Its page said they weren't. They are silent now.
  • The phone menu button still animated with reduced motion. Its lines become a cross at once.
  • The search box pulled the keyboard back. Tab on from it before it had loaded, and a moment later focus jumped back to it. It takes the focus only if you are still there.

The fifth, on six Content components, found two more (fixed in Somnia 1.84.0):

  • "Copied" was shown and told to nobody. A code block's button changed its word, which a screen reader doesn't read out. Copying is now announced.
  • Every code sample was a stop for the keyboard, with no name or role, whether or not it scrolled. Only code that scrolls sideways is a stop now, and it has a name.

The sixth, on the last five Content components, found two more (fixed in Somnia 1.85.0):

  • "Show all reviews" left the keyboard behind. The rest came in above the button, and focus stayed on the button, past them. It goes to the first review shown.
  • An arrow was read out as part of a link's name on the checklist offer. It is decoration now.

The seventh, on four Messages and status components, found one more (fixed in Somnia 1.86.0):

  • Closing a toast from the keyboard lost your place. Focus fell to the top of the page. It goes to the next toast, or back to where you were.

The eighth, on the last four Messages and status components, found five more (fixed in Somnia 1.87.0):

  • The cookie banner came last in the page. It is drawn at the foot of the window, and the keyboard reached it after everything else. It now comes straight after the skip link.
  • Answering the cookie banner lost your place, and asking for it again from Cookie settings said nothing to a screen reader. It takes the focus when asked for and gives it back after a choice.
  • The Suggest button was disabled while Claude worked, which can drop the keyboard's focus. It is marked busy and keeps it.
  • The Status indicator's page told people to write a class that existed nowhere but in these docs. It is a real class now, for every site.
  • The Cookie banner's page said this site shows no banner. It has shown one since 4 November. The page is corrected, and its checks run on this site's own banner.

The ninth, on the five Media and dialogs components, found eight more (fixed in Somnia 1.88.0):

  • The About page's video looped for ever with no way to stop it. Anything that moves by itself for more than five seconds needs a pause (WCAG 2.2.2, level A). It has a pause button now, the same one as Headland's hero.
  • Three buttons said two things at once. The carousel's play button, Headland's pause button and both viewers' full-screen buttons changed their name and their pressed state together: "Play background video, pressed". Each now does one or the other.
  • The carousel's dots were tabs named "1 of 9". Nine stops for the keyboard that promised arrow keys and had none, and said nothing of where each led. They are buttons named for their case studies.
  • A carousel slide slid across with reduced motion on. It changes at once.
  • Both viewers' strips of small pictures had a name and no role, so the name was told to nobody. Each is a group.
  • Headland's white heading couldn't be read where its video is pale. Words over a picture now carry a dark edge round each letter.
  • The Modal page's example was a drawing of a dialog. There is a real one now, .sn-dialog, and its checks run on it.
  • The video player has no captions. Not fixed: written down on its page. The clips in use have no speech.

One check also came back wrong before it came back right: it said the sticky header covered links as the keyboard reached them. It was measuring while the page was still scrolling. Measured once the page had stopped, nothing was covered, and nothing was changed.

Running them

From the repository: npm run build -w sites/mediadreams, then npm run proof -w sites/mediadreams. It writes src/data/somnia-proof.json, which these pages read, and stops with an error if anything fails. Each component's keyboard checks are in scripts/somnia-proof.mjs; the words on its page are in src/data/somnia-components.js. Run it before each release: the date above is when a run last found something different.

What comes next

  • A first pass with VoiceOver and NVDA, component by component, recorded here.
  • The four older pattern pages brought to the same standard.
  • Captions in the video player.
  • Forced colours and 400% zoom, by a person.