Conduct an Accessibility review of the module (Late May 2022) [#3282265]

Problem/Motivation

See https://www.drupal.org/docs/accessibility/how-to-do-an-accessibility-review.
The goal of this issue is to open more issues, not solve them here.

@narendraR is going to lead this effort

Steps to reproduce

Proposed resolution

Remaining tasks

✅ File an issue about this project
☐ Addition/Change/Update/Fix to this project
☐ Testing to ensure no regression
☐ Automated unit/functional testing coverage
☐ Developer Documentation support on feature change/addition
☐ User Guide Documentation support on feature change/addition
☐ Code review from 1 Drupal core team member
☐ Full testing and approval
☐ Credit contributors
☐ Review with the product owner
☐ Release

User interface changes

API changes

Data model changes

Release notes snippet

Comments

Comment #1

25 May 2022 at 14:14

tim.plunkett created an issue. See original summary.

Comment #2

narendrar

He/Him

English

Jaipur, India

commented 27 May 2022 at 10:11

Status:

Active

» Needs review

Found below mentioned issues:

Skipped heading level (h6 on XXX Results).
Clicking Pagination should move focus to first card in list.
User is not informed when he moves to project data/tile with number of items on page etc.
XXX Results count should be announced whenever number changes due to search.
Installed button should have sufficient color contrast.
Redundant image alt text for VBO/Pathauto etc.
Focus needs to be updated when pop-up is opened/closed.
Font size should not be fixed on applied filters like Actively maintained, Covered etc
Moving to categories checkbox by tab does not let user what this is for. May be Fieldset and legend can be used instead.
Voiceover does not read out the applied filters (just read the close button)
Advance filters are not accessible through keyboard.
Sort options are not accessible through keyboard.
Missing role="navigation" from pagination

I will create individual tickets for all the issues mentioned/discovered/discussed on this ticket after review is completed.

Comment #3

narendrar

He/Him

English

Jaipur, India

commented 27 May 2022 at 10:12

Assigned:

narendrar

» Unassigned

Comment #4

bnjmnm

he/him

English

Ann Arbor, MI

commented 27 May 2022 at 13:36

Title:

Conduct an Accessibility review of the module

» Conduct an Accessibility review of the module (Late May 2022)

I've noticed accessibility review issues have a tendency to remain open for a very long time because it's difficult to know when a review is "done". @narendraR did a good job surfacing some important concerns here. I think this issue can be closed once the individual issues are filed. We can always do another round of review, and probably should anyway as things will continue to change.