This is a build-stage statement, not a claim of full conformance. A formal audit and issue log are required before the production beta.
What the interface supports
- Keyboard access to navigation, filters, forms and actions.
- Visible focus styles that do not rely on colour alone.
- Semantic headings, landmarks, labels and status announcements.
- Text resizing and reflow through 200% zoom.
- Responsive layouts from narrow mobile screens upward.
- Reduced motion when the operating system requests it.
- Minimum 44px touch targets for routine controls.
Plain, consistent language
Actions use the same wording before and after they happen. Verification, profile ownership and governing-body accreditation are labelled separately so a badge never has to carry an unclear meaning.
Images and player cards
Decorative graphics are hidden from assistive technology. Functional card descriptions communicate the football information needed for the task without unnecessarily describing a child’s appearance.
Testing before beta
The acceptance pass includes keyboard-only use, common desktop and mobile screen readers, 320px layouts, 200% zoom, high-contrast conditions and reduced motion.
Report an accessibility problem
An accessible feedback route and response target will be published before beta applications open. If a barrier also creates a safeguarding concern, use the safeguarding routes.