Accessibility

Our aim

We aim to meet WCAG 2.2 Level AA. We are not claiming to have been formally audited against it — we have not — so this page describes what is actually true rather than asserting compliance.

What works today

• Keyboard navigation. Every interactive control is reachable and operable by keyboard, with a visible focus ring that we styled deliberately rather than removing.
• Reduced motion. If your system asks for reduced motion, animations and hover transitions are switched off. Nothing in the layout depends on movement, so no information is lost.
• Light and dark themes. The store defaults to dark, and there is a visible toggle in the header. Dark is a design choice, not something imposed on you.
• High contrast mode. Under Windows forced-colours mode the decorative gradient, glass and grid layers are removed so text keeps system contrast.
• Labelled forms. Every input has a real associated label, and errors are announced to screen readers rather than only shown in colour.
• Ratings are not colour-only. Star ratings carry a text alternative with the numeric rating and count.
• Text scaling. Layout uses relative units, so browser zoom and larger default font sizes work without clipping.
• Semantic structure. Headings, lists and landmarks are used for meaning, not just appearance, so screen-reader navigation works.

What is not good enough yet

Being honest about the gaps is more useful to you than a compliance badge:

• Screenshots have generic alternative text. We label them "screenshot" because only the developer knows what they show. We intend to let developers supply real descriptions.
• Horizontal app rails on the home page are keyboard-scrollable but have no explicit previous/next controls, which makes them awkward with a screen reader.
• No formal audit or assistive-technology testing has been carried out. We have tested with keyboard and browser tooling, which is not the same as testing with real users of screen readers.
• The Android app has not been assessed for TalkBack support yet.

Apps published here

We do not control the accessibility of apps in the catalogue — those are built by third-party developers. We encourage developers to support TalkBack, large text and sufficient contrast, but we cannot verify it.

One thing we do watch: apps requesting Android's accessibility service permission. It is a legitimate permission for genuine accessibility tools and also the single most abused permission on Android, so every app requesting it is flagged for closer review.

Tell us when we get it wrong

If something on this site is difficult or impossible to use, please email support@playbix.store with what you were trying to do, the page, and the assistive technology or settings you use. Reports about accessibility are treated as bugs, not as feature requests.

We aim to acknowledge within 5 business days and to tell you what we intend to do.