ACCESSIBILITY
Last updated 24 October 2026
We want everyone to be able to use Restaurant Versus, including people who use screen readers, keyboards, voice control or magnification. This page explains what we’ve done, what we’ve checked, and what we know still needs work.
OUR GOAL
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We haven’t had the site professionally audited, so we can’t yet say it fully meets that standard.
WHAT WE’VE DONE
Pages have a clear heading order: one main title, then section headings, so you can jump around by heading.
Text on the site is real text, so screen readers, browser read-aloud tools and text resizing all work with it.
The restaurant search box has a label for screen readers, and the decorative food pictures are hidden from screen readers so they don’t interrupt your reading.
We checked the main text colours against the WCAG AA contrast requirements.
HOW WE’VE TESTED
We ran basic automated checks on the published pages, covering headings, image descriptions and colour contrast. A friend with a disability has also tried the site and shared feedback with us.
This was informal testing, not a professional audit. It didn’t cover every page, device or assistive technology.
WHAT STILL NEEDS WORK
The scrolling banner on the home page and the floating food stickers move on their own, and there is no pause button yet. We’ve turned on our site builder’s setting that respects your device’s “reduce motion” preference, but we haven’t yet confirmed that it stops every animation.
Nominations and voting rounds close at a set time, shown by a countdown. Because each competition runs to a public deadline, we can’t extend that time for one person, but every round stays open for several days.
The voting and nomination tools are custom-built. We haven’t tested them with every screen reader and keyboard setup, so some parts may be harder to use than they should be.
The example bracket on the home page is a visual diagram. It isn’t fully described in text for screen reader users yet.
HAVING TROUBLE?
If something is hard to use, or you need this information in another format, email hello@restaurantversus.com and tell us the page and what went wrong. We’ll reply and do our best to fix it.
LISTENING TO THIS PAGE
This page is plain text with headings. You can have it read aloud by your screen reader or your browser’s read-aloud feature, and move between sections by heading.