1. Which version and conformance level of WCAG does the product currently conform to (e.g., WCAG 2.1 AA, WCAG 2.2 AA), and what is the scope of that conformance claim (which interfaces, user roles, and product modules are included)?
Why it matters. A 'WCAG compliant' claim that omits the version, level, or covered parts of the product cannot be checked. Buyers need an explicit version/level/scope statement to map vendor conformance to their own legal obligations under ADA, EAA, and Section 508.
- Names a specific WCAG version (2.1 or 2.2) and level (A or AA)
- Identifies which user interfaces are in-scope (admin console, end-user UI, mobile, embedded widgets)
- Distinguishes conformance status across modules rather than making a blanket claim
- Generic 'WCAG compliant' with no version or level
- Scope is silent on admin interfaces, mobile, or AI chat surfaces
- Conformance claim attributed only to internal self-assessment with no date