Accessibility statement

What does not work yet

• Nobody has yet used the site with a screen reader, or tested it with people who rely on one. The checks are automated, and automated checks find only part of what a screen reader user meets.
• The map of the current wipe is a picture. Its name, size and seed are given in words beside it, but what is on it — monuments, roads, rivers — is not described in text.
• Two settings named in the design — dimming values that have gone out of date, and always showing the time zone — are not built, because the features they act on do not exist yet. Times on this site are UK time.
• Text to speech uses whatever voices your browser and operating system provide, so voice quality and languages vary. Some mobile browsers cannot pause and resume; on those, Pause stops reading. A screen reader, or your device’s own read-aloud feature, does the same job with the voices you already use.

This is what is known to be missing, not a guarantee that nothing else is. If you hit something that is not on this list, it is a gap we do not know about yet — please tell us.

Outside this statement

• Signing in happens on Steam’s website, paying on Tebex’s, and linking an account on Discord’s. How accessible those pages are is up to Valve, Tebex and Discord.
• The Rust game and the Scrap Racket screens inside it are not covered by this statement.

Tell us about a problem

If something on this website does not work for you, or you need what it says in another form, tell us. An accessibility problem is treated as a fault in the site, not as a special request.

Email: [email protected]

Or write to us through the support centre, which reaches the same people.

Using the keyboard

• Press Tab from the top of any page: the first stop is Skip to content, the second is Accessibility settings.
• The settings also open from the Accessibility settings button in the footer of every page.
• The arrow keys move between links, buttons and fields in the direction you press, like a TV remote, and Enter opens or presses the one you are on. Text fields, lists, the calendar and the map keep their own arrow keys. Where there is nothing that way, or a long text in between, the arrows scroll the page. In the navigation, the footer and rows of filters, Home and End jump to the first and last link.
• Inside the settings and the menu, Tab and Shift+Tab stay within the panel, Escape closes it, and focus returns to the control that opened it.
• A message such as “Copied” has a close button, and Escape closes it while the keyboard is on that button.
• There is no single-key or modifier shortcut. Screen readers, browsers and operating systems already claim most of them, and a clash would take a key away from someone who relies on it.

Two further settings named in the design — dimming of stale values, and always showing the timezone — are not built, because the features they act on do not exist yet. A control that changes nothing would be worse than its absence.

How this site is built

• Every state carries a word or a glyph, never colour alone.
• Keyboard operation end to end, with a focus ring that is never removed.
• Every control at least 24 by 24 pixels, and 44 by 44 on touch screens.
• No horizontal scrolling, tested at widths from 320 to 1440 on every page.
• No page depends on a viewport taller than 700 pixels.
• Automated accessibility checks run against every route on every build.

How this website was tested

• On every change, every page — signed in and signed out — is checked with axe-core against WCAG 2.2 levels A and AA, target size included, at widths from 320 to 1440 pixels.
• The same checks run with high contrast and 200% text, and with OpenDyslexic and wider text spacing. No page may scroll sideways at any width with any of them.
• Automated keyboard-only walks report a player, appeal a ban, and go through the store, the map vote and the account page with Tab, the arrow keys, Enter and Escape, checking for a visible focus ring at every stop.
• Tests also cover reduced motion, each typeface really loading, messages that stay until closed, and settings that survive a reload and follow a signed-in account.
• Not tested yet: use with a screen reader, voice control or switch access, and testing by disabled people.