MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Feature]: IsAccessibleBrowser - Detect if Accessibility Support is Enabled

Open
#4,735 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Describe the feature/enhancement you need

I need to be able to detect the presence of assistive technology in order to handle enabling some settings that help the application work with screen readers better.

The scenario/use case where you would use this feature

For users who are using a screen reader, we want to be able to detect that and toggle the appropriate settings.

How important is this request to you?

Impactful. My app's user experience would be significantly compromised without it.

Suggested implementation

In Electron, we were calling IsAccessibilitySupportEnabled which used a Chromium class IsAccessibleBrowser. We were also listening for the accessibility-support-changed event. To detect whether assistive technology was being used. Something similar to that would be ideal.

What does your app do? Is there a pending deadline for this request?

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the referenced Electron app API, the accessibility-support-changed event, and Chromium's IsAccessibleBrowser implementation. Define the equivalent WebView2 detection and change-notification behavior, then verify that assistive-technology use can be detected and the requested settings can respond to it.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron
Domain
accessibility, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.