Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What are the performance implications of always running in screen reader mode? #117

Closed
nikitavoloboev opened this issue Feb 21, 2020 · 2 comments

Comments

@nikitavoloboev
Copy link

I am wondering this as it seems like this would cause a lot of CPU time to process everything in screen reader mode. Maybe I am wrong?

Is the effect negligible?

@dexterleng
Copy link
Collaborator

dexterleng commented Feb 21, 2020

I assume this is a prompt you received with an Electron/Chromium app like Discord.

Webapps, unlike native mac apps, do not report UI element information (e.g. button location) to the Accessibility API until you specify you are a screen reader to them.

I've yet to do profiling, but yeah, there should be a performance impact:

electron/electron#7206 (comment)

@dexterleng
Copy link
Collaborator

dexterleng commented Feb 21, 2020

I will look into disabling the screen reader mode when it is not used.

One solution I've tried is to enable the AXManualAccessibility attribute right before Hint/Scroll mode, but there is some race condition preventing it from working.

The AXManualAccessibility attribute could also be set to false when the electron app is no longer front-most so it doesn't suck up battery while in the background.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants