-
Notifications
You must be signed in to change notification settings - Fork 34.8k
Closed
Labels
accessibilityKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuesKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersmacosIssues with VS Code on MAC/OS XIssues with VS Code on MAC/OS Xon-testplan
Milestone
Description
As part of https://bugs.chromium.org/p/chromium/issues/detail?id=1143047 chromium added a runtime feature called AutoDisableAccessibility and it works like this:
Adds logic that disables accessibility under these circumstances:
* There are 3+ user input events in web content (mouse down, key down,
or touch start count)
* Over a period of more than 30 seconds
* And no usage of accessibility APIs in that time.
The goal of this logic is to avoid disabling accessibility
simply due to inactivity, i.e. the browser is idle - but instead
to try to disable accessibility when there's evidence that the
user is actively using their browser but no longer using assistive
technology or anything else using accessibiltiy APIs.
We should try out this flag to see how it affects our accessibility detection on macOS.
Metadata
Metadata
Assignees
Labels
accessibilityKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuesKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersmacosIssues with VS Code on MAC/OS XIssues with VS Code on MAC/OS Xon-testplan
Type
Projects
Status
🏃 In Progress