Accessibility Test Cases

A11Y-WCAG-040

WCAG 2.5.8 Target Size (Minimum)

Generated file current Authoring: Content complete
What file status means

This status reports only whether the generated procedure matches the current controlled source hash. It is not independent content verification, regulatory approval, product evidence or a conformance decision.

Recorded standards review: No optional specialist review recorded. Next review: Not scheduled.

MethodWCAG check
TesterAccessibility tester
Indicative effort33–48 min small scope

Check each pointer target against the 24 by 24 CSS-pixel minimum and all five normative exceptions.

Available formats

Use this test in the format you need

The HTML procedure includes the working worksheet. JSON provides the structured source data. Editable Markdown files are delivered inside package downloads.

Purpose

What this test checks

Check each pointer target against the 24 by 24 CSS-pixel minimum and all five normative exceptions.

What this result means: This WCAG 2.5.8 Target Size (Minimum) procedure determines whether the recorded targets meet WCAG 2.5.8 on web-desktop-cross-browser in the tested states. A broader conformance decision must also account for every applicable target in the declared scope, complete processes, accessibility-supported use and the other WCAG conformance requirements.

Why it matters

Detect pointer targets that are too small and too close to other targets for reliable activation. People most likely affected: people with hand tremors, limited dexterity or reduced fine-motor control; People using touch, a stylus or a pointer in difficult conditions. Users may activate the wrong control, be unable to activate a target reliably or abandon a task. In the recorded web-desktop-cross-browser environment, apply the criterion to every relevant state and named normative exception; failures in critical tasks and complete processes carry the greatest user impact.

When to use it

Apply to pointer input targets. Do not count a target only while it is obscured by interaction-generated content; do test targets in the newly displayed content.

Confirm before starting

Mark it not applicable only when

Exceptions

Spacing

Decision condition
The target is undersized, but a 24 CSS-pixel-diameter circle centred on its bounding box does not intersect another target or the corresponding circle for any other undersized target.
Evidence needed
CSS-pixel bounding boxes, circle centres/radii and intersection results for all adjacent targets.
Common error
A vague visual gap is not sufficient; the 24 CSS-pixel circles must be evaluated, including against full-size targets.
Scope
Only the measured undersized target.

Equivalent control

Decision condition
Another control on the same page performs the same function and itself meets the target-size requirement or an allowed exception.
Evidence needed
Identifiers, functions and measurements for both controls, plus evidence that either can complete the same result.
Common error
A different route, partially equivalent action or inaccessible alternative is not an equivalent control.
Scope
Only the undersized target with the qualifying equivalent.

Inline target

Decision condition
The target is in a sentence or its size is otherwise constrained by the line-height of non-target text.
Evidence needed
Rendered text context, line box and DOM extract showing that the target is inline within or constrained by non-target text.
Common error
Being visually near text does not make an icon button or standalone link inline.
Scope
Only the target constrained by the text line.

User-agent control

Decision condition
The size of the target is determined by the user agent and has not been modified by the author.
Evidence needed
Identification of the native user-agent control and evidence that author styles or scripts did not modify its target size.
Common error
A native-looking author control or an author-styled scrollbar does not qualify automatically.
Scope
Only the unmodified user-agent-controlled target.

Essential presentation

Decision condition
The particular target size or spacing is essential to the information being conveyed or is legally required for the presentation.
Evidence needed
A specific rationale showing why changing the target geometry would fundamentally change the information or make the legally required presentation invalid.
Common error
A design preference, density goal, brand layout or implementation difficulty is not essential.
Scope
Only the portion whose geometry is demonstrably essential.

Prepare

What you need

  • The product area and test targets are agreed before testing starts.
  • The operating system, browser, viewport and input method are recorded.
  • Test data is safe to use and does not expose unnecessary personal information.

Targets and required variations

  • Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box.
  • Default and every responsive layout that changes target geometry.
  • Revealed menus, dialogs, validation, toolbars and other layers containing new targets.

