Everyone gets to play.
How playably.ai is built to be used with a keyboard, a screen reader or a zoomed-in phone, what still falls short, and how to tell us when something gets in your way.
WCAG 2.2, level AA.
That is the bar we build and test against across playably.ai, the campaign landing pages we run for brands, and the games themselves. Where we fall short, it is listed below rather than left for you to find.
The parts that are done.
Structure and keyboard
- A skip link and a single main landmark on every page.
- Headings run in order, one page title per page.
- Everything you can click, you can reach and operate with a keyboard, with a visible focus ring.
- Carousel and tab controls have a 24px touch target even where the visible dot is smaller.
Colour and text
- Body text and buttons meet 4.5:1. Large display type meets 3:1.
- Our red is used at full strength for headlines and marks, and one step deeper for small text and button grounds, so the brand reads the same and the words stay readable.
- Links in running text are underlined, so colour is never the only signal.
- Text scales to 200% without sideways scrolling, and pinch zoom is never disabled.
Motion and media
- Animation respects the reduce motion setting in your operating system.
- Nothing flashes more than three times a second.
- Embedded frames carry a title, and images carry alt text or are marked decorative.
What is not done yet.
Written plainly, because a list of gaps is more useful to you than a claim of full compliance.
The games
Our play-and-win games are visual and timed by nature. Most can be played with a keyboard, but a few arcade formats need a pointer, and none currently offer an audio-only route. If a game is the only way into an offer, the offer is always claimable another way. Ask us and we will do it manually.
Client campaign pages
Campaign pages carry each brand's own colours and type. We check contrast on every page we build, but where a brand's palette cannot meet the bar we tell the brand and record the exception rather than ship it silently.
Embedded third parties
Booking is handled by Calendly and some content sits in embedded frames. Those follow their own accessibility, not ours. Anything you cannot do in an embed, you can do by emailing us.
Machines first, then people.
Automated checks with Lighthouse and axe-core run against the home page, the rebates and case-study pages, a client page, the demo form, the arcade and the blog, followed by manual keyboard and zoom passes in Chrome and Safari. Automated tools catch roughly a third of what matters, so a report from a person carries more weight than a score.
Found a barrier?
Email hello@playably.ai or use the contact form. Say which page you were on and what happened. We aim to reply within five working days, and to fix the barrier rather than only log it. If something blocks you from claiming a rebate, say so and we will settle it manually while we fix the page.
Questions your legal or comms team still has?
We will walk your reviewers through the structure, the trigger policy, and the campaign terms.
Book a demo →