accessibility

The Digital Door Is Closing on Disabled Americans: Please Help Us Keep It Open

by

Imagine you are blind. Your child has a disability. The school district has just posted crucial updates to its website about your son’s Individualized Education Program — his IEP, the legally mandated document that governs every support, accommodation, and service your child is supposed to receive in school. You open the site. Your screen reader — the software that speaks text aloud so you can navigate a world built for sighted people — hits a wall. Images have no descriptions. Forms won’t load. Buttons have no labels. You click again and again, trapped in a digital maze with no exit.

Now imagine learning that your tax dollars paid for that website.

This is not a hypothetical. This is the daily reality for millions of Americans with disabilities. And right now, the federal government is moving to weaken a rule that was specifically designed to end this kind of exclusion.

We are asking you — disabled people, parents, family members, friends, teachers, healthcare workers, religious leaders, and every person of conscience — to take one action: request a virtual meeting with the Office of Information and Regulatory Affairs (OIRA) and tell them to leave the 2024 Title II accessibility rule intact.

Click here to request a meeting.

What Is Happening and Why It Matters

In April 2024, after decades of advocacy by disabled people and their allies, the U.S. Department of Justice finalized a rule under Title II of the Americans with Disabilities Act requiring state and local governments to make their websites and mobile applications accessible to people with disabilities. The technical standard adopted — the Web Content Accessibility Guidelines, version 2.1, Level AA (known as WCAG 2.1 AA) — is an internationally recognized benchmark. For large government entities serving populations of 50,000 or more, the compliance deadline is April 24, 2026.

This rule was hard-won. The DOJ has recognized since at least 2003 that state and local government websites must be accessible under the ADA. The 2024 rule finally put concrete, enforceable teeth into that obligation.

But on February 13, 2026, OIRA — the Office of Information and Regulatory Affairs, an arm of the Office of Management and Budget — published a notice revealing that the Department of Justice had submitted a revised rule to OIRA as an “Interim Final Rule,” or IFR. Unlike a proposed rulemaking, an IFR does not require a public comment period. The public has not been shown what revisions are being proposed. This has never been done before with an accessibility regulation.

The changes could push back or eliminate the April 2026 deadline. They could hollow out other requirements. No one outside the agencies knows yet.

What we do know is this: anyone can request a virtual meeting with OIRA under Executive Order 12866 to explain why the rule matters and should not be changed. The agency is not required to grant a meeting, and a meeting does not guarantee an outcome. But if thousands of people and organizations step forward, their voices will be on the record — and in any future legal challenge to changes in the rule, that record may matter enormously.

The deadline is urgent. The April 24 compliance date for large governments is weeks away.

The Price of Inaccessibility: A Door Slammed in Your Face

When a government website is inaccessible to a blind person, it isn’t a minor inconvenience. It is the digital equivalent of a flight of stairs at the entrance of a government building — it says, without apology, you do not belong here.

Seven out of ten blind people report being unable to access information and services through government websites. Two-thirds of internet transactions initiated by people with vision impairments end in abandonment because the websites they visit are not accessible enough.

Consider what those transactions represent. They are not online shopping. They are applications for Medicaid. They are searches for food assistance. They are registration for school services for disabled children. They are requests for healthcare accommodations. They are the mechanisms through which citizens — including disabled citizens who are fully taxpaying members of their communities — participate in public life.

Inaccessible websites and mobile apps can make it difficult or impossible for people with disabilities to access government services, like ordering mail-in ballots or getting tax information, that are quickly and easily available to other members of the public online. They can keep people with disabilities from joining or fully participating in civic or other community events like town meetings or programs at their child’s school.

The harm is not abstract. During the COVID-19 pandemic, in at least seven states, blind residents said they were unable to register for the vaccine through their state or local governments without help. Phone alternatives, when available, were beset with long hold times and were not available at all hours like websites. “This is outrageous,” declared one disability advocate at the time, noting that blind people were being denied the ability to access something to get vaccinated during a public health emergency.