Clean state

  • Start from a documented clean or known state and record pre-existing preferences, extensions and cached data that can change the result.

Effort estimate

Setup
10 min
Per target
8 min
Evidence
7 min
Technical review
8 min

Assumptions: one page or component state; add another execution block for each materially different template or state

Variation: Add a new per-target execution and evidence allowance for each additional target class or state that could produce a different result. Add setup time for each distinct environment.

Excluded: Client coordination, inaccessible-environment recovery, recruitment, legal review, remediation implementation and waiting time unless the procedure states otherwise.

Execute

Test steps

Follow each action in order. The expected result is always visible; open the guidance when you need setup, tool, evidence, decision or repeat details. Step-level recording is optional while work is in progress and required only to export a completed execution.

Step 1

Inventory pointer targets

Purpose: For WCAG 2.5.8 Target Size (Minimum), prepare the named scenario: Inventory pointer targets. Target: Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box. The preparation must establish this result: The inventory identifies every applicable target class and state to measure.

User impact: Users may activate the wrong control, be unable to activate a target reliably or abandon a task. This scenario isolates that risk in the action named Inventory pointer targets.

List every unique pointer target and repeated target class in each selected responsive and revealed state. Record targets hidden by an overlay separately from targets introduced by that overlay.

Expected result

The inventory identifies every applicable target class and state to measure.

Failure observation

During WCAG 2.5.8 Target Size (Minimum), the target, starting state, environment or scope record remains ambiguous for the scenario named Inventory pointer targets. The preparation result cannot be demonstrated: The inventory identifies every applicable target class and state to measure.

Setup, evidence and decision guidance
Target
Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box.
Required state
All selected viewport widths, orientations and revealed layers.
Tool or command
Browser developer tools and a pointer-target inventory worksheet.
Record
Page, state, viewport, target identifier, function and repetition count.
Pass
Record passed for the WCAG 2.5.8 Target Size (Minimum) scenario named Inventory pointer targets only when the evidence (Page, state, viewport, target identifier, function and repetition count.) supports: The inventory identifies every applicable target class and state to measure.
Fail
Record failed when the action is completed and this failure observation is reproduced: During WCAG 2.5.8 Target Size (Minimum), the target, starting state, environment or scope record remains ambiguous for the scenario named Inventory pointer targets. The preparation result cannot be demonstrated: The inventory identifies every applicable target class and state to measure.
Not applicable
No pointer input target exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Repeat when layout, content or component geometry changes.
Limitations
This WCAG 2.5.8 Target Size (Minimum) scenario covers only the action named Inventory pointer targets for the recorded target and state. It contributes evidence to 2.5.8; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
The visible icon is not always the complete clickable target; inspect the actual hit area.
Record this step

Step 2

Measure the target area

Purpose: For WCAG 2.5.8 Target Size (Minimum), execute the named scenario: Measure the target area. Target: Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box. Compare the observation with this result: Each target is classified as at least 24 by 24 CSS pixels or undersized.

User impact: Users may activate the wrong control, be unable to activate a target reliably or abandon a task. This scenario isolates that risk in the action named Measure the target area.

Measure the active target's width and height in CSS pixels using its actual pointer hit area. A target meets the size branch only when a 24 by 24 CSS-pixel square fits within it.

Expected result

Each target is classified as at least 24 by 24 CSS pixels or undersized.

Failure observation

After the tester completes the WCAG 2.5.8 Target Size (Minimum) scenario named Measure the target area, the recorded observation for the target is inconsistent with the required result: Each target is classified as at least 24 by 24 CSS pixels or undersized.

