Built for everyone.
A living summary of how Glaze Games supports keyboard, screen-reader, and reduced-motion users — plus a way to tell us what is still missing.
- WCAG 2.2Level AA target
- 45Languages
- RTLArabic · Hebrew · Persian
- 4.5:1Min contrast ratio
Shipped and tested
The features below are live across the site we control. Game iframes are owned by their developers — accessibility there varies.
- Keyboard navigationEvery interactive element is reachable via Tab, Enter, and Space. Search, language modal, and result grids all support arrow-key navigation.
- Visible focusA high-contrast pink ring appears on every focusable element so keyboard users always know where they are.
- Screen readersARIA labels on icon-only buttons, role="dialog" / role="listbox" on modals, and aria-live announcements for action feedback.
- Color contrastWhite body text on the pink page background hits 4.5:1+. Dark navy on white cards exceeds 12:1.
- Reduced motionprefers-reduced-motion is respected — animations drop to ~0ms and hover lifts disable for users who opt out.
- Localisation45 languages with automatic LTR/RTL layout swap for Arabic, Hebrew, and Persian, including category names.
- Zoom & reflowThe layout reflows down to 320px wide and up to 200% browser zoom without horizontal scroll.
- No flashing contentNo content flashes more than three times per second — protecting users with photosensitive epilepsy.
What we are working on next
Public roadmap. Each item is scoped and assigned. Email if you want to weigh in on priorities.
High-contrast theme
A toggle for users who need stronger separation than the default brand palette provides.
Game caption guidance
A standard for embedded games to expose captions and audio descriptions to assistive tech.
Live screen-reader audit
A quarterly NVDA + VoiceOver pass against the top 50 game pages and every aux page.
We treat accessibility issues as P1 bugs
Email us with the page URL and a sentence about what didn’t work. We respond within one business day, every day.
Standards we follow
We aim for WCAG 2.2 Level AA across navigation, search, account, and content pages we control. We pair automated checks (axe-core in CI) with manual passes on Tab + screen-reader flows for every release.
Accountability
Accessibility is owned by the founder, not deferred to a backlog. Tickets tagged a11y are P1 by policy and ship in the next release. If something on this page is out of date, tell us and we’ll correct it the same day.