Accessibility

This statement covers MockCert, operated by Barwalia Labs. It is written to be useful rather than reassuring: it says what has actually been done, and names what has not.

The standard aimed for

WCAG 2.2 Level AA. That is the target, not a claim of conformance. No independent audit has been carried out, and no automated tool has been treated as if it were one, so this page claims partial conformance and nothing more. A blanket claim would be easy to write and impossible to stand behind.

What has been done

• Controls are real buttons, links and inputs, reachable and operable by keyboard. Where a custom control is needed, such as the study search's results list, it follows the matching ARIA pattern.
• Text alternatives on images that carry meaning, and empty alternatives on ones that are decorative.
• Color is never the only way information is conveyed — a wrong answer is labelled, not merely tinted red.
• A light and a dark theme, both checked for contrast on body text.
• Layouts reflow to narrow screens without a horizontal scrollbar, and tolerate browser zoom.
• Form fields have labels, and errors are described in words rather than by color alone.

Known gaps

Stated honestly, because a person deciding whether this tool will work for them deserves to know before they invest time in it:

• No screen-reader testing has been done with NVDA, JAWS or VoiceOver. Semantic markup gets some of the way there by construction, but that is not the same as having been used.
• The timed mock-exam runner is the most complex screen in the application, and its keyboard order and live announcements have not been verified against assistive technology.
• The analytics charts convey their meaning visually. Underlying numbers appear in adjacent tables, but the charts themselves are not separately described.
• Some form errors (sign-in, account creation and the MockCert certificate check) are written next to the form but are not yet linked to their field for screen readers. This is being fixed.
• An independent review of the live site's usability (October 2026) sampled pages, widths and themes and reported accessibility concerns, which are being worked through. It was not a WCAG conformance audit, and none has been commissioned.

If something blocks you

Please write to [email protected] and describe what you were trying to do, which page, and what assistive technology you were using. Accessibility reports are treated as bugs, not as feature requests, and specific ones get fixed fastest.

If you need something on this site in a different format in order to use it, ask — it will be provided.