Setup, evidence and decision guidance
Target
Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box.
Required state
Rendered state at the recorded viewport and zoom; browser zoom does not change CSS-pixel dimensions.
Tool or command
Browser geometry inspection, hit-area overlay or a validated measurement tool.
Record
Target bounding box, active-area dimensions, viewport and tool/version.
Pass
Record passed for the WCAG 2.5.8 Target Size (Minimum) scenario named Measure the target area only when the evidence (Target bounding box, active-area dimensions, viewport and tool/version.) supports: Each target is classified as at least 24 by 24 CSS pixels or undersized.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the WCAG 2.5.8 Target Size (Minimum) scenario named Measure the target area, the recorded observation for the target is inconsistent with the required result: Each target is classified as at least 24 by 24 CSS pixels or undersized.
Not applicable
No pointer input target exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Repeat when responsive layout or state changes the hit area.
Limitations
This WCAG 2.5.8 Target Size (Minimum) scenario covers only the action named Measure the target area for the recorded target and state. It contributes evidence to 2.5.8; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
Rounded, clipped or irregular shapes can be undersized even when their bounding box is 24 by 24; confirm a 24-pixel square fits inside the active area.
Record this step

Step 3

Calculate spacing for undersized targets

Purpose: For WCAG 2.5.8 Target Size (Minimum), execute the named scenario: Calculate spacing for undersized targets. Target: Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box. Compare the observation with this result: Every undersized target either satisfies the exact spacing calculation or proceeds to another exception.

User impact: Users may activate the wrong control, be unable to activate a target reliably or abandon a task. This scenario isolates that risk in the action named Calculate spacing for undersized targets.

For each undersized target, centre a circle with a 24 CSS-pixel diameter on the centre of its bounding box. Confirm that the circle intersects neither another target nor the 24-pixel circle of another undersized target.

Expected result

Every undersized target either satisfies the exact spacing calculation or proceeds to another exception.

Failure observation

After the tester completes the WCAG 2.5.8 Target Size (Minimum) scenario named Calculate spacing for undersized targets, the recorded observation for the target is inconsistent with the required result: Every undersized target either satisfies the exact spacing calculation or proceeds to another exception.

Setup, evidence and decision guidance
Target
Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box.
Required state
Same geometry and adjacent targets measured in S2.
Tool or command
Geometry overlay or calculation that records bounding-box centres, 12 CSS-pixel radii and intersection results.
Record
Coordinates or overlay for each circle, adjacent-target geometry and intersection result.
Pass
Record passed for the WCAG 2.5.8 Target Size (Minimum) scenario named Calculate spacing for undersized targets only when the evidence (Coordinates or overlay for each circle, adjacent-target geometry and intersection result.) supports: Every undersized target either satisfies the exact spacing calculation or proceeds to another exception.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the WCAG 2.5.8 Target Size (Minimum) scenario named Calculate spacing for undersized targets, the recorded observation for the target is inconsistent with the required result: Every undersized target either satisfies the exact spacing calculation or proceeds to another exception.
Not applicable
No pointer input target exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Recalculate for every layout or state that changes position or dimensions.
Limitations
This WCAG 2.5.8 Target Size (Minimum) scenario covers only the action named Calculate spacing for undersized targets for the recorded target and state. It contributes evidence to 2.5.8; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
Measure from the bounding-box centre, including for irregular shapes; do not substitute edge-to-edge gap alone.
Record this step

Step 4

Evaluate the remaining exceptions

Purpose: For WCAG 2.5.8 Target Size (Minimum), execute the named scenario: Evaluate the remaining exceptions. Target: Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box. Compare the observation with this result: A named normative exception is supported by evidence, or the target fails.

User impact: Users may activate the wrong control, be unable to activate a target reliably or abandon a task. This scenario isolates that risk in the action named Evaluate the remaining exceptions.

For each target that does not meet size or spacing, evaluate equivalent control, inline target, user-agent control and essential presentation in that order. Record the exact condition and evidence for any exception used.

Expected result

A named normative exception is supported by evidence, or the target fails.

Failure observation

After the tester completes the WCAG 2.5.8 Target Size (Minimum) scenario named Evaluate the remaining exceptions, the recorded observation for the target is inconsistent with the required result: A named normative exception is supported by evidence, or the target fails.

