You Don't Have to Be Blind to Use and benefit from the use of a Screen Reader, vy Simon Miner, August 18, 2025, received 2025 09 11
0 views
Skip to first unread message
Colin Howard
Sep 11, 2025, 9:54:20 AM (8 days ago) Sep 11
to post AVIP list
I am putting David Goldfield's list info and contacts at the start of this,
to aid ease of immediate accessability, it has been removed from the end of
this post.
David Goldfield,
Blindness Assistive Technology Specialist
If you need help using your assistive technology learn about my training
services by visiting
http://WWW.ScreenReaderTraining.com
JAWS Certified, 2022
NVDA Certified Expert
Subscribe to the Tech-VI announcement list to receive news, events and
information regarding the blindness assistive technology field.
Email: tech-vi+...@groups.io
http://www.DavidGoldfield.com
https://pedalpoint.com/2025/08/you-dont-have-to-be-blind-to-use-a-screen-reader/
A screen reader is a piece of assistive technology software that turns
on-screen text and interface elements into speech or braille output. It
works by sending information from the operating system, applications, and
web browsers through an accessibility API, which the screen reader
interprets and then reads aloud or displays on a refreshable braille device.
With keyboard commands or touch gestures, users can navigate headings,
links, buttons, forms, and other elements, making it possible to interact
with a computer or smartphone without needing to rely on vision.
More than a tool for blind users
When most people hear "screen reader," they picture someone who is
completely blind using it to access a computer or phone. That's true for
many-but far from all-users. The most recent WebAIM Screen Reader User
Survey found that 23.4% of screen reader users are not blind.
Some have low vision, some have dyslexia or other reading differences, and
some simply prefer the flexibility of audio. Others are developers,
designers, content creators, or testers who use screen readers as part of
their work.
I'm one of them. I have low vision and am legally blind, but I still read
with magnification and zoom. Even so, I often use screen readers and
text-to-speech because they're faster, easier on my eyes, and more
comfortable for long stretches. For me-and for many others-screen readers
aren't about replacing sight, but about expanding options.
Listening as speed reading
On my Apple devices, I've set up easy-to-use shortcuts to activate the
built-in VoiceOver screen reader and set its speaking rate to 85% of its
maximum speech rate. For context, typical human conversation is around 150
words per minute. At 85% of VoiceOver's top speed, I'm hearing words roughly
three to four times faster than that.
It didn't start this way. I began at a comfortable pace, then gradually
increased the speed over time. My brain learned to process synthetic speech
the same way you might adapt to a fast talker. Now, that pace feels normal,
and I can move through emails, articles, and reports in a fraction of the
time.
Speed aside, the other benefit is comfort. If my eyes are tired from hours
of visual work, I can switch to listening mode and keep going without strain
or headaches. It's a tool I can pick up whenever it fits the task.
Who else benefits from screen readers
Plenty of people beyond the blind community use screen readers or similar
tools:
People with low vision: Alternating between magnification and audio can
prevent fatigue and headaches.
Individuals with dyslexia or other learning differences: Listening can make
text easier to process and understand. (More from dyslexia.com.)
Multitaskers: Screen readers let you consume text while cooking, walking,
cleaning, or commuting.
Anyone with eye strain or migraines: Audio provides a break from bright
screens and fine print.
Auditory and language learners: Hearing words reinforces learning and
improves pronunciation.
Accessibility professionals: Designers, developers, and content creators use
them to test how accessible their work is.
For many, it's simply about using the right mode of reading for the right
moment.
Common concerns-and practical solutions
Here are some concerns and questions that often come up for sighted folks
when they first consider trying out a screen reader.
"The controls look complicated." They can be at first, but you don't have to
learn everything. Start with turning it on/off, making it start and stop
reading, and moving forward/back. Build from there.
"What if my device starts reading aloud in public?" Use headphones. Learn
the quick mute command (often just pressing Ctrl or a two-finger tap on
mobile).
"The voice is too fast." Adjust the speed to a comfortable pace. You can
always increase it later as you get used to it.
"I'm not blind-is it okay to use this?" Absolutely! Accessibility features
are built for anyone who can benefit from them.
Getting started with a screen reader
Almost every modern flavor of smartphone, tablet, or computer today comes
with a screen reader already pre-installed. So chances are it's just a
matter of turning it on trying it out. Here are some basic commands for the
built-in screen readers for the most common devices and operating systems.
Windows: Narrator
Pre-installed on all PCs running Windows 10 or 11.
Turn on/off: Press Ctrl + Windows + Enter.
Read everything on the page: Caps Lock + M.
Stop reading: Press Ctrl.
Microsoft's complete Narrator user guide includes detailed instructions and
all commands.
Many Windows users also love NVDA, a more full-featured screen reader that's
free to download and easy to install.
macOS: VoiceOver
Turn on/off: Press Command + F5.
Move forward: Control + Option + Right Arrow.
Read from the top: Control + Option + A.
See Apple's VoiceOver guide for Mac for much more.
iPhone/iPad: VoiceOver
Turn on/off: Triple-click the side or Home button.
Read the screen: Swipe down with two fingers.
Apple's iOS VoiceOver guide explains all gestures.
Android: TalkBack
Turn on/off: Hold both volume keys for a few seconds (if enabled).
Read from the top: Swipe down then right, then select "Read from top."
See Google's TalkBack tutorial for many more details.
Chrome OS: ChromeVox
This screen reader comes pre-installed on Chromebooks.
Turn on/off: Press Ctrl + Alt + Z.
Start reading from the top: Press Search + Ctrl + Right Arrow.
Stop reading: Press Ctrl.
Move to the next item: Press Search + Right Arrow.
Move to the previous item: Press Search + Left Arrow.
Google provides a ChromeVox tutorial with more commands and training
resources.
A gentle first step: Site Unseen
If you'd like to experience what navigating by structure feels like-but
without fully switching to a screen reader-try Site Unseen.
Site Unseen is a Chrome extension that approximates a screen reader by
obscuring the visible content of the page and showing details of the
currently focused element in a small box at the bottom right of the screen.
You navigate with screen reader-like commands-jumping through headings,
links, form fields, and more-and can use its "Peek" feature for a brief
three-second view of where you are on the page. I wrote a post that offers a
deep dive into the what, why, and how of Site Unseen.
It's not a substitute for a real screen reader, but it's a great training
ground for learning keyboard navigation and understanding how structural
elements on a webpage matter.
Everyday scenarios where screen readers help
Here are a several examples of how screen readers can be put to everyday
use, whether for accessibility, productivity, or both:
Making dinner: Have an article read to you while cooking.
Commuting: Let VoiceOver or TalkBack read the news or email while on a bus
or train.
Tidying up: Listen to a report while folding laundry or cleaning the
kitchen.
Walking or exercising: Catch up on long blog posts while staying in shape
without having to stare at your phone.
Research days: Use a screen reader to skim and navigate long documents
quickly.
Language practice: Hear correct pronunciations in context and follow along
visually if you like.
Rest days for your eyes: Give your eyes a break from magnification or bright
screens.
Testing your own work: If you design or publish online content, a quick
screen reader check can reveal accessibility issues you'd miss visually.
Reading when vision is limited by environment: In low light or glare,
listening can be far easier than reading.
Give it a try
You might discover that listening is sometimes more efficient than
reading-especially for repetitive or text-heavy work. It's also an
eye-saver. Even if you have perfect vision, switching to audio for part of
the day can prevent fatigue.
Learning a screen reader also builds empathy. Navigating your own site or a
favorite app without sight gives you a clear sense of what works and what's
frustrating for users with disabilities. For developers and content
creators, that insight can directly improve the quality and accessibility of
your work.
And there's a personal bonus: once you've built some fluency, you gain
flexibility. You can choose to read visually, listen hands-free, or mix the
two depending on your needs. For me, that means I can keep working or
reading comfortably whether my eyes are fresh or tired.
It doesn't have to be an all-or-nothing commitment. You can start small-have
one article read aloud on your commute, or use Narrator for a quick email
scan-and see how it fits. Over time, you may find it becomes an everyday
tool, not just an "accessibility feature."
Acknowledgement
Thank you to James Warnken for inspiring this post through his interview on
the Equal Entry blog, and for sharing his own experiences that challenge
assumptions about who uses screen readers.
Colin Howard, Southern England.
to aid ease of immediate accessability, it has been removed from the end of
this post.
David Goldfield,
Blindness Assistive Technology Specialist
If you need help using your assistive technology learn about my training
services by visiting
http://WWW.ScreenReaderTraining.com
JAWS Certified, 2022
NVDA Certified Expert
Subscribe to the Tech-VI announcement list to receive news, events and
information regarding the blindness assistive technology field.
Email: tech-vi+...@groups.io
http://www.DavidGoldfield.com
https://pedalpoint.com/2025/08/you-dont-have-to-be-blind-to-use-a-screen-reader/
A screen reader is a piece of assistive technology software that turns
on-screen text and interface elements into speech or braille output. It
works by sending information from the operating system, applications, and
web browsers through an accessibility API, which the screen reader
interprets and then reads aloud or displays on a refreshable braille device.
With keyboard commands or touch gestures, users can navigate headings,
links, buttons, forms, and other elements, making it possible to interact
with a computer or smartphone without needing to rely on vision.
More than a tool for blind users
When most people hear "screen reader," they picture someone who is
completely blind using it to access a computer or phone. That's true for
many-but far from all-users. The most recent WebAIM Screen Reader User
Survey found that 23.4% of screen reader users are not blind.
Some have low vision, some have dyslexia or other reading differences, and
some simply prefer the flexibility of audio. Others are developers,
designers, content creators, or testers who use screen readers as part of
their work.
I'm one of them. I have low vision and am legally blind, but I still read
with magnification and zoom. Even so, I often use screen readers and
text-to-speech because they're faster, easier on my eyes, and more
comfortable for long stretches. For me-and for many others-screen readers
aren't about replacing sight, but about expanding options.
Listening as speed reading
On my Apple devices, I've set up easy-to-use shortcuts to activate the
built-in VoiceOver screen reader and set its speaking rate to 85% of its
maximum speech rate. For context, typical human conversation is around 150
words per minute. At 85% of VoiceOver's top speed, I'm hearing words roughly
three to four times faster than that.
It didn't start this way. I began at a comfortable pace, then gradually
increased the speed over time. My brain learned to process synthetic speech
the same way you might adapt to a fast talker. Now, that pace feels normal,
and I can move through emails, articles, and reports in a fraction of the
time.
Speed aside, the other benefit is comfort. If my eyes are tired from hours
of visual work, I can switch to listening mode and keep going without strain
or headaches. It's a tool I can pick up whenever it fits the task.
Who else benefits from screen readers
Plenty of people beyond the blind community use screen readers or similar
tools:
People with low vision: Alternating between magnification and audio can
prevent fatigue and headaches.
Individuals with dyslexia or other learning differences: Listening can make
text easier to process and understand. (More from dyslexia.com.)
Multitaskers: Screen readers let you consume text while cooking, walking,
cleaning, or commuting.
Anyone with eye strain or migraines: Audio provides a break from bright
screens and fine print.
Auditory and language learners: Hearing words reinforces learning and
improves pronunciation.
Accessibility professionals: Designers, developers, and content creators use
them to test how accessible their work is.
For many, it's simply about using the right mode of reading for the right
moment.
Common concerns-and practical solutions
Here are some concerns and questions that often come up for sighted folks
when they first consider trying out a screen reader.
"The controls look complicated." They can be at first, but you don't have to
learn everything. Start with turning it on/off, making it start and stop
reading, and moving forward/back. Build from there.
"What if my device starts reading aloud in public?" Use headphones. Learn
the quick mute command (often just pressing Ctrl or a two-finger tap on
mobile).
"The voice is too fast." Adjust the speed to a comfortable pace. You can
always increase it later as you get used to it.
"I'm not blind-is it okay to use this?" Absolutely! Accessibility features
are built for anyone who can benefit from them.
Getting started with a screen reader
Almost every modern flavor of smartphone, tablet, or computer today comes
with a screen reader already pre-installed. So chances are it's just a
matter of turning it on trying it out. Here are some basic commands for the
built-in screen readers for the most common devices and operating systems.
Windows: Narrator
Pre-installed on all PCs running Windows 10 or 11.
Turn on/off: Press Ctrl + Windows + Enter.
Read everything on the page: Caps Lock + M.
Stop reading: Press Ctrl.
Microsoft's complete Narrator user guide includes detailed instructions and
all commands.
Many Windows users also love NVDA, a more full-featured screen reader that's
free to download and easy to install.
macOS: VoiceOver
Turn on/off: Press Command + F5.
Move forward: Control + Option + Right Arrow.
Read from the top: Control + Option + A.
See Apple's VoiceOver guide for Mac for much more.
iPhone/iPad: VoiceOver
Turn on/off: Triple-click the side or Home button.
Read the screen: Swipe down with two fingers.
Apple's iOS VoiceOver guide explains all gestures.
Android: TalkBack
Turn on/off: Hold both volume keys for a few seconds (if enabled).
Read from the top: Swipe down then right, then select "Read from top."
See Google's TalkBack tutorial for many more details.
Chrome OS: ChromeVox
This screen reader comes pre-installed on Chromebooks.
Turn on/off: Press Ctrl + Alt + Z.
Start reading from the top: Press Search + Ctrl + Right Arrow.
Stop reading: Press Ctrl.
Move to the next item: Press Search + Right Arrow.
Move to the previous item: Press Search + Left Arrow.
Google provides a ChromeVox tutorial with more commands and training
resources.
A gentle first step: Site Unseen
If you'd like to experience what navigating by structure feels like-but
without fully switching to a screen reader-try Site Unseen.
Site Unseen is a Chrome extension that approximates a screen reader by
obscuring the visible content of the page and showing details of the
currently focused element in a small box at the bottom right of the screen.
You navigate with screen reader-like commands-jumping through headings,
links, form fields, and more-and can use its "Peek" feature for a brief
three-second view of where you are on the page. I wrote a post that offers a
deep dive into the what, why, and how of Site Unseen.
It's not a substitute for a real screen reader, but it's a great training
ground for learning keyboard navigation and understanding how structural
elements on a webpage matter.
Everyday scenarios where screen readers help
Here are a several examples of how screen readers can be put to everyday
use, whether for accessibility, productivity, or both:
Making dinner: Have an article read to you while cooking.
Commuting: Let VoiceOver or TalkBack read the news or email while on a bus
or train.
Tidying up: Listen to a report while folding laundry or cleaning the
kitchen.
Walking or exercising: Catch up on long blog posts while staying in shape
without having to stare at your phone.
Research days: Use a screen reader to skim and navigate long documents
quickly.
Language practice: Hear correct pronunciations in context and follow along
visually if you like.
Rest days for your eyes: Give your eyes a break from magnification or bright
screens.
Testing your own work: If you design or publish online content, a quick
screen reader check can reveal accessibility issues you'd miss visually.
Reading when vision is limited by environment: In low light or glare,
listening can be far easier than reading.
Give it a try
You might discover that listening is sometimes more efficient than
reading-especially for repetitive or text-heavy work. It's also an
eye-saver. Even if you have perfect vision, switching to audio for part of
the day can prevent fatigue.
Learning a screen reader also builds empathy. Navigating your own site or a
favorite app without sight gives you a clear sense of what works and what's
frustrating for users with disabilities. For developers and content
creators, that insight can directly improve the quality and accessibility of
your work.
And there's a personal bonus: once you've built some fluency, you gain
flexibility. You can choose to read visually, listen hands-free, or mix the
two depending on your needs. For me, that means I can keep working or
reading comfortably whether my eyes are fresh or tired.
It doesn't have to be an all-or-nothing commitment. You can start small-have
one article read aloud on your commute, or use Narrator for a quick email
scan-and see how it fits. Over time, you may find it becomes an everyday
tool, not just an "accessibility feature."
Acknowledgement
Thank you to James Warnken for inspiring this post through his interview on
the Equal Entry blog, and for sharing his own experiences that challenge
assumptions about who uses screen readers.
Colin Howard, Southern England.
mj.ba...@gmail.com
Sep 11, 2025, 12:50:08 PM (8 days ago) Sep 11
to avip...@googlegroups.com
Hi Colin
Thanks for this article, which I found interesting.
I find your recent practice of putting David Goldfield's long list of contact details and qualifications at the head of articles a nuisance, rather than a help. It seems more logical to leave it where it was at the bottom, so that, having read the article, if someone then wishes to contact the author they can do so. That probably does not apply to most of us, so we can exit at that point.
Best wishes
Mike
--
You received this message because you are subscribed to the Google Groups "AVIP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to avipworld+...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/avipworld/004a01dc2323%248e885880%240d01a8c0%40Colin1.
Thanks for this article, which I found interesting.
I find your recent practice of putting David Goldfield's long list of contact details and qualifications at the head of articles a nuisance, rather than a help. It seems more logical to leave it where it was at the bottom, so that, having read the article, if someone then wishes to contact the author they can do so. That probably does not apply to most of us, so we can exit at that point.
Best wishes
Mike
You received this message because you are subscribed to the Google Groups "AVIP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to avipworld+...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/avipworld/004a01dc2323%248e885880%240d01a8c0%40Colin1.
Colin Howard
Sep 11, 2025, 1:45:38 PM (8 days ago) Sep 11
to avip...@googlegroups.com
Mike,
I only started putting it at the head because people may not read to the end
of posts hence miss this what I consider to be important info.
You are the only person who so far, has expressed an opinion on my changes,
if others find it irksome, I'll stop including the info.
https://groups.google.com/d/msgid/avipworld/001701dc233c%241eba5490%245c2efdb0%24%40gmail.com.
I only started putting it at the head because people may not read to the end
of posts hence miss this what I consider to be important info.
You are the only person who so far, has expressed an opinion on my changes,
if others find it irksome, I'll stop including the info.
Chris Biles
Sep 11, 2025, 3:11:36 PM (8 days ago) Sep 11
to colinho...@gmail.com, avip...@googlegroups.com
Colin.
As you clearly consider the contact details for David Goldfield to be so important, might not the simplest solution be to revert to the previous practice of including his contact details at the end of any message sent from this source, so that those who are interested in such details can locate them if required.
Thanks.
CB.
---Original Message---
From: Colin Howard <colinho...@gmail.com>
Sent: 2025-09-11 17:45:36
Subject: Re: [avip] You Don't Have to Be Blind to Use and benefit from the use of a Screen Reader, vy Simon Miner, August 18, 2025, received 2025 09 11
To view this discussion, visit https://groups.google.com/d/msgid/avipworld/005301dc2343%24dee1e740%240d01a8c0%40Colin1.
Reply all
Reply to author
Forward
0 new messages