Skip to content

Customize WCAG 2.0 Default Findings

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

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

Organizations maintaining older contractual or policy obligations often repeat the same accessibility barriers across products. Auditors may rewrite missing text alternatives, keyboard failures, form-label issues, contrast failures, and parsing observations differently in every engagement. That variation makes review slower and can accidentally mix newer WCAG requirements into a WCAG 2.0 report.

Before you begin

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

Step-by-step

  1. Confirm that WCAG 2.0 is the version required by the engagement.
  2. Open the WCAG 2.0 local Default Findings Engine from Admin.
  3. Search for the exact success criterion rather than a broad accessibility topic.
  4. Add a neutral summary, reusable description, and outcome-based remediation guidance.
  5. Review the automatically mapped severity, Open status, and Pending validation state.
  6. Create a test finding from the template and adapt it to the observed page and user impact.

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

  • Missing text alternatives for meaningful images, icons, or controls under 1.1.1.
  • Keyboard access failures where an interactive control cannot be reached or operated under 2.1.1.
  • Form controls whose visible purpose is not programmatically identified under 1.3.1 or 3.3.2.
  • Insufficient text contrast under 1.4.3, documented with the measured colors and affected content.
  • Page titles, focus order, labels, names, roles, and status messages described in user-facing language.

Check your result

  • Do not mention WCAG 2.1 or 2.2-only behavior in a WCAG 2.0 default.
  • Keep selectors, page names, user data, and measurements out of the reusable template.
  • Map the smallest accurate set of success criteria.
  • Use the project finding for actual evidence and reproduction details.
  • Retest before changing validation from Pending.

Open the WCAG 2.0 engine

Read the technical guide

How to customize WCAG 2.0 default findings | voiqq