Professional review status
No professional domain review recorded
This bundle covers regulatory subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.
Review before reliance: A qualified compliance professional appropriate to the question, decision, organization, and jurisdiction.
Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.
Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Overview
WCAG Overview
Defines the source scope, applicability framing, and safety boundaries for WCAG accessibility compliance work.
Read the fileWorkflow
WCAG Accessibility Triage
source-backed workflow for turning a WCAG question into an evidence-backed accessibility brief.
Read the fileTemplate
source-backed WCAG Brief
Output format for WCAG answers that must separate W3C/WAI source facts, user evidence, assumptions, missing verification, and review needs.
Read the fileQuality rubric
WCAG source verification Check
Rubric for checking whether a WCAG answer is source-backed, cautious, and suitable for professional review.
Read the fileIs this bundle right for your task?
Who it is for
- Compliance, legal, risk, security, operations, and product teams assessing WCAG (Web Content Accessibility Guidelines)
- Teams working in cross-industry
When to use it
- A WCAG (Web Content Accessibility Guidelines) question needs to be scoped to the correct rule, guidance, regulator, date, and affected entity.
- A draft conclusion needs its stated facts, missing evidence, source citations, and professional-review handoff checked.
What you need to provide
- The jurisdiction, entity and relationship facts, applicable dates, exact question, and accountable professional reviewer.
- Current official sources plus the policies, contracts, records, system evidence, and missing facts relevant to the situation.
Tasks and expected outputs
Questions it helps answer
- Triage WCAG questions without inventing conformance or legal conclusions.
- Separate W3C/WAI source facts, user-provided product evidence, assumptions, and missing verification.
- Produce source-backed WCAG accessibility briefs for professional review.
What it helps produce
- source-backed WCAG brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the jurisdiction, entity and relationship facts, applicable dates, exact question, and accountable professional reviewer. Ask the agent to assess WCAG (Web Content Accessibility Guidelines) and draft source-backed WCAG brief that separates stated facts, assumptions, missing evidence, relevant source sections, and actions requiring professional approval. Begin with W3C/WAI WCAG 2 Overview, then confirm that the reference is current and applicable. Inspect WCAG Overview before drafting.
Context path: bundles/compliance/wcag
What the bundle includes
Frameworks
- POUR source-evidence matrix
- conformance target triage
- accessibility evidence separation
Evaluations
- WCAG source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Final legal or compliance conclusions, filings, notices, or operational changes without current source review and accountable professional approval.
Known limitations
- This bundle is a compliance hub, not legal advice or a WCAG certification.
- Scenario-specific answers require current W3C/WAI source inspection, a defined conformance target, product scope, test method, and user-provided evidence.
- Jurisdiction-specific legal obligations, procurement requirements, VPAT/ACR claims, and tool-specific scanner findings must be inspected separately before reliance.
Safety notes
- Require qualified accessibility, legal, compliance, or procurement review before relying on outputs for regulatory, contractual, litigation, public conformance, or procurement decisions.
- Do not claim that a product conforms to WCAG from incomplete scanner output or unsupported assumptions.
- Require explicit confirmation before publishing accessibility statements, submitting VPAT/ACR materials, changing live products, or sending legal/compliance communications.