The Taxpayer Injustice

Here is something that should make every American’s blood boil, regardless of disability status.

The overwhelming majority of state and local government websites — the portals that serve parks departments, public schools, health departments, voting offices, libraries, transit authorities, courts, and social services — are funded by taxpayers. Property taxes. Sales taxes. Income taxes. Every resident pays into the system that builds and maintains these digital public squares.

Blind taxpayers pay these taxes. Deaf taxpayers pay these taxes. People with physical, cognitive, and neurological disabilities pay these taxes. And then, in far too many cases, they are locked out of the very websites and apps their money built.

This is not just bad policy. It is a profound ethical failure. It is taxation without representation. It is saying to an entire class of citizens: you will fund this, but you will not be allowed to use it.

The 2024 rule was an attempt to right this wrong — to ensure that when government spends public money on digital infrastructure, all the public can actually use it. Weakening or delaying this rule is a choice to perpetuate that injustice.

When Inaccessibility Has Real Consequences: Maria’s Story

Maria, a blind mother of two in a mid-sized American city, spent three days trying to access her daughter’s school district website after her daughter — who has a learning disability — was referred for a special education evaluation. The site, like most school district websites of its era, was built without accessibility in mind.

The forms to request records were PDF images — effectively photographs of documents, invisible to a screen reader. The contact directory was a graphic with no text alternative. The link to the district’s special education office was buried in a nested navigation menu that her screen reader could not parse. When she finally found a phone number and called, she was told to visit the website.

Maria’s story is representative. Administrative burdens — including inaccessible and poorly designed websites and complex application processes — cause real, lasting harm to disabled Americans, making it difficult to navigate a system that is supposed to help them cover basic necessities such as food, housing, and medical treatments. For a blind parent trying to advocate for a disabled child in a system that was never built with either of them in mind, the barriers compound each other into something that can feel insurmountable.

Maria eventually got help — from a sighted neighbor who could access the forms on her behalf. But consider what that means. A blind mother, exercising her legal rights on behalf of her disabled child, was forced to surrender her privacy and independence to a third party because a taxpayer-funded website could not do what basic accessibility standards would have required. Her child’s educational rights, her own dignity, and her family’s confidentiality were all casualties of inaccessibility.

When Accessibility Is Won: Angela Fowler’s Story

The story does not have to end in barriers. When accessibility is fought for and won, careers are saved, lives change, and the principle of equal access becomes real rather than rhetorical.

Angela Fowler had worked hard her entire life. She was a longtime member of the National Federation of the Blind, and she had earned a provisional job offer from an insurance carrier — contingent on passing California’s online insurance agent licensing exam. It should have been the next step in a promising career. Instead, it became a wall.

When Fowler sat down to take the state-administered exam, she discovered that the online testing platform used by the California Department of Insurance was completely inaccessible to her screen reader. She could not navigate it. She could not take the test. And when she asked the state to simply make the platform accessible — as California’s own disability access laws required — she was told she would first need to submit her private medical records to justify using a screen reader. Nondisabled applicants were not required to do anything of the sort. The process dragged on. The job offer she had worked toward disappeared.

In 2021, Fowler, joined by a second blind applicant named Miguel Mendez and later the National Federation of the Blind, filed suit against the California Department of Insurance and its testing vendor, PSI Services LLC. The case, Fowler et al. v. PSI Services LLC and California Department of Insurance, was a landmark disability rights action. It argued the obvious: that a state-run licensing examination system must be independently usable by blind applicants who use screen readers — without extra hoops, without burdensome medical documentation requirements, and without segregation from the testing experience available to everyone else.

In August 2024, the case settled. Under the agreement, the California Department of Insurance agreed to no longer require blind or low-vision test-takers who use screen access software to first provide medical documentation. Blind and low-vision test-takers who use screen readers gained access to the same examination scheduling options as those offered to others without disabilities.

