Tracking : accessibility (a11y)

[Miaourt]

Hi, pretty new here, but as a discussion where ongoing on the project Discord, doing a tracking issue for this seemed like a good idea (Disclaimer : I'm not an accessibility expert at all, let alone a Tauri one, so suggestions are highly encouraged)

Accessibility is something very important, it allows people with vision problems and movement difficulties to use our application.

Electron cover this issue by using Chromium, that since it's a fully featured web browser, already have accessibility feature built-in.

Tauri, on the other side, use many system independent webviews, we must make sure to exploit all their built-in accessibility features, and if possible.

While Tauri can't force everyone into doing accessible application, we must make sure that many point are covered by it :

• Make sure screen readers have access to the website content. Aka being able to read it like a website.
• Make sure others inputs aren't overridden by Tauri, like arrows, tabs, shift + tabs, so navigation on websites can be possible.

[ghost]

Is support for the underlying OS' voice over implicit or out of scope?

[cary-rowen]

Hi, How accessible is tauri currently? I found that the icon in the Windows notification area toolbar is missing a label when using an app built with tauri. Should this be reported to tauri or the app developer? Thanks

[Isaac-Leonard]

I'm a blind developer and so far have found that tauri is basically as accessible as the underlying web view and native controls like the file dialogs. I'd particularly be interested in having programmatic access to accessibility features such as toggling the screen reader off and back on in apps, theres stuff where I want to provide custom accessibility tools in my app that conflict with the system accessibility or where the system accessibility gets in the way, for example enabling direct touch when a users screen reader is enabled on mobile devices so I can capture my own gestures without having to have the user manually turn off their screen reader when using my app.