ACCESSIBILITY

EN — 2026

WCAG 2.2 is not a checklist, it is a better experience

For someone who cannot complete a form by keyboard, an interface that merely looks good does not work.

← Back to all notes

ACCESSIBILITY

WCAG 2.2 is not a checklist, it is a better experience

05 October 20267 min readWYN Studio

For someone who cannot complete a form by keyboard, cannot read text because of contrast, or cannot understand what is on screen with assistive technology, a good-looking interface simply does not work.

Three areas to look at first

  • Perceivable: are text, colour, media and icons understandable for different needs?
  • Operable: can the whole flow be used by keyboard and touch device?
  • Understandable: does an error message say what happened and how to fix it?

The technical side of visual design

Good contrast is not only colour choice. Visible focus states, resizable text, buttons with sufficient tap area, and the ability to reduce motion are the accessibility side of design.

Why semantic HTML matters

A div can look like a button visually, but keyboards, screen readers and browsers cannot know what it is on their own. Correct HTML elements and meaningful aria labels let the interface reach people through different channels.

How testing progresses at WYN

Automated checks are a good start; human testing, keyboard navigation, different zoom levels and mobile use show real quality. We check accessibility while components are designed, not at the end of the project.

Source / further readingWYN working approachThis article does not copy the original content of the source; it is WYN’s practical interpretation. For current headlines, check the publication date and the source page separately.