---
id: kb_accessibility_wcag_operable_controls
title: Operable and perceivable controls
category: accessibility
appliesToAppTypes: [generic]
appliesToLenses: [accessibility]
steps: [evaluate]
tags: [accessibility, wcag, controls, keyboard]
citation:
  source: "W3C: Web Content Accessibility Guidelines (WCAG) 2.2"
  url: "https://www.w3.org/TR/WCAG22/"
  retrievedAt: "2026-06-01T00:00:00.000Z"
freshness:
  volatility: stable
  lastReviewed: "2026-06-01T00:00:00.000Z"
---

## Summary

Interactive controls should be perceivable, keyboard operable, named, and sized so users can
complete tasks without relying on a mouse or visual-only cues.

## Deep Guidance

Ground accessibility findings in observable controls and WCAG-aligned expectations: controls
need accessible names, visible focus, keyboard access, clear relationships to labels or helper
text, and target geometry that does not create unnecessary precision demands. Prefer measured
evidence from accessibility tooling or DOM inspection. When a finding is heuristic rather than
measured, phrase it as a user-impact risk and cite the specific control, selector, or region that
creates the barrier.