Tryit
Accessibility statement
What we can show about accessibility on this site, what we cannot, and how to tell us when we got it wrong.
Our commitment
Accessibility is part of how this site is built rather than a page added afterwards: colours are measured, the keyboard path is designed, and every release runs an automated accessibility sweep. This statement describes what is true today, including the parts we have not solved.
Conformance status
Tryit targets the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is a design target, not a certification: the site has not been externally audited and we do not claim full conformance.
Measures we take
Keyboard operability
Links, buttons and disclosures are native HTML controls with a visible focus ring, so every action can be reached and operated with a keyboard alone.
Names and announcements
Meaningful icons carry accessible names, decorative ones are hidden from assistive technology, and dynamic states such as progress and play outcomes are announced through ARIA live regions.
Colour contrast
Text and interface colours come from a token palette whose pairs are measured against the AA thresholds — 4.5:1 for body text, 3:1 for large text and UI borders — in both themes. Changing a token means re-measuring it.
Reduced motion
Motion is decoration: under prefers-reduced-motion the site stops animating, and every flow still completes without it.
Focus management
Dialogs and overlays hold focus while they are open and hand it back to the control that opened them when they close.
Skip link and landmarks
The first thing a keyboard user reaches is a "Skip to content" link, and each page carries exactly one main landmark for it to jump to.
Semantic structure
Pages keep one h1, headings in order without skipped levels, and real list, navigation and disclosure elements instead of click handlers on generic boxes.
Labelled inputs
Controls that ask for something (a short description, quiz answers, a name) are labelled, and problems are stated in text rather than by colour alone.
Target size
Interactive targets, including every FAQ disclosure row, are at least 44 by 44 pixels.
Automated checks as a release gate
Every release runs an axe-core sweep (WCAG 2.0/2.1 A and AA plus WCAG 2.2 AA rules) across the site in both themes at 1440px, 390px and 320px with a horizontal-overflow check, and a failing sweep blocks the release.
Known limitations
- AI-generated images
A generated image cannot be described by assistive technology. We label an image result with what it is — the experience and the result — but not with what it depicts, and we would rather say that than claim an image description we cannot produce.
- Canvas-based games
Some games draw their board on an HTML canvas, which exposes nothing to assistive technology by design. Those games announce their state in text, and they are still harder to play with a screen reader than our quiz experiences.
- Third-party content
Pages we link to on other sites, including our own products, are outside this statement. Tryit shows no third-party advertising.
Feedback
If something here gets in your way, we want to hear about it. The page, what you were doing, and the browser or assistive technology you were using is everything we need to start.
Email: hi@tryit.fun
Feedback lands with the people who build the site: gaps we can fix get fixed, and ones we cannot get named in the limitations above.
Technical specifications
This site is built to work with your browser and with assistive technology already installed on your device:
- HTML5 markup
- WAI-ARIA where ARIA is genuinely needed
- CSS including prefers-reduced-motion and prefers-color-scheme
- JavaScript with no plugin required