Accessibility issues in gitlab.com
I am a screen reader user of gitlab.com and I have found some issues regarding accessibility. I told GitLab about them on Twitter and I was told to open an issue here.
So, here are them (a bit more detailed):
- When posting a comment in an issue (and I assume merge requests, too), the editing of comments is done by pressing the arrow keys in a blank edit field. There is no warning of that, and I at least didn't figure out I was editing a comment rather than posting a new one until Iposted it. Perhaps this could be done with an edit button next to the comment, to avoid confussion.
- The editor used for files and snippets is inaccessible. See issue 2164 for details. This could be fixed by making it optional, with a checkbox next to the edit box.
- Some links have no text and expose their function with the title attribute. In Windows, this means that only the tab key can be used to navigate between those links (the arrow key navigation and link list function of most screen readers rely on link text), and on iOS there is a delay of like one second between the announcement of the link and its function. This would be solved by using the link's text. Even stranger, it appears the title of the links is updated between each link, as pressing tab rapidly on a Windows machine leads the screen reader to not announce some titles. Also, some links do not have any text or title.
- Lastly,
aria-expanded
is used incorrectly in some context (as in the all / personal / contributed projects list), and in others, the default collapsed role is not announced until the control hasbeen expanded and collapsed.
Thanks!