After enabling or disabling a view, convey changes to screen reader users.

Created on 15 May 2018, over 6 years ago
Updated 30 May 2023, over 1 year ago

Follow up to #1848940: When enabling or disabling a View, don't move the cursor to the top of the page β†’ . Further accessibility improvements.

When a screen-reader user enables or disables a view, the screen content changes - a table row jumps from the enabled list, to the disabled list. I think it'll be important to inform a screen reader:

1. The outcome of the enable/disable operation was successful
2. The page content has changed - the row has now moved to the other table.
3. The user's keyboard focus is now IN the other table.

Drupal.announce() can provide this. Let's see if we can add custom callbacks for the enable/disable AJAX operations.

πŸ› Bug report
Status

Active

Version

11.0 πŸ”₯

Component
Views UIΒ  β†’

Last updated 2 days ago

Created by

πŸ‡¬πŸ‡§United Kingdom andrewmacpherson

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024