Accessibility

Accessibility mode

The Enable accessibility button in the header — the figure-in-a-circle icon with its label, after the navigation on a wider screen and beside the menu button on a phone, where only the icon shows — turns on, all at once:

• links in running text are underlined, so a link is never told apart by colour alone;
• a strong two-colour focus outline that stays visible on the blue header, on the artwork and on white;
• header links that stay white when hovered or focused, instead of turning light blue;
• no animation: nothing slides or fades, and the What’s new band on the home page holds still;
• text that is normally faded for a quieter look — the slogan, page taglines, the footer — shown at full strength;
• footer links at least 24 pixels tall.

The choice is remembered in this browser and applies to every page on evomedia.net. If your system is set to ask for more contrast, the mode starts on. The same button, which then reads Disable accessibility, turns it off. The default look is the one every page was designed in; this is the alternative for when it gets in the way.

What every visitor gets

• A Skip to content link first in the tab order, a sticky header that never hides the element you have just moved to, and a visible focus marker on every control.
• Menus that open on a click or a key press, close on Escape and hand focus back to the button that opened them, and close when you tab past them.
• Code blocks, wide tables, formulas and charts that scroll sideways are reachable with the keyboard and scroll with the arrow keys.
• Pages that reflow to a 320-pixel-wide screen without sideways scrolling, and survive wider letter and line spacing.
• Nothing that moves on its own without a control to stop it: the home page’s What’s new band has a pause button, and holds still when your system asks for reduced motion.
• Captions on the walkthrough video, burned into the picture from the words that were spoken.
• Text and the edges of form fields that clear the WCAG AA contrast bars, form fields with visible labels and autofill hints, and status messages that are announced.
• Pages that pass the W3C HTML checker with no errors or warnings, so assistive technology gets the structure it expects.

How it is checked

On 2026-10-09 every page was run through axe-core’s WCAG 2.2 Level A and AA rules at desktop and phone widths, in the default look and with Accessibility mode on; through the W3C HTML checker; and through a reflow check at 320 pixels with WCAG’s text-spacing overrides applied. The keyboard paths, the pause control, the button and the heading structure of every page are pinned by the site’s own test suite, which runs on every change.

One thing the default look does not meet: the light-blue colour the header navigation turns when hovered or focused is below the 4.5:1 contrast bar for text. Accessibility mode keeps that text white.

Something in the way?

If a page does not work with your screen reader, your keyboard, your magnifier or your switch, tell me which page and what happened: get in touch. It is one person’s site, and the person reads every message.