NFB President Mark Riccobono called it a meaningful step toward a society that provides equal opportunity to everyone. Attorney Timothy Elder of TRE Legal Practice put it plainly: this case establishes that people who depend on assistive technology should not need a doctor’s note before they can expect an accessibly designed online exam.

Angela Fowler lost the job she had earned. But her fight — her refusal to accept that a government-run system could simply exclude her — ensured that the next blind person who wants to become an insurance agent in California will not face what she faced. That is what accessibility wins look like. That is what is at stake.

The 2024 rule was not asking for perfection. It was asking for a reasonable, internationally recognized standard. It was asking that government — of the people, by the people, for all of the people — actually serve all of the people.

A Word to Every Parent

If you have a disabled child, this message is for you.

You already know what it means to fight for your child in systems that were not built for them. You’ve sat in IEP meetings, argued with insurance companies, driven across town to accessible playgrounds, and spent countless hours researching, advocating, and never giving up.

The 2024 rule was a victory for you and your child. It said: the school district’s website that posts your child’s rights, their services, their calendar, their teacher contacts — that website must be accessible to you, whether you have low vision, blindness, cognitive differences, or any other disability. It said your child deserves parents who can access every digital tool that other parents take for granted.

If that rule is weakened or delayed, it is your child who loses. The IEP portal that you can’t open. The therapy scheduling app that won’t work with your screen reader. The school board meeting you couldn’t participate in because the registration link was broken.

Please. Request a meeting with OIRA. Tell them what your family’s digital access means to you. Tell them that your disabled child deserves parents who can fight for them with the same tools as everyone else.

Request a meeting here.

A Word to Every Friend and Ally

If you have a disabled friend — someone you love, laugh with, and care about — and you call yourself their ally, this is the moment that word is tested.

Disability is not a narrative device. It is not a cause for pity. It is a part of human experience shared by one in four Americans, including people who are brilliant, creative, funny, accomplished, and fully deserving of every digital door that the rest of the world walks through without a second thought.

When your blind friend cannot apply for transit benefits on her phone because the app is inaccessible, she is not experiencing a personal inconvenience. She is experiencing systematic exclusion. When your deaf colleague cannot watch the captionless public health video his county just posted, he is being told — by his own government — that he is not important enough to include.

Allyship means showing up when the stakes are real, not just retweeting hashtags. Requesting a five-minute virtual meeting with a federal regulatory office is one of the lowest-barrier, highest-impact things you can do right now for every disabled person in your life.

Do it because you love them. Do it because they would do it for you.

A Word to Teachers, Educators, and Healthcare Workers

You chose your profession because you believe in the dignity and potential of every person you serve. Every day, you work to ensure that students with disabilities get the education they deserve, that patients with disabilities receive the care they need.

But your work is undermined when the digital tools that are supposed to support it are inaccessible. A teacher of blind students who cannot access the district’s curriculum portal. A school counselor who cannot help a deaf student register for services online. A social worker who cannot guide a disabled client through a state benefits application because the site won’t work with assistive technology.

The 2024 rule would have made these failures less common. Weakening it makes them more so.

You have professional standing. You have community standing. A message from an educator or healthcare provider to OIRA carries weight. Please use it.

A Word to Religious Leaders — and to the Faithful

Every major world religion calls its followers to care for the vulnerable, to remove obstacles from the paths of those who struggle, and to treat all people as beings of sacred worth.

The Hebrew Bible commands, in Leviticus 19:14: “You shall not curse the deaf or place a stumbling block before the blind.” Jewish tradition teaches that stumbling blocks come in many forms — from inaccessible buildings to health care that is harder to access — and that we are obligated to remove them. The Torah repeatedly instructs: “If there be among you a person with needs, you shall not harden your heart, but you shall surely open your hand.” (Deuteronomy 15:7)

