Are there any examples on how to handle screen reading accessibility for go js? I saw that version 2.3 included SVG context which could help with reading the text on a diagram as a whole but is it possible to have a more interactive flow? For example, could someone use the arrows on the key board to navigate between selected nodes, and as selection changes, be able to read the specific text of the node?
I also saw that Text graph objects have fields like ariaLabel that are exposed in typescript. Do setting these even do anything?
I need to get an idea of what is possible with screen reader accessibility in regards to reading / editing a diagram. I know it for the most part falls on the developer to implement, but what even is possible on my end? I have keyboard functionality that allows me to navigate the diagram but now need to know how can a screen reader come into play, if at all possible.
You would have to mostly build this functionality yourself.
For example, could someone use the arrows on the key board to navigate between selected nodes, and as selection changes, be able to read the specific text of the node?
Which has the option DrawCommandHandler.arrowKeyBehavior which can be set to"select"
But to read the node to the user would require setting some property for the screen reader on selection change. I believe the right thing to do is to create a hidden div with an aria-live attribute, and update that DIV as the selection changes. We are happy to help with the GoJS side of that, but it is mostly non-GoJS work, and we are not experts at screen reader capabilities.
Ok, thanks for the quick response. I have the DrawCommandHandler integrated and I’m familiar with handling the on selection change event. I’ll look further into aria-live, I was thinking that may be the best route possible.