Accessibility statement

This statement covers whylearn.ai. The site is built to meet WCAG 2.2 level AA. What has been tested, and what has not, is set out below.

What has been done

Every page is delivered as complete HTML and needs no JavaScript to be read, navigated or understood. One small script does two things, and neither of them creates content or is the only route to anything. It runs an entrance animation on a diagram that is already drawn in the markup, and on the longer pages it marks which section you are reading in the list of links at the top. Turn JavaScript off and you lose the animation and the marking, and keep every link and every word. The site navigation and that list are plain links in the page at every screen size, so neither needs a script and there is nothing to open.

• Body and interface text meets at least 4.5:1 against its background, and large display text at least 3:1. Boundaries that are not text, such as form borders and button outlines, meet 3:1. Contrast was checked against every background the site uses, including the tinted and dark bands, and not only against white.
• The brand colours are used as graphics only. Where they would carry text they are replaced by darkened variants that meet the contrast requirement, because the logo greens and teals do not.
• Colour is never the only way information is conveyed. In the diagram each strand is labelled in words as well as coloured, and the full content of the diagram is repeated in the caption beneath it.
• Every interactive element is reachable and operable by keyboard, with a visible focus indicator. There are no keyboard traps.
• Interactive targets are at least 24 by 24 CSS pixels, which is what level AA asks for. The navigation links are 44 pixels tall with at least 10 pixels of clear space between them. They are as wide as their labels, so they clear the AA minimum without reaching the stricter AAA target size.
• A skip link is the first focusable element on every page.
• Headings are nested in order and describe the structure rather than being chosen for their size.
• Where the site presents form fields, they have persistent visible labels, and the reason for each is given in text and not hidden in a placeholder.
• Text reflows down to a 320 pixel viewport and the page itself never scrolls sideways at any width. Three things scroll horizontally inside their own bounds: the diagram between roughly 620 and 660 pixels wide, the navigation row below about 440 pixels, and on the longer pages the strip of section links. All three are reachable by keyboard, and none of them hides anything that is not also reachable by scrolling the page. The navigation row is the one we are least happy with: on a small phone the last link can sit off the edge until you push the row sideways. It is listed again in the footer of every page.
• On short viewports the sticky header releases and scrolls away with the page, so it cannot cover content or a focused element.
• The diagram on the home page draws itself in once, over about a second and a half. Buttons and section links change colour over 150 milliseconds. On the longer pages, the strip of section links scrolls itself sideways to keep the current section visible as you read. If your system is set to reduce motion, none of these run: the first two are stopped in the stylesheet and the third in script, which also watches for the setting being changed while the page is open. The diagram is complete and readable in the markup before any script runs.
• On the longer pages a list of links to that page's own sections sits under the header. It is a list of links, so it works from the keyboard in reading order and does not trap focus, and the section you jump to always comes to rest below both bars rather than behind them.
• No cookie banner, interstitial or overlay ever appears in front of the content.

Known limitations

The diagram on the home page is wide. On a tablet it scrolls horizontally inside its own container, which is reachable by keyboard, and the surrounding page never scrolls sideways. On a phone the diagram is not shown at all: at that width it would be cropped and its labels illegible, so the caption beneath it, which states the same content in words, is shown on its own. The cut-off is a width rather than a device: below 620 pixels the diagram is replaced by its caption, which covers every phone held upright and some held sideways.

What has not been tested

The site has not been independently audited, and it has not been tested with disabled users. We test it ourselves against WCAG 2.2 level AA, using automated tooling together with manual keyboard and screen-reader checks, and anything we know about is listed under known limitations above. We are not going to claim we have found everything, because nobody who only tests their own work has. We would rather say that than imply an assurance we have not paid for.

Reporting a barrier

If something here does not work for you, please tell us. Email contact@whylearn.ai with the page and what went wrong. We acknowledge within two working days, which is the commitment we make on the contact page, and come back within five with what we will do about it and by when. If you need anything on this site in a different format, ask and we will provide it.

If you are not satisfied with how we respond you can contact the Equality Advisory and Support Service at equalityadvisoryservice.com.