The Gospel of Luke records Jesus saying that when you give a feast, you should invite those who cannot repay you — the poor, the crippled, the lame, the blind — “and you will be blessed.” (Luke 14:13–14) In Matthew 25:40, Jesus declares: “Whatever you did for the least of these brothers and sisters of mine, you did for me.” Turning away from the exclusion of disabled people is, in this framework, turning away from Christ himself.

In Islamic teaching, the Prophet Muhammad said: “If you want to find me, find me amongst the weak, because you are not given victory or aid from Allah except by the way that you treat those who are weak and oppressed.” The Quran directly addresses the treatment of blind people: in Surah Abasa (80:1–10), Allah rebukes the Prophet for turning away from a blind man who came seeking knowledge, teaching that every person — regardless of ability — deserves full attention and dignity. A Hadith states: “Cursed is the one who misleads a blind person away from his path” (Sunan Abu Dawud 2594) — understood both as an individual prohibition and a communal warning: a society that does not respect or care for those with special needs will be cursed.

In Buddhist teaching, karuna — compassion — is one of the four divine abodes, a foundational virtue applied without distinction to all beings. The Hindu concept of seva, selfless service, calls the faithful to act on behalf of those who are vulnerable. In the Sikh tradition, sewa — selfless service — is among the highest moral obligations.

If your faith calls you to love your neighbor, then your neighbor includes every blind person who cannot open a government website, every deaf person who cannot watch a public health video without captions, every person with a cognitive disability who cannot navigate a form that was built without them in mind.

Religious leaders: preach this. Organize your congregations. Help your laypeople understand that accessibility is a moral issue, not a technical one. Encourage every member of your community to request a meeting with OIRA. This is the work of faith made concrete.

What You Need to Do Right Now

Requesting a meeting with OIRA is straightforward. Here is how:

  1. Go to this link: https://www.reginfo.gov/public/do/eo/neweomeeting?rin=1190-AA82
  2. Provide your name, email, and phone number. You will receive a confirmation with a link to schedule your virtual meeting.
  3. When prompted, describe what you will present. You do not need legal language. You do not need to be an expert. Write in plain language. You might say things like:
    • How inaccessible government websites have affected you or your family member
    • Why the April 2026 deadline matters and should not be extended
    • What specific government services — parks, schools, libraries, health departments, voting — you depend on and need to be accessible
    • That the DOJ has recognized since 2003 that government websites must be accessible under the ADA, and this rule simply puts concrete standards to a long-standing obligation
    • That many state and local governments are already in compliance with the rule — and that following it has actually helped lower their costs over time
  4. You can request a meeting as an individual or on behalf of an organization. Both matter. The more voices, the stronger the record.
  5. Share this article. Send it to parents, teachers, pastors, imams, rabbis, priests, coaches, neighbors, and friends. Post it on social media. Read it aloud to someone who cannot read it themselves. The power of this moment lies entirely in how many people choose to show up.

The Rule Is Still the Rule — Until It Isn’t

It bears repeating: as of the publication of this article, the 2024 Title II accessibility rule is still in effect. The ADA still requires that state and local government websites and apps be accessible to disabled people. No change has yet been made.

But “not yet” is not “never.” An Interim Final Rule process moves quickly. Changes could come before the April 24 deadline. The window for public voices to be heard is narrow.

We have waited long enough. Disabled people have waited decades for a digital world that includes them. We have watched as every other aspect of public life went online — voting, education, healthcare, civic participation — and watched as too much of it was built without us.

We are not asking for special treatment. We are asking for access to what everyone else already has.

We are asking for the right to open the door.

Please, request your meeting today. For yourself. For your child. For your friend. For your neighbor. For the blind grandmother who cannot access her county health department’s website. For the deaf father who cannot watch the public school board meeting. For every disabled person who has ever stared at a screen that stared back — blank, impassable, indifferent.

This is the moment. The door is still open. Let’s make sure it stays that way.

Request Your OIRA Meeting Now →

