Problem/Motivation
Currently, the Views UI employes no specialized ARIA roles to describe the structure of the interface. Moreso than any other UI in Drupal, Views is complex and deserves a bit more attention in terms of how we describe the interface to non-visual and keyboard-only users.
We should look specifically at Widget Roles.
Complex application UIs like GMail make extensive use of these roles and such UIs should be used to mine for examples.
Proposed resolution
This is going to involve some develop-and-test iteration cycles. I don't know if anyone really knows how to do this well, but we can certainly give it our best effort.
Remaining tasks
Propose an initial patch.
User interface changes
Non-visual interactions using a screen reader will be richer and more usable.
API changes
None.
Related Issues
#1806308: Review Views JavaScript + generic modals for accessibility
Comments
Comment #1
mgiffordEspecially with a complex interface like Views UI, this would be beneficial for non-sighted users.
Comment #2
mgiffordIt is good to remember that if we are using the proper HTML5 values then we don't need to also assign an ARIA role to it. Mostly tagging but also including this list of Widget roles to consider.
5.3.2. Widget Roles
The following roles act as standalone user interface widgets or as part of larger, composite widgets.
The following roles act as composite user interface widgets. These roles typically act as containers that manage other, contained widgets.
Comment #3
mgiffordComment #4
mgiffordComment #5
mgiffordComment #21
mgiffordThis sounds like https://www.w3.org/WAI/WCAG21/Understanding/name-role-value
Providing richer semantic content to the Views UI.