A healthcare appointment form may look straightforward but still block someone who uses a keyboard or screen reader. Choosing WCAG 2.2 Level AA as a target brings those barriers into planning: the journey needs visible focus, labeled fields, enough time to finish, and a flow that works without a mouse. section 1.2
Level AA means meeting the applicable Level A success criteria plus the additional Level AA criteria. It is not a separate checklist that replaces Level A. WCAG organizes its testable criteria around content being perceivable, operable, understandable, and robust; Level AAA adds further requirements beyond AA. section 1.5
Scope the target to what is actually present
Inventory a site's images, text, forms, video, icons, and animations, starting at the home page and following common journeys. If there is no audio or video, time-based-media criteria are not currently in scope. Add a video later, and that scope changes. This inventory identifies which criteria to check; it is not itself a pass/fail audit. section 1.5.2
Treat AA as an ongoing design and engineering target, not a badge earned once. Requirements shape the journey; designers establish logical order and visible focus; developers implement labeled fields, suitable semantic HTML, and keyboard-operable components. Recheck conformance as pages, content, and features change. section 1.2 section 1.5.2
