Additionally, screen readers provide further information for people with limited vision. I'll update as discussion continues.Many people with disabilities use text readers or screen readers both types of software read out the text that is on the page. I have started this discussion on an issue in the Emulator repo. Looking at the new en-US.json, I think this would be possible.Īs a note, there is currently a related problem on Edge regarding using arrows to navigate up and down the DOM. However, I would like to discuss this either with or the Localization team since I am not as familiar with the difficulties of combining multiple variables.I believe this would work with accessibility by using multiple strings to identify the full key combination according to browser, OS, and accesskey (regardless of using default or customized key).
I'm thinking the default accesskey could be 'f' for focus, but if the dev wants to change it they would be able to do so.
An example string that the screenreader would announce would be: "There are new messages available.Access keys allow for focusing on specified DOM elements.I will summarize in bullets to be as concise as possible: I am considering using an access key to accommodate this a11y deficiency. Screen reader should read as "New Messages button, hit ENTER to see the new messages". Screen reader should provide the descriptive information ,when focus is on "New Messages" button. Screen reader is reading as "New Messages button" Screen reader is not providing the descriptive information when focus is on "New Messages" button. Navigate to "New Messages" button and verify whether screen reader is providing the descriptive information when focus is on "New Messages" button.Navigate to "Test in Web Chat" element and activate it.Navigate to already created web app bot.Users who depends on screen reader will get confuse if screen reader is not providing the descriptive information when focus is on "New Messages" button. Original: microsoft/BotFramework-Emulator#1978
0 kommentar(er)
