Closed marisademeglio closed 4 months ago
We should create an isolated example of a large table in react vs browser and show how the screen reader behavior differs, and report it to electron.
We can close this with the new TTS voices page in the settings dialog, as of 1.4.0-beta-2
From recent tester feedback
"Screen Reader behaviour is sluggish in the voice selection table in Settings
Anubhav: just got released that there was a confusion in Marisa's mail where i was talking about grid. Currently the list of table is being marked as a normal table where a lot of interactive items are there. I am proposing to change it to a data grid, something like Fluent UI 9 DataGrid example. it will be more screen reader and keyboard only user friendly.
Regarding her question on navigation in dialogue box navigation from table to close button, this is another pain point here. as a keyboard user, one has to tab around the table depending on the number of TTS user has configured. So if i have enabled both Microsoft and google cloud TTS then you can imagine.
another point is table has provided search function but it is also a matter of investigation if screen reader announce how many search results are available or "no search results". something like Announced - Search Results"