Contact

Thanks for wanting to get in touch. This page explains what we read, what we need from you, and how quickly things get fixed. One honest note up front: we are not publishing a support email address yet — this is a small independent project and we are setting up a durable channel before advertising one. Until it appears here, the categories below describe exactly how reports are handled once it does, so your draft message is ready the day the address goes live.

What we want to hear about

Factual errors

If a page states something wrong — a prevalence figure that drifted from its source, a mislabeled plate group, an outdated claim about clinical testing — that is a top-priority fix. Include the page URL, the sentence in question, and if possible the correcting source. Corrections ship with an updated page date; we do not silently edit published facts.

Translation quality

The site runs in seven languages, and every language was written to be read natively, not machine-translated. If a French, German, Spanish, Japanese, Korean or Italian page reads awkwardly or mistranslates a concept, tell us the exact sentence — native-reader reports are how multilingual quality actually improves.

Accessibility barriers

Color vision tools should themselves be accessible. Report anything that fails you: keyboard traps, missing focus states, screen-reader labeling on the answer controls, contrast problems outside the test plates, or layout breakage at your viewport size. Name the page and the device/browser; a sentence about what you expected versus what happened is enough.

License and provenance questions

Questions about the MIT components, attribution, or plate provenance go straight to the top of the queue — see the licenses page for the published ledger. If you believe an attribution is missing, we treat it as urgent.

Privacy questions

The tests collect nothing (the privacy policy explains the mechanics), but privacy questions still get answers. Ask us "what does feature X transmit?" about anything on the site and you will receive a specific, technical answer rather than a form letter.

What we cannot help with

To set expectations honestly: we cannot interpret your test results or provide medical advice. "I scored 6 of 13 — what does that mean?" is a question for an optometrist or ophthalmologist, and the result pages themselves point the way. What we can do is fix the tool if the tool is wrong.

How to write a report that gets fixed fast

1. One issue per message, with the URL of the page it concerns.
2. What you did — device, browser, and the display settings if the issue is visual.
3. What you expected, and what happened instead. Screenshots help for visual bugs; for text issues, quote the sentence.
4. For translation fixes: the sentence, why it is wrong, and your suggested phrasing if you have one.

Response expectations

This is a maintained side project, not a staffed helpdesk. Substantive reports — factual errors, license issues, accessibility blockers — are aimed at a first response within a week of a channel going live. Feature requests are read and triaged honestly, which sometimes means "no, on purpose": the tests will stay free, account-less and non-diagnostic, and no amount of asking will add a "90% colorblind" verdict, because that number would be fiction.

Follow the project

Changes worth knowing about (new languages, plate-version bumps, the contact channel going live) will be announced on the site itself — the about page describes how updates are dated and published. Until then, thank you for testing carefully, reading critically, and holding the site to its own standard: honest tools, honest words.