Accessibility

What we aim for

WCAG 2.2 Level AA. That is a target we design and test against, not a certification. No external audit has been carried out and SamePage does not claim to be certified by anyone.

What is built in

• The whole product works from the keyboard. Creating, joining, spending hype, taking it back, committing, and reading the result. Dragging a hype chip is an optional shortcut — every option has a plain button to add and to remove, and nothing requires a pointer.
• Focus is always visible, including on top of bright accent-filled buttons, where a single-colour ring would disappear.
• Nothing is communicated by colour alone. The winner is labelled, ranks are written out (“1st”, “2nd”), committed players are marked in text, and a tie is named as a tie.
• Text contrast is checked numerically against the background and against panels. Glow is never counted as contrast.
• Screen readers get the state, not the show. How much hype you have left, how much is on each option, whether you can commit, who has joined, how many have committed, and the final result — announced once, when it is actually known. The reveal's theatrics are never narrated.
• Reduced motion is honoured. With prefers-reduced-motion set, animation is dropped and the product lands in exactly the same readable state.
• Nothing important depends on an animation finishing. If motion never starts, every screen still shows its content.
• Touch targets for the main controls are at least 44 by 44 pixels.

Known gaps

• SamePage has not been tested with a real screen reader by a person who uses one daily. Its structure has been audited, which is not the same thing.
• Dragging a hype chip has not been verified with assistive input devices. The button-based route is the supported one.
• The reveal is a timed sequence. It cannot currently be paused, and there is no control to skip straight to the result other than reloading the page once it has finished.
• No formal audit against every WCAG 2.2 AA success criterion has been completed.

Telling us about a problem

If something is unusable for you, we want to know — it is treated as a defect, not a request. Include the page, what you were trying to do, and the assistive technology and browser you were using.

ACCESSIBILITY CONTACT EMAIL REQUIRED

RESPONSE TIME COMMITMENT DECISION REQUIRED — some jurisdictions expect a stated turnaround for accessibility reports.