What this FAQ covers
This page answers recurring questions about web accessibility for website owners, agencies, and technical teams. The answers define practical boundaries, identify the evidence that matters, and explain when a question requires account-specific, technical, contractual, or legal review.
- What is WCAG?
- Which version should I use?
- Can an automated scan prove WCAG conformance?
- What does keyboard accessible mean?
Use the answers responsibly
Apply each answer to the actual website, scope, agreement, and evidence. Avoid claiming conformance from an automated scan alone. When the decision could affect production availability, security, accessibility, billing, privacy, or contractual commitments, document the responsible reviewer and verification plan.
Questions and answers
01What is WCAG?
The Web Content Accessibility Guidelines are an international W3C standard for making web content more accessible to people with disabilities.
02Which version should I use?
W3C encourages use of the latest WCAG 2 version. Review contractual and legal requirements separately.
03Can an automated scan prove WCAG conformance?
No. Automation can detect some failures and indicators, but many success criteria require human and assistive-technology evaluation.
04What does keyboard accessible mean?
A person can reach, operate, understand, and leave interactive components using a keyboard without becoming trapped.
05Do charts need text alternatives?
Complex charts need accessible names and usually a summary, data table, or equivalent explanation of the meaningful information.
06Is color contrast enough?
No. Accessibility also includes structure, names, roles, values, focus, keyboard use, media, forms, errors, timing, motion, cognition, and task completion.
07What should happen after a fix?
Retest the specific rule, component, assistive-technology interaction, and user task.
Turn web accessibility into an accountable record.
A clear, supportable answer set for web accessibility linked to the relevant workflow or policy.