rbxoffsets intends this site to be usable by everybody, and aims at WCAG 2.2 level AA. This statement describes what has actually been done, and — more usefully — where the site currently falls short. The second list is the honest one; a statement with nothing in it is a statement nobody checked.

How the site is built

• Every page is rendered by the server. Nothing on this site requires JavaScript to read. With scripting disabled entirely you lose the collapsible navigation on narrow screens, the search dropdown and the cookie notice; every page, every table and every download link continues to work, and search still works as a full page of results.
• Semantic HTML throughout. Real headings in order, real tables with real header cells, real links and real buttons — a link that navigates is an <a> and a control that acts is a <button>, never the other way round.
• Keyboard operable. Everything interactive can be reached and used with a keyboard alone, in an order that matches the visual one. Focus is always visible, and the focus ring is drawn explicitly rather than left to whatever the browser defaults to. The search field is reachable by Tab without needing a pointer to hover it open, and Escape closes its suggestions.
• Reduced motion is respected. The site’s only animations are short colour and size transitions. If your system asks for reduced motion, they are switched off entirely rather than merely shortened.
• Contrast. Body text, headings and the accent colour are all above the 4.5:1 ratio AA requires against the background they sit on. The muted grey used for secondary detail is above 4.5:1 as well; the faintest grey, used only for supporting detail that is never the sole carrier of meaning, is above 3:1.
• Colour is never the only signal. Where a state is shown in colour — a healthy loop, a failed one — the word says the same thing as the colour.
• Text scales. Sizes are in relative units and the layout reflows to 400% zoom without loss of content or horizontal scrolling. Wide content, such as the API tables, scrolls inside its own container rather than forcing the whole page sideways.
• Landmarks and labels. The navigation, the main content and the footer are marked up as landmarks; the current page is marked in the sidebar for assistive technology, not only by shading; every control has an accessible name.
• No traps. Nothing takes focus on load, nothing auto-plays, nothing obscures the page modally, and the cookie notice can be ignored indefinitely without blocking anything.

Where it currently falls short

• Some pages refresh themselves. The status pages reload on a timer so a left-open tab stays current. A refresh moves screen-reader focus back to the top of the document, which is disruptive mid-read. This is a known problem and a poor trade; it is on the list to replace with an update that does not reload the page.
• The expanding search control is pointer-first. It opens on hover, which is a pointer gesture. Keyboard and touch users get an equivalent route — focus opens it, and on narrow screens the field is simply always visible — but the hover behaviour is the primary design and the alternatives are accommodations rather than equals.
• Build identifiers are long and unreadable aloud. A hash like version-ddf602d9cfe44005 is announced character by character by a screen reader. Where a friendlier dotted version exists it is shown first and the hash second, but on pages where the hash is the identity there is no better option available.
• Dark only. The site has one colour scheme. There is no light theme and no high-contrast theme; browser and operating-system contrast settings still apply, but the site does not offer its own.
• The scrollbars are drawn faintly, and are invisible when nothing is moving. They are still present and still draggable — the track keeps its full width, so the thumb can be grabbed exactly where the operating system would have put it — and wheel, trackpad, keyboard and touch scrolling are unaffected. But a thumb you cannot see is a thumb that is harder to aim at, which matters most to precisely the people for whom dragging is already the difficult option. They fade in whenever the page is scrolling and whenever the pointer is over a scrollable region, and Windows high contrast mode overrides the styling entirely and restores the system scrollbar. It remains a deliberate trade of a small amount of usability for a quieter page, and it is the one item on this list chosen rather than merely tolerated.
• Third-party pages are outside our control. Downloads redirect to Cloudflare and the offsets we mirror originate elsewhere; the accessibility of anything served from another origin is not something this project can speak for.

Assessment

This site has been assessed by its maintainer against WCAG 2.2 AA, by review of the markup and by keyboard-only and zoom testing. It has not been audited by an independent third party, and it has not been tested with every combination of screen reader and browser. Treat the list above as a good-faith account rather than a certification.

Telling us about a problem

If something here is unusable for you, that is a defect and it will be treated as one. Write to the contact route published on this project’s public repository describing what you were trying to do, what happened, and what you were using — the page address and your browser and assistive technology are the three things that make a report actionable. Accessibility reports are prioritised above feature work.