
Visual and motor access
Use large tabular digits, more than color to mark the active side, strong contrast and generous controls separated from destructive actions. Support keyboard switching and avoid gestures that require precision. The board orientation control should rotate labels without changing logical player ownership.
Source for the factual guidance above: Web Content Accessibility Guidelines 2.2.
Assistive technology
Announce start, pause, side changes and flag fall through a polite live region without reading every animation tick. Buttons need stable names and state. A reduced-motion preference should remove decorative transitions while preserving instant feedback.
Respect the table
Some players benefit from sound or vibration; others find it distracting. Make feedback optional and agree accommodations before the game. In organized play, involve the organizer early so accessible equipment can be accepted and tested.
Test more than contrast
Evaluate the clock from both player positions and with the actual input methods people will use. Confirm that active state is communicated by text, shape, position, or sound as well as color. Check digit size, glare, low-time visibility, focus order, keyboard activation, touch-target separation, and whether pause can be found without risking reset. Zoom the browser and enable high contrast or reduced motion. Accessibility problems often appear where status changes quickly, not on a static settings screen.
Source for the factual guidance above: W3C Web Accessibility Initiative principles.
Announce events without creating noise
A screen reader does not need every tenth-of-a-second update. It needs meaningful state changes such as clock started, White active, paused, resumed, and time expired. Use stable control names and expose pressed, disabled, or selected states programmatically. A polite live region can announce ordinary transitions without moving focus; urgent expiry may justify stronger feedback if it remains understandable. Sound and vibration should be optional because the same cue that helps one player may distract another or conflict with event conditions.
Plan accommodations before the game
Ask what barrier the player encounters instead of assuming one universal accessible mode. Possible solutions include a larger display, keyboard switch, adjusted clock position, tactile markers, optional audio, an assistant permitted by the organizer, or a slower practice control. Test the complete setup with both players before timed play. In an event, involve the organizer early because equipment and assistance may require approval. Inclusive design succeeds when the timing information remains equally trustworthy, not when every player is forced to interact in exactly the same way.
For the controls available on this product, read the ChessClock.now accessibility statement.
Common questions
Is a high-contrast mode enough for accessibility?
No. Players may also need keyboard access, larger targets, non-color status cues, controlled motion, optional sound, screen-reader announcements, or a different physical position.
Should a screen reader announce every second?
Usually not. Continuous announcements create noise and can obstruct control use. Announce meaningful events and provide remaining time on request through a clearly named control or status.
Primary references & further reading
Rules and browser capabilities can change. These links are provided for the current governing or technical source.