Accessibility conformance
Standard: WCAG 2.2 Level AA Scope: the participant view, the presenter view, and the creator console Status: self-assessment. No independent review has been carried out.
That last line comes first on purpose. A self-assessment presented as an audited conformance report would be read as assurance that someone qualified had checked, so there is no VPAT or EN 301 549 statement until an independent review has been done.
Enforced automatically
These run on every change and fail the build:
| Area | How it is enforced |
|---|---|
| Participant view, WCAG AA | Automated accessibility checks (axe) run over every question type, unanswered and answered. A new question type cannot ship without passing. |
| Keyboard and names | Every button and input must have an accessible name. The two pointer-based question types are answered start to finish with the keyboard alone in a test. |
| Not colour alone | Every results chart has a table alternative; a correct answer at the reveal is marked in text, not only in colour. |
| Reduced motion | The device's setting is honoured, and there is an independent setting on the join screen and in the session header. |
| Timed questions | The host can extend or remove a limit; a participant can ask for more time privately. |
| Right-to-left readiness | Layout uses logical directions throughout, checked automatically, so a right-to-left language can be added without a redesign. |
Automated checks catch roughly a third of WCAG issues. They cannot judge whether a focus order makes sense, whether a label is correct as well as present, or whether a colour pair that passes is readable on a projector in daylight.
Asking for more time, privately
WCAG asks for a way to extend time limits; Murmle also makes it private. A participant presses I need more time; the server counts it; the host sees "3 people have asked for more time" - never a list or a name. No record of who asked is kept anywhere, so the request cannot become a stored record correlated with disability.
Known exceptions
- Video captions and audio transcripts are supported but not compulsory. A creator may publish a video slide, or a question with a video or audio clip, without captions or a transcript; the editor warns when both are missing. A description of every image and video is compulsory, and nothing autoplays.
- Third-party video players. YouTube and Vimeo videos play in those providers' players, whose accessibility Murmle cannot control.
- The creator console and presenter controls are in English only. The participant view is available in four languages.
- Spatial questions are coarse by keyboard. Pin on an image and draw an answer can be answered with a keyboard, but more slowly and less precisely than by touch, and keyboard drawing makes straight lines rather than curves.
Not yet done
| Area | Gap |
|---|---|
| Independent review | None carried out, so no VPAT or EN 301 549 statement. This page is the interim self-assessment. |
| Screen readers | Testing with NVDA, JAWS or VoiceOver across the whole join-and-answer journey has not been carried out. Automated checks do not substitute for it. |
| Presenter view | Covered by shared component tests, but without its own automated accessibility suite. |
| Contrast | Not yet checked automatically across both colour themes. |
| Reflow and text size | 320-pixel reflow and 200% text are handled by the phone-first layout but not asserted by a test. |
Reporting a problem
An accessibility problem is treated as a defect, not an enhancement. Report it to the organisation that runs your Murmle deployment.