Accessibility Statement

We want H5 Games Hub to be usable by as many people as possible. This statement describes what we have done to make the site's own interface accessible, where the hard limits are, and how to reach us if something is not working for you.

Our target standard

We aim for the site's own pages and interface — everything outside the embedded game frames — to meet WCAG 2.1 Level AA as a working target. This is a target, not a certified conformance claim. We have not commissioned a formal external audit. We work toward this standard in our day-to-day development and we address accessibility issues when they are reported.

What we do on the site's own interface

Semantic HTML structure: Page content is marked up with appropriate heading levels, landmark regions, lists, and other semantic elements so that screen readers and assistive technologies can interpret the page structure correctly.

Keyboard navigation: The site's navigation menus, game listing links, search features, and interactive controls are reachable and operable using a keyboard alone. Focus order follows a logical reading sequence.

Visible focus indicators: Interactive elements display a visible focus ring when they receive keyboard focus, so keyboard-only users can track their position on the page.

Colour contrast: We target a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, in line with WCAG 2.1 AA requirements. We test our colour choices against this standard when making design changes.

Text alternatives for images: Meaningful images carry descriptive alternative text. Decorative images have empty alt attributes so they are skipped by screen readers.

No autoplay audio: The site's own pages do not autoplay audio or video content. Sound is only produced when a user actively starts a game inside an embedded frame.

Responsive layout: The site adapts to screen widths from small mobile screens up to wide desktop displays without requiring horizontal scrolling.

Reduced-motion preference: Where CSS animations are used on the site's own interface, we respect the `prefers-reduced-motion` media query and reduce or remove animations for users who have set that preference in their operating system.

Link and button text: Links and buttons have descriptive text or accessible labels so that their purpose is clear when read out of context by a screen reader.

The hard limit: embedded games

Every game on this site runs inside an embedded iframe served by a third-party game distribution network. We have no ability to modify the game code, its interface, its input requirements, or its visual presentation.

Many HTML5 games are designed for fast mouse input, precise touch gestures, or keyboard combinations that do not map well to alternative input devices. Games may not have been tested with screen readers, and their graphics may not meet contrast requirements. Some games require visual information — colour, motion, spatial positioning — that cannot easily be conveyed in text form.

We cannot make embedded games accessible, and we do not represent that they are. If accessibility of the games themselves is important to you, we recommend checking the individual game developer's or distributor's own accessibility information before playing.

Browser and OS accessibility tools

The major operating systems and browsers include built-in accessibility tools that work independently of individual websites:

• Screen readers such as NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android work with the site's semantic HTML for browsing listings and navigating to games.
• Browser zoom (typically Ctrl/Cmd and +) enlarges the site's interface. The layout is designed to reflow at higher zoom levels.
• OS-level display settings for high contrast, large text, and pointer size apply to the site's interface.

Feedback

If you find a part of the site's own interface that is not working well with your assistive technology, or if you have a suggestion for improvement, please email us at contact@your-domain.com. Tell us which page or feature the issue is on, what assistive technology or input method you are using, and what you expected to happen. We read every accessibility report and aim to respond within a few business days.

We are committed to improving accessibility over time. Feedback from real users is the most useful guide we have.