Recommended Free Tools
Test a website in Microsoft Edge with both a real screen reader and Edge’s accessibility inspection tools. Use Narrator, NVDA, JAWS, or VoiceOver as appropriate; exercise keyboard and dynamic workflows; then inspect the Accessibility tree, names, roles, states, and focus behavior in DevTools. An automated report or a clean tree is useful evidence, but it cannot prove that people can use the site.
What a reliable Edge screen-reader test covers
There are two complementary questions:
- What does Edge expose? DevTools can show the accessibility tree and computed properties derived from the DOM.
- What does a person experience? A screen reader user must hear the page structure, move through controls, complete tasks, and understand changing states.
Microsoft notes that browsers can map content differently to platform accessibility APIs. Therefore, an Edge result applies to the tested operating-system and assistive-technology combination, not automatically to every browser or reader.
Choose a test setup that matches your users
Start with the combinations your product supports and your audience actually uses. On Windows, begin with Narrator, then add NVDA or JAWS when those readers matter to your users or support commitments. macOS includes VoiceOver. A built-in reader is an accessible starting point, not a universal minimum test matrix.
| Decision | What to record |
|---|---|
| Operating system | Windows or macOS edition and build |
| Browser | Microsoft Edge version and channel |
| Screen reader | Narrator, NVDA, JAWS, or VoiceOver and its version |
| User relevance | Supported platforms, customer reports, and contractual requirements |
| Task coverage | Pages and workflows that must work, including authenticated and error states |
If you cannot install a reader locally, Microsoft identifies Assistiv Labs as a commercial service that provides browser-accessible virtual machines, emulators, or real devices. Verify its current availability and terms directly.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- 20-cell braille display: Brailliant BI 20X gives blind users a compact 20-cell refreshable braille display with cursor routing keys for reading, writing, and screen reader access.
- Portable multi-device connection: connect to 5 Bluetooth devices and 1 USB device at the same time, making it easier to switch between a phone, tablet, computer, or other compatible device.
- More than a display: use onboard KeySoft Lite apps including Editor, Braille Editor, Calculator, Date and Time, Online Libraries, Victor Reader, and Terminal.
- Built for braille reading: access participating online libraries including Bookshare, NLS BARD, and NFB Newsline, with DAISY support and unprotected audio playback.
- Compact daily companion: HumanWare thumb keys, 8-dot Perkins keyboard, text-to-speech in supported languages, USB-C charging, 16GB internal storage, and up to 20 hours of battery life.
Prepare the page and a repeatable test plan
- Use a representative URL, not only the home page. Include navigation, search, forms, dialogs, menus, tables, media controls, and at least one state that changes after an action.
- Use a clean session or document cookies, account state, feature flags, and test data. Record whether a consent dialog, authentication wall, or network-dependent component was present.
- Write the task and expected result before testing. For example: “Open Filters, choose Price, apply it, and hear that the results count changed.”
- Learn the reader’s navigation commands first. Microsoft cautions that unfamiliarity with commands can be mistaken for a product defect.
- Record browser, reader, operating system, URL, page state, navigation mode, expected result, actual announcement, and reproduction steps for every finding.
Run the keyboard test before listening for detail
Keyboard access exposes failures that a mouse-only pass hides and gives the screen-reader test a predictable baseline.
- Reload the page and press Tab repeatedly. Confirm that focus reaches every actionable control in a sensible order.
- Use Shift+Tab to move backward and check that the order remains understandable.
- Look for a clear, persistent focus indicator. Do not accept a focus ring that disappears against the background or is clipped.
- Activate links and buttons with Enter (and Space where the control pattern requires it). Confirm that the control actually operates.
- Open and close menus, dialogs, date pickers, accordions, and search suggestions. Check that focus moves into a dialog, stays contained while it is open, and returns to a sensible element when it closes.
- Submit valid and invalid forms. Verify that errors are reachable, associated with the relevant fields, and announced without requiring a mouse.
Microsoft’s accessibility walkthrough specifically calls out missing focus indication, unreachable or inoperable controls, and illogical focus order as problems to identify.
Use a real screen reader in Edge
Listen to structure and names
Turn on the chosen reader, reload the page, and move by headings, landmarks, links, form fields, and buttons. Check that the heading hierarchy describes the page, landmarks have useful labels, and link text makes sense out of context. For each interactive element, verify an understandable accessible name, the correct role, and the current state such as expanded, pressed, selected, checked, or disabled.
Exercise complete workflows
Do not stop after the initial page load. Navigate to a destination, open a menu, search, submit a form, trigger validation, change a filter, and operate a dialog. Listen again after each state change. A screen reader should announce newly inserted status text, changed results, and control state without forcing the user to guess what happened.
Rank #2
- 40-cell braille display: Brailliant BI 40X gives blind users a 40-cell refreshable braille display with cursor routing keys for reading, writing, and screen reader access.
- Reliable multi-device connection: connect to 5 Bluetooth devices and 1 USB device at the same time, with Bluetooth 5 technology for faster, more stable wireless use.
- More than a display: use onboard KeySoft Lite apps including Editor, Braille Editor, Calculator, Date and Time, Online Libraries, Victor Reader, and Terminal.
- Built for braille reading: access participating online libraries including Bookshare, NLS BARD, and NFB Newsline, with DAISY support and unprotected audio playback.
- Comfortable daily use: HumanWare thumb keys, 8-dot Perkins keyboard, text-to-speech in supported languages, USB-C charging, 32GB internal storage, and up to 20 hours of battery life.
Check reading order and hidden content
Compare the spoken order with the visual and task order. Ensure decorative content is not announced as meaningful, while essential instructions and labels are available. Check that content hidden visually is not unexpectedly exposed and that content revealed by an interaction becomes reachable.
Test with the reader’s normal browse and focus modes. A page can appear correct while browsing but fail when focus enters a custom widget, so switch modes as users would during the task.
Inspect the Accessibility tree in Edge DevTools
- Open the target page in Edge.
- Open DevTools, select the Elements tool, and choose the element you want to inspect.
- Open the Accessibility tab.
- Review the element in the Accessibility Tree, its ARIA attributes, and computed accessibility properties.
- Use the Inspect overlay when available to view the accessible name, role, and keyboard focusability for an element.
The tree is a subset of the DOM containing information relevant to assistive technology. Use it to find missing names, unexpected roles, incorrect states, and elements excluded from exposure. It is not a recording of the complete spoken experience and cannot replace manual use.
Complement manual work with automated checks
Edge’s Issues tool and Lighthouse can report detectable page-wide issues. Accessibility Insights for Web provides guided checks and assessment against WCAG 2.2 Level AA success criteria. Run these tools after the manual pass to triage repeated problems and inspect suspicious elements, not to certify that every person can use the site. Automated tools cannot find barriers that appear only during interaction.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #3
- Power Specification：Power Supply with Input 100-240V- 50/60Hz;
- Safety Provide: This power supply ensures safe use with over voltage, over current, and over temperature protection.
- Package Included: 1 x wall Charger. Lightweight and easy to carry.
- Prior to using this charger, consult a qualified professional or the device manufacturer to verify compatibility. Device specifications, power requirements, and safety certifications may vary by model, version, region, or country.
Build a practical test matrix
Expand coverage when audience evidence or a support commitment justifies it. A useful matrix varies the operating system, Edge version, screen reader, account state, viewport, and task. At minimum, include:
- Initial load and a reload after a validation error.
- Keyboard-only navigation from the address bar through the main task.
- Headings and landmarks navigation on a long page.
- A form with required, invalid, and successfully submitted states.
- A modal dialog, menu, or disclosure that changes focus and visibility.
- Dynamic content such as search suggestions, live results, alerts, or loading indicators.
- At least one page with tables, images, and links whose context matters.
Repeat critical tests after major browser, reader, or component-library updates. Product interfaces and browser-to-platform mappings can change.
Document findings so another person can reproduce them
Use one issue per record. Include:
- Environment: operating system, Edge build, screen-reader name and version.
- URL, account or feature-flag state, and the exact page state.
- Navigation mode and the command or key sequence used.
- Expected announcement or behavior.
- Actual announcement or behavior, including missing or misleading information.
- Minimal reproduction steps, severity rationale, and a screenshot or recording when policy permits.
- Whether the issue appears with another tested combination.
Retest the same steps after a fix. A changed DOM or ARIA attribute is not sufficient evidence if the spoken workflow remains confusing.
Common failures and fixes
Focus skips a control
Likely cause: a disabled-looking element is not keyboard focusable, or positive tabindex values reorder the page. Fix: use native controls where possible, remove inappropriate tabindex values, and retest forward and backward traversal.
Rank #4
- Power Specification：Power Supply with Input 100-240V- 50/60Hz;
- Safety Provide: This power supply ensures safe use with over voltage, over current, and over temperature protection.
- Package Included: 1 x wall Charger. Lightweight and easy to carry.
- Prior to using this charger, consult a qualified professional or the device manufacturer to verify compatibility. Device specifications, power requirements, and safety certifications may vary by model, version, region, or country.
The reader announces “button” with no useful name
Likely cause: an icon-only control lacks an accessible name. Fix: provide a programmatic label that describes the action, then verify it in DevTools and through speech.
A dialog opens but the reader remains on the page behind it
Likely cause: focus was not moved or constrained when the dialog opened. Fix: move focus to the dialog’s meaningful starting control, keep keyboard focus inside while modal, and return focus to the invoking control on close.
Updated results are silent
Likely cause: status text is inserted without an announced live region or focus change. Fix: expose concise status information using an appropriate semantic pattern and verify announcements after the update.
Automated checks pass, but the task is confusing
Likely cause: the barrier occurs during interaction, in reading order, or in the wording of announcements. Fix: keep the manual task test as the acceptance criterion and use automation to locate additional detectable defects.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteBest Value
- Power Specification：Power Supply with Input 100-240V- 50/60Hz;
- Safety Provide: This power supply ensures safe use with over voltage, over current, and over temperature protection.
- Package Included: 1 x wall Charger. Lightweight and easy to carry.
- Prior to using this charger, consult a qualified professional or the device manufacturer to verify compatibility. Device specifications, power requirements, and safety certifications may vary by model, version, region, or country.
The tester cannot tell whether a command is correct
Likely cause: unfamiliarity with the screen reader’s browse, focus, or rotor commands. Fix: practice the reader’s documented navigation model or pair with an experienced user before filing a product defect.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
For a visual record of a page state alongside your accessibility notes, ScreenshotNeo can return a screenshot or PDF from one request. It accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status.
See the parameter details in the ScreenshotNeo documentation. cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Its MCP server also gives Claude, Cursor, and other MCP clients take_screenshot, get_page_info, and capture_pdf tools. One thousand screenshots per month are free with no card; paid plans start at $5 for 3,000. Sign up for the free plan.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Frequently Asked Questions
Does testing with Edge prove the site works in Chrome or Safari?
No. Browser-to-platform accessibility mappings differ. Test the combinations your audience and support commitments require.
Can Lighthouse certify that a page is screen-reader accessible?
No. Lighthouse and other automated checks find detectable conditions, while many barriers appear only during interactive use with a real assistive technology.
Should I test every screen reader?
There is no universal minimum matrix. Start with the operating systems and readers your users rely on, then expand when product evidence or support requirements justify it.
What should I do when a screen-reader command seems not to work?
Confirm the reader’s navigation mode and command first. Once you can reproduce the expected command behavior, determine whether the page or the reader is responsible.
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.
