can everyone use it?
Our accessibility statement: what we’ve done so Gwecode works with a keyboard, a screen reader and your own settings, and what we know isn’t right yet.
Last checked 8 November 2026
what we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
We haven’t had an independent audit yet, so this page comes from our own checks. We’ll update it when that changes.
what works.
- A “skip to content” link is the first thing the Tab key reaches.
- Every link and button shows a clear ring when you reach it with a keyboard.
- Moving parts stop when your device asks for reduced motion.
- Text grows with your browser’s text size and zoom.
- A dark and a light theme, switched with the face in the header.
- The video in the HTML lessons has captions.
- Errors from your code come with a plain-English explanation.
- In the code editor, Ctrl + Enter runs your code, and Esc then Tab moves you out of it.
not right yet.
- The site starts in dark mode and doesn’t follow your device’s light or dark setting. The face switch in the header changes it, and the site remembers.
- We haven’t yet tested every page with a screen reader.
- Language engines need a recent browser that runs WebAssembly, so code won’t run in older browsers.
something in your way?
Tell us which page it was and what happened. If a lesson doesn’t work with how you browse, say so and we’ll look for a way round it.
help@gwecode.com