Blind Access Journal covers accessibility, disability rights, and assistive technology. We are grateful to disability rights attorney Lainey Feingold, whose legal analysis at lflegal.com provided essential background for this article. We encourage all readers to visit her site for in-depth legal context and additional resources.

The Americans with Disabilities Act continues to require accessible websites and apps regardless of any changes to the 2024 rule. The fight for digital inclusion continues.

Sources

  1. Feingold, Lainey. “Tell the Federal Government Not to Change the Title II Accessibility Regulations.” Law Office of Lainey Feingold, March 2, 2026. https://www.lflegal.com/2026/03/title-ii-action-needed/
  2. Office of Information and Regulatory Affairs (OIRA). “Pending EO 12866 Regulatory Review — RIN 1190-AA82.” Reginfo.gov, February 13, 2026. https://www.reginfo.gov/public/do/eoDetails?rrid=1282112
  3. OIRA Meeting Request Portal — EO 12866 Virtual Meeting Request (RIN 1190-AA82). https://www.reginfo.gov/public/do/eo/neweomeeting?rin=1190-AA82
  4. U.S. Department of Justice. “Accessibility of Web Information and Services of State and Local Government Entities — Final Rule.” Federal Register, April 24, 2024. https://www.federalregister.gov/documents/2024/04/24/2024-07758/accessibility-of-web-information-and-services-of-state-and-local-government-entities
  5. Settlement Agreement: Fowler v. PSIhttps://dralegal.org/wp-content/uploads/2021/11/Settlement-Agreement-Fowler_fully-executed_Accessible.pdf
  6. Web Content Accessibility Guidelines (WCAG) 2.1. World Wide Web Consortium (W3C), June 5, 2018. https://www.w3.org/TR/WCAG21/
  7. The Holy Bible, New International Version. Leviticus 19:14. BibleHub. https://www.biblehub.com/leviticus/19-14.htm
  8. The Holy Bible, New International Version. Deuteronomy 15:7. BibleHub. https://www.biblehub.com/deuteronomy/15-7.htm
  9. The Holy Bible, New International Version. Luke 14:13–14. BibleHub. https://www.biblehub.com/luke/14-13.htm
  10. The Holy Bible, New International Version. Matthew 25:40. BibleHub. https://www.biblehub.com/matthew/25-40.htm
  11. The Quran. Surah Abasa (80:1–10). Quran.com. https://quran.com/80
  12. Hadith. Sunan Abu Dawud 2594: “Cursed is the one who misleads a blind person away from his path.” Sunnah.com. https://sunnah.com/abudawud:2594
  13. Hadith. Narrated by Abu Darda: Prophet Muhammad on seeking victory through the weak and oppressed. Sunan Abu Dawud 2594. Sunnah.com. https://sunnah.com/abudawud:2594
  14. Feingold, Lainey. “Title II Web and Mobile Technical Accessibility Standards: History + Current Status.” Law Office of Lainey Feingold, originally published 2022, updated 2026. https://www.lflegal.com/2022/08/doj-web-regs-announce/

Beyond the Screen Reader: Can Gemini’s AI Agent “Accessify” the Web?

by

AI as an Accessibility Bridge: Testing Gemini’s Auto Browse

For blind and low-vision users, the modern web is a minefield of good intentions gone wrong. Developers build visually polished interfaces — date pickers, multi-step dialogs, dynamic dropdowns — but the underlying code often fails to communicate with assistive technology. Screen readers like JAWS and NVDA rely on semantic structure and proper focus management to guide users through a page. When that structure breaks down, so does access.

That gap is exactly what I set out to probe in a recent demonstration of Auto Browse, an agentic AI feature built into the Gemini for Chrome side panel. My test case was deliberately unglamorous: a Salesforce “Add Work” form on the Trailblazer platform, featuring a date picker that routinely defeats standard keyboard navigation. The question wasn’t whether the interface looked functional. It was whether an AI agent could step in and make it work.

The Problem with Date Pickers (and Why It Matters)