Setup, evidence and decision guidance
Target
Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box.
Required state
Same target function and state used for measurement.
Tool or command
DOM/style inspection, functional comparison and documented standards judgement.
Record
Exception name, decision condition, evidence and reviewer question where judgement is material.
Pass
Record passed for the WCAG 2.5.8 Target Size (Minimum) scenario named Evaluate the remaining exceptions only when the evidence (Exception name, decision condition, evidence and reviewer question where judgement is material.) supports: A named normative exception is supported by evidence, or the target fails.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the WCAG 2.5.8 Target Size (Minimum) scenario named Evaluate the remaining exceptions, the recorded observation for the target is inconsistent with the required result: A named normative exception is supported by evidence, or the target fails.
Not applicable
No pointer input target exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Retest the target without the exception if the design or function changes.
Limitations
This WCAG 2.5.8 Target Size (Minimum) scenario covers only the action named Evaluate the remaining exceptions for the recorded target and state. It contributes evidence to 2.5.8; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
Do not use “allowed spacing” or “essential” without the exact calculation or rationale.
Record this step

Step 5

Repeat material variations and recovery

Purpose: For WCAG 2.5.8 Target Size (Minimum), execute the named scenario: Repeat material variations and recovery. Target: Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box. Compare the observation with this result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

User impact: Users may activate the wrong control, be unable to activate a target reliably or abandon a task. This scenario isolates that risk in the action named Repeat material variations and recovery.

Repeat the WCAG 2.5.8 Target Size (Minimum) action for each inventoried variation that can change the outcome. Include relevant default, revealed, error, interruption, recovery and confirmation states and complete the selected process from start to finish where this test can affect task completion.

Expected result

Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

Failure observation

After the tester completes the WCAG 2.5.8 Target Size (Minimum) scenario named Repeat material variations and recovery, the recorded observation for the target is inconsistent with the required result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

Setup, evidence and decision guidance
Target
Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box.
Required state
For WCAG 2.5.8 Target Size (Minimum): Default and every responsive layout that changes target geometry. Revealed menus, dialogs, validation, toolbars and other layers containing new targets.
Tool or command
For WCAG 2.5.8 Target Size (Minimum), use the same recorded method, then change only the state, environment or recovery condition being compared.
Record
Variation identifier; changed state or environment; start and end points; actual observation; recovery result; intervention; evidence reference and target outcome.
Pass
Record passed for the WCAG 2.5.8 Target Size (Minimum) scenario named Repeat material variations and recovery only when the evidence (Variation identifier; changed state or environment; start and end points; actual observation; recovery result; intervention; evidence reference and target outcome.) supports: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the WCAG 2.5.8 Target Size (Minimum) scenario named Repeat material variations and recovery, the recorded observation for the target is inconsistent with the required result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.
Not applicable
No pointer input target exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Repeat this action for every required variation of Measure pointer target size and spacing and after a material target, content, state, environment or configuration change. Preserve the original observation.
Limitations
This WCAG 2.5.8 Target Size (Minimum) scenario covers only the action named Repeat material variations and recovery for the recorded target and state. It contributes evidence to 2.5.8; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
For WCAG 2.5.8 Target Size (Minimum), change one material condition at a time where practical. Do not assume that a passing default state covers errors, overlays, orientation changes, interruptions or recovery.
Record this step

Decide

How to decide

Passed

The target contains a 24 by 24 CSS-pixel area or satisfies one documented normative exception using its exact decision condition.

Failed

The target is undersized and does not satisfy spacing, equivalent control, inline target, user-agent control or essential presentation.

Not applicable
No pointer input target exists in the selected subject.
Cannot tell
The active hit area, adjacency or an exception condition cannot be determined after reasonable inspection.
Not tested
The target is applicable, but a required state, environment, action or evidence item was not completed.
Aggregation and reporting boundaries

