Add hidden span labels for help links.

[somiaj]

This adds a hidden span that gives a label for the help links for the main help link using the helpMacro and the help links on the course configuration page. There is now an aria-labelledby setting for this description which describes what the help link is for.

The page title is used for the description for the main help link. For the course configuration links, the setting short description is used for the title. A few of the short descriptions ended in a period, those were all removed to make the description "desc help." consistent and not have a period before the help statement.

I couldn't figure out a better label for the course configuration help statements than the short description. This seems a little long in some cases, but overall identifies what setting the help buttons is for.

[drgrice1]

When we talked about this in the meeting I think that you got mislead on a few things.

You mentioned that the visually hidden spans for the help icons on the course configuration page merely say "help", and that they should be more specific. However, that isn't true. Those should just say "help". The thing is that when designing a page for a screen reader, it is important to control the verbosity and prevent text from being read multiple times. If these buttons say, for instance, "Title for course displayed on the Assignments page help" and the text for the table also says "Title for course displayed on the Assignments page", then the screen reader reads both of those together making it rather verbose. In the context since the text in the table will be read with together with the text for the icon, "help" is sufficient.

The same is true for the help links for the page by the page title. Of course, those should not have the question mark for the content of the visually hidden span since that is not read by screen readers, but should have "help" for the content instead.

Also, the actual icons should are for sighted users only, and don't add anything for those using a screen reader. So they should not have the aria-labelledby attribute, and instead should have the aria-hidden attribute. This is so that the visually hidden span becomes what is read for link and the icon is completely ignored. So the point is that the visually hidden spans as they were are structurally and semantically correct.

I actually also did some work on this after we discussed this in the meeting, and created a branch to fix the "?" help links, and removed the addition of the visually hidden spans by javascript. I will go ahead and put that in as a pull request for comparison.

[somiaj]

Ahh, I was considering the links in isolation too much, and thought having a lot of "Help link" would not be clear what the help was for, so added more to make that clear without considering where the link was being placed. Thanks.

Closing in favor of #2631.

[drgrice1]

Actually, I am going to reopen this. I would like @Alex-Jordan's opinion on this (or anyone else who has experience in this area). I am certain that the aria-labelledby is not correct, but the more verbose text I am not certain of. I tested with both Gnome Orca and Android Talkback. With Gnome Orca the headers are read with the link, and it does seem rather redundant in that case. However, with Android Talkback the link is read separately, although it is still the next thing that is read after the header.

[drgrice1]

It seems that it is difficult to get screen reader support right. Largely due to the fact that different screen readers seem to do rather different things. It seems that screen reader support is not entirely standardized.

[somiaj]

I removed the aria-labelledby tags and ids. If we do end up needing to with the more verbose text, I'll also update this to remove more of the alt text being added by javascript like #2631.

I am unsure what is best here, I do know with normal links the standard seems to be descriptive (don't use things like 'click me') and that links that do different things should have different text (which is partly why I thought all the links saying "help" might not be best). Anyways waiting to see if others know the best accessible standards here.