Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWeb accessibility means making websites, apps, documents, and digital services usable by people with disabilities. To get started, target WCAG 2.2 Level AA for new work unless a law, contract, or policy says otherwise, then test core tasks with automated tools, a keyboard, zoom, and a screen reader.
Accessibility is not a score, an overlay, or a one-time scan. It is the practical work of ensuring that people can perceive information, navigate pages, operate controls, understand content and feedback, and complete important tasks such as finding information, booking an appointment, buying an item, or submitting a form.
Key takeaways
- WCAG 2.2 Level AA is the practical modern target for most new web projects, but applicable law, procurement rules, contracts, and internal policies may require a different version or scope.
- The highest-impact first fixes are keyboard access, visible focus, meaningful structure, usable forms, useful alternative text, adequate contrast, captions, and content that works at 200% zoom.
- Automated tools can find some detectable problems, including missing labels, certain contrast failures, invalid ARIA, and duplicate IDs, but no tool alone can prove that a website is accessible.
- A useful first audit covers core user journeys—not just the homepage—with keyboard testing, zoom and reflow checks, screen-reader testing, and human review.
- Accessibility is shared by designers, developers, writers, content editors, product managers, QA teams, procurement staff, vendors, and support teams.
What is web accessibility?
Web accessibility is the practice of designing and developing websites, applications, documents, and digital services so people with disabilities can perceive, navigate, operate, and understand them. Accessibility supports people with blindness or low vision, deafness or hearing loss, mobility or motor impairments, cognitive or learning disabilities, speech disabilities, and neurological disabilities.
Accessibility also matters when a limitation is temporary or situational. Someone with a broken arm may need keyboard access instead of a mouse. Someone in bright sunlight may struggle to distinguish low-contrast content. Someone in a noisy environment may need captions. Someone on a slow connection may need a page that does not depend on a large, complicated interface.
#1 Best Overall
People do not all experience the same disability in the same way, and not every person with a disability uses a screen reader. The goal is not to create an identical experience for every visitor. The goal is to provide equivalent access to information, controls, feedback, and tasks through appropriate combinations of text, semantics, keyboard operation, captions, visual design, and assistive technology.
What are the four WCAG principles?
The Web Content Accessibility Guidelines (WCAG) principles describe four broad requirements:
- Perceivable: Users can detect information and controls, such as through text alternatives, captions, sufficient contrast, and adaptable layouts.
- Operable: Users can interact with controls and navigation using the input methods they need, including a keyboard.
- Understandable: Content, instructions, forms, and interface behavior are predictable and comprehensible.
- Robust: Content works reliably across browsers and with assistive technologies.
What should you do first for web accessibility?
Start with the user journeys that matter most, not with a promise to fix every WCAG success criterion immediately. Choose one important journey—such as searching for information, contacting your organization, logging in, booking an appointment, purchasing a product, or submitting an application—and test that journey from beginning to end.
A 30-minute first pass can expose serious barriers:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Choose one core task and open the pages involved, including login, checkout, booking, or confirmation screens where relevant.
- Run an automated check on the pages with a tool such as axe DevTools, WAVE, Lighthouse, or another tool from the W3C evaluation tools directory.
- Put the mouse aside and use Tab, Enter, Space, arrow keys, and Escape to complete the task.
- Zoom the browser to 200% and check whether text, controls, menus, dialogs, and forms remain usable.
- Record blockers with the URL, steps, expected result, actual result, affected task, owner, and proposed fix.
This first pass is triage, not certification. A clean result is a reason to continue testing, not evidence that the site has no accessibility barriers.
Which WCAG standard should a beginner follow?
WCAG 2.2 Level AA is the practical modern benchmark for most new web work. The W3C WCAG 2.2 recommendation is the current W3C recommendation, and W3C advises using WCAG 2.2 to maximize future applicability.
Check requirements that apply to your situation before choosing a target. A law, public-sector rule, procurement requirement, contract, customer requirement, or organizational policy may specify WCAG 2.1, WCAG 2.2, a particular conformance level, or additional requirements.
| WCAG level | Meaning | Practical use |
|---|---|---|
| Level A | Minimum conformance requirements. | A baseline, but usually not a sufficient accessibility program by itself. |
| Level AA | A broader set of important accessibility requirements. | The usual practical target for a website or application. |
| Level AAA | More demanding criteria, some of which cannot reasonably apply to all content or situations. | Use selectively for particular audiences, content, or organizational goals rather than treating AAA as a universal site-wide target. |
The WCAG Quick Reference is the most useful working checklist because it can be filtered by role, technology, topic, and conformance level. “WCAG compliant” is not a universal legal status, and meeting a technical standard does not automatically settle every legal question.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Web accessibility checklist: what should you check?
Content and structure
Clear content structure helps people using screen readers, keyboard navigation, browser features, magnification, and cognitive strategies. Check that every important page has:
- One clear, descriptive page title.
- Headings arranged in a meaningful hierarchy.
- Headings used for structure, not merely to make text look larger.
- Descriptive link text that explains the destination or purpose.
- Lists marked up as lists and data tables marked up as tables.
- Concise language and explanations for unusual terms.
- Instructions provided before users need to act.
- Important information available as text instead of only inside an image or video.
Inspect the page with a screen reader or accessibility tree and ask whether the page title, headings, landmarks, links, buttons, and reading order make sense without relying on visual position.
Images and alternative text
Alternative text should communicate an image’s purpose or meaningful information, not serve as an SEO keyword field. An informative image needs concise, useful alt text. A purely decorative image should generally have empty alternative text, written as alt="", so assistive technology can skip it.
Do not use filenames such as IMG_4821.jpg, keyword stuffing, or generic descriptions. Do not repeat nearby text when the surrounding text already supplies the image’s complete meaning. Charts, diagrams, maps, and instructional images may need the important information in surrounding text or a longer description. Human review is required for AI-generated image descriptions before publication.
Rank #2
<img src="staff.jpg" alt="Jordan Lee, customer support manager"><img src="divider.svg" alt="">The WCAG non-text content requirements explain when text alternatives are required and describe exceptions for decorative, redundant, and user-control content.
Keyboard access and focus
Every interactive function must work without a mouse. The safest starting point is native HTML: use <button> for actions, <a href="..."> for navigation, and native form controls for inputs and selections.
- Make every interactive item reachable by keyboard.
- Keep the tab order logical and consistent with the page’s visual and reading order.
- Make keyboard focus clearly visible.
- Do not let focus disappear behind a sticky header.
- Do not trap focus inside a component unless the component is a deliberately managed modal dialog.
- Provide a way to bypass repeated navigation, such as a skip link.
- Give menus, accordions, tabs, carousels, date pickers, dialogs, and custom widgets expected keyboard behavior.
- Do not make a clickable
<div>or<span>when a native button or link is appropriate.
WCAG keyboard requirements cover keyboard operation, while the focus-visible, focus-order, and bypass-blocks criteria address common navigation and focus failures.
Color, contrast, and non-color cues
Do not use color as the only way to communicate an error, category, required field, selected state, or status. A form error should include text and an association with the relevant field, not only a red border.
Check normal text, large text, controls, icons, borders, focus indicators, links, placeholders, disabled states, hover states, selected states, and error states. A page can have acceptable default contrast while failing when focus, validation, or selected states appear. The WCAG contrast minimum, use of color, and non-text contrast criteria cover different parts of this problem.
Forms and error recovery
Accessible forms tell users what information is needed, what format to use, which fields are required, and how to recover when submission fails.
- Give every input a programmatically associated label.
- Do not use placeholder text as the only label.
- Identify required fields in text and programmatic markup where appropriate.
- Use
<fieldset>and<legend>for related groups of controls. - Explain formats, limits, and required information before submission.
- Associate error messages with the relevant field.
- Identify errors with text, not just color or an icon.
- Preserve entered data when validation fails where practical.
- Use appropriate autocomplete tokens.
- Explain password requirements and other constraints before the user submits.
<label for="email">Email address</label>
<input id="email" name="email" type="email" autocomplete="email">Test the failure path deliberately. Submit an empty form, enter an invalid email address, exceed a character limit, correct one field at a time, and confirm that the user can identify and reach every error. WCAG’s input assistance requirements cover labels, instructions, error identification, suggestions, and error prevention.
Responsive design, zoom, and reflow
Test the site at 200% browser zoom, narrow desktop widths, and mobile widths. The page should remain usable rather than merely technically present.
Free tools Windows power users keep installed
One-click scans. No signup required.
Look for clipped text, overlapping controls, inaccessible horizontal scrolling, menus that disappear, dialogs larger than the viewport, fixed-height containers that cut off expanded text, and focused elements hidden behind sticky headers. Also test increased text spacing and larger system text where relevant. The WCAG reflow and text spacing requirements are useful references.
Audio and video
Prerecorded video with speech needs accurate captions. Depending on the content, users may also need a transcript, audio description, or an equivalent alternative for important visual information.
- Review automatically generated captions for accuracy, speaker changes, punctuation, and important sounds.
- Provide transcripts where they improve access to the content.
- Describe important visual information through audio description or an equivalent text alternative.
- Do not autoplay audio.
- Make media controls keyboard accessible and give controls meaningful names.
These requirements are addressed in the WCAG time-based media guidance.
Dynamic content, motion, and status messages
Users need to discover changes that sighted mouse users may notice immediately. Check cart updates, form errors, loading states, save confirmations, search results, and success messages.
Recommended Free Tools
- Announce or otherwise expose important status messages without forcing users to search the page.
- Move focus appropriately when a dialog opens, and return focus to the triggering control when the dialog closes.
- Do not refresh or change content unexpectedly.
- Give users control over carousels, animations, and time limits.
- Respect reduced-motion preferences where appropriate.
- Avoid flashing content that could trigger seizures or physical reactions.
Review the status messages, timing adjustable, animation from interactions, and seizures and physical reactions guidance when testing dynamic interfaces.
How do you test a website for accessibility?
A credible basic evaluation combines automated checks, keyboard testing, zoom and reflow testing, screen-reader testing, and human review. Perform the tests on representative pages and complete workflows rather than scanning only the homepage.
1. Define the scope
Include the homepage, main navigation, search, contact or lead form, login and account recovery, checkout or booking flow, important content templates, high-traffic pages, high-risk pages, PDFs, and third-party integrations. Include mobile app screens when a native app is part of the service, and distinguish native-app testing from mobile-web testing.
2. Run automated checks
Automated tools can identify some programmatically detectable issues, such as missing labels, missing or suspicious alt text, certain contrast failures, invalid ARIA, duplicate IDs, and some landmark or heading problems.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallPossible starting points include the axe DevTools browser extension, WAVE, Lighthouse, browser accessibility tools, and other tools listed by W3C. W3C maintains a directory but does not endorse specific products.
Automated testing cannot reliably determine whether instructions are understandable, alt text communicates the right purpose, keyboard focus follows a sensible order, errors are recoverable, a custom widget behaves correctly, dynamic updates are discoverable, or a person can complete the core task. W3C states that no tool alone can determine whether a site meets accessibility standards; knowledgeable human evaluation is required.
3. Test the complete journey with a keyboard
- Unplug or ignore the mouse.
- Press Tab repeatedly and confirm that every interactive item receives focus.
- Confirm that focus is visible and follows a logical order.
- Use Enter and Space where expected.
- Use arrow keys for components such as tabs, menus, or date pickers where that interaction is expected.
- Use Escape to close dialogs, menus, or other dismissible interfaces where appropriate.
- Open menus, submit forms, trigger validation, operate accordions and carousels, change quantities or dates, and reach footer links.
- Confirm that focus is not trapped, lost, or hidden behind fixed page elements.
- When a dialog closes, confirm that focus returns to the control that opened it.
4. Test with a screen reader
For a beginner-level representative test, use NVDA on Windows and VoiceOver on macOS or iOS. Add JAWS, TalkBack, or mobile-browser combinations when the audience, platform, or risk justifies broader coverage.
Do not simply turn on a screen reader and listen to the page from beginning to end. Use headings, landmarks, links, form controls, and reading-order commands in the way a user navigates. Check whether:
- The page title is announced and identifies the page.
- Headings and landmarks provide useful navigation.
- Links and buttons have meaningful names.
- Images have useful alternatives or are correctly ignored when decorative.
- Form labels, required states, instructions, and errors are announced.
- Dialogs are identified, operable, and correctly managed.
- Dynamic updates and status messages are discoverable.
- The user can complete the core task and recover from an error.
5. Test zoom, reflow, and text spacing
Check 200% browser zoom, a narrow desktop viewport, a mobile viewport, increased text spacing, and larger system text where relevant. Record whether ordinary text requires problematic horizontal scrolling, whether controls overlap, whether menus are lost, whether dialogs exceed the viewport, and whether content is hidden behind fixed elements.
6. Include people with disabilities when appropriate
Expert review and testing with disabled participants can reveal confusing instructions, poor reading order, unclear control names, difficult error recovery, excessive cognitive load, and incompatibilities with real assistive-technology setups. Recruit participants who match the tasks and access needs being evaluated, explain the scope clearly, and compensate participants fairly. User testing complements—not replaces—standards-based review and automated checks.
How should accessibility issues be prioritized?
Fix issues according to the task and user impact rather than treating every automated finding as equally urgent. A missing label on a rarely used decorative control is not the same risk as a keyboard trap in checkout or an error message that prevents an application from being submitted.
- Core-task blockers: Fix problems that prevent a user from completing a key task.
- Keyboard and screen-reader blockers: Address unreachable controls, trapped focus, missing names, broken forms, and inaccessible dialogs.
- Repeated component defects: Fix the shared component or design-system pattern so the correction reaches many pages.
- Legal and contractual requirements: Meet requirements that apply to the organization, service, jurisdiction, or procurement agreement.
- High-value preventive fixes: Address easy changes that prevent new defects, such as editor guidance, component rules, linting, and reusable form patterns.
| Issue record field | What to write |
|---|---|
| Location | URL, screen, component, or document name. |
| User task | The task affected, such as booking, login, search, or checkout. |
| Access need | The affected disability or access need when known, without guessing about an individual. |
| Reproduction | Exact steps, input, browser, device, and assistive technology where relevant. |
| Expected result | What a user should be able to perceive or do. |
| Actual result | What happens instead. |
| Standard reference | A WCAG criterion only when the mapping is reasonably confident. |
| Action | Recommended fix, owner, priority, and verification status. |
How do you prevent accessibility regressions?
Accessibility work is more reliable when it becomes part of normal delivery rather than a final inspection. Designers can specify focus, contrast, error, motion, and responsive states. Developers can use semantic HTML, reusable accessible components, linters, automated checks, and CI testing. Content teams can follow rules for headings, links, alt text, tables, captions, and documents. QA teams can repeat keyboard, zoom, and assistive-technology checks on core journeys.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →For a component library, document the expected behavior for buttons, menus, dialogs, tabs, accordions, carousels, date pickers, forms, notifications, and loading states. Test the shared component once in depth, then verify that each implementation preserves its accessible name, role, state, focus behavior, and keyboard interaction.
What about PDFs, vendors, and third-party widgets?
Accessibility responsibility does not end when content is hosted by another provider. Audit PDFs, downloadable forms, embedded video players, payment widgets, chat tools, maps, scheduling systems, authenticated pages, and other third-party integrations that are part of the user journey.
Ask vendors for accessibility documentation, representative testing evidence, supported browsers and assistive technologies, remediation commitments, and a way to report defects. Review contracts and procurement requirements. The DOJ first-steps guidance for public entities specifically recommends reviewing vendor contracts and determining whether vendors can provide accessible content.
Do not assume that a third-party defect is irrelevant because the third party hosts the code. If users must interact with the widget to complete your service, the widget belongs in the evaluation scope. Provide an alternative route only when the alternative is genuinely usable and equivalent.
Should you use an accessibility scanner, platform, or consultant?
Choose a tool or service according to the testing problem it solves. A scanner is useful for finding recurring, detectable defects; it is not a complete audit or a legal-compliance guarantee.
| Need | Suitable category | What it can and cannot prove |
|---|---|---|
| Check one page quickly | Free browser scanner or WAVE | Useful for page-level findings; cannot prove that the whole site or a complete workflow is accessible. |
| Catch defects during development | axe DevTools, an accessibility linter, or CI-integrated testing | Useful for preventing repeatable coding defects; still requires manual interaction and content review. |
| Monitor many pages | Enterprise scanning and reporting platform | Useful for scale and trend tracking; coverage depends on page selection, authentication, technology, and configuration. |
| Validate a legal or procurement obligation | Qualified accessibility auditor | Can provide manual findings, remediation advice, and verification; does not make legal decisions for every jurisdiction or organization. |
| Understand real user barriers | Manual testing plus testing with disabled participants | Reveals usability and assistive-technology problems that automated rules cannot establish. |
| Add a toolbar or preference controls | Only a supplementary widget after underlying fixes | Does not replace semantic HTML, accessible components, captions, document remediation, keyboard testing, or user testing. |
axe DevTools is a reasonable option for developers and teams that want automated, guided, and developer-integrated testing. The axe DevTools browser extension provides a starting point, while Deque describes additional capabilities and plan differences on its axe DevTools pricing page. Verify current plan details before purchasing.
WAVE is useful for quick page-level inspection and automated analysis. Use the WAVE evaluation tool for an individual page and consult the WAVE API information if you need programmatic analysis. Do not treat a WAVE result as proof of full-site accessibility.
When hiring an accessibility consultant or auditor, look for a documented manual-testing methodology, more than one browser and assistive-technology combination, experience with your framework and components, reproducible issue reports, remediation verification, references or anonymized sample reports, and experience involving disabled users where appropriate. Be cautious of a vendor that offers only an automated score or a generic “compliance certificate.”
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Why do common accessibility fixes fail?
“The scan says zero issues.”
Why it fails: Automated tools test only a subset of accessibility requirements. A clean scan does not prove that content is understandable, keyboard flow is logical, focus behavior works, errors are recoverable, or screen-reader users can complete a task.
Recovery: Test core journeys with a keyboard, at 200% zoom, and with a screen reader, then obtain human review where the task or risk justifies it. The DOJ accessibility guidance also cautions against treating automated results as conclusive.
“We added an accessibility widget or overlay.”
Why it fails: An overlay may offer limited preferences or identify some issues, but it cannot reliably repair every semantic, interaction, document, or third-party problem. A script can also fail to load, conflict with the site, or provide a different experience that still does not work with assistive technology.
Recovery: Fix the underlying HTML, content, components, documents, and workflows. Evaluate any widget as a supplementary feature, not as a guarantee of accessibility or legal compliance.
Recommended Free Tools
“We used ARIA everywhere.”
Why it fails: ARIA can expose roles, names, states, and properties, but ARIA does not automatically supply keyboard behavior, focus management, validation, or usable interaction.
Recovery: Prefer native HTML. Add ARIA only where needed, then test the complete component with a keyboard and assistive technology.
“Alt text is just an SEO field.”
Why it fails: Alt text communicates an image’s purpose or meaningful information to people who cannot see it. Filenames, keyword stuffing, and generic descriptions are not useful alternatives.
Recovery: Write alt text according to the image’s contribution to the page, and use empty alt text for decorative images.
“We need WCAG AAA everywhere.”
Why it fails: Level AAA is not generally a practical universal target because some AAA criteria cannot reasonably apply to all content or use cases.
Recovery: Establish the required legal or contractual target—normally WCAG 2.1 or 2.2 Level AA—then adopt stricter requirements selectively for particular audiences, content, or organizational goals.
What does U.S. accessibility law require?
Technical best practice and legal obligation are related but not identical. The ADA applies to state and local governments under Title II and to businesses open to the public under Title III, but the exact obligations and enforcement context differ. There is not one uniform federal technical rule or one general deadline for every private website.
The current DOJ Title II web and mobile application rule for state and local government entities specifies WCAG 2.1 Level A and AA requirements. As of the supplied August 2026 DOJ materials, the compliance date is April 26, 2027 for public entities with populations of 50,000 or more, and April 26, 2028 for public entities with populations below 50,000 and special district governments. The DOJ compliance-date fact sheet and 2026 interim final rule reflect the changed deadlines; do not repeat the earlier dates without noting that they were extended.
Those dates concern public entities under Title II. They are not a general deadline for every commercial website. Organizations should separately identify applicable law, procurement rules, contracts, internal policy, and risk-management needs. An accessibility statement, feedback form, or remediation plan can support governance and communication, but none by itself makes a website accessible or establishes legal compliance.
What should you do next?
Select one important user journey and test it today. Run an automated check, complete the journey with only a keyboard, repeat it at 200% zoom, and inspect it with a screen reader if you can. Fix blockers first—especially unreachable controls, trapped focus, unusable forms, missing names, and inaccessible dialogs—then retest the journey and apply the lessons to shared components and content workflows.
After the first pass, expand to high-traffic pages, templates, PDFs, mobile experiences, and third-party services. Keep an issue register, assign owners, verify fixes, train content and development teams, and repeat testing whenever a component, workflow, or vendor integration changes.
Frequently Asked Questions
Can an automated accessibility scan prove that a website is accessible?
No. An automated accessibility scan can find some detectable problems, such as missing labels, certain contrast failures, invalid ARIA, and duplicate IDs, but no tool alone can determine whether a website meets accessibility standards. Keyboard, zoom, screen-reader, and human testing are also required.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchIs WCAG 2.2 legally required for every website?
No. WCAG 2.2 is the current W3C recommendation and a practical target for new web work, but legal and contractual requirements vary. The current DOJ Title II rule for state and local governments references WCAG 2.1 Level A and AA, not WCAG 2.2.
What is the fastest way to start testing web accessibility?
Choose one important user journey, run an automated check, complete the journey with a keyboard, test at 200% zoom, and review it with a screen reader if possible. Record and fix blockers before expanding the test to more pages and workflows.
Does an accessibility overlay make a website compliant?
No. An overlay or widget may provide limited preferences or identify some issues, but it does not replace accessible source code, content, components, captions, document remediation, keyboard testing, or user testing. Do not treat an overlay as a guarantee of accessibility or legal compliance.
The Bottom Line
Bottom line: Web accessibility starts with usable tasks, not an automated score. Target WCAG 2.2 Level AA for new work unless another requirement applies, then check structure, keyboard access, focus, forms, contrast, media, zoom, dynamic updates, documents, and third-party tools. Combine automated checks with human testing, fix blockers first, and retest after every significant change.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