Aggregation: Preserve one result per target and material geometry state. Any failure prevents a passed aggregate; cantTell and untested remain unresolved.

WCAG decision: A WCAG 2.5.8 decision may be satisfied only after all applicable targets in the conformance scope and conformance requirements are considered. Inapplicable rule outcomes are not copied directly into that report decision.

Automation: Automation may find candidate dimensions, but a tester must verify actual hit areas, adjacency, irregular geometry and every exception. A passed automated or ACT result must never set the criterion to satisfied automatically.

Record

Record the result

Record the target, state and observed behaviour. Add evidence or technical details only when needed.

Choose the option that best matches what happened to this target.

Describe the actual behaviour and why it supports the selected result.

When more than one target is recorded, the overall procedure result is calculated from all target results.

Environment: Not set.
Add evidence or details

Choose only the group needed for this record. These fields remain optional for a working draft.

Evidence references

Enter one file name, issue ID or evidence reference per line. Files stay on your device.

Test environment

Save a named profile once to reuse the same product, platform and environment details on other procedures in this browser.

Engagement and tester identifiers

WCAG report decisions

These report-level decisions are separate from the target outcome and require complete declared-scope evidence.

Formal completion and limitations

Identify the frozen list or sampling record used to select every target represented by this execution.

Choose a final result before marking the execution complete. Completed records require the full environment, step, evidence and method-specific information.

Data management

Export before clearing if the record must be retained. Apply the engagement retention schedule and delete browser data when it is no longer needed.

Saved drafts stay in this browser and are not uploaded. Do not enter credentials, secrets or unnecessary personal data.

Reference

Supporting information

Standards and requirement mappings
  • W3C-WCAG22 · 2.5.8 conformance · full

    The 24 CSS-pixel requirement is a minimum. Larger targets may still be needed for usability and WCAG 2.5.5 is a separate Level AAA criterion.

  • W3C-WCAG22-QUICKREF · W3C-WCAG22-QUICKREF advisory · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

  • W3C-WCAG22-TECHNIQUES · W3C-WCAG22-TECHNIQUES advisory · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

  • W3C-TARGET-SIZE-MINIMUM · Understanding 2.5.8 advisory · supporting

    Understanding guidance is informative and does not add a WCAG conformance requirement.

Supporting and advisory guidance

Supporting sources are identified in the mappings and source register. They do not add conformance requirements.

Evidence specification
  • Target inventory

    Target identifiers, functions, pages, viewports and revealed states.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • Geometry measurement

    Active-area dimensions and bounding boxes in CSS pixels.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • Spacing calculation

    Circle centres, 12 CSS-pixel radii, neighbouring geometry and intersection result.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • Exception decision

    Named exception, condition and evidence for each exception used.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

Worked example and outcome calibration

A11Y-WCAG-040-WORKED-001: representative worked example

Context: Representative synthetic example for WCAG 2.5.8 Target Size (Minimum) on a fictional, version-frozen product target; no client or participant execution occurred.

Inspected: The tester follows S2 (Measure the target area) using the target, required state, tool and repeat rule stated in this procedure.

Observed output: After the tester completes the WCAG 2.5.8 Target Size (Minimum) scenario named Measure the target area, the recorded observation for the target is inconsistent with the required result: Each target is classified as at least 24 by 24 CSS pixels or undersized.

Evidence:

  • example-evidence-001: target and state record for Each author-controlled pointer input target, measured by its CSS-pixel target area and bounding box.
  • example-evidence-002: contemporaneous observation from the named method — Target bounding box, active-area dimensions, viewport and tool/version.
  • example-evidence-003: comparison note linking the actual observation to the expected result and claim boundary

Tester reasoning: The recorded observation does not demonstrate the expected result: Each target is classified as at least 24 by 24 CSS pixels or undersized. The failed decision is limited to this synthetic target and state; unexecuted coverage is not inferred.

Decision: failed

