Skip to content

Customize WCAG 2.2 Default Findings

Create, edit, and safely use reusable WCAG 2.2 findings in your local Default Findings Engine.

Repeated findings are useful only when they stay accurate. The WCAG 2.2 Default Findings Engine lets an authorized team leader or admin save a reusable starting point against a canonical success criterion. It reduces repeated typing while leaving the actual observation, evidence, scope, and validation inside each project finding.

What this solves

Modern product audits repeatedly find inaccessible authentication, hidden focus indicators, small pointer targets, dragging-only controls, and repeated-entry barriers. Copying old tracker text creates vague findings, while raw automated wording can include selectors and technical fragments that do not explain the human impact or produce polished report remarks.

Before you begin

  • Sign in as a team leader or team admin with access to the local engine.
  • Confirm that WCAG 2.2 is the correct Library for the work.
  • Choose a recurring issue pattern, not one client-specific finding.
  • Remove names, URLs, selectors, credentials, personal data, dates, and evidence from the reusable wording.
  • Keep the official Web Content Accessibility Guidelines (WCAG) 2.2 scope and terminology available for reference.

Step-by-step

  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.

What the default saves

A local default can save the summary, description, remediation guidance, severity behavior, and canonical success criterion mapping. When a reviewer selects it from New Finding, voiqq prefills those values. The new finding still starts Open with Pending validation and must be changed to match the real observation.

Good patterns to predefine

  • 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.

Check your result

  • 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.

Open the WCAG 2.2 engine

Read the technical guide

How to customize WCAG 2.2 default findings | voiqq