Accessibility

Last updated 9 September 2026.

What's been done

• Colour contrast is measured, not guessed. Every text and border colour is checked against the WCAG formula. Body text is around 14:1, secondary text around 7:1, and buttons carry their own labels at better than 5:1. Field and button edges pass the 3:1 rule for interface components.
• Colour is never the only signal. The two sides of an argument are told apart by their own words and their position, not just by blue and amber. The side you picked is announced in words to a screen reader, not only outlined.
• Results are announced. When you vote, the result and the running total are read out, rather than silently appearing elsewhere on the page.
• Everything works from the keyboard, with a visible focus outline, and dialogs keep focus inside themselves and return it when they close.
• Touch targets are at least 44 pixels.
• Help is never hover-only. The small "?" helpers open on tap or Enter, stay open while you read, and close with Escape. Nothing important is hidden behind a mouse-over, because touchscreens have no mouse-over.
• Motion respects your settings. If your device asks for reduced motion, animations are switched off.
• Pages work without JavaScript for reading. An argument's question and both sides are written into the page itself, so a reader that doesn't run scripts still gets the content.
• Text can be resized and the layout reflows to a single column. Body text starts at 16 pixels and honours whatever default your browser is set to.

What still needs work

Being honest about the gaps is more useful than claiming there are none.

• Arguments are written by other people. We cannot make someone else's wording clear, and an automatic check can't judge readability. Some questions will be confusing through no fault of the site.
• The dashboard chart is a picture. The same numbers are also written out as text for screen readers, but there is no visible table for people who would simply rather read the figures.
• The search box accepts technical lookups (receipt fingerprints and key ids) that are not explained on the page itself. Ordinary word searches work exactly as you'd expect.
• This site has not been audited by a third party, and it has not been tested with every screen reader. The checks behind the claims above are our own.

Telling us about a problem

Email justin@cronkcompanies.com. Useful things to include, if you can: the page, what you were trying to do, and what happened instead. Your browser, device, and any assistive software you use help a lot, but don't let missing details stop you writing.

You will get a reply. If something is broken and it can be fixed quickly, it will be.

See also: Help, Terms, Privacy, The rules.