Skip to main content

Accessibility

Accessibility statement

We want everyone — including people who use assistive technologies — to be able to read our content, enter the awards and verify a result. This statement describes where we are and how to reach us if something gets in your way.

Our commitment

JIMSO is building toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is the target we design, build and test against across the site.

Measures we have taken

Accessibility is part of how the site is built, not a check bolted on at the end. In practice that means:

Semantic structure
Pages use real landmarks — a skip link, a single main region, header and footer — and a correct heading order, so assistive technology can navigate the structure.
Keyboard support
Interactive elements are reachable and operable with the keyboard alone, in a logical order, with no keyboard traps.
Visible focus
Every focusable element shows a clear focus indicator, so keyboard users always know where they are.
Reduced motion
Motion is minimal by design and honours the operating-system reduced-motion preference; nothing essential depends on animation.
Colour-independent meaning
Status and category signals always pair colour with a text label and, where used, an icon — meaning is never carried by colour alone.
Theme and zoom
Light and dark themes are both supported, and pages reflow without loss of content at 320px width and at 200% zoom.

Where we are

This work is ongoing. We test against WCAG 2.2 AA and address issues as we find them. Because that testing is not yet complete, we do not claim full or perfect conformance — we would rather tell you honestly where we are than overstate it. If you find a barrier we have missed, we want to hear about it.

Reporting a problem

If you encounter an accessibility barrier anywhere on the site, please tell us. It helps to describe the page you were on, what you were trying to do, and the assistive technology or browser you were using, if any.

Contact us to report an accessibility problem. We review accessibility feedback as part of our regular development cycle, respond to reports, and update this statement as our testing progresses.