Playable by as many people as possible — honestly, a work in progress.
What works with a keyboard, what a screen reader can and cannot do, and where the honest gaps are — per activity type.
Where accessibility stands today
Puzzel.org is built on regular web technology: real buttons, real text inputs and browser-native rendering wherever possible. There is no formal WCAG certification yet — an audit against WCAG 2.1 AA was done in September 2026 and this page follows it: it says plainly what works well and what doesn't, and the redesign you are looking at is part of closing the gap.
Keyboard support
Typing activities listen to the keyboard directly: on a crossword or wordle you simply type, and the letters land in the puzzle without hunting for the right cell with a mouse. Arrow keys move between cells, Tab and Shift+Tab walk the grid and leave it at either end, and Escape hands the keyboard back to the page. Every button answers to Enter and Space, a visible focus ring follows keyboard focus, and dialogs keep focus inside them until they close.
Screen readers
Honest answer: it depends on the activity. Question-and-answer activities are read out well, because their buttons and inputs are real HTML controls. Buttons, dialogs and form fields carry spoken names, and progress, completion, time-up and submitted states are announced as they happen — never a correct/incorrect verdict when the activity's owner has switched answer feedback off. Grid puzzles are drawn as visual cells, so a screen reader still cannot announce a grid the way a sighted player sees it — we would rather tell you that here than let a student discover it mid-lesson.
Vision, motion and sound
You style your own activities, so contrast and font choices are in your hands per activity. Timers and sounds are settings you control in the builder: the activity countdown is off unless you add it, while the quiz's per-question clock and the sound effects of the board game and the wheel start switched on. If a device asks for reduced motion, animations, card flips and confetti are turned off automatically.
Tell us what's in your way
Accessibility problems are treated as bugs, not feature requests. If something blocks you or a student, describe the activity type and the assistive technology involved — it goes straight onto the roadmap.