GameSpark StudioACCESSIBILITY
Menu

LAST REVIEWED 3 SEPTEMBER 2026

More people
in the game.

GameSpark aims to make creating, hosting and playing party games clear across desktop, tablet and mobile. This page records current support and known limitations rather than claiming formal conformance.

01

What is already supported

  • A skip link, semantic headings, labels and landmark regions across the launch journey.
  • Keyboard-operable links, forms, checklists and native disclosure controls with a consistent visible focus indicator.
  • Responsive layouts for desktop, tablet and mobile screens, including browser zoom.
  • High-contrast core colours, increased-contrast support and large primary controls.
  • Text alternatives or accessible labels for decorative and interactive elements.
  • Reduced-motion support and reduced reliance on colour alone for status and scoring information.
02

Known limitations

  • Some advanced host dashboards are densest on small screens and work best on a larger display.
  • Not every live score or timer change has yet been independently verified with every screen reader.
  • Full-screen audience experiences may depend on browser and device controls.
  • Generated game wording still needs a human host to review reading level, clarity, sensitivity and audience suitability.
  • PDF or printed exports may need separate checking for a particular audience.
03

Make an event easier to join

Use plain first names or nicknames, read instructions aloud, allow extra answer time, offer a non-phone way to participate, avoid relying on audio alone and give guests permission to skip any prompt. Test the actual venue screen, sound and network before the event.

04

Feedback, alternative formats and adjustments

If a GameSpark screen prevents someone from taking part, email support@gamesparkstudio.co.uk and describe the device, browser, page and task. Ask there for information in an alternative format or another reasonable way to use the service. Do not include passwords, recovery codes or unnecessary personal information.

05

Recorded browser evidence

  • The homepage, maker, pricing, app and Arcade routes have been exercised at desktop and representative mobile widths.
  • A horizontal-overflow defect was identified on guest joining; the current layout constrains the card, fields, header and footer to the viewport.
  • The installable app exposes its web-app manifest and dismissible install guidance.
  • The skip link and core controls expose visible keyboard focus.
06

Continuing checks

Code-level controls cover keyboard focus, skip navigation, reduced motion, increased contrast and forced-colour modes. We continue to check 200% browser zoom, common screen-reader flows, representative phones and tablets, and large host displays. Confirmed issues are prioritised as part of ongoing improvement.