Finding: A11Y-WCAG-040-example-finding-001 — Measure pointer target size and spacing: expected result is not demonstrated. The represented barrier may affect People with hand tremors, limited dexterity or reduced fine-motor control.; People using touch, a stylus or a pointer in difficult conditions.

Remediation: Change the represented target or process so it demonstrates this result: Each target is classified as at least 24 by 24 CSS pixels or undersized. Then rerun the affected step and every dependent variation.

Reviewer feedback: The reviewer confirms applicability, environment, actual-versus-expected comparison, evidence references and bounded wording; unsupported product-wide or conformance language is removed.

Final client wording: Synthetic training finding: the sampled Measure pointer target size and spacing target does not meet the procedure expectation in the recorded state. User impact and broader scope require evidence from the buyer's real execution.

Retest: Synthetic retest example: after the represented change, repeat the failed step plus material error and recovery states. Close the finding only when new evidence demonstrates the expected result; otherwise retain the non-pass outcome.

Boundary: This is a representative, synthetic worked example for training and calibration. It is not evidence from a client product, participant or real assistive-technology execution.

Outcome calibration

Passed
A 20 by 20 CSS-pixel icon has a bounding-box-centred 24-pixel circle that intersects no target or other undersized-target circle.

The target passes through the exact spacing exception.

Failed
Two 20 by 20 CSS-pixel icon targets touch, so their 24-pixel circles intersect.

The targets fail size and spacing and no other exception applies.

Not applicable
A static article contains no pointer input target.

No target matches applicability.

Cannot tell
An embedded cross-origin control exposes no measurable hit area and ownership cannot be established.

The tester cannot determine the target geometry or responsibility defensibly.

Not tested
Portrait targets were measured, but the selected landscape layout was not tested.

A required responsive variation remains untested.

Passed
A small map pin is fixed to the only position that conveys the mapped location, with an evidence-backed essential-presentation decision.

This is a borderline exception example; the exception applies only to the pin geometry, not the rest of the map interface.

Sampling, complete processes and platform limitations

Test every in-scope instance when practical. For a large population, document a sample that includes each template, content or control type, meaningful state and high-risk task.

If this check is part of a user journey, test the selected journey from start to finish, including relevant errors and recovery. Record any path that was not tested.

  • Check relevant browser, tool or assistive-technology release notes before assigning unexpected behaviour to the product.
  • If responsibility is unclear, record the reproducible behaviour and use cannot tell until it is resolved.
Related procedures

No related procedure is recorded.

ACT rules and WCAG technique traceability

This is a project-authored manual procedure, not a W3C Approved ACT Rule. An ACT result can support only the part of this procedure covered by that rule. It does not replace the remaining manual or assistive-technology checks.

No supporting W3C Approved ACT Rule is selected for this procedure.

  • Understanding SC 2.5.8. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
Review history and source register
  1. 2026.08.27-rc.9 — Reworked for plain language, case-focused steps, scoped evidence and transparent draft review status.
  2. 2026.08.27-rc.9 — Migrated to professional catalogue schema v3 with separated outcomes, structured authority, applicability, evidence, decision and review records.
  3. 2026.08.27-rc.9 — Individually prepared WCAG 2.5.8 procedure content mapped to current normative and informative sources and checked for internal consistency; competent review, real execution and formal claim authority remain separate.
  4. 2026.08.27-rc.9 — Replaced migrated boilerplate with a case-specific reference implementation and completed generated-file integrity review.
  5. 2026.08.27-rc.9 — Added explicit preparation and variation/recovery steps plus a bounded representative worked example for paid-template use.
  6. 2026.08.27-rc.9 — Procedure guidance and presentation simplified without changing draft governance status.

Review decision: pending. Open issues: Independent standards review must confirm exception interpretation and the spacing fixture calculations before status promotion.

Source historyReport an accuracy issue
WCAG
SC 2.5.8
Execution
Manual test with tool support
Catalogue version
2026.08.27-rc.9