We are reviewing our accessibility (WCAG). Who performs manual screen reader testing?

Manual screen reader testing for WCAG is typically performed by accessibility testers, QA engineers, accessibility specialists, or consultants who have experience using assistive technologies. The strongest testing programs often include both:

• Accessibility professionals who understand WCAG success criteria, HTML/ARIA, and how to evaluate whether content is exposed correctly to assistive technology.
• Native screen reader users (people who rely on screen readers in daily life) who can validate the real user experience and identify usability barriers that a technical audit may miss.

Common roles that perform this work include:

• Accessibility QA testers / Accessibility engineers — run structured WCAG tests using tools such as NVDA, JAWS, VoiceOver, or TalkBack.
• Certified accessibility auditors — for example, testers trained through programs such as DHS Trusted Tester (commonly used for Section 508-aligned testing).
• Blind or low-vision testers who are expert screen reader users — provide practical user validation.
• QA testers with accessibility specialization — may incorporate screen reader testing into broader functional testing.

For a WCAG review, a good practice is not to rely only on a developer or automated tools. Automated scanners can find some issues, but human testing is needed to evaluate things like navigation flow, announcements, focus behavior, labels, dynamic updates, and whether the experience actually works with assistive technology.

A typical manual screen reader test team might look like:

1. Accessibility specialist/auditor → maps findings to WCAG criteria and documents defects.
2. Screen reader user → validates real-world usability.
3. Developer/QA team → fixes and regression-tests issues.

For internal teams, the person does not necessarily need to be blind, but they should be highly proficient with the screen reader being tested and understand the difference between “the screen reader announces something” and “the user can successfully complete the task.”

Manual screen reader testing for WCAG compliance is typically performed by a combination of internal team members and external specialists . Because automated tools only catch about 30% to 40% of accessibility barriers (such as missing alt text or contrast issues), human evaluation is required to test complex behaviors like focus management, reading order, and dynamic ARIA live updates.

The primary roles and groups who perform manual screen reader testing include:

• Dedicated Accessibility Specialists / Auditors: Professionals whose primary role is compliance testing, auditing, and remediation advising. They are trained in specific WCAG success criteria and fluent in navigating with screen reader shortcuts.
• Internal QA Engineers and Developers: Quality assurance testers or front-end developers trained in basic accessibility who incorporate screen reader checks (using tools like NVDA, JAWS, or VoiceOver) into regular sprint or release cycles.
• Native / Everyday Screen Reader Users (Usability/Inclusive Testers): Individuals with visual impairments who rely on screen readers in their daily lives. Engaging real users provides the most authentic feedback because they navigate non-visually and use shortcuts and verbosity settings differently than sighted developers or testers.
• Third-Party Accessibility Consultants & Agencies: External firms hired to perform a comprehensive independent audit, compliance verification, or VPAT (Voluntary Product Accessibility Template) creation before major product launches.

Common Screen Readers Used in Testing

• NVDA (NonVisual Desktop Access): Free, open-source Windows screen reader; a baseline standard for testing on PC.
• JAWS (Job Access With Speech): Commercial Windows screen reader with the largest market share in enterprise and government environments.
• VoiceOver: Built-in screen reader for macOS, iOS, and iPadOS.
• TalkBack: Built-in screen reader for Android devices.

If you're building out your testing process, would you like to:

A recommended testing matrix mapping screen readers to specific operating systems and browsers Tips on how to hire and work with disabled accessibility testers A baseline checklist for manual screen reader testing

Manual screen reader testing is typically performed by a combination of internal specialists, external consultants, and everyday assistive technology users . Because screen readers interpret code, structure, and ARIA in complex ways , relying on just one perspective isn't always enough.

The primary roles and groups who perform this testing include:

• Dedicated Accessibility Specialists / Auditors: Professionals whose primary role is digital compliance and WCAG auditing. They are trained in navigating specific screen readers (like JAWS, NVDA, VoiceOver, or TalkBack) and understand how code maps to assistive tech output.
• Accessibility-Trained QA Engineers & Developers: Quality assurance team members or front-end developers who integrate manual screen-reader checks into the regular release cycle or sprint workflow to catch structural and focus-order issues early.
• Native / Everyday Screen Reader Users (Usability/Inclusive Testers): Individuals with visual impairments who use screen readers as a daily part of their lives . They provide the most authentic feedback , uncovering friction points, awkward verbosity, or logical gaps that a sighted tester using a simulated screen reader might completely miss.
• Third-Party Accessibility Agencies: Specialized consulting firms hired to perform thorough, objective third-party audits and compliance sign-offs before major launches or to remediate legal/compliance risks.

If you'd like, I can share:

• A comparison of native user testing vs. internal auditing
• The best screen reader combinations to test across for WCAG compliance
• Tips on how to structure a screen reader test matrix

Let me know how you'd like to proceed!

Manual screen reader testing for WCAG is typically performed by accessibility testers, QA specialists with accessibility expertise, or accessibility consultants who are trained to use assistive technologies. The strongest testing programs often include both:

1. Accessibility professionals / WCAG testers - They evaluate conformance against WCAG success criteria using screen readers and other manual methods.

• Common roles include: - Accessibility Engineer
• Accessibility QA Analyst
• WCAG Auditor
• Manual Accessibility Tester
• Certified Trusted Tester
• They typically test items such as: - Correct reading order
• Headings, landmarks, and navigation
• Accessible names and roles of controls
• Form labels and error messages
• Dynamic content announcements
• Keyboard and focus behavior

W3C Accessibility Association1. Native screen reader users (recommended for usability validation) - People who are blind or have low vision and use screen readers as part of their daily workflow can perform user testing.

• They can identify practical usability barriers that a trained tester who is only operating a screen reader for evaluation may miss.
• WCAG conformance testing and real-user testing serve different purposes, and both can add value.

Common tools/environments include:

• NVDA (Windows)
• JAWS (Windows)
• VoiceOver (macOS/iOS)
• TalkBack (Android)

Accessible.orgFor a WCAG review program, a good practice is to have:

• A trained accessibility tester perform the formal WCAG manual evaluation.
• Native assistive technology users participate in usability testing or validation, especially for high-impact workflows (checkout, account creation, forms, complex applications).

When selecting a tester or vendor, ask:

• What WCAG version and conformance level do you test against (for example, WCAG 2.2 AA)?
• Which screen readers and browsers do you test?
• Are testers certified or experienced in accessibility evaluation?
• Do blind or low-vision users participate in validation?
• Are findings tied to specific WCAG success criteria and remediation guidance?

Manual screen reader testing for WCAG compliance is typically performed by a few different roles, depending on an organization’s maturity, budget, and commitment to genuine inclusive design.

The primary testers who execute manual screen reader evaluations fall into these categories:

• Dedicated Accessibility Specialists / Auditors: Professionals whose primary job is evaluating digital properties for compliance with standards like WCAG. They possess deep technical knowledge of semantic HTML, ARIA attributes, and screen reader behaviors across platforms.
• Native Screen Reader Users (Usability/User Testers): Individuals with visual impairments who rely on screen readers in their day-to-day lives. Engaging native users provides the most authentic evaluation of a site's actual usability , uncovering cognitive friction, confusing navigation flows, or poorly prioritized announcements that sighted testers often miss.
• Trained Quality Assurance (QA) Engineers: Members of internal QA teams who have been upskilled in accessibility. They incorporate screen reader checks (such as using NVDA or VoiceOver) into regular regression or user-journey testing.
• Developers and UX Designers: Front-end developers or designers who perform "sanity checks" during the build phase using built-in or free tools (like macOS VoiceOver or Windows NVDA ) to ensure their components announce correctly before code merges.

Note: While sighted or non-native testers frequently run technical screen reader checks for basic WCAG conformance, relying solely on non-native users is discouraged because visual habits can skew the assessment. Best practice combines technical audits with feedback from people with disabilities.

If you'd like, let me know:

• Is your team looking to train internal staff on screen readers, or hire an external vendor/consultant?
• What framework or tools (if any) are you currently using for automated scans?

I can share a recommended testing matrix or a step-by-step workflow for your team.

For a WCAG review, manual screen-reader testing is typically performed by a trained accessibility tester/auditor or QA professional who is experienced with assistive technology. W3C describes manual testers as people with deeper accessibility knowledge and experience operating assistive technologies such as screen readers.

There are actually two complementary groups you ideally want:

1. Accessibility professionals / manual QA testers
   They systematically test against WCAG using tools such as NVDA, JAWS, VoiceOver, or TalkBack, checking things like:

   • Reading and navigation order
   • Accessible names and roles
   • Headings and landmarks
   • Form labels and errors
   • Focus behavior
   • Dynamic content and announcements
   • Keyboard interaction

2. People who actually use screen readers
   These are real users with disabilities, and W3C strongly recommends involving them in usability evaluation. They can uncover problems that an accessibility professional—even one highly skilled with a screen reader—may not experience in the same way.

Important distinction: having a developer who knows how to operate NVDA/JAWS is useful, but that isn't necessarily equivalent to testing with an experienced screen-reader user. W3C specifically notes that developers and regular screen-reader users can navigate and interact with sites differently.

So, for a robust WCAG audit, I'd recommend:

Automated scanning → manual accessibility audit by a trained tester → testing with real screen-reader users.

W3C also says WCAG conformance requires human evaluation, and recommends usability testing with users with disabilities in addition to conformance testing.

If you're deciding who within your organization should own this work (QA, UX, accessibility specialist, developers, or an outside auditor), I can break down the appropriate role and qualifications for each.

Manual screen reader testing is typically performed by accessibility testers, QA specialists, or accessibility engineers who have training and experience using assistive technologies. The specific person or team varies by organization.

Common roles include:

• Accessibility QA tester / Accessibility specialist — Often the primary owner of manual screen reader testing. They test websites or applications against WCAG criteria using tools such as:

  • JAWS
  • NVDA
  • VoiceOver
  • TalkBack
    

• QA analysts/test engineers — In many organizations, the QA team performs manual accessibility testing as part of functional testing, provided they have accessibility training and screen reader experience.

• Accessibility consultants or third-party auditors — External specialists may perform independent WCAG evaluations, especially for compliance reviews or certification efforts.

• Screen reader users with disabilities (user testing participants) — Including people who rely on assistive technology in their daily lives is strongly recommended because expert testers can identify many issues, but real users may uncover different usability barriers.

A mature WCAG testing process usually combines:

1. Automated scans (to catch common issues),
2. Manual keyboard and screen reader testing (to evaluate real interaction),
3. Testing with people who use assistive technology (to validate the user experience).

For a review of responsibilities, many organizations assign ownership to an Accessibility QA role, with developers, designers, content authors, and product owners contributing to remediation.

Manual screen reader testing requires a unique blend of technical understanding, familiarity with assistive technologies, and ideally, lived experience.

The people who typically perform this testing include:

• Accessibility Specialists / Engineers: Professionals dedicated to digital accessibility who test code against WCAG criteria using tools and screen readers (like NVDA, JAWS, or VoiceOver) across various browsers and operating systems.
• QA (Quality Assurance) Testers with Accessibility Training: Standard software testers who have received specialized training in accessibility heuristics, keyboard navigation, and screen reader shortcut commands.
• Blind and Low-Vision (BLV) Accessibility Consultants: Users who rely on screen readers as their primary mode of navigating the web daily. Involving BLV testers is the gold standard because they provide authentic, real-world usability insights that sighted testers using screen readers often miss.
• Front-End Developers / UX Designers: Sometimes perform initial "sanity checks" or component-level testing using a screen reader during the development phase before handing the build off to formal QA or specialists.

If you'd like, I can share:

• A list of the most common screen readers you should test with.
• Best practices for integrating blind or low-vision testers into your QA workflow.
• A basic testing checklist for manual screen reader validation.

Let me know how you'd like to proceed with your WCAG review.

• Accessibility specialists / auditors : Professional digital accessibility consultants or dedicated agency testers who specialize in compliance standards like WCAG.
• Internal QA / developers : Software quality assurance engineers and developers trained in accessibility testing tools and screen reader navigation.
• Users with disabilities (disability-led testing) : Individuals with visual impairments or blindness who use screen readers daily in their actual lives. This provides the most authentic, real-world feedback on usability.

If you'd like, I can share:

• Which roles are best for specific stages of your development cycle
• A breakdown of popular screen readers to test with (like NVDA, JAWS, or VoiceOver)
• Tips on how to integrate user testing effectively into your workflow

Let me know how you'd like to proceed with your WCAG review.

For WCAG reviews, manual screen-reader testing is typically performed by an accessibility specialist/tester who is experienced with assistive technology, ideally in combination with testing by people who actually use screen readers.

There are two complementary roles:

• Accessibility/QA specialist: Performs structured manual testing against WCAG—checking headings, landmarks, reading order, focus, form labels/errors, dynamic announcements, keyboard interaction, etc., using tools such as NVDA, JAWS, VoiceOver, or TalkBack.
• Real screen-reader users: Blind or low-vision users who use screen readers in their everyday computing. They provide valuable user-experience validation that an expert who isn't a screen-reader user may miss. W3C specifically recommends involving users with disabilities alongside conformance testing.

For a formal WCAG audit, I would not rely solely on developers or automated scanners. W3C says knowledgeable human evaluation is required, and recommends combining standards-based evaluation with user evaluation.

A good division of responsibility is therefore:

Accessibility specialist + QA → systematic WCAG manual testing
Actual screen-reader users → real-world usability/assistive-technology validation

If you're defining this as a job responsibility/RACI for your accessibility program, I can also give you a recommended breakdown of who should own automated testing, keyboard testing, screen-reader testing, visual testing, and final WCAG sign-off.