Skip to content

WCAG 2.2 Default Findings Engine

Understand how reusable WCAG 2.2 findings are mapped, inherited, customized, and used without changing existing project evidence.

The WCAG 2.2 Default Findings Engine is a requirement-aware template layer for Web Content Accessibility Guidelines (WCAG) 2.2. It helps a team define consistent starting language for recurring findings while the normal project remains the source of truth for scope, evidence, ownership, remediation progress, validation, and reports.

Library and standards scope

WCAG 2.2 is the current WCAG recommendation supported by voiqq and includes inherited WCAG 2.0 and 2.1 requirements plus criteria for focus appearance, dragging alternatives, target size, consistent help, redundant entry, and accessible authentication. The chosen A, AA, or AAA level determines which criteria belong to the project and its VPAT or ACR snapshot.

Global, local, and project layers

  • Global defaults are standards-based templates published by voiqq platform owners for a system Library.
  • Local defaults belong to the signed-in workspace administrator and can override editable wording without changing the global source.
  • A project finding receives copied template values and then becomes an independent record.
  • Later global changes do not silently rewrite a local override or a finding already created in a project.
  • Status is Open and validation is Pending when the reusable default is applied, unless an authorized project workflow later changes them.

Fields and canonical mapping

Each template is owned by a canonical success criterion in the WCAG 2.2 Library. The reusable record contains a stable identifier, summary, description, remediation guidance, severity key, mapped values, source Library, and display order. The visible wording can be edited locally, while the background requirement identity continues to support filters, reports, imports, and New Finding suggestions.

Create or customize a default

  1. Choose the WCAG 2.2 Library and confirm the project target level.
  2. Open the local engine, search by success-criterion number or title, and expand it.
  3. Create a concise default summary that names the reusable accessibility barrier.
  4. Write a description around user impact and expected accessible behavior.
  5. Add remediation guidance that is useful without prescribing one framework-specific patch.
  6. Test the default in New Finding and confirm that VPAT-required mappings remain accurate.

Writing rules for reusable findings

Write the summary as a concise statement of the recurring failure. Use the description to explain the expected behavior, likely impact, or control concern in neutral language. Use remediation to describe the desired outcome rather than a patch tied to one framework or customer. Store actual results, reproduction steps, affected assets, evidence, people, dates, measurements, samples, and environment details in the project finding.

Suitable template subjects

  • Focus indicators that are obscured, too small, or too low contrast under the applicable 2.4 criteria.
  • Dragging interactions without a non-dragging pointer alternative under 2.5.7.
  • Interactive targets that do not meet the applicable target-size requirement under 2.5.8.
  • Previously supplied information that must be entered again without an allowed exception under 3.3.7.
  • Authentication that depends on a cognitive function test without an accessible alternative under 3.3.8 or 3.3.9.

Use a default in a project

Open New Finding inside a project configured with WCAG 2.2. Choose Template mode or select a prepared template after choosing the applicable success criterion. voiqq prefills the reusable values. Review every field, add the real evidence and context, and save the finding. Comments, attachments, assignments, history, validation, sharing, exports, and reports then use the same normal project workflow.

Accuracy and safety checks

  • Keep client names, URLs, selectors, and raw scanner text out of defaults.
  • Do not state conformance inside a reusable finding.
  • Use affected elements and actual results for instance-specific evidence.
  • Confirm 4.1.1 Parsing is handled by the WCAG 2.2 reporting rules rather than a new default.
  • Review every generated report row even when a default was used.

Review the standards source

Open the WCAG 2.2 engine

Explore the Library guide

WCAG 2.2 Default Findings Engine documentation | voiqq