Accessibility
Accessibility
What we have built in, what we are still missing, and how to tell us when something blocks you. Last updated 29 July 2026.
The commitment
GAMSAT Practice Test targets WCAG 2.2 Level AA. Every part of the site, including the timed test, is operable with a keyboard alone. Where we fall short of that target, we would rather hear about it than have you work around it.
Why this matters more here than on a normal site
This is a timed test. If a control is hard to reach, the cost is not inconvenience, it is minutes off a clock. Anything that slows you down for reasons unrelated to the questions is a defect, and we treat it as one.
What is in place
| Feature | How it works here |
|---|---|
| Keyboard navigation | Every interactive element is a real button or link and sits in the natural tab order. Nothing requires a mouse, a hover or a drag. |
| Skip link | A “Skip to content” link is the first thing in the tab order on every page and jumps past the header. |
| Visible focus | A 2px accent outline with an offset is applied to every focusable element, site-wide. It is never removed. |
| Reduced motion | prefers-reduced-motion: reduce is honoured globally — animations and transitions are cut to effectively zero. |
| Colour scheme | prefers-color-scheme is honoured, with a full dark palette rather than an inverted filter. |
| Tabular numerals | Scores, timers, cutoffs and every other figure in a table use tabular numerals so digits align in a column and do not shift as they count. |
| Semantic structure | One h1 per page, headings in order, real tables with header cells and captions, lists marked up as lists, landmarks for header, main, footer and navigation. |
| No decoration in the way | No drop shadows, no auto-playing media, no carousels, no interstitials, no cookie wall, and no CAPTCHA — the test needs no account, so there is nothing to prove. |
| Text that reflows | Layout is fluid and text-based. Zooming or narrowing the window reflows content rather than clipping it, and wide tables scroll inside their own container instead of forcing the page sideways. |
The timed test is keyboard-operable
This is the part that would be easiest to get wrong, so it is worth stating in detail.
Without touching a mouse, you can:
- start the test, move to the next and previous question, and submit it;
- select and change an answer;
- flag a question for review and unflag it, with the flag state announced;
- jump to any question from the question navigator, where each target announces its number and whether it is answered or flagged;
- pause and resume the clock.
The remaining time is exposed as a labelled value rather than as decoration, and it is announced when the clock reaches its critical threshold rather than being read out continuously, which would make the test unusable with a screen reader.
On the time limit itself. The timer is the point of the exercise: the real exam is timed and practising without a clock does not prepare you for it. Under WCAG 2.2, a time limit that is essential to the activity is permitted, and the clock can be paused and resumed at any time. If the timing is still a barrier for you, tell us. That is a design problem we would like to solve rather than a limitation we are defending.
What we have not done
An accessibility statement that lists no gaps is not a statement, it is marketing.
- No independent audit. We have not commissioned a third-party accessibility audit. WCAG 2.2 AA is our target and our working standard, not a certified conformance claim.
- Not every page has been walked end to end with a screen reader. The test itself gets the most attention. Newer content pages get less.
- Some question material is inherently visual. Section 3 reasoning routinely depends on graphs, diagrams and structures. We write alternative text for these, but a diagram whose whole purpose is to be interpreted cannot always be reduced to a sentence without giving away the answer. Where we cannot describe something adequately, that is a gap and we would rather you told us which question it was.
- Third-party pages are outside our control. We link to ACER, universities and application bodies. Their accessibility is theirs.
Tell us what is blocking you
Report a barrier
Email hello@gamsatpracticetest.com. A person reads it.
If you can, include:
- the page, and what you were trying to do;
- what happened instead;
- your browser and any assistive technology you were using, including the version if you know it.
You do not need to know the technical term for the problem, and you do not need to cite a success criterion. “I could not get to the next question” is a complete and useful report.
We treat accessibility reports the same way we treat factual corrections: we fix the page, and if the fix is substantive we say what changed rather than editing quietly. If something cannot be fixed quickly, we will tell you what the workaround is in the meantime.