Michele Meloni
Contact

Write to me directly.

For a collaboration, a question about my work or an initial conversation, use this form. For a detailed estimate, use the dedicated flow on the Services page.

Your message is sent directly to info@michelemeloni.com.

Back to articles
Article · Accessibility & UXMichele Meloni9 min read

Accessibility by design: applying WCAG 2.2 in practice

A practical method for integrating keyboard access, focus, legibility, input and testing into design rather than checking them only at the end.

Published · 4 September 2026Updated · 4 September 2026

00 · Premise

Conformance is a baseline. An accessible experience also requires judgement.

WCAG provides testable criteria, while day-to-day design translates them into hierarchies, components, content and journeys that work for different people and assistive technologies.

Two necessary levels

Automation and human review answer different questions.

Automated checks find recurring code problems. Keyboard, zoom, screen-reader use and journey comprehension require manual testing and, where possible, the involvement of people with disabilities.

Automated checks

  • Structure and attributes
  • Measurable contrast
  • Recurring technical failures

Manual checks

  • Focus order and visibility
  • Understanding errors and instructions
  • Real use with assistive technology
01

Start with structure, keyboard and focus

Semantic hierarchy, logical order and visible focus make the interface understandable and usable without relying on a pointer.

Practical actions

  • Use HTML elements that match their purpose.
  • Complete every task with the keyboard alone.
  • Check that overlays and fixed elements do not hide focus.
02

Design input and targets for different people

Fields, buttons and gestures should remain usable with limited precision, zoom and different devices. Do not make an action depend on one complex gesture.

Practical actions

  • Keep labels visible and associated with fields.
  • Provide alternatives to dragging.
  • Check the size and spacing of interactive targets.
03

Make errors and authentication accessible

Errors should be identifiable, described in text and connected to the item that needs correction. Access should not depend only on memory, transcription or cognitive puzzles.

Practical actions

  • Announce errors to assistive technology.
  • Preserve data that is already valid.
  • Allow copy, paste and password managers where appropriate.
04

Test beyond the checklist

Verification combines automated tools, keyboard, zoom, contrast, screen readers and complete tasks. Results should enter the roadmap with clear ownership.

Practical actions

  • Test at least keyboard use and 200% zoom.
  • Check dynamic states and confirmation messages.
  • Include people with disabilities in priority journeys where possible.

Ready to use

Essential accessibility check

  • Structure and headings describe the page.
  • Every action is keyboard accessible.
  • Focus, contrast and zoom preserve legibility.
  • Fields and errors have understandable labels.
  • Complex gestures have an alternative.
  • Priority journeys are tested manually.

Key principle

Accessibility works when it is part of design decisions.

It is not a technical finishing step. It shapes priorities, content, components and the ways people understand and complete a task.