Accessibility Statement
Last updated
PyLearn should be usable with a keyboard, with a screen reader, at whatever text size you need. Here is where that is true, and where it is not yet.
What we aim for
Web Content Accessibility Guidelines 2.2, Level AA. We are not claiming full conformance — a claim like that made without an audit is worth nothing — but it is the standard the site is built and reviewed against.
What is in place
- A skip-to-content link on every page, and headings in a real order rather than chosen for their size.
- Keyboard access throughout: every control is reachable and operable without a mouse, and focus is visible where it lands.
- A text-size control in the header with four steps. It scales from your browser’s own default rather than overriding it, so raising the default in Chrome or Safari still counts.
- Light and dark themes that follow your system setting, with contrast checked against the AA thresholds in both.
- Semantic HTML and ARIA where semantics run out: labelled form fields, described errors, and status messages announced rather than only shown.
- Layouts that reflow to 320 pixels and survive 200% zoom without losing content.
What still falls short
Known, and listed here rather than discovered by you:
- The code editor. It is CodeMirror, an editable region rather than a plain text box, and screen reader support for it varies by reader and browser. If it fights you, tell us — for some lessons we can offer a simpler input, and we would rather know than assume.
- Resizable panels. The lesson layout has draggable dividers. They have keyboard equivalents, but the drag itself is a mouse gesture and the layout is dense on small screens.
- Reduced motion. The site’s animation is limited to small fades and slides, but we do not yet turn them off for people who ask their system for reduced motion. That is a gap, and it is on the list.
- Certificates. The generated PDF is not yet tagged for screen readers. The same information is on your certificates page as ordinary HTML.
Telling us
If something here blocks you, write to support@pylearnapp.com and say what you were trying to do, what happened, and what you use — the browser, and the screen reader or other assistive technology if any. We reply within two business days and treat an access barrier as a bug rather than a feature request.
If we cannot fix something quickly, we will tell you what we can do meanwhile rather than going quiet.