Accessibility

POPIAdesk should be usable by everyone, including people who rely on a keyboard, a screen reader, or reduced motion. This page says where that stands today, plainly.

Our target

We build against WCAG 2.1 level AA and test against it automatically on every page, on every change. We do not claim full conformance: no independent audit has been done, and our own screen-reader testing is still in progress. When that changes, this page will say so.

What works today

• Every page can be navigated by keyboard, with a visible focus indicator and a skip-to-content link as the first stop.
• Colours meet AA contrast in both the light and dark themes, checked per pairing rather than assumed.
• Animations respect your reduced-motion setting.
• Form fields have proper labels, and validation errors are linked to the field they belong to and announced, not shown silently.
• Pages reflow to a single column without horizontal scrolling down to 320 pixels wide, so browser zoom works.
• Assessment answers behave as a real radio group: one tab stop per question, with arrow keys moving between options.
• Long-running actions, like a website scan, announce that they have started and what the result was.

What we know is missing

• Our screen-reader testing is not finished. Automated checks confirm the labels and roles are present; they cannot judge whether every announcement is clearly worded.
• Generated PDF documents are not tagged for screen readers. If you need a document in an accessible format, ask us and we will provide one.
• No independent accessibility audit has been carried out.

Tell us what is broken

If any part of POPIAdesk does not work with your assistive technology, email hello@popiadesk.co.za with the page and what happened. We respond within 5 business days, and fixing it becomes our work, not yours.

If you need something from POPIAdesk in a different format to use it, ask in the same email and we will arrange it.

Related

See our Privacy Policy and Terms of Service.