Custom date pickers represent one of the most persistent accessibility failures on the web. Unlike native HTML <input type="date"> elements, which browsers render with built-in keyboard support, custom-built widgets frequently rely on mouse interaction, non-semantic markup, or JavaScript behavior that strips focus away from the user mid-task.

In my demo, the Salesforce dialog presents a “start date” selector with separate Month and Year dropdowns. For a sighted mouse user, this is trivial. For a screen reader user navigating by keyboard, it becomes a trap — the list receives focus but refuses to respond to arrow keys or selection commands, leaving the user stuck with no clear path forward.

This is not a niche problem. Date pickers appear in job applications, medical intake forms, financial dashboards, and e-commerce checkouts. When they break, they don’t just create friction — they create exclusion.

Letting the AI Take the Wheel

My approach was straightforward: rather than fighting the inaccessible interface, I delegated the task entirely. With the Gemini side panel open (activated via Alt+G), I issued a plain-language command: “Please set the start date to December 2004.”

What followed was notable not just for what the AI did, but for how it communicated while doing it. Auto Browse autonomously interacted with the form elements — opening the Year dropdown, scrolling to 2004, selecting it — while simultaneously providing real-time status updates in the side panel. Critically, those updates (“Updating the start year to 2004”) were announced by the screen reader, keeping me informed throughout the process without requiring me to shift focus manually.

A “Take Over Task” button remained visible at the top of the browser at all times, ensuring that AI autonomy didn’t come at the cost of user control — a design principle that will resonate with anyone familiar with WCAG’s emphasis on predictability and user agency.

Where It Still Falls Short

I want to be candid about the rough edges, because that honesty is part of what makes this worth examining closely.

During the interaction, the dialog closed unexpectedly at one point, requiring a page reload before I could restart the task. For sighted users, this is a minor inconvenience. For screen reader users, an unexpected context shift — a dialog closing, focus jumping to an unrelated part of the DOM, a dynamic content update that goes unannounced — can be deeply disorienting. Recovery depends on knowing where you are, and that knowledge is precisely what gets lost.

This points to a fundamental challenge for agentic AI in accessibility contexts: it isn’t enough to complete the task correctly; the AI must also maintain a coherent focus environment throughout. If a script refreshes a page region mid-task, the virtual cursor needs to land somewhere intentional. If a dialog closes, the user needs to know what replaced it. These aren’t edge cases — they’re the everyday texture of dynamic web applications, and they’ll need to be handled reliably before tools like Auto Browse can be genuinely depended upon.

A Glimpse of What’s Possible

Despite those caveats, I came away from this demonstration genuinely encouraged. Gemini successfully populated both fields with the correct date, confirmed by the screen reader’s final readout. More importantly, it did so through natural language — no custom scripts, no manual DOM inspection, no workarounds requiring technical knowledge that most users don’t have and shouldn’t need.

The implications extend well beyond date pickers. Agentic AI that can interpret intent and act on a user’s behalf has the potential to make complex web interfaces navigable for people who have been effectively locked out of them. Not by fixing the underlying code — though that remains the gold standard — but by providing a capable, responsive intermediary that can bridge the gap in real time.

The web has always required remediation to be accessible. What’s new is who, or what, might be doing the remediating.

Visual Descriptions (Alt-Text for Video Keyframes)

To ensure this post is as accessible as the technology it discusses, here are descriptions of the critical visual moments in the video:

Frame 1: The Accessibility Barrier
A screenshot of the Salesforce “Add Work” dialog box. The “Month” and “Year” drop-down menus are highlighted, showing the visual interface that I am unable to navigate using standard screen reader commands.
Frame 2: The Gemini Interface
The Chrome browser split-screen view. On the left is the Trailblazer site; on the right is the Gemini side panel where I have typed my request. The AI is showing a progress spinner labeled “Task started.”
Frame 3: Agentic Interaction
The video shows the “Year” drop-down menu on the webpage opening and scrolling automatically as the Gemini agent selects “2004” without any manual mouse movement or keyboard input from the user.
Frame 4: Success Confirmation
The final state of the form showing “December” and “2004” successfully populated in the fields. The Gemini side panel displays a “Task done” message with a summary of the actions performed.

