Accessibility statement

Review access to both the website and the course activities before deciding whether the material meets your learners’ needs.

For the activity limitations, read “Access to the course activities” below.

This website is built to WCAG 2.2 AA. What we tested, how, and what it found — including the parts we have not tested — is set out in the accessibility statement.

This is a design and testing target. It is not a certified conformance claim.

• Text and background contrast in light and dark modes, including links and buttons on hover and keyboard focus.
• Keyboard access to the skip link, menus and galleries, visible focus and focus returning when a control closes.
• Target sizes against the accessibility standard’s minimum, with its exception for links within sentences.
• Reflow on narrow screens and at enlarged zoom, without horizontal scrolling of ordinary content.
• Heading order, landmarks, page titles, form labels, error messages and status announcements.
• Image descriptions that name the activity shown.
• Layout stability as the page loads.
• No animation starting by itself, carousels, autoplay or timers.

Assistive technology. The website has not been tested with a person who relies on a screen reader. Automated checks and keyboard testing do not establish that experience.

The support chat. The checks above have not been run against the chat button or the chat panel. What the chat service says about them is set out below, under “The support chat”.

Independent audit. None has been commissioned.

We do not claim conformance. If an audit is completed, we will publish its date, scope and findings, including failures.

• The course catalogue is long. Its filters work by keyboard, but reaching an activity can require many tab stops. Use the search field to narrow the results.
• Where charts are used, their values are also given in a table for readers who cannot use the visual presentation.
• Dark mode follows your system setting. There is no switch within the page.

The activities are visual and audio-led and were built for a pointer or a finger. They have not been assessed against an accessibility standard. If you have learners who need keyboard-only or screen-reader access, raise it on the first call.

An audit would not change the activities’ interaction model or make them accessible.

This material will not serve learners who need keyboard-only or screen-reader access to the activities themselves.

A chat button sits in the corner of every page, and the panel it opens is a frame served by the chat service. There is no microphone button in it: the chat takes typed text only. Speech input would change what the panel stores and what it sends, so it would be described here and on the cookie policy before it was turned on.

The rest of this section is what the chat service says about the panel. Our own testing has not reached inside it, so treat these as its statements rather than our findings.

• The launcher is a proper button, operable by keyboard, with a spoken label in the language of the page.
• The panel is a frame titled with the product name.
• The conversation is announced as it grows, so a new reply is read out without the reader losing their place.
• Everything in the panel can be reached and used by keyboard.
• Movement in the panel is reduced when your system asks for that.
• The reply comes back in the language you wrote in, and a line mixing left-to-right and right-to-left text is laid out by the direction of its own words.
• The chat button sits at the bottom right of the page, and at the bottom left on the Arabic, Persian, Hebrew and Urdu pages.

If any of that does not hold when you use it, write to hello@speakenglish.courses and we will say so here.

Write to hello@speakenglish.courses. Tell us what you were trying to do and where you were stopped. We will tell you whether we can fix it and when, and add it to the known limitations.