- π¨π¦Canada mgifford Ottawa, Ontario
After performing bulk actions on the content search page, the result of the action is displayed at the top of the page. In Chrome, if the result is an error the screen reader reads the error message; however, if the result is successful the screen reader does not read the success message. In IE, neither result is read by the screen reader. The expected result is that the screen reader is able to read the message, success or failure, across browsers. The issue appears to be similar to work being done for π Provide screen reader feedback when Views List is filtered by name or description Needs work and π Provide screen-reader feedback when Views UI filterable options are updated Needs work , but I couldn't tell if this work would be covered under those tickets.
After performing bulk actions on the content search page, the result of the action is displayed at the top of the page. In Chrome, if the result is an error the screen reader reads the error message; however, if the result is successful the screen reader does not read the success message. In IE, neither result is read by the screen reader. The expected result is that the screen reader is able to read the message, success or failure, across browsers. The issue appears to be similar to work being done for https://www.drupal.org/node/2805499 β and https://www.drupal.org/node/2805197 β , but I couldn't tell if this work would be covered under those tickets.
Active
11.0 π₯
Last updated
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.