WCAG 2.1 AA explained for business owners: levels A, AA, and AAA, ten high-impact criteria, testing limits, remediation, and documentation.
WCAG 2.1 is a technical accessibility standard organized around content being perceivable, operable, understandable, and robust. Level A addresses foundational barriers, AA adds widely used requirements such as contrast and visible focus, and AAA is the most demanding level. JubilantWeb benchmarks remediation to WCAG 2.1 A and AA.
Published 2026-09-22 · Last updated 2026-09-22 · By Nelson Penagos, JubilantWeb
The Web Content Accessibility Guidelines provide testable criteria for digital content and interfaces. They translate broad accessibility goals into checks developers, designers, authors, and testers can use. The four principles are often summarized as perceivable, operable, understandable, and robust: users need to receive information, operate controls, understand content and behavior, and use compatible technologies.
The Department of Justice web accessibility guidance identifies WCAG as a helpful technical resource. DOJ’s guidance says businesses open to the public are covered by ADA Title III and that inaccessible web content can deny people with disabilities equal access. It does not turn a WCAG report into a DOJ certificate for a private business.
Level A criteria address foundational access. If a keyboard user cannot reach a control or a meaningful image has no alternative, an essential part of the experience may be missing. Level AA adds criteria that commonly affect practical use, including specified contrast thresholds, text resizing and reflow considerations, consistent behavior, error support, and visible focus.
Level AAA includes additional criteria with more demanding requirements. It is not simply a premium badge, and applying every AAA criterion across an entire site may not be practical for every kind of content. A scope statement should say which version, levels, pages, states, documents, and platforms were evaluated rather than using “WCAG” as an undefined label.
JubilantWeb benchmarks remediation work to WCAG 2.1 Level A and AA. WCAG 2.2 findings can be reported as additional items, but they are not silently folded into a claim about the 2.1 benchmark. This keeps the agreed scope understandable and avoids overstating what was tested.
This list is a practical orientation, not the whole standard. Relevant criteria depend on the page and task. A brochure site, ecommerce checkout, restaurant menu, patient portal, and streaming service expose different states and risks.
Begin with scope. Inventory page templates, essential user journeys, documents, media, and third-party components. Select representative pages and states, including mobile navigation, validation errors, open dialogs, account screens, search results, and checkout steps. A homepage-only review is not enough when the most important work happens elsewhere.
Automated checks are valuable for repeatable patterns such as some missing attributes, relationships, and contrast failures. Code inspection confirms how semantics and events are implemented. Keyboard testing reveals focus order, traps, hidden controls, and unexpected interactions. Screen-reader checks can show whether names, states, messages, and reading sequence make sense when presented audibly.
Human review also evaluates meaning. Software cannot consistently decide whether an image description serves the page’s purpose, whether instructions are clear, or whether a reservation flow is understandable. Testing should record the browser, device, assistive technology, steps, observed behavior, expected behavior, and criterion used.
No technical team should promise that passing a defined WCAG scope creates a universal legal status. DOJ points to WCAG as helpful technical guidance but does not provide a private-business certification in its web guidance. Legal duties and claim strategy should be discussed with qualified counsel.
That does not make WCAG optional as an engineering tool. A consistent benchmark helps teams find barriers, specify repairs, retest changes, and communicate what was covered. The accurate statement is that identified pages or components were evaluated and remediated against named WCAG 2.1 A and AA criteria within a stated scope—not that the work eliminates legal risk.
Prioritize by task impact, severity, reach, and frequency. A keyboard trap blocking checkout deserves urgent attention. A broken navigation component repeated on every page may outrank an isolated content issue. Missing access to a menu, appointment form, application, or contact method directly affects why customers visit.
Fix shared templates and components before chasing repeated page instances. Then repair content and documents, coordinate external vendor work, and retest the complete journey. Record dependencies honestly. If a third party owns a booking tool, document the finding, vendor communication, interim route, and later verification.
A remediation record should identify each barrier, affected location, criterion, repair, date, and verification result. Separate automated, keyboard, code, and assistive-technology checks. Note unresolved limitations and do not transform a scoped result into a certificate. An accessibility statement can describe the organization’s ongoing effort and provide a monitored feedback channel.
Monitoring matters because websites change. New images may lack alternatives, new plugins may alter focus, and updated forms may lose labels. Recheck after releases and on a schedule suited to the site’s update frequency. A documented process is more informative than a badge with no scope.
Identify the top customer tasks and request an initial review. JubilantWeb offers WCAG 2.1 AA remediation for Florida businesses starting at $2,449, with monitoring from $49 per month. Deliverables can include code and content repairs, testing notes, statement support, and a remediation record, depending on scope.
You can request a free accessibility scan. The page currently collects requests and is not an instant scan engine, so it does not promise immediate results. The review is a starting point rather than a complete manual audit, legal opinion, independent certification, or guarantee against a claim.
IRS Form 8826 describes a nonrefundable Disabled Access Credit for eligible small businesses with eligible access expenditures. Eligibility requires prior-year gross receipts not exceeding $1 million or no more than 30 full-time employees. The form subtracts $250, caps eligible expenditures used in the calculation at $10,000, and applies 50%, for a maximum form credit of $5,000 subject to its rules.
Eligibility depends on both the taxpayer and the expenditure. Do not assume an audit, remediation project, or monitoring plan qualifies. Use the current IRS materials and ask a qualified tax professional to evaluate the specific expense.
We review the submitted site and return a plain-English summary. This is a request for review, not an instant public scanner or legal advice.
It is a technical benchmark combining foundational Level A criteria with Level AA requirements that address practical access, including contrast, focus, resizing, forms, and consistent interaction. It helps teams test and repair websites, but it is not a private-business legal certificate.
WCAG 2.2 is a later version that adds criteria and makes limited changes to the earlier standard. JubilantWeb benchmarks contracted remediation to WCAG 2.1 A and AA and can report 2.2 findings separately, so the tested scope remains clear.
No. Automation finds some repeatable code patterns, but many criteria require human judgment, interaction, or context. Combine automated checks with keyboard use, code inspection, screen-reader review, visual review, and complete task testing across relevant pages and states.
AAA contains additional, more demanding criteria and is not automatically the right whole-site target for every organization or content type. Define the applicable scope with technical and legal advisers. JubilantWeb’s stated remediation benchmark is WCAG 2.1 A and AA.
A useful audit includes third-party components in essential journeys, even when another vendor controls the code. Test the experience, document barriers and ownership, report issues to the provider, and offer an effective alternative where possible. Scope and dependencies should be explicit.
It depends on templates, issue severity, platform access, documents, integrations, and the number of essential journeys. A small brochure site and a custom checkout are not equivalent. Establish scope after review, prioritize blockers, and document staged repairs instead of promising a universal timeline.