The Blind Bridge · Work Guides
Work Tools That Work With a Screen Reader
In short
The biggest barrier to blind employment usually isn’t skill — it’s software: in a 2023 study, more than 75% of Fortune 500 job application systems had critical accessibility barriers. This guide gives honest verdicts on the tools employers actually use — Zoom is the best of the video meetings, Teams is clunky, Google Meet weakest — plus job boards, HR portals, and the JAWS-versus-NVDA question at work. It also covers the clock that matters: the EEOC filing deadline is 180 days, or 300 if your state has its own fair-employment agency.
The biggest barrier to blind employment usually isn't skill — it's software. In a 2023 study, three experienced blind screen-reader users tried to apply for jobs at 30 randomly chosen Fortune 500 companies, and more than 75% of those companies' application systems had critical accessibility barriers. This guide gives honest verdicts on the tools employers actually use — video meetings, job boards, HR portals, whiteboards — plus the workarounds that get you through the bad ones. This guide contains no buy links.
Video meetings: Zoom, Teams, or Google Meet
If your employer lets you pick, the choice matters. Blind and low-vision screen-reader users consistently rank these three in the same order:
Zoom: the best of the three
Zoom is the most screen-reader-friendly meeting platform of the big three, and the one most blind professionals recommend. Buttons and menus are clearly labeled, it works well with JAWS, NVDA, and VoiceOver, it offers granular control over screen-reader alerts, and its keyboard shortcuts are intuitive enough to memorize: Alt+A mutes and unmutes, Alt+V toggles video, Alt+Y raises your hand. Accessibility reviewers widely regard Zoom and Teams as the two most accessible conferencing platforms, with Zoom the stronger of the two.
Verdict: best. If you get a say, pick Zoom. Its weak spots: the raised-hand button sits a menu level down and can be hard to find mid-meeting; breakout rooms and the built-in whiteboard can have accessibility issues; and nobody's shared screen is readable to a screen reader (see the shared-screen rule below).
Microsoft Teams: workable, clunkier
Teams is usable, but blind users describe navigating it as "clunky" — workable with patience rather than smooth. University accessibility reviewers warn that Teams "can be difficult for screen readers to navigate," and the American Foundation for the Blind's Workplace Tech Study flags Teams navigation problems and shared screenshows appearing as images. One consistent blind-user tip: the Teams mobile app is easier to navigate than the desktop app — worth knowing when you just need to join and talk.
Verdict: usable with patience. Learn the keyboard shortcuts for Teams screen-reader users, and keep the mobile app as your fallback for joining meetings. Microsoft documents a long list of screen-reader, keyboard, and high-contrast features — the platform has the features; the navigation is the friction.
Google Meet: improving, still the weakest
Meet keeps getting better, but in head-to-head comparisons of screen-reader compatibility it still ranks third. Blind-user research found the process of joining as a host time-consuming and not user-friendly. Meet's strengths are real-time captions and translation, which are genuinely good — but captions help hearing access, not screen-reader navigation.
Verdict: check before you commit. If your employer standardized on Meet, test-drive joining, muting, and hand-raising with your screen reader before your first real meeting so there are no surprises.
The shared-screen rule. No meeting platform reads someone else's shared screen to your screen reader — a shared screen is an image to every screen reader on every platform. This will never be a technical fix on your end. The fixes are social: ask the presenter to describe what they're showing, and ask for the slides or document before the meeting. "Materials are never provided to me in advance" is one of the most-reported workplace frustrations in the AFB's Workplace Tech Study — asking is not being difficult, it's the accommodation.
Job boards: where to look, what to avoid
The application is where most blind job seekers hit the wall first. Choose your hunting ground carefully.
Indeed: the most accessible major board
Indeed is the standout among mainstream job sites. It publishes an explicit accessibility commitment: its products are tested against JAWS and NVDA with Chrome, VoiceOver with Safari, and TalkBack with Chrome. Blind job seekers on the AppleVis forums repeatedly name the Indeed app and website as accessible and easy to use across Mac, Windows, and iOS.
Verdict: good — the default starting point. Set up job alerts by criteria and let the notifications come to you.
LinkedIn: fairly accessible, quick-apply helps
LinkedIn gets second place among blind job seekers: described as "fairly accessible" with a quick-apply feature that shortens the most painful part of the process, plus customizable search criteria and job notifications. ZipRecruiter also gets a positive mention from blind users who landed jobs through its app.
Verdict: good, especially quick-apply. Pair it with Indeed for coverage.
The traps: Taleo, Interview Exchange, and most company career pages
This is where the 75% figure bites. Hiring systems like Taleo (legacy; Oracle's successor is Oracle Recruiting Cloud) and Interview Exchange are documented as unusable for blind applicants — one applicant couldn't complete an application at his own alma mater. Simple widgets like date pickers and college dropdowns block entire applications. Monster gets "needs improvement" reviews from blind users.
The workaround that is your legal right: when an employer's application system blocks you, contact the employer's HR or accessibility contact and request an alternative way to apply — an email address, a phone number, a PDF form. Accessible application procedures are an ADA requirement, not a favor. HR telling you to "ask a friend or family member" to complete your application, as documented in AFB's hiring research, is not an acceptable answer.
HR and benefits portals: the software your employer picks
You don't choose this software — your employer does. But you have more leverage here than you think, because the law is unusually clear: the EEOC has sued over exactly this.
ADP: sued, then forced to fix it
ADP is the cautionary tale with a hopeful ending. After LightHouse for the Blind and Visually Impaired implemented ADP Workforce software in 2017, blind staff immediately hit barriers — and after years of trying to resolve them, LightHouse filed a class-action suit in September 2020. In December 2021 they reached an agreement: ADP would bring in a leading accessibility expert, fix the barriers in its Workforce Now web and mobile apps (timekeeping, pay, benefits, open enrollment), and — tellingly — the agreement explicitly states that overlay widgets like AudioEye and accessiBe "will not suffice" to achieve accessibility.
Verdict: much improved after the lawsuit; test your employer's instance. If your ADP portal still blocks you, your employer's IT can point at this agreement and demand the same fixes.
Workday: claims conformance; test your employer's instance
Workday publishes accessibility conformance reports against WCAG 2.2 AA, offers screen-reader support and keyboard navigation, and runs a dedicated accessibility team. But platform claims and your employer's customized instance are two different things — blind employees continue to report problems inside Workday deployments, and custom configurations can reintroduce barriers the base platform fixed.
Verdict: varies by employer. Workday the platform is committed on paper; your employer's implementation is what you actually live in. Run the same test: can you view your pay stub, request time off, and complete open enrollment with only your screen reader? If not, see the rights section below.
If your HR portal is inaccessible: what the Pearson case means for you
In August 2026, the EEOC announced that Pearson Education will pay $150,000 and submit to a three-year consent decree because its benefits, leave, and training platforms were unusable by visually impaired employees — and the company failed to provide reasonable accommodations that would have put blind employees' access on par with everyone else's. Under the decree, Pearson must have an accessibility consultant audit and fix the platforms, train HR staff annually, and report to the EEOC.
If this is your situation:
- Document it. Dates, screenshots or recordings, exactly which task failed (viewing a pay stub, enrolling in benefits, completing a training module).
- Put your accommodation request in writing — to HR and to your manager. A written request is protected activity. Describe the barrier and propose the fix: an accessible alternative, an accessible version of the content, or hands-on assistance as an interim measure.
- Know the clock. The EEOC filing deadline is 180 days, or 300 days if your state or city has its own fair-employment agency — check, don't assume. You don't have to file to get results — many employers fix the problem once the request is in writing — but the deadline is your backstop.
Screen-reader tip for HR portals: these portals are often the worst-coded sites you'll use. Try the task in a second screen reader before concluding it's broken — what fails in NVDA sometimes works in JAWS, and vice versa. And try the mobile app; enterprise mobile apps are frequently more accessible than their desktop portals.
Whiteboards and shared canvases: the Miro problem
The scenario blind employees dread: your team adopts a visual collaboration tool you can't use, and the choice is between asking the team to change tools (and being seen as "not a team player") or shouldering the workarounds yourself. Miro is the most-reported example.
Miro's official position is that it supports screen readers (NVDA, JAWS, VoiceOver) and keyboard control — creating, reading, updating, and deleting board objects. But independent audits tell a cooler story: University College London's accessibility statement for Miro lists real failures, including widgets with no programmatic name, role, or state information. A whiteboard is inherently spatial, and even best-case screen-reader support makes live whiteboard sessions slow and partial for blind participants.
Verdict: don't count on participating live. Practical moves: ask a teammate to export or read the board's content into a shared doc after the session; ask for the session's decisions and action items in writing (reasonable and normal); and if you're ever consulted before a team adopts a whiteboard tool, ask one question: "Has anyone tested this with a screen reader?" That question, asked early, prevents the whole problem.
Screen readers at work: JAWS vs NVDA
You probably know both, but at work the trade-offs sharpen:
- JAWS is the enterprise standard — the screen reader most employer software is actually tested against. That testing matters: JAWS tends to work better with enterprise applications and heavy Excel workbooks. Pricing: around $90/year for a home license, $900–$1,600/year for professional (seen Oct 2026). Many employers purchase the professional license as a reasonable accommodation — ask; it is a standard, uncontroversial request.
- NVDA is free and excellent for general use, but it struggles more with enterprise software and has no professional support channel — when something breaks at 4 PM before a deadline, there is no one to call.
Verdict: keep both. Most blind professionals run JAWS as the workhorse (often employer-funded) and NVDA as the free backup — and switching between them is itself a troubleshooting technique, since the two readers handle broken web apps differently.
Everyday workarounds that actually work
- JAWS OCR: when a button or dialog is unlabeled, JAWS's convenient OCR can read the pixels. It is the single most-used emergency tool in blind workplaces (documented in Mississippi State's 2026 accessibility workarounds tip sheet).
- Switch readers: testing the same broken page in JAWS, NVDA, and VoiceOver is legitimate troubleshooting, not superstition.
- Memorize with a sighted colleague: for controls that never get labeled, a five-minute session mapping "third button from the left does X" beats fighting the same dialog daily.
- Go mobile: Teams, job-board apps, and HR portals are frequently more accessible on iOS or Android than on desktop. If the desktop app fights you, try the phone version before concluding the tool is unusable.
- Watch for update regressions: accessibility breaks in updates constantly — Slack's Activity view became incompatible with screen readers' Simplified Layout Mode in a February 2026 update (Slack v4.47.69) — Slack fixed it on March 4, 2026, and Uber's app updates have broken rating flows before. When something that worked stops working, check whether an update landed, report it, and roll back if you can while you wait.
Low-vision note: if you have usable vision, lean on the visual-accessibility settings before anything else: high-contrast and dark themes (Teams and Meet both offer them), Zoom's chat font-size control in its accessibility settings, and text scaling in Indeed and LinkedIn. Many low-vision professionals combine magnification with a screen reader for the dense parts (spreadsheets, HR portals) and read visually for the rest. Also: colorblind filters in meeting and office apps fix more than people expect — check whether yours are actually applied in every mode, since some apps drop them in certain views.
The bottom line
Zoom first for meetings, Indeed and LinkedIn for the hunt, both screen readers installed, and a written paper trail the moment an employer's system blocks you. The software landscape is genuinely better than it was five years ago — Indeed tests with screen readers, Zoom labels its buttons, ADP got sued into fixing its portal — but the traps (Taleo-style application systems, inaccessible HR portals, whiteboard tools adopted without testing) are still the norm, not the exception. The Pearson consent decree is your proof that "the software just is that way" is not an acceptable answer from an employer. It isn't.