- 🇨🇦Canada mgifford Ottawa, Ontario
I don't think this falls as a WCAG failure, but definitely a useful addition.
Creating a view can be a trial-and-error endeavor. Make a change, check the preview, and then keep the change or revert it depending. For a blind user, the effects of a change to a view's definition are not immediately apparent.
We can use the Drupal.announce method on the front end to give the screen reader user a summation of the changes to the preview area. Or even just its current state after a change. Is it a list? Well, how many items are in the list? Is it a table? How many rows are in the table? With views, the change to a view often results in either some data or no data. Just knowing that you added one filter too many or of the wrong type and wiped out your results is super helpful.
Propose an initial patch.
Screen reader users will have some indication of what their changes to a view's definition did to the result set in the preview.
None.
#1806308: Review Views JavaScript + generic modals for accessibility →
Needs work
11.0 🔥
Last updated
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Related to the Views in Drupal Core initiative.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I don't think this falls as a WCAG failure, but definitely a useful addition.