Category: Testing and Evaluation

Manual Testing

Also known as: Manual Accessibility Testing, Human Testing

Simply put

Manual testing is a process in which a person checks software directly, rather than relying on automated scripts to do it for them. In accessibility work, this often means a human evaluates a website or application by interacting with it to find problems that automated tools may miss. It commonly involves reviewing the user interface, display, and how the software responds to a real person's actions.

Formal definition

Manual testing is a software testing approach in which testers execute test cases by hand, interacting directly with the software without using automation scripts. It is commonly used to validate the user interface, including display, responsiveness, and general design behavior, and to identify bugs, inconsistencies, and user-experience issues. In an accessibility context, manual testing generally complements automated testing, since automated checks detect only a portion of potential issues and human evaluation (including testing with assistive technologies) is typically required to assess whether an experience is genuinely usable. This entry describes testing methodology generally and is not legal advice.

Why it matters

Automated accessibility tools are efficient at flagging certain machine-detectable issues, but they detect only a portion of the barriers a person with a disability may encounter. Many accessibility problems depend on context and judgment that software cannot reliably assess, such as whether an interface behaves correctly when a real person interacts with it or whether the experience is genuinely usable end to end. Manual testing addresses this gap by having a human evaluate the software directly, interacting with it as a user would to surface bugs, inconsistencies, and user-experience issues that scripts miss.

Because manual testing lets a person validate the user interface, including display, responsiveness, and general design behavior, it is well suited to the holistic questions that matter for accessibility. A human can check whether the complete setup behaves correctly, assess how the software responds to actual actions, and, in an accessibility context, evaluate the experience using assistive technologies. This kind of hands-on evaluation is generally treated as a complement to automated checks rather than a replacement for them.

It is important to note that neither manual testing nor automated testing guarantees full accessibility or legal compliance. Manual testing improves the likelihood that real barriers are found and addressed, but the specific requirements that apply to an organization evolve through regulation and case law and vary by jurisdiction. This entry describes testing methodology generally and is not legal advice; organizations with compliance questions should consult qualified legal counsel and current agency guidance.

Who it's relevant to

Accessibility Engineers and QA Testers

Those responsible for evaluating websites and applications rely on manual testing to find issues that automated tools cannot reliably detect. Executing test cases by hand and testing with assistive technologies lets them assess whether an experience is genuinely usable, not just whether it passes machine-detectable checks.

UX Designers

Designers benefit from manual testing because it validates the user interface directly, verifying display, responsiveness, and general design behavior. Observing how the software responds to a real person's actions helps identify usability problems that would otherwise go unnoticed.

Compliance Officers and Business Leaders

Decision-makers should understand that automated checks detect only a portion of potential issues and that manual, human evaluation is typically required to assess real usability. Manual testing supports a more thorough accessibility effort, but it does not by itself guarantee legal compliance; specific obligations evolve through regulation and case law, and qualified legal counsel should be consulted on those questions.

Software Development Teams

Developers integrating accessibility into their workflow use manual testing to complement automated tooling. Holistic manual approaches, such as checking that the software behaves correctly once the complete setup is in place, help catch defects and inconsistencies before they reach users.

Inside Manual Testing

Keyboard Navigation Testing

Verifying that all interactive elements can be reached, operated, and exited using only a keyboard, including checking logical focus order, visible focus indicators, and the absence of keyboard traps.

Assistive Technology Testing

Evaluating content with screen readers (such as JAWS, NVDA, or VoiceOver), screen magnifiers, and other assistive tools to confirm that information, structure, and functionality are conveyed as intended to users who rely on them.

Human Judgment and Contextual Evaluation

Applying reviewer expertise to assess aspects that automated tools cannot reliably measure, such as whether alternative text is meaningful, whether reading order makes sense, and whether error messages are understandable in context.

Success Criteria Verification

Manually checking content against specific WCAG success criteria that require interpretation, commonly targeting Level AA, since many criteria cannot be fully evaluated through automated scanning alone.

Visual and Interaction Inspection

Reviewing rendered content for issues such as color contrast in real usage, reflow at different zoom levels and viewport sizes, and the usability of custom components that may not behave like native controls.

Common questions

Answers to the questions practitioners most commonly ask about Manual Testing.

Can automated testing tools replace manual accessibility testing?

No. Automated tools detect only a portion of accessibility issues, and passing automated checks does not confirm that a page is usable by people relying on assistive technologies. Many success criteria involve judgment, such as whether alternative text is meaningful, whether reading order is logical, or whether a focus indicator is genuinely visible, that automated scanning cannot reliably evaluate. Manual testing is generally needed to assess these aspects, and the two approaches are best treated as complementary rather than interchangeable.

Does passing manual testing guarantee legal compliance or a fully accessible experience?

No. Meeting WCAG success criteria through manual testing supports accessibility efforts, but it does not by itself guarantee an accessible experience for every user, nor does it provide immunity from legal claims. Conformance, usability, and legal compliance are distinct concepts. Accessibility requirements in the US evolve through regulation and case law, so this information is not legal advice; organizations should consult qualified legal counsel regarding their specific obligations.

What does manual accessibility testing typically involve?

Manual testing commonly includes reviewing content and functionality against WCAG success criteria using human judgment, testing keyboard-only navigation, evaluating the experience with assistive technologies such as screen readers, checking focus order and visible focus indicators, and assessing whether alternative text and other non-text content convey meaning appropriately. It is generally combined with automated testing to broaden coverage.

Which assistive technologies are commonly used during manual testing?

Testers often exercise a range of assistive technologies to reflect how different users interact with content. This can include screen readers, screen magnification, keyboard-only operation without a pointing device, and voice or speech input tools. Testing across more than one combination of assistive technology and browser is generally recommended, since behavior can vary between combinations.

How often should manual testing be performed?

Manual testing is commonly performed at meaningful points in a development lifecycle, such as when new features are introduced, when significant content or design changes occur, and during periodic reviews of existing content. Because accessibility can regress as products change, many teams integrate manual testing into ongoing quality processes rather than treating it as a one-time activity.

Who should perform manual accessibility testing?

Manual testing is generally most effective when conducted by individuals familiar with WCAG success criteria and experienced with assistive technologies. Involving people who use assistive technologies in their daily lives can provide additional insight into real-world usability that criterion-based checks may not fully capture. The specific mix of roles depends on an organization's resources and goals.

Common misconceptions

Automated testing tools can find all accessibility problems, making manual testing unnecessary.

Automated tools detect only a portion of accessibility issues. Many WCAG success criteria require human interpretation, and manual testing with assistive technology is needed to evaluate the actual experience for users with disabilities.

Passing manual testing and meeting WCAG success criteria guarantees an accessible experience and legal compliance.

Meeting success criteria does not by itself guarantee a fully usable experience for all users, nor does it guarantee immunity from legal claims. Conformance, usability, and legal compliance are related but distinct. This information is not legal advice; consult qualified legal counsel for compliance questions.

Manual testing means simply looking at a page visually to judge whether it seems accessible.

Effective manual testing is a structured process that includes keyboard-only operation, testing with assistive technologies, and evaluation against specific criteria, rather than an informal visual impression.

Best practices

Combine manual testing with automated scanning, using automated tools to catch programmatically detectable issues and manual review to address criteria that require human judgment.

Test with a keyboard alone to confirm all interactive elements are reachable and operable, with a visible focus indicator, a logical focus order, and no keyboard traps.

Evaluate content with actual assistive technologies, such as widely used screen readers, rather than relying solely on code inspection or vendor claims.

Map testing to specific WCAG success criteria and target level, commonly Level AA, and note which criteria require manual verification.

Include checks that tools cannot reliably assess, such as the meaningfulness of alternative text, logical reading order, and the clarity of error messages in context.

Document findings, testing methods, and any limitations, and recognize that requirements evolve through regulation and case law, so consult qualified legal counsel for compliance decisions.