I am a CPWA-certified digital accessibility specialist. When I’m not testing the latest in AI or keeping up with my family, you can find me on the amateur radio bands under the call sign NU7I.

Using Apple’s Built-In Accessibility Features to Reduce Screen Exposure During Severe Headaches

by

Summary

Some people experience severe headaches or migraines that make screen use difficult—especially when light sensitivity (photophobia) and flicker or refresh effects are major triggers. While display adjustments can help, there are days when the most effective strategy is to reduce visual reliance as much as possible.

If you use an iPhone and Mac, Apple includes several built-in accessibility tools that can support a “low-screen” or even “no-screen” workflow—particularly for everyday tasks like reading and replying to email.

This article focuses on the built-in Mail app and outlines a practical approach using:
VoiceOver (screen reader),
Voice Control (hands-free voice operation),
and Dictation (speech-to-text composition).

Why VoiceOver and Voice Control can help when light and flicker are triggers

VoiceOver reads on-screen content aloud and provides a structured navigation model that does not require visually scanning the interface. Instead of looking for buttons or reading text, users move through content sequentially and receive spoken feedback.

Voice Control complements this by allowing users to operate their device through spoken commands. Actions such as opening Mail, scrolling, replying, and sending messages can often be completed without touching or looking closely at the screen.

For people whose primary headache triggers include light sensitivity and flicker, combining these tools can significantly reduce both the duration and intensity of screen exposure.

iPhone: Building a low-screen Mail workflow on iOS

Turn on VoiceOver

VoiceOver can be enabled from Settings > Accessibility > VoiceOver. Apple provides a built-in practice experience that introduces the gesture model and basic navigation concepts.

Learn a minimal set of VoiceOver gestures

It is not necessary to learn every gesture. Starting with a small core set allows users to begin working quickly and add complexity later.

  • Swipe right: move to the next item.
  • Swipe left: move to the previous item.
  • Double-tap: activate the selected item.
  • Two-finger swipe up: read the entire screen from the top.
  • Two-finger tap: pause or resume speech.
  • Four-finger tap near the top: jump to the first item.
  • Four-finger tap near the bottom: jump to the last item.

Use Screen Curtain to eliminate display light

When VoiceOver is enabled, the screen itself can be turned off while the device remains fully usable. This feature, called Screen Curtain, allows users to rely entirely on audio output while avoiding light exposure.

  • Three-finger triple-tap: toggle Screen Curtain on or off.
  • If both Zoom and VoiceOver are enabled, a three-finger quadruple-tap may be required.

Adding Voice Control for hands-free interaction

Voice Control allows users to interact with on-screen elements using spoken commands. This can be particularly helpful when precise touch input or visual targeting is uncomfortable.

Common Voice Control commands

  • Open Mail
  • Scroll down / Scroll up
  • Go home
  • Show names (labels interface elements)
  • Show numbers (adds numbered overlays)

When an on-screen control is difficult to activate, VoiceOver can be used to identify the control’s name, and Voice Control can then activate it using that spoken label.

Reading and replying to Mail on iPhone using audio

  1. Open the Mail app using Voice Control or VoiceOver navigation.
  2. Move through the message list using swipe left and swipe right.
  3. Open a message with a double-tap.
  4. Listen to the message using a two-finger swipe up.
  5. Reply using Voice Control or VoiceOver navigation.
  6. Compose the reply using Dictation, speaking punctuation as needed.
  7. Send the message using a spoken command or VoiceOver activation.
  8. Enable Screen Curtain when light sensitivity is a concern.

Mac: Reducing visual load with VoiceOver

On macOS, VoiceOver enables spoken feedback and keyboard-based navigation across apps, including Mail. This allows users to work with less reliance on visual scanning.

Turn VoiceOver on or off

  • Command + F5: toggle VoiceOver.

Core VoiceOver navigation concepts

The VoiceOver cursor moves independently of the system focus and determines what is spoken. Navigation is performed using the VoiceOver modifier keys (often Control + Option).

  • VO + Arrow keys: move between items.

Quick Nav for streamlined navigation

Quick Nav can simplify navigation by allowing arrow keys or single keys to move through content without holding modifier keys. This can be especially useful once the basics feel comfortable.

  • VO + Q: toggle single-key Quick Nav.
  • VO + Shift + Q: toggle arrow-key Quick Nav.

Pacing and learning considerations

When screen exposure can trigger symptoms quickly, it helps to approach learning incrementally.

  • Practice in short sessions (5–10 minutes).
  • Focus first on listening and basic navigation.
  • Add Screen Curtain early if light sensitivity is significant.
  • Introduce Voice Control gradually for common actions.

Sources

Asked to Make Your iOS App Accessible to Blind People? There’s a Plan for that!

by

Are you a developer who has been asked to make your iOS app accessible to blind people using Apple’s built-in VoiceOver screen reader? Are you uncertain how to respond, why you should care or where you can go to get started? I hope to demystify these questions and encourage you to create and improve your product in ways that empower and include all your customers, even those who can’t see the screens of their smart phones and tablets.

How should I respond to a request for VoiceOver accessibility in my app?

However you choose to respond, I would encourage you not to simply ignore the request. As a professional, you expect a timely response to communications you initiate, so please afford your blind customers that same courtesy when approached. Please consider the following ideas for communicating with users regarding accessibility requests:

  1. Respond to the request right away informing the customer you have received it and you will take steps to follow up promptly.
  2. If you have a bug-tracking or case management system, create a ticket and escalate it as needed in order to get an answer.
  3. If you do not possess the authority to make this strategic decision, please work with your company’s owner or executive leadership to urge them in the right direction. If you do have the necessary authority, please read on for information on how you can open your doors to your blind customers.
  4. If your business has decided to be inclusive to blind people, please respond affirmatively to your customer, utilize the resources provided here and elsewhere online and start working actively with the connected, online blind community.
  5. Regardless of the outcome, please remember to follow up with your customer by providing updates as you are able to release information to the public.

Why should I care?

There are at least four reasons why you should incorporate accessibility into your apps:

  • Accessibility is simply the right thing to do. Would you create an app designed to categorically exclude women, African-Americans, Chinese or any other group of people? If not, then why would you want to exclude blind people or anyone else with a disability? The answer to the accessibility question determines whether or not everyone, including people with disabilities, will be afforded the opportunity to learn, work, enjoy leisure activities or otherwise participate in the benefits your app offers.
  • There is a business case for accessibility.
  • Accessibility can be easy, fun and interesting. In 2015, the White House and several other U.S. government agencies sponsored a hackathon demonstrating and discussing techniques for improving the accessibility of several forms of technology.
  • Accessibility is the law of the land in many parts of the world. In the United States, the Americans with Disabilities Act, Individuals with Disabilities Education Act (IDEA), Sections 504 and 508 of the Rehabilitation Act, 21st Century Communications and Video Accessibility Act (CVAA), and numerous other lesser-known laws require accessibility and full inclusion of people with disabilities in activities, education, employment, products, programs and services offered to the public at large. Similar laws are on the books in many other nations. Failure to empower people with disabilities to use your app may result in complaints, lawsuits, loss of business, negative publicity and a poor reputation.

Where can I go to learn more about iOS accessibility and get started with developing my apps in an inclusive manner?

Apple provides an excellent overview of all the accessibility features available on its iOS platform. The Applevis online community hosts Information For Developers On How to Build Accessible iOS and Mac Apps. Finally, a comprehensive, systematic plan has been published to aid developers and others in beta testing and evaluating the accessibility of iOS apps with VoiceOver.