Accessibility statement

How accessible this site is

I aim to meet WCAG 2.2 Level AA on every public page of easeweb.dev, in English and Japanese. The site doesn’t fully meet it yet: the issues under “What doesn’t work yet” don’t.

What works

• A “Skip to content” link is the first thing on every page, for moving past the menu with the keyboard.
• Every link, button and field shows a focus ring when you reach it with the keyboard.
• Every page is in English and Japanese. The language switch is at the bottom of each page, and each page declares its language, so screen readers read it in the right voice.
• When your device is set to reduce motion, the site’s animations and transitions are turned off.

What doesn’t work yet

• The request form (Get started) is 25 pixels wider than a 320-pixel screen, about the width of a laptop at 400% zoom, so it scrolls sideways there. You can email the same details to [email protected] instead.
• On the home page, in a contrast theme such as the Windows contrast themes, the “Try it on this page” buttons don’t show which one is chosen. They change only that demo.

Demos in the Learn guides

Each Learn guide has a “Try it” demo that opens on a broken version of a web component, built to be inaccessible on purpose so that you can meet the problem the guide teaches. It is marked “Broken”, and a note under it says the broken version is intentionally inaccessible. “Apply fix” switches to the repaired version, and the guide’s text and code describe both.

Parts made by others

The request form uses Cloudflare Turnstile to stop spam. It usually runs without asking you anything. If it asks you to prove you are human and you can’t, email your request to [email protected] instead.

The client space, where clients sign in to read their reports, is in English only and wasn’t part of the check below.

Tell me about a problem

If anything here is hard to use with your setup, email [email protected] with the page and what happened. I read and answer every email myself, and aim to reply within two working days. If you need something from the site in another format, ask in the same email.

How this was checked

On 13 October 2026, I ran EaseWeb’s own automated audit on 11 public pages in English and Japanese: axe-core, ANDI, and EaseWeb’s checks for keyboard focus, contrast, reflow and contrast themes. I then checked each issue it found by hand in a browser, and set aside the ones that turned out not to be problems. This is a self-assessment, and it doesn’t yet include testing with screen readers.