Skip to main content
Commerce Security logo, "All 12 PCI DSS Requirements in Plain English," "Get it now for free," "Complete Survival Guide" and a button toclick to get it
A Test Protocol Template for WCAG 2.2 Focus AppearanceWCAG Principles and Conformance
3 min readFor Accessibility Program Managers

A Test Protocol Template for WCAG 2.2 Focus Appearance

Purpose of the Template

Focus Appearance, a criterion in WCAG 2.2, often leads to inconsistent audit results. Currently Assistive Technology Level AAA as 2.4.13, it presents an operational challenge: different testers may interpret the same criteria differently. This template provides a structured protocol to ensure consistent and repeatable results, which is essential for an Accessibility Governance program when audit findings might be scrutinized by legal or procurement teams.

Use this template if you've adopted Focus Appearance as an internal target, if a contract or Accessibility Conformance Report commits you to AAA, or if you need a documented method for the related Level AA requirement, 2.4.7 Focus Visible.

Prerequisites

  • Decide if 2.4.13 is a pass/fail requirement, an advisory target, or out of scope. Most programs targeting WCAG 2.2 Level AA will treat it as advisory. Document this decision.
  • Inventory focusable elements by shared styling (e.g., buttons, links, form fields).
  • Agree on a measurement method, such as browser developer tools and a color contrast tool. Specify these tools in the protocol.
  • Document tested viewports and languages. Component size changes can affect results, so ensure styles are tested across different conditions.

The Template

Copy this into your test plan and complete one block per component group.

FOCUS APPEARANCE TEST RECORD (WCAG 2.2, SC 2.4.13)

Component group: ______________________
Representative element(s) tested: ______________________
Viewport / language / state tested: ______________________
Tester: ____________  Date: ____________  Tool(s): ____________

STEP 1. APPLICABILITY
[ ] Element receives keyboard focus
[ ] Focus indicator is author-defined (not browser default)
    Note: if browser default, record browser/version and
    follow your program's default-indicator policy.

STEP 2. INDICATOR GEOMETRY
Indicator type: [ ] outline  [ ] border  [ ] background change
                [ ] shadow   [ ] other: __________
Encloses the component entirely?  [ ] Yes  [ ] No
Measured indicator thickness (px): ______
Measured component dimensions (px): ______ x ______
Required area (per SC text, using the component's perimeter): ______
Measured indicator area: ______
Margin between measured and required: ______

STEP 3. CONTRAST
Indicator color: ______  Adjacent color(s): ______
Ratio between focused and unfocused states: ______
Ratio between indicator and adjacent colors: ______
Any pixels below 3:1? [ ] Yes  [ ] No
If yes, did alternate calculation apply? [ ] Yes  [ ] No

STEP 4. VERDICT
[ ] Clear Pass   [ ] Clear Fail   [ ] Borderline
Borderline = any measured margin within the tolerance set
in your program (see customization).

STEP 5. EVIDENCE
Screenshot (focused / unfocused): ______
Measurement notes: ______
Reviewer sign-off (required for Borderline): ______

Explanation of Each Step: Step 1 ensures measurements aren't wasted on irrelevant elements. Step 2 requires precise perimeter-based area calculations, as small differences can affect outcomes. Step 3 separates contrast evaluations to prevent confusion. Step 4 introduces a "Borderline" verdict for close calls, requiring a second review. Step 5 documents evidence for future audits.

Customizing the Template

Set Borderline Tolerance: Choose a pixel margin for "Borderline" results and document it. Decide this with your accessibility lead and apply it consistently.

Add Responsive Testing: If components resize or localize into different languages, test each condition separately.

Treat Shared Styles Consistently: For shared focus styles, test the smallest and largest components, then apply the verdict to the entire group. Document this reasoning.

Pre-approve Patterns: Maintain a list of pre-approved design patterns to streamline testing. Update this list with any design system changes.

Align with Reporting Language: Decide how to report "Borderline" outcomes in your Accessibility Conformance Report. Use "Partial Conformance" with notes for accuracy.

Validation Steps

  1. Calibration Exercise: Have two testers evaluate the same components and compare results. Adjust protocol wording if needed.
  2. Re-test After Design Changes: Re-evaluate components after any design-system updates, as global changes can affect focus styles.
  3. Quarterly Borderline Review: Analyze patterns in borderline results to identify areas for design improvement.
  4. Independent Verification: Ensure completed records can be independently verified using measurements and screenshots.
  5. Check Against Level AA: Ensure indicators meet 2.4.7 Focus Visible requirements, even if 2.4.13 is advisory.

Complex criteria often lead to disagreements rather than measurement issues. A fixed protocol shifts disagreements to a single documented rule, ensuring consistent application across your program.

Green background, the words "The Biggest AI Security Risk Isn’t the Model. It’s the Agent." A robot drawing. A button for "Get the Free Guide."

You Might Also Like