I am open for suggestions we do not find a good role I would have to introduce a vs code command that passes focus to the status bar. So idealy we would need a role like the status but that is not chatty as status. However looking at the aria spec only one part should have the contentinfo which out titlebar already has, thus going with complimentary.
So for now I could return to using the contentinfo role for the status bar. Whenever I change a cursor possition, the screen reader would say the content of the status bar which is a bad experience.
Though let's see how it you are right, the status role is definetly too spamy when I try it out with VoiceOver and NVDA. So my personal preference is that we try to make this status role work and on top of that you can use different commands in the command palette. I believe this was originaly added by to not make screen readers too chatty.Īlso note that all actions in the status bar are accessible via the command palette. Sure, having a focus status bar command would be nice, but when I have test selected and just want to hear the selection length or otherwise want to know my line / column position I definitely would like to type a command and hear that information without leaving the text good catch, there was an issue with line and columns missing when screen reader is attached. I personally think that vscode should follow the standard behavior, to voice its status bar contents.
#Status bar access plus#
JAWS uses the insert (or other key configured as modifier) plus pagedown key, while NVDA uses the insert (or other key configured as modifier) plus end to achieve this goal. Historically, screen readers have provided commands that allow blind users to check the status bar content also without moving their focus from the current task at hand. For example, one can look at selection information without touching the focus, otherwize the selection will be destroied. Usually, the status bar provides contextuual information that does not require the main focus to move from the task at hand. It can show the line / column the cursor is currently at, it can show the length or other information relative to a selection or it can show status on asynchronous information. Usually, the status bar shows information contextual to a given operation. I am sorry for the delay on this comment, but let me show another point of view. First of all thank you so much for the great work you are doing on vscode accessibility.
0 kommentar(er)
