You asked us and we answered. Here are 15 questions that we get from everyone, especially new prospective clients.
Table of Contents
What is a WCAG accessibility audit?
A formal evaluation of your digital asset against Web Content Accessibility Guidelines (WCAG 2.1 AA or 2.2 AA).
An accessibility audit identifies every instance where your website, app, or software doesn’t meet WCAG requirements. Accessible.org audits use screen reader testing, keyboard testing, visual inspection, and code review to find all issues. The audit report details each issue with its location, the WCAG criterion it violates, and specific remediation recommendations.
How much does a WCAG audit cost?
Between $1,500 and $3,500 for most websites, with primary pages costing $100-$250 each and lighter pages ranging from $25-$100.
Cost primarily depends on three factors: number of pages in scope, complexity of interactive elements, and current accessibility status. Simple informational sites cost less than complex e-commerce platforms. Accessible.org audits include desktop evaluation with optional mobile testing. The price tracks directly with the time needed for thorough manual evaluation.
What’s the difference between an audit and a scan?
Audits are formal (manual) evaluations by experts; scans are automated tools that flag a limited number of issues by scanning code using rule sets.
Automated scans only flag about 25% of WCAG success criteria. They cannot evaluate user experience, meaningful alternatives, or proper structure. Accessible.org conducts fully manual audits where experts use screen readers, keyboard testing, and visual inspection. Scans serve as a secondary check, never the primary evaluation method.
How long does an accessibility audit take?
Accessibility audits typically take 1-2 weeks to complete for digital assets with a standard scope (e.g., 10-20 pages/screens).
The audit itself takes 10-15 days. After receiving your report, remediation time depends on issue count and team capacity. Using Accessibility Tracker to manage fixes speeds this process. Validation follows remediation, then certification documentation if you’ve reached full WCAG conformance.
Do I need both desktop and mobile audits?
Yes, if your audience accesses your digital asset using both mobile and desktop environments.
Desktop audits cover 70% of accessibility issues; add mobile for comprehensive accessibility across all devices.
What WCAG version should I use?
WCAG 2.1 AA is the technical standard necessary for compliance with nearly all laws and regulations. WCAG 2.2 AA is increasingly being referenced and required in the marketplace.
WCAG 2.1 AA is incorporated into ADA Title II and provides robust accessibility. Version 2.2 AA adds six new success criteria. WCAG conformance is a heuristic for European Accessibility Act (EAA) material compliance. WCAG 2.2 AA mean more criteria to evaluate, but better accessibility.
How can I track remediation progress after an audit?
Upload your audit spreadsheet to Accessibility Tracker for organized tracking and validation. Or use the spreadsheet itself to track issues manually.
The platform tracks which issues are fixed, assigns them to team members, and lets auditors validate corrections. Built-in AI tools also explain each issue and help guide remediation with code emaxamples.
What makes an audit “fully manual”?
Human experts evaluate every element using multiple methodologies, not automated tools.
Manual audits involve screen reader testing with NVDA or JAWS, keyboard navigation testing, visual inspection, code review, and zoom testing at 200% and 400%. Accessible.org auditors are accessibility experts who meticulously evaluate each page. Automated results only serve as a final review check.
How do I know which issues to fix first?
Use risk-based or impact-based prioritization to address critical issues immediately.
Accessibility Tracker provides two formulas: Risk Factor prioritizes based on lawsuit frequency data, while User Impact scores issues by how severely they block access. Fix issues that completely prevent access before those with workarounds. Focus on your most-visited pages and primary user flows.
What’s included in an audit report?
Issue description, location, WCAG criterion violated, code snippets, screenshots, and fix recommendations.
Each issue gets documented with steps to reproduce, the specific element affected, applicable WCAG requirements, and clear remediation guidance. Accessible.org reports come as Excel spreadsheets listing all details your developers need. Reports also include evaluation methodologies, environments tested, and standards used.
Do audits include user testing?
No, audits evaluate WCAG conformance; user testing is a separate service.
Audits comprehensively identify all WCAG non-conformance through technical evaluation. User testing involves people with disabilities using assistive technology to test real-world usability. User testing best serves as a supplement after audit remediation, catching nuanced issues technical evaluation might miss.
Are Shopify accessibility audits different?
Yes and no. We take the same approach, but Shopify stores definitely follow a common pattern.
E-commerce platforms like Shopify have unique complexities: product galleries, shopping carts, checkout flows, and third-party apps. Each element needs evaluation. Theme customizations often introduce accessibility issues. Accessible.org audits evaluate your complete Shopify implementation including all customer-facing functionality.
How do I get WCAG certification?
Complete an audit, fix all issues, validate fixes, then receive certification documentation.
Certification requires full WCAG conformance for your defined scope – no exceptions. After your audit identifies issues, remediation brings you into conformance. Validation confirms all fixes work correctly. Then you receive Accessible.org certification, conformance statements, or VPAT/ACR documentation.
What if my site constantly changes?
Quarterly audits for frequently updated sites; annual for stable ones.
Websites with regular content updates, new features, or design changes need periodic re-auditing. Phase your audits by rotating through different page sets. Accessibility Tracker helps track ongoing fixes between audits. Build accessibility into your development process to maintain conformance.
Can AI replace manual audits?
No, AI cannot evaluate context, meaning, or user experience required for WCAG conformance.
AI tools cannot determine if alt text meaningfully describes images, if error messages are clear, or if content structure makes sense. These require human judgment. WCAG conformance demands understanding intent and context. Accessible.org’s manual approach ensures every issue gets identified correctly.
Bonus FAQ
Q: How do I choose pages for my audit scope?
A: Include your homepage, primary user flows, unique layouts, and most-trafficked pages. For larger sites, 10-20 pages typically cover the main templates and functionality.
Q: Can I use my audit for ADA compliance?
A: Yes, WCAG 2.1 AA conformance demonstrates good faith effort toward ADA compliance and is the recognized standard for digital accessibility.
Q: What’s the difference between WCAG levels A, AA, and AAA?
A: Level A provides basic accessibility, AA removes major barriers (industry standard), and AAA offers enhanced accessibility but isn’t required for conformance.
Q: Should I audit before or after a redesign?
A: After, unless you’re auditing to inform the redesign. Auditing the old version wastes resources if everything will change.
