The WCAG 2.1 Default Findings Engine is a requirement-aware template layer for Web Content Accessibility Guidelines (WCAG) 2.1. 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.1 includes applicable WCAG 2.0 criteria and adds requirements that improve coverage for mobile experiences, people with low vision, and people with cognitive and learning disabilities. The project target still controls whether Level A, AA, or AAA criteria are available, while WCAG 2.2-only criteria remain outside scope.
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.1 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 the project version and A, AA, or AAA target.
- Open the WCAG 2.1 local engine and locate the precise inherited or 2.1-specific criterion.
- Describe the reusable user-facing failure without naming one client or page.
- Add remediation that states the accessible outcome and leaves room for the product architecture.
- Save the local default and verify that its criterion mapping is retained.
- Select it in a test project and add page, component, device, and assistive-technology evidence.
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
- 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.
Use a default in a project
Open New Finding inside a project configured with WCAG 2.1. 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 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.