Accessibility Statement
Commitment statement
We aim to meet widely recognized accessibility guidance and to continuously improve. We build with semantic HTML, real buttons, visible focus styles, sufficient colour contrast, and announcements for game results so assistive technology users can follow along.
Keyboard support
- A "Skip to main content" link appears when you start tabbing.
- All controls are reachable and operable with the keyboard.
- Solitaire cards, foundations, and the stock are real buttons and controls; you can select and place cards with Enter or Space.
- Chess squares are buttons — tab to a piece, press Enter to select it, then move to a highlighted square and press Enter again.
- Fifteen can be played entirely with the arrow keys once the puzzle grid is focused, in addition to tapping tiles.
- Reversi squares are buttons; your legal moves are highlighted, and you place a disc with Enter or Space.
Screen-reader considerations
Each game includes a polite live region so that results and status updates are announced without moving focus. Board squares and cards carry descriptive labels (for example, a chess square announces its coordinate and the piece on it). Form fields use associated labels and error messages that are announced when validation fails.
Visual design
We use warm, high-contrast colour — deep plum and brass against a light parchment background — with clear focus outlines and a reduced-motion mode that respects your system preference to minimize animation.
Known limitations
We know of three. The solitaire tableau gets dense on very small screens, so overlapping cards can be fiddly to hit. Chess squares are small on compact phones. And every board relies on tap-to-select rather than drag, which is deliberate for touch but takes a moment to learn. If you hit a barrier we have not listed, tell us and we will prioritise it.
Contact for accessibility issues
If you experience any difficulty using Brisk Sox, contact us at [email protected] or through our Contact page. Please describe the page, the device and browser you used, and what happened, so we can respond effectively.