Transparency notice
Intentional violations
The Reverse Accessibility Lab is a simulation. Each room deliberately breaks criteria from WCAG 2.2 (the Web Content Accessibility Guidelines, the international standard for accessible websites) so that visitors can experience some of the barriers students with disabilities face in digital tools. Every issue below is intentional, limited to a single challenge room, and there to teach something. This page lists each one.
rooms/1/ to rooms/5/) are intentional and documented here. They are not bugs or regressions. The landing page, this page and the final code page are not part of the challenge and are designed to be fully accessible — if you find a problem on them, please let us know.
Room 1 — Keyboard only
⌨️ Keyboard navigationSimulates: Students who can’t use a mouse or trackpad — because of a physical disability, a tremor, repetitive strain injury or sight loss — and rely on the keyboard or a switch device.
-
2.1.1
Keyboard — pointer events disabled on all interactive elements
Nav links have
pointer-events: noneand the unlock button intercepts pointer and touch events via JavaScript, making every control mouse-unreachable. The lesson: everything works by keyboard — tab focus is intentionally enhanced with a strong visible glow. -
2.4.7
Focus Visible — no hover styles, mouse cursor signals failure
Hover states are deliberately absent and the cursor is set to
not-allowed. Focus-visible styles are amplified instead, inverting the usual pattern of hover-rich, focus-minimal interfaces.
Room 2 — Screen reader
🔊 Semantic structureSimulates: Blind and partially sighted students who use a screen reader to hear the page and its structure read aloud.
-
1.3.1
Info and Relationships — heading hierarchy inverted
The
<h1>is visually tiny and muted while a<p>is styled to look like the main heading (large, bold, high-contrast). Screen readers announce the correct DOM order; sighted users read the visual lie. -
4.1.2
Name, Role, Value — a
<div>pretending to be a buttonSix articles each have a "Read" control. Five are real
<button>elements; the sixth is a<div>with the same styling and no button role. It looks identical on screen, but a screen reader never announces it as a button and it is missing from the screen reader's list of buttons. -
2.1.1
Keyboard — the impostor control only responds to a mouse click
The
<div>can receive keyboard focus, but has no Enter or Space handler, so it can only be activated with a pointer. Keyboard and screen-reader users cannot open the article it belongs to. -
2.4.6
Headings and Labels — identical visible button labels
Every control reads "Read" visually. Each real button has a distinct
aria-labelnaming its article, so screen-reader users can tell them apart; sighted users see six identical labels.
Room 3 — Voice control
🎙️ Name, role, focus orderSimulates: Students with limited hand movement, chronic pain, fatigue or an injury who control their computer by voice.
-
2.4.3
Focus Order — tabindex values create a non-sequential tab sequence
Twelve controls are assigned explicit
tabindexvalues that jump the keyboard cursor across sections in an illogical order, making keyboard navigation disorienting. One control — the correct target — has a unique, descriptive label. -
2.5.3
Label in Name — buttons carry vague or duplicated visible labels
Labels include "Click here" (×3), "Submit" (×2), "More info" (×2), "Go", "Option", and "Next" (×2) — none actionable for voice control. The target button's accessible name matches a specific, unique spoken phrase.
-
1.3.1
Info and Relationships — mouse-blocking overlay hides controls from pointer
An
aria-hidden="true"overlay sits above each interactive button at a higher z-index, intercepting mouse events. The accessibility tree exposes the real button beneath; pointer users hit a dead layer.
Room 4 — Zoom & magnification
🔎 ReflowSimulates: Students with low vision who zoom in to 200% or more, or use screen magnification, to read.
-
1.4.10
Reflow — critical control hidden in a narrow third column
At 100% zoom a three-column grid keeps the "Acknowledge" button in a cramped annotations column with
overflow: hidden, clipping it from view. At 200% zoom the viewport narrows below the grid breakpoint, columns stack, and the button becomes fully visible and operable — reflow reveals what bad layout hid. (All text meets contrast minimums; the difficulty is size and clipping, not color.)
Room 5 — Reduced motion
🌀 Motion & vestibularSimulates: Students with vestibular disorders, migraines, ADHD, autism or a concussion, for whom movement on screen can cause dizziness, nausea or difficulty concentrating.
-
2.3.3
Animation from Interactions — continuous motion with no page-level off switch
Five keyframe animations run on page load: bounce, spin, drift, pulse-border, and flicker — including on the button container itself. There is no on-page toggle; motion stops only when the OS
prefers-reduced-motion: reducesetting is enabled. The lesson: the OS setting exists precisely for this, and enabling it unlocks the room.
Questions or corrections? Email hello@genio.co.