Accessibility statement.

Last updated 17 October 2026

This statement describes the beta as it behaves today, including the parts we have not finished.

Our commitment.

Bridge Unlocked is built for people who are new to screens as well as new to bridge. We work to WCAG 2.1 AA across the site and the app. Where we fall short of that, we would rather say so on this page than let you find out for yourself.

What we do.

• Large default text and touch targets on new surfaces.
• Full keyboard operability.
• Screen reader support with meaningful labels: cards are announced by rank and suit, never by colour.
• Visible focus everywhere.
• prefers-reduced-motion honoured.
• No time limits in lessons, practice or play. Sign-in and password reset links expire after 15 minutes, and two-step codes change every 30 seconds, for your security; ask for a new one any time.
• Suits distinguished by shape, not only colour.
• Text you can make bigger: choose Smaller, Standard or Larger with Aa in any lesson or in Settings, and your browser’s own zoom works on every page.

How we test, precisely.

Vague promises about testing are easy to make, so here is the real shape of ours.

Automated, on every release. An axe-core scan runs against forty-four states of the live site and app: the home page, pricing and a help article; sign-up, the check-your-email and password screens and the reset landing; onboarding at each step; the dashboard, the return interstitial and stats; a lesson mid-question and at its end card; the play table during the auction, during card play and at hand complete; the Daily Deal and its archive; the paywall; the in-app pricing and checkout pages; your account with an active subscription and in grace; settings, the confirm dialog and both report modes; the admin screens and the two-factor challenge; the home screen with the notice that the launch period is ending; the Your Call surfaces; the enrolment ceremony and the sign-in challenge; the unsubscribe landing; the handouts page and a free handout; Cancel contract here; the open-source licences page; the Advanced system card, as a dialog, as a phone sheet and as its own page; and Bridge Tips, the handouts hub during the launch period, the contact page, the help centre with an answer open, About us with what’s next, the page for bridge teachers and Find a club. It also covers learning without an account: the start screen, a free lesson’s end card with its offer to save and the lesson’s settings sheet, the free lessons page with its system sheet and clear dialog, the end of Hand Evaluation, and Your First Hand with a free practice set. And it covers saving that progress: the save screen and the sign-in screens at the edge of the free lessons, the note that your link is on its way, the page for a saving link that has expired, and the one question we ask after you save, the question before adding progress to an account and the Home card. It is run with the WCAG 2.0, 2.1 and 2.2 A and AA rule sets, and the bar is zero violations with nothing waved through. Many of those states are scanned again at phone width in the same pass.

Automated keyboard and motion checks, on every release. Skip links first, focus visible, Escape closing a dialog and returning focus where it came from; Tab and Enter through a lesson, through the legal calls and the playable cards at the table; the archive grid’s arrow keys, Home and End, and its locked-day dialog holding and returning focus; toggles that work with the space bar; payment pages with no keyboard trap. A separate motion suite checks that prefers-reduced-motion really does quiet the lesson, the play choreography, the dashboard tiles, toasts, dialogs, onboarding, the archive and this website, and that sound stays independent of it.

Checked in two browsers, before each release. We check the app and this website in Chrome and in Safari’s engine at phone, tablet and laptop sizes, held upright and sideways: that each screen fits, how big each button is to tap, that the text grows with Aa, and what a screen reader is told for the cards, suits, calls and contracts, read from each browser’s accessibility tree. Listening through the app with a screen reader such as VoiceOver or NVDA, and testing by hand on an iPad and an Android phone, are not yet part of each release.

Conformance status.

Partially conformant during the beta. The known issues, stated plainly:

• The bidding box at the table grows with the screen, and its tiles are never smaller than 24px, so on a small phone they are under 44px. A call already made in the auction can be tapped to see what it means: on a phone or tablet these calls can be drawn smaller so that the whole auction fits on the screen, but on a screen 320px wide or wider they are at least 33px to tap, and on a computer they are at least 44px. On a screen 320px wide or wider, every other button and link in the app is at least 44px to tap (a control that looks smaller, such as a switch, has a 44px area around it that takes the tap), and Hint and Notes at the table are 48px. The cards in your hand are an exception: on a phone they overlap, so the part of a card you can tap can be as narrow as 17px on a small phone or a phone held sideways; it is at least 48px on a phone 390px wide held upright, and at least 46px on a computer. A link inside a sentence or a heading is the size of its words. On a laptop at the Standard text size, a lesson card too tall for the window is drawn slightly smaller so that it fits; its buttons stay at least 44px to tap. In a laptop window under 860px tall, each day in the Daily Deal’s list of the week is 38px to tap, so that the whole week and the deal library stay in view.
• The automated scans run on one desktop browser, with many of the states scanned again at phone width; only the handout tables are also scanned in Safari’s engine. Safari’s engine is also checked before each release, but not yet on a real iPad or iPhone, and Android is not yet checked on a real phone.
• The automated target-size measurement is a spot check of a named set of controls, not every control on every screen.
• Screen reader support is not yet tested by a person listening with a screen reader. There is no automated check that an announcement reads well, only that a label exists.
• Payment is taken on a page hosted by Stripe. We chose it partly because its accessibility record is good, but it is not our page and we cannot fix it. If it gives you trouble, tell us and we will help you finish.
• This statement covers the beta. We will review it again when the beta ends.

Feedback and contact.

Tell us what device you were using and what happened, through the contact page. Accessibility reports go to the top of the list, and we aim to reply within two working days. If something on this site or in the app is stopping you, say so plainly and we will find another way to get you what you needed while we fix it.

Enforcement.

If you are unhappy with our response, please tell us and we will look at it again.

Prepared and reviewed.

Prepared 12 August 2026. Reviewed at least at every release; the date at the top of this page is the date of the last revision.