Accessibility
Accessibility statement
We want people to be able to use the Portal and Slices. We have done some of that work and not all of it. This page says which is which.
What is in place
- The pages declare their language, and the Portal and its play pages offer a skip link to the main content.
- Interactive controls show a visible focus outline when you use the keyboard.
- Dialogs are labelled, and status messages are announced to screen readers through live regions.
- Motion is reduced when your device asks for reduced motion.
- Form fields in the sign-in and feedback forms have text labels, and star ratings expose their pressed state.
- Our build rules require keyboard controls as well as taps or clicks, and a pause key, in every game. We have not tested each game against those rules for accessibility.
Known gaps
- Small text. Some secondary labels in the play shell and feedback forms are set very small, in places 7 to 9 pixels, which is hard to read and does not meet accessible text size guidance. We plan to raise these.
- Colour contrast. We have not measured contrast ratios across the whole interface, so some grey-on-dark text may fall short of WCAG 2.1 AA.
- Screen readers. We have not completed a full test with a screen reader such as VoiceOver or NVDA on the Portal shell, the dialogs, the feedback forms or Slices.
- The games. The games draw to a canvas. They do not expose their content to screen readers, and many depend on sight and fast reactions. We do not currently offer an accessible alternative for them.
- Slices. Slices is built around swipe scrolling. We have not tested whether every action can be done from a keyboard alone.
- Dialog focus. We have not verified that keyboard focus returns to the right place after every dialog closes.
Tell us about a barrier
If something here is hard for you to use, email privacy@gamefoundry.ai with the page, the device and browser or assistive technology you use, and what went wrong. We read every message.