fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-09-19 20:02:10 +00:00
Code Issues Projects Releases Wiki Activity

New note: comparing screen readers

Browse source
This commit is contained in:
Rohan Kumar 2022-09-01 09:28:14 -07:00
parent 06bc35f25b
commit 96c01dfacf
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
content/notes/comparing-screen-readers.md Normal file
View file

@ -0,0 +1,15 @@
---
title: "Comparing screen readers"
date: 2022-09-01T09:28:07-07:00
replyURI: "https://mastodon.social/@modulux/108923799270415125"
replyTitle: "NVDA is the one to try on Windows"
replyType: "SocialMediaPosting"
replyAuthor: "David P A"
replyAuthorURI: "https://mastodon.social/@modulux"
---
On Windows, NVDA is more capable but Narrator + Edge is more secure. Narrator and Edge were designed to work without giving Narrator access to the content process, using the UI Automation API (UIA). Edge’s UIA was merged into upstream Chromium but it was only enabled in Edge. Matt Campbell wrote about it [on the orange site in January 2021](https://news.ycombinator.com/item?id=25667055); I don’t know if the situation has changed since then.
Try both. If Narrator works for you I’d stick to that. My main issue isn’t the lack of functionality, but the speech synthesizer delays (when it starts reading, the first words get dropped).
Mobile screen readers (Android TalkBack, iOS VoiceOver, KaiOS Readout) are more beginner-friendly but also much more limited.