The WCAG 2.0 Default Findings Engine is a requirement-aware template layer for Web Content Accessibility Guidelines (WCAG) 2.0. 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.0 established testable Level A, AA, and AAA success criteria under the principles Perceivable, Operable, Understandable, and Robust. A WCAG 2.0 project must stay limited to criteria in that version and the selected target level. Later WCAG 2.1 and 2.2 criteria should not enter the project merely because they exist in a newer library.
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.0 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
- Confirm that WCAG 2.0 is the version required by the engagement.
- Open the WCAG 2.0 local Default Findings Engine from Admin.
- Search for the exact success criterion rather than a broad accessibility topic.
- Add a neutral summary, reusable description, and outcome-based remediation guidance.
- Review the automatically mapped severity, Open status, and Pending validation state.
- Create a test finding from the template and adapt it to the observed page and user impact.
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
- 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.
Use a default in a project
Open New Finding inside a project configured with WCAG 2.0. 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
- 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.