Accessibility

We are building to WCAG 2.2 Level AA, the current version of the international standard. It is the bar we hold ourselves to internally. It is not a claim that every page already meets it.

Every question can be answered by typing instead of speaking, and typing produces exactly the same result. Nothing requires a working microphone.

The interview works from the keyboard alone, including starting and stopping a recording. Focus is visible on every control and we never remove the focus outline.

New questions are announced to a screen reader politely rather than interrupting, and the page does not steal focus while you are part-way through typing.

Body text sits above the AAA contrast threshold on the pages you are reading now. Text zooms to 200 percent without losing content, and nothing depends on colour alone. Animation is removed when your system asks for reduced motion.

These are real, currently open, and we would rather tell you than have you discover them.

The recording length limit. A voice answer currently stops at four minutes without warning you first and without a way to extend it. Under WCAG that is a Level A failure, and it is the most serious item on this page. The fix is a warning before the limit with a way to continue, and it is the next accessibility change we make. Typing has no limit, so there is a working path today.

Automated checks do not yet cover the interview screens. Our automated accessibility checks run against a set of screens that predates the conversation, so the interview itself is not measured on every build. It is built to the same rules and it is not yet verified by machine on every change.

A full manual screen-reader pass has not been done. Nobody has yet sat down with VoiceOver and NVDA and walked the whole thing end to end. Automated tools catch roughly the mechanical half of accessibility, and the half they miss is the half that decides whether something is actually usable.

The recording timer. The running clock during a recording may announce more often than is useful on a screen reader. We have not measured it, and it is on the same list as the item above.

Email hello@askfivetest.com and describe what happened. Tell us what you were trying to do, what you were using, and what the page did. A person reads that address.

If something on this site is stopping you from doing something you want to do, we will help you do it another way while we fix it. That includes taking an interview with a person's help if that is what works for you.

This statement covers askfivetest.com and the interview it contains. It does not cover services other companies run, like our payment processor's own screens.

AskFive is offered in the United States and is designed for people aged 18 and over. The privacy policy covers what happens to anything you write or say.