Skip to content
72 Networks

Accessibility.

What this site does so that anyone can use it, what we know still falls short, and how to reach us when something gets in your way.

How the site is built

Every page can be used with a keyboard alone. A skip link is the first thing a keyboard reaches, the focus ring is always visible, and the tiles and rows that react to a mouse react the same way to keyboard focus.

Pages are structured with real headings, lists, tables and landmarks, so a screen reader can move through them by structure. Form fields have visible labels above them, errors are written next to the field they concern, and they are announced when they appear.

Text colours were chosen and checked to meet WCAG 2.2 level AA contrast against the backgrounds they sit on, including the small labels. Colour is never the only way something is said: the fee chart carries its figures beside it, and status is always written in words.

Motion

The site moves: headings rise into place, tiles tilt under a pointer, a chart draws itself. If your device is set to reduce motion, none of that happens. Every page is delivered finished and still, with nothing hidden behind an animation that did not run.

Nothing flashes, nothing plays sound, and nothing moves for more than a few seconds without your doing something to cause it, apart from one slow band of text on the homepage and the pulses on the About page's diagram. Both stop under reduced motion.

Text size and small screens

Text can be enlarged to 200% in the browser without anything being cut off, and every page works on a phone held upright, with no sideways scrolling.

What we know falls short

The decorative drawings at the top of each page are hidden from screen readers. They repeat something the text already says, and carry no information of their own.

This site has not yet had an independent accessibility audit. What is written here is what we built and checked ourselves.

Telling us about a problem

If something on this site does not work for you, write to gaurav@72networks.com and tell us the page and what happened. We reply within one working day, and we would rather hear about a barrier than not.