Practise the standard verbs for running a genuinely useful accessibility audit.
0 / 5 completed
1 / 5
Fill in: 'We ___ every core page against WCAG criteria before launch, rather than treating accessibility as an afterthought fixed only once a complaint actually arrives.'
We 'audit a page' — the standard, simple collocation for systematically checking accessibility compliance. The other options are less idiomatic here.
2 / 5
Fill in: 'Treating accessibility as a final afterthought instead of an audited requirement can ___ a genuinely disabling barrier shipped straight to production unnoticed.'
We say a skipped audit will 'leave' a real barrier unnoticed — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every interactive element with a screen reader directly, since an automated scanner alone reliably misses a large share of real usability problems.'
We 'test an element' — the standard, simple collocation for manually checking accessibility behaviour. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ each finding a concrete severity, blocking versus minor, so a genuinely disabling issue doesn't sit in the same queue as a cosmetic contrast tweak.'
We 'assign a severity' — the standard, simple collocation for prioritising accessibility findings. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the audit results with real assistive-technology users where possible, since a rule followed to the letter can still fail badly in actual practice.'
We 'validate results' — the standard, simple collocation for confirming findings against real-world use. The other options aren't idiomatic here.