Improve the aural interface for tour tips

Those values come from shepherd jsut fyi

Try this

thanks! i've quickly recorded a brief screencast with voiceover and keycastr (see voiceover.mp4). there are two aspects to note:

1. the announced output for a tip is sort of redundant an confusing orderwise. tip two reads:

Edit tour Here you can choose what actions to apply to your tour. 2 of 3, web dialog, with 7 items, Previous, button, Edit tour Here you can choose what actions to apply to your tour. 2 of 3

you cant really distinguish between the title and the body text. maybe adding a brief pause between the two? and the steps "2 of 3" are position wise, without any context, just based on the announced text, hard to comprehend. maybe if everything after previous button would be cut if that is possible. that would tackle the redundancy. but another level of complexity for example in tip 3 of 3 on admin/config/user-interface/tour where you have three headings and after the first two a body text (probably more of an editorial problem and the tour tip should be broken up and improved sticking to the style guide - sticking to the one heading one short body pattern). and one detail that is sort of odd but i always missed to mention is, that the default element in focus on a new tip modal is the previous button. shouldnt that be the next button instead to keep the user in flow?

2. if you navigate with the arrow key the tour tip is not announced, you only get:

You are currently on a button, inside of a content information. To click this button, press Control-Option-Space. To exit this group, press Control-Option-Shift-Up Arrow.

which is sort of odd.

Not gonna lie this feels like it shouldn’t be fixed. We’re removing aria attributes that serves a specific purpose. Now we are trying to add everything into a single attribute which could end up long

Actually am going to push back on this one some. The aria attributes were added for a reason to shepherd. So unless we are saying all of shepherd isn’t compliant not sure what we are doing differently that make it any different.

If we are doing something to break shepherd accessibility we should address that obviously

And from what I can tell these aria attributes are being used correctly and definitely do not want to get into the business of redefining accessibility haha

Okay shepherd js has been updated to latest version. This needs to be re-evaluated