Native Windows testing. Real user journeys.
Manual Website Accessibility Testing with JAWS
JAWS (Job Access With Speech) is a Windows screen reader used for web navigation and form interaction. We offer scoped, hands-on native JAWS testing with Google Chrome and Microsoft Edge to evaluate your website’s key tasks.
Request a JAWS Accessibility AuditServing Oregon, Las Vegas, and businesses across the USA nationwide.
Why JAWS testing matters
Automated Tools Cannot Simulate Real Screen Reader Behavior
Automated tools can inspect static markup and dynamic DOM states, but they cannot replace expert testing of actual screen reader journeys. A scan alone cannot fully evaluate whether someone can understand an error, operate a menu, or complete a checkout using JAWS.
JAWS journey testing complements standards review within our full website accessibility audit and remediation program, connecting observed usability barriers with a broader technical roadmap.
Real desktop browser pairings
Native JAWS on Windows with Google Chrome and Microsoft Edge lets us compare actual interaction and speech output in the agreed environments. Results apply to the versions tested, not every browser or assistive technology.
Complete user journeys
We follow selected navigation, search, filters, lead forms, dialogs, or checkout tasks using the keyboard and JAWS output. Responsive menus are tested in desktop Windows browsers; this is not phone-based JAWS testing.
Evidence developers can use
Reports connect expected versus observed behavior to the affected URL and component, user impact, applicable WCAG 2.1/2.2 success criteria, and practical source-code changes. A scanner score alone does not explain a task-level barrier.
What we test in JAWS
Core JAWS Evaluation & Remediation Points
We inspect the DOM, accessibility tree, keyboard interaction, and actual native JAWS output together, including dynamic states within the agreed scope. These seven areas support complete selected user journeys, not just isolated element checks.
Virtual PC Cursor & Forms Mode Transitions
Check movement between reading with the Virtual PC Cursor and entering or selecting information in Forms Mode. We respect and record the configured Auto, Semi-Auto, or Manual Forms Mode behavior, rather than expecting every control to switch automatically. Users should be able to enter, leave, and continue the selected task without a keyboard trap.
ARIA Landmarks & Page Regions
Inspect semantic header, nav, main, and footer elements and their appropriate landmark exposure. We check region navigation, clear names where needed, and access to primary content. Context matters: a footer inside an article or section is not automatically a page-level contentinfo landmark; adding redundant ARIA is not the goal.
Heading Hierarchy & Structural Navigation
Use H and the 1–6 heading-navigation keys to review a logical content outline. Headings should identify meaningful sections and relationships, not exist solely for visual styling. We compare the heading list and reading order with the information a user needs to understand and complete the agreed journey.
Form Labels, Instructions & Error Announcements
Review visible and programmatic labels, correct accessible names, required states, instructions, and recoverable validation errors. Not every input needs a literal label element, but its labeling must be appropriate. Meaningful errors should be available and announced through focus or status mechanisms as appropriate—not every error needs an immediate alert.
Interactive Widgets, Modals & Accordions
Prefer native controls and verify keyboard behavior, roles, names, and states for menus, tabs, carousels, and expandable components. Check expanded or selected states against observed output. For modal dialogs, inspect initial focus, focus containment, dismissal, and restoration; ordinary accordions and other non-modal widgets should not trap focus.
Data Tables & Complex Content
Navigate actual data tables to hear row and column context. Review table headers with scope or appropriate header associations for complex structures, plus captions and reading context where useful. Charts are not automatically tables; visualizations need suitable accessible alternatives based on the information and task, rather than table markup applied indiscriminately.
Images, Buttons & Link Context
Check meaningful image alternatives and empty alt text or appropriate hiding for decoration. Native buttons need meaningful visible labels, and link purpose should be understandable in context. Use ARIA naming only where needed, retaining the visible label in the accessible name. Inspect actual JAWS output instead of assuming that an attribute alone fixes the experience.
Deliverables & reporting
What You Receive After a JAWS Audit
Your report documents what was tested, what was heard, and what needs attention. These are scoped engagement deliverables—not a claim that this agency website has already passed native JAWS testing.
Prioritized Issue Log
Critical, High, and Medium severity reflects user impact, including whether a barrier blocks a core task. Findings identify affected URLs, templates, components, relevant WCAG 2.1/2.2 success criteria, and the exact Windows, JAWS, and Chrome or Edge versions used for each observation.
Speech Output & Reproduction Steps
Step-by-step keyboard sequences, relevant JAWS settings, and expected versus observed behavior help developers reproduce findings. Speech-output transcriptions reflect what was actually observed during native testing; they are not invented logs or assumed announcements from an accessibility tree.
Code-Level Remediation Guidance
Specific semantic HTML, CSS, ARIA, and focus-management recommendations address underlying source-code barriers. We prioritize resilient native patterns rather than brittle third-party overlays. Implementation responsibilities and any additional support are agreed with your development team.
Post-Fix Re-Testing Verification
Re-test agreed fixes in the recorded native environments and provide a dated, scoped status record. Outcomes distinguish resolved, unresolved, and untested items, with the tested URLs and flows. This documents the verification performed, not whole-website certification or coverage of every assistive technology.
For broader implementation and re-testing, our accessibility auditing and source-code remediation program can connect this JAWS issue log with agreed fixes, developer collaboration, and scoped verification.
Official JAWS learning resources
Independent links to Freedom Scientific documentation; no vendor affiliation or endorsement is implied.
Listen to the experience, not just the score
Verify How Your Website Sounds to Real Users
Start with your website’s priority tasks and your development workflow. We work with teams in Oregon, Las Vegas, and nationwide to define a practical native JAWS audit and a clear next step for remediation.
Schedule Your JAWS 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