ModelLineup

Accessibility

The target is WCAG 2.2 AA. This page says what that means here, and what is not there yet.

Last updated .

What is in place

  • Everything works from the keyboard. Nothing depends on hover or on a pointer. Focus is always visible, with a two-pixel outline that meets the contrast requirement.
  • A skip link is the first thing in the tab order on every page.
  • Answer text wraps. Long lines never force a sideways scroll. Code blocks and tables scroll inside their own box, which you can reach and move with the keyboard.
  • Every result is stated in words. A pass or a miss is shown with the word and a symbol as well as colour, and a score is always a number.
  • Every chart has a table. The same figures are available as a table beside each chart.
  • Side-by-side answers stack below tablet width, so each answer keeps a comfortable line length on a phone.
  • Text meets 4.5:1 against its background, and large text and interface borders meet 3:1, including text over the glass panels.
  • Headings are in order, one h1 per page, and tables have real header cells.
  • Motion is respected. There is very little of it, and it stops when your system asks for reduced motion. Transparency effects are replaced by solid panels when your system asks for reduced transparency.
  • Zoom is not locked. The layout reflows to 320 pixels wide without a horizontal scrollbar.
  • The site works without JavaScript and stores nothing on your device.

What is not there yet

  • The site has been checked against the standards above and with keyboard navigation, but not yet tested by screen reader users in practice, which is a different thing and a better one.
  • Screenshots of web pages that a model built are images. Each has a description, and the code that made the page is available beside it as text.
  • No formal audit has been carried out by a third party, so this page describes what has been done rather than a certification.

If something does not work

Please write to hello@modellineup.com and say what you were using and what happened. An accessibility problem is a defect in ModelLineup and is treated as one.