Our goal

We want every guide on Services Accessible to be usable by as many people as possible, including people using a screen reader, a keyboard alone, voice input, or a browser zoomed in well past 100%. We work toward conformance with WCAG 2.2 Level AA as our target. We are not certified and we do not claim full conformance — this page describes what we have actually built and where we still fall short.

What's implemented today

  • Structure. Every page has exactly one h1 and a logical heading order underneath it, so screen reader users can jump between sections instead of reading top to bottom.
  • Skip link. A "skip to content" link is the first stop on every page, letting keyboard users bypass the header and navigation.
  • Keyboard operation. The navigation menu and on-site search are fully operable from a keyboard. Search is built as an ARIA combobox, so you can move through suggestions with the arrow keys the same way a screen reader expects.
  • Visible focus. Every interactive element — links, buttons, form fields, the search combobox — shows a visible focus outline when reached by keyboard, so you can always tell where you are on the page.
  • Images. Every photograph and illustration carries descriptive alt text, and every image ships with its width and height set so the page layout doesn't shift as images load.
  • No autoplaying media. Nothing on the site plays audio or video automatically.
  • Typography and color. We use system fonts, not web fonts, so text renders immediately and respects the reading settings your device already has. Text and background colors are chosen for readable contrast.
  • Responsive layout. Pages reflow down to small phone screens without losing content or requiring horizontal scrolling.
  • Voice search. Where your browser supports it, on-site search offers voice input as an optional extra way to search — typing and the keyboard-operable combobox always work as the primary method.

Known limitations

Some in-article diagrams are original SVG illustrations that convey dense information — a process sequence or a comparison, for example. We support each one with surrounding body text and a caption that state the same information in words, but we know a diagram alone is not always as clear to a screen reader as it is visually. If a specific diagram isn't working for you, tell us and we'll fix it or add more descriptive text.

Some pages link out to third-party sites — government agencies, standards bodies, published research — for verification. Those sites are outside our control and may not meet the same standard we hold ourselves to.

Reporting a barrier

If you hit something on this site that doesn't work with your screen reader, keyboard, voice software, or any other assistive technology, we want to know. Email editor@servicesaccessible.com with the page URL and what happened. We aim to respond within five business days. You can also reach us through the general contact page.

If the format of a specific page is the barrier — for example you need the content of a guide read out in a different structure — tell us which page and what format would help, and we'll provide it directly.

Tell us what breaks

This statement describes what we've built and tested, not a guarantee that every page is perfect for every assistive technology. If you use a screen reader, switch device, voice control, or any other assistive technology and something on Services Accessible doesn't work the way it should, we would genuinely like to hear about it. Reports from real assistive-technology use are the fastest way we find and fix problems that automated checks miss.