Open-source screen reader. Source-level insights.
Manual Website Accessibility Testing with NVDA
NVDA (NonVisual Desktop Access) is a free, open-source Windows screen reader. Our hands-on testing with Mozilla Firefox and Google Chrome examines semantic HTML, ARIA, and real user journeys to identify barriers that a scan alone cannot fully explain.
Request an NVDA Accessibility AuditServing Oregon, Las Vegas, and businesses nationwide.
Why NVDA testing is essential
Code-Level Verification Across Firefox and Chrome
A website can look clear while its labels, reading order, or dynamic updates remain difficult to understand with a screen reader. We examine your source semantics, browser accessibility APIs, and NVDA feedback together. Browser and screen-reader behavior can differ, so no single pairing or automated score proves conformance.
Manual NVDA testing complements WCAG review within our website accessibility audit and remediation program, connecting observed barriers with practical development priorities.
Firefox + Chrome Comparison
We test NVDA in Mozilla Firefox and Google Chrome on Windows to compare how the agreed pages expose structure, labels, and interactive states. Documenting the exact versions helps separate a source-code issue from behavior that differs between browser and screen-reader configurations.
Speech Viewer Evidence
NVDA Speech Viewer displays the text NVDA generates during a session. We capture relevant output from the agreed tasks with keyboard reproduction steps and expected announcements, giving developers a written record of each reported barrier—not an assumed transcript of every website element.
End-to-End Task Testing
Follow menus, search filters, dynamic accordions, and multi-step forms using keyboard commands and actual NVDA feedback. We examine whether a user can understand the next step, complete the selected task, and recover from errors rather than relying on a scanner score alone.
What we test in NVDA
Core NVDA Evaluation & Remediation Points
Our manual audits inspect how your front-end architecture communicates structure, state, and dynamic updates. These seven areas are evaluated within selected real user journeys, including the agreed interactive states.
Browse Mode & Focus Mode Behavior
Review reading and navigation in Browse Mode and direct interaction with fields or custom controls in Focus Mode. Check entry, exit, and continued task progress using the configured automatic behavior and NVDA+Space when appropriate. Relevant settings and the NVDA modifier key are recorded with the findings.
Elements List: Links, Headings & Landmarks
Inspect the NVDA Elements List using NVDA+F7 to review available links, headings, and landmarks. Check logical heading relationships and understandable destinations. Descriptive link labels help when read out of context; we assess any surrounding programmatic context against the applicable WCAG requirement rather than automatically failing every repeated link label.
ARIA Live Regions & Dynamic Status Messages
Test search-result counts, cart changes, notifications, and validation feedback as they occur in selected flows. Use polite status announcements or urgent alerts as appropriate, without unnecessary interruptions. Error recovery may deliberately move focus where that helps the user; not every update or inline error needs role=alert.
Custom Controls & Interactive States
Verify the role, accessible name, value, and state of menus, tabs, sliders, checkboxes, and expandable controls. Compare expanded, selected, or checked states with actual NVDA output. Prefer native elements; properly implemented custom controls also need the appropriate keyboard behavior and semantics, not ARIA attributes alone.
Keyboard Focus Order & Visual Focus Ring
Follow Tab and Shift+Tab through a logical sequence with clearly visible focus. Inspect pop-ups and embedded widgets for keyboard traps. Modal dialogs should contain focus while open, support dismissal, and restore focus appropriately; ordinary accordions and non-modal controls should not trap the user.
Skip Navigation & Bypass Blocks
Activate Skip to Main Content links and other bypass mechanisms to move past repeated navigation. Check that the destination is meaningful and that focus or reading position supports continued navigation. Review sticky headers so they do not obscure the controls a keyboard user reaches.
Graphics, Icons & SVG Accessibility
Inspect meaningful alternatives for informative images and suitable hiding for decorative icons or SVG graphics. Functional search and menu buttons need clear accessible names; where a visible label exists, retain it in the spoken name. Hiding a decorative child icon must not hide the interactive control itself.
Deliverables & reporting
What You Receive After an NVDA Audit
Receive findings your team can reproduce, prioritize, and act on. The report connects the user experience to code-level remedies and a clear record of what was verified.
Prioritized Accessibility Defect Report
Critical, High, and Medium severity reflects user impact and task completion. Findings identify affected URLs, templates, and components, map to applicable WCAG 2.1/2.2 Level A and AA criteria, and record the Windows, NVDA, Firefox, and Chrome versions actually used.
NVDA Speech Viewer Transcripts
Relevant captured speech, expected-versus-observed announcements, keyboard reproduction steps, and NVDA settings make reported defects reproducible. Transcripts document output generated during the scoped native sessions and distinguish missing or unexpected announcements from assumptions about the accessibility tree.
HTML & ARIA Code Remedies
Clear, framework-agnostic semantic HTML, ARIA, CSS, and keyboard-interaction recommendations help engineers address root causes in the source. We favor resilient native patterns over brittle overlay patches and agree implementation responsibilities with your development team.
Verification Re-Test
Re-test the agreed fixes in recorded NVDA and browser environments after deployment. Receive a dated status record identifying resolved, unresolved, and untested items, with the tested URLs and flows. Verification documents the agreed scope; it does not promise every barrier on an entire website has been eliminated.
For implementation support and coordinated re-testing, our accessibility auditing and source-code remediation program brings this NVDA issue report together with agreed fixes, developer collaboration, and scoped verification.
Official NVDA learning resources
Independent links to NV Access documentation; no vendor affiliation or endorsement is implied.
Turn screen reader feedback into actionable fixes
Catch Accessibility Defects at the Code Level
Start with the tasks that matter to your visitors. Contact Optimize Media Marketing to scope a manual NVDA accessibility audit, identify source-level barriers, and give your team a practical remediation plan. Available for Oregon, Las Vegas, and nationwide businesses.
Schedule Your NVDA AuditPrefer to talk? Calling is optional.
Use the audit request link or either regional number to discuss your scope.
Oregon
(541) 844-4880Las Vegas
(702) 343-9322