Skip to content

Customize WCAG 2.1 Default Findings

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

Repeated findings are useful only when they stay accurate. The WCAG 2.1 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

Responsive products often repeat orientation, reflow, text spacing, input purpose, pointer gesture, motion activation, and status-message problems. When consultants describe the same pattern differently across engagements, engineering teams receive inconsistent instructions and report reviewers spend time normalizing language instead of checking evidence.

Before you begin

  • Sign in as a team leader or team admin with access to the local engine.
  • Confirm that WCAG 2.1 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.1 scope and terminology available for reference.

Step-by-step

  1. Confirm the project version and A, AA, or AAA target.
  2. Open the WCAG 2.1 local engine and locate the precise inherited or 2.1-specific criterion.
  3. Describe the reusable user-facing failure without naming one client or page.
  4. Add remediation that states the accessible outcome and leaves room for the product architecture.
  5. Save the local default and verify that its criterion mapping is retained.
  6. Select it in a test project and add page, component, device, and assistive-technology evidence.

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

  • Orientation restrictions that prevent use in a supported device orientation under 1.3.4.
  • Content loss or two-dimensional scrolling at the required reflow viewport under 1.4.10.
  • Loss of content or function after applying the text-spacing settings in 1.4.12.
  • Multipoint or path-based gestures without a single-pointer alternative under 2.5.1.
  • Dynamic status information that is not announced without moving focus under 4.1.3.

Check your result

  • Do not map a mobile symptom to a broad criterion when a specific 2.1 criterion applies.
  • Keep viewport sizes, devices, and tested values in the project finding.
  • Use plain language that remains useful to designers and engineers.
  • Confirm the template does not introduce WCAG 2.2-only criteria.
  • Treat the default as a starting point that remains Pending until validated.

Open the WCAG 2.1 engine

Read the technical guide

How to customize WCAG 2.1 default findings | voiqq