WCAG 2.2 in Practice: Mobile Targets, Keyboard Focus, and Real Testing
How the 2023 WCAG 2.2 Recommendation shaped 2024 web work: focus visibility, drag alternatives, target sizes, and mobile testing.
A page loading does not make it accessible
Accessibility is more than increasing text contrast or adding alt text to every image. Can a visitor open a menu with a finger on a small screen, see where keyboard focus has moved, and hear a meaningful button label through a screen reader? The Web Content Accessibility Guidelines 2.2 became a W3C Recommendation in October 2023; applying these criteria to everyday engineering was a major practical concern for projects in 2024. A successful accessibility review is not a single tool score. It is the ability to complete real tasks with different input methods and assistive technologies. Reading an article, submitting a comment, and returning to site navigation should be tested end to end.
The nuance behind the 24-pixel target rule
WCAG 2.2 success criterion 2.5.8 generally expects pointer targets to measure at least 24 by 24 CSS pixels, but it includes defined exceptions for spacing, equivalent controls, inline elements, and other cases. Checking only the visible width of a button is therefore incomplete. Small carousel thumbnails, densely packed filters, and close icons in comment forms are common risk areas. Expanding the interactive area beyond the visible icon can reduce accidental taps on neighboring controls. Test the same interface at both 320- and 390-pixel widths and inspect spacing between nearby targets. A desktop mouse provides far more pointing precision than a finger on a moving phone.
Focus must remain visible beneath sticky UI
Keyboard users should know where they are as they move through an interface with Tab and Shift+Tab. WCAG 2.2 criterion 2.4.11 requires that author-created content not completely obscure a component receiving focus. Sticky navigation bars, cookie panels, bottom action bars, and expandable side panels deserve special attention. When a modal closes after moving focus programmatically, focus should return to the control that opened it. Testing clicks alone misses these problems; complete the same journey using a keyboard without touching the mouse. A well-designed focus indicator is visible against surrounding content and remains useful as the interface changes across screen sizes.
Provide an alternative to dragging
A news strip may support horizontal swiping on touch screens. Yet a visitor with limited motor control or a different pointing device can be blocked if dragging is the only way to navigate. WCAG 2.2 criterion 2.5.7 generally requires functionality that uses dragging to have a single-pointer alternative without dragging. For a carousel, previous and next buttons and direct thumbnail links should provide functional alternatives to a swipe gesture. Screen-reader names and keyboard navigation still need separate attention. Supporting gestures can improve usability, but making a gesture the only available route creates an unnecessary barrier. Verify that the alternative controls reach the same content and do not silently drop functionality.
Error messages, language, and form context
Forms should not communicate errors through a red border alone. Explain which field failed and why, associate the explanation with the input, and manage focus carefully if a summary of errors is presented. On a bilingual site, the HTML language attribute matters because an incorrect value can change how a screen reader pronounces content. Heading hierarchy, link purpose, and localized dates also shape the experience. If an email-verification service is unavailable, a disabled action should have a meaningful state rather than appearing active and silently failing. Accessibility testing must cover errors, empty data, and connection loss as well as the ideal visual layout. Visitors should understand what happened and whether they can retry.
A real test matrix and regression protection
Test a publishing page across four viewport classes: wide desktop, tablet, typical phone, and narrow phone. In each, exercise the main menu, carousel, search, comment form, and image enlargement. Next, navigate without a mouse and inspect focus order; use a screen reader to hear whether links make sense. Automated accessibility scanners catch many basic errors, but they cannot prove full conformance. A new CSS release may eliminate horizontal overflow while leaving tap targets too small. Combine user-task testing, automated checks, and manual verification. Record findings with page URLs, viewport widths, and reproducible steps so future releases can detect regressions instead of relying on visual impressions alone.
Comments
No comments yet. Be the first to contribute.
Reading “WCAG 2.2 ile mobil erişilebilirlik: Tıklama hedefi, klavye odağı ve gerçek test” raised this question for me: compatibility and debugging impact deserve review.
Editor note: Product claims and measured outcomes should be assessed separately. A small pilot with defined metrics is a useful first step.
We should also discuss maintenance cost. An easy rollout does not guarantee trouble-free upgrades.
I would start with a pilot and measurable success criteria rather than assuming a launch means proven value.
✎ Write a comment