Accessibility
Accessibility statement
ChainChoice aims to be usable by everyone who compares onchain products here, including people who use a screen reader, a keyboard, zoom or reduced motion. This statement covers chainchoice.io. The standard we work to is WCAG 2.2 level AA.
How far we meet it
The site is partially conformant with WCAG 2.2 level AA: the exceptions below are known, measured and listed. No independent audit has been carried out, and the site has not yet been tested by people using a screen reader, a magnifier, voice control or switch access. The conformance report below is our own evaluation against the WCAG evaluation methodology (WCAG-EM), made from the code and our automated checks. Automated checks and code review find only part of the barriers a person meets, so there may be problems this statement does not list.
Every WCAG 2.2 A and AA criterion, judged one by one on every template, is in the accessibility conformance report
What is not yet accessible
The automated checks below find no barrier today, with no exception allowed. That is not the same as none existing: our own evaluation against each criterion found 2 that the site does not yet fully meet.
Some text over coloured gradients is lighter than the AA contrast minimum in the light scheme. Our colour check lists each place, and each is being fixed.
Turning off Saved on the compare page un-saves that comparison at once, without a way to undo. Everywhere else, Remove shows Undo where the item was.
How we test
We run these checks in a browser as part of our release checks:
- The main page templates (the homepage, ranking, category and country pages, the Explorer, Find my best, compare, head-to-head, provider pages and the methodology page) are run through axe-core's WCAG 2.2 A and AA rules and more of its rules (every element carries only a role its tag allows, headings step down one level at a time, a control's name contains the words it shows, and each page has one main area and named, top-level landmarks), at a phone's width and at desktop width, and on a phone with the cookie bar shown. A failure that is not one of the exceptions listed here fails our release checks. Its result
- Every link, button, image and form control has a name in the browser's own accessibility tree, the one a screen reader reads, on every page these checks load. Its result
- The running text of each main page is measured for how hard it is to read. The target is a US school grade of 8, and a page above it may not get harder. Its result
- Text drawn over illustrations is measured for contrast against the pixels behind it. Its result
- A control that takes keyboard focus is never hidden behind a sticky header or bar. Its result
- Moving to another page moves focus to that page's main heading, so a screen reader says where you arrived and the keyboard starts there. Its result
- Each page has one main heading. Its result
- Links inside running text are underlined, not marked by colour alone. Its result
- Text is never set below the site's minimum size. Its result
- Animation stops when your device asks for reduced motion. Its result
- On a phone, the Explorer's filter drawer is a dialog: focus moves into it, stays inside while you tab, and returns to where you were when it closes. Its result
- The same holds for the filter sheet on ranking pages, and nothing on the page is drawn over it. Its result
- Find my best moves focus to each new question and announces which question you are on. Its result
- Back to top moves focus to the start of the page as well as scrolling there. Its result
Accessibility conformance report
The report sets out every WCAG 2.2 A and AA criterion and the EN 301 549 clauses beyond the web chapter, each with its conformance level and remarks. It opens here once the page has loaded.
Keyboard shortcuts
/ opens site search when you are not typing in a field. Ctrl+K (Cmd+K on a Mac) does too, and Ctrl+/ opens the assistant. If you use speech input, a single-key shortcut can fire by mistake, so you can turn it off here. The choice is kept in this browser.
Report a barrier
If something on the site is hard or impossible for you to use, write to mathias@cryptopaymentfinder.com. Tell us the address of the page and what you were trying to do. If you need what a page says in another form, ask at the same address.
Response time: Reviewed within 7 days.
This statement was prepared on . It is built from the same checks it describes, so it changes when they do.