Problem/Motivation

We have several filterable admin listings in Drupal core, e.g. the modules page.
The behaviour of these is inconsistent in various ways:

  • The way they are labelled
  • Some have feedback for screen reader users, others don't.

Filterable lists in core:

  • Modules install
  • Modules uninstall
  • Simpletest - Drupal.behaviors.simpletestTableFilterByText
  • Blocks - Drupal.behaviors.blockFilterByText
  • Views main listing - Drupal.behaviors.viewTableFilterByText
  • Views handlers ("add field" dialog, etc)
  • Layout builder blocks - in progress, see #2998862: The Layout Builder block listing should be filterable
  • .

Proposed resolution

Add announcements to filters which don't have them yet.

Consistent language in filter field - label, description. #2942037: Admin list filter fields are inconsistently labelled.
Consistent language in Drupal.announce() messages.
Correct pluralization of result count in Drupal.announce().
Drupal.announce() should also announce that all items are shown, after a user clears the filter field (i.e. no items are hidden).
Search by machine name and human-readable name where appropriate.
Display machine name in any lists that allow filtering on it.

Creating a reusable component for this? To remove the individual implementations we have so far. NEEDS CHILD ISSUE.

  • Views main listing has one filter which controls 2 lists.
  • Views handlers have 2 inputs that both control the same list (a text field and a select).

Add behaviour to visually highlight the matched strings in the result list?

Add a developer handbook page about all this, with all the advice they need to follow.

Remaining tasks

See related/child issues.
Anything else?

User interface changes

Improvements to filterable lists, for consistency and accessibility.

API changes

TBD - possibility of introducing a re-usable filter component.

Data model changes

TBD - none?

Comments

andrewmacpherson created an issue. See original summary.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

mgifford’s picture

Issue summary: View changes
Issue tags: -JavaScript +JavaScript
mgifford’s picture

Issue tags: +vpat

Linking open issues from the CivicActions Accessibility - VPAT.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

mgifford’s picture

Issue tags: +wcag323

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

nod_’s picture

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.