9 examples, 9 fixes
Your accessibility
checklist.
Every barrier in the simulator is common on real websites, and most customers who hit one leave without telling anyone. Here is what to check on yours.
Is your website doing any of this?
Run a free EaseAccess24 accessibility check on any page. You get the issues it finds and how to fix them. For a full review, our team audits your key journeys by hand.
01 / Color vision
Is your website saying things in color alone?
We added “Available” and “Sold out” labels, plus checkmarks and crosses. The color filter stays the same.
- Pair every color cue with text, an icon or a pattern, such as a “Sold out” label.
- Show form errors with a written message and an icon, not only a red border.
- Underline links in body text, or give them another cue that isn’t color.
- Check charts, maps and status badges in grayscale and with a color-vision filter.
WCAG 2.2: 1.4.1 Use of Color (A) · 1.4.11 Non-text Contrast (AA)
Try the color vision example02 / ADHD & distractions
What is pulling your customers away mid-checkout?
We removed unrelated popups and offers, made the next step clear, and kept your ticket choice.
- Don’t open popups, chat prompts or offers in the middle of a task such as checkout.
- Let people pause, stop or hide anything that moves or updates for more than five seconds.
- Give each step one clear primary action.
- Keep people’s choices when they close a dialog or go back a step.
WCAG 2.2: 2.2.2 Pause, Stop, Hide (A) · 2.2.4 Interruptions (AAA)
Try the ADHD & distractions example03 / Dyslexia & reading
Can your customers find the one fact they came for?
We gave refunds their own heading, shortened the sentences and added space. The same letter effect remains.
- Split long pages and policies into sections with descriptive headings.
- Use short sentences and put key facts such as dates and prices first.
- Left-align body text, and avoid justified text and long passages in italics or capitals.
- Make sure text still fits when people increase line, letter and word spacing.
WCAG 2.2: 1.3.1 Info and Relationships (A) · 2.4.6 Headings and Labels (AA) · 1.4.12 Text Spacing (AA)
Try the dyslexia & reading example04 / Low vision
What happens to your website at 200% text size?
We increased contrast and let the text wrap. The text remains enlarged to 200%.
- Give body text at least 4.5:1 contrast with its background (3:1 for large text).
- Test every page at 200% text size and at 400% zoom (a 320-pixel-wide viewport).
- Avoid fixed heights and hidden overflow on containers that hold text.
- Let content reflow into one column instead of scrolling sideways.
WCAG 2.2: 1.4.3 Contrast (Minimum) (AA) · 1.4.4 Resize Text (AA) · 1.4.10 Reflow (AA)
Try the low vision example05 / Keyboard access
Can a customer get through your checkout without a mouse?
We put the controls in a logical focus order and added a clear outline. Your booking choices stay selected.
- Use native buttons, links and form controls so Tab, Enter and Space work.
- Keep the code order the same as the visual order, and avoid positive tabindex values.
- Never remove the focus outline without a clearly visible replacement.
- Make sure sticky headers, banners and dialogs never cover the focused element.
WCAG 2.2: 2.1.1 Keyboard (A) · 2.4.3 Focus Order (A) · 2.4.7 Focus Visible (AA) · 2.4.11 Focus Not Obscured (AA)
Try the keyboard access example06 / Blurry vision
Can your customers tell which option they picked?
We enlarged the ticket cards, added clear labels, increased contrast and made the selected option obvious. The blur stays exactly the same.
- Make tap targets at least 24 × 24 CSS pixels, and ideally 44 × 44.
- Label options and icons with visible text, not symbols alone.
- Show the selected option with more than a thin border or a color change.
- Use strong contrast for prices, labels and small print.
WCAG 2.2: 2.5.8 Target Size (Minimum) (AA) · 2.5.5 Target Size (Enhanced) (AAA) · 1.4.3 Contrast (Minimum) (AA)
Try the blurry vision example07 / Deaf & hard of hearing
What are your videos saying to people who can’t hear them?
We added captions that follow the speech and a full transcript below the video. It still plays without sound.
- Add accurate captions, timed to the speech, to every prerecorded video.
- Publish a transcript next to the video, including important sounds and speaker names.
- Don’t autoplay sound. If media plays automatically, give an obvious way to pause or mute it.
- Put key facts such as places, dates and prices in the page text as well as in the video.
WCAG 2.2: 1.2.2 Captions (Prerecorded) (A) · 1.2.8 Media Alternative (Prerecorded) (AAA) · 1.4.2 Audio Control (A)
Try the deaf & hard of hearing example08 / Motor & tremor
Can your buttons be hit with an unsteady hand?
We made the buttons large and well spaced, and replaced slide-to-confirm with a normal button. The tremor stays the same.
- Make targets at least 24 × 24 CSS pixels, ideally 44 × 44, with space between them.
- Give every drag, swipe or slide action a single-tap or click alternative.
- Make sure every control also works with a keyboard.
- Avoid actions that need precise timing or holding, and let people undo mistakes.
WCAG 2.2: 2.5.7 Dragging Movements (AA) · 2.5.8 Target Size (Minimum) (AA) · 2.1.1 Keyboard (A)
Try the motor & tremor example09 / Time limits
Is your website timing customers out before they’re done?
We hold tickets for 10 minutes, show the time clearly and let you add more time without losing your choices.
- Avoid time limits unless they are truly necessary.
- Warn people at least 20 seconds before time runs out, and let them extend it with one simple action.
- Keep what people entered when a session expires, so they can pick up where they left off.
- Let people turn off or adjust time limits, for example to ten times the default.
WCAG 2.2: 2.2.1 Timing Adjustable (A) · 2.2.5 Re-authenticating (AAA) · 2.2.6 Timeouts (AAA)
Try the time limits example
This checklist covers 9 common barriers, not every WCAG requirement. Automated checks find only part of the issues; manual and assistive-technology testing remain essential. To learn more, read guides on the EaseAccess24 blog.