Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 make key indicator collection more accessible #3527

Merged
merged 1 commit into from
May 30, 2024

Conversation

sophiamersmann
Copy link
Member

@sophiamersmann sophiamersmann commented Apr 23, 2024

I dropped the ball on the accordion's accessibility, so here I am making amends 😇

This PR makes the key-indicator-collection component more accessible to keyboard and screen reader users.

In particular,

  • Hidden content (i.e. closed accordion items) is removed from the tab sequence and the accessibility tree (uses the inert attribute to do so)
  • Fixes a bug where "clicking" on an accordion item by tabbing to it and then pressing Enter made the focus jump back to the first focusable element on the screen (the OWID logo in the header)

Copy link
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sophiamersmann and the rest of your teammates on Graphite Graphite

@sophiamersmann sophiamersmann marked this pull request as ready for review April 23, 2024 15:13
@sophiamersmann sophiamersmann requested a review from ikesau April 23, 2024 15:14
Copy link
Member

@ikesau ikesau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank youuuu!!

the fixes work - one last thing that would be nice is to change the key-indicator-header__title spans to be h3s so they show up in the heading rotor?

@sophiamersmann
Copy link
Member Author

The accordion headers show up in the headings rotor for me (the whole button is wrapped in an h3). Don't they for you?

Copy link

This PR has had no activity within the last two weeks. It is considered stale and will be closed in 3 days if no further activity is detected.

@github-actions github-actions bot added the stale label May 15, 2024
@sophiamersmann
Copy link
Member Author

hey @ikesau, is this good to merge or should we make some more changes to the markup?

@github-actions github-actions bot removed the stale label May 16, 2024
Copy link

This PR has had no activity within the last two weeks. It is considered stale and will be closed in 3 days if no further activity is detected.

@github-actions github-actions bot added the stale label May 30, 2024
@sophiamersmann
Copy link
Member Author

Ups, this one slipped through the cracks. I'll just merge this now and if there is something else to be done, we can do so in a separate pr :)

@sophiamersmann sophiamersmann force-pushed the a11y-key-indicator-collection branch from 12c56e8 to 9be1f64 Compare May 30, 2024 07:28
@owidbot
Copy link
Contributor

owidbot commented May 30, 2024

Quick links (staging server):

Site Admin Wizard

Login: ssh owid@staging-site-a11y-key-indicator-collection

SVG tester:

Number of differences (default views): 0 ✅
Number of differences (all views): 0 ✅

Edited: 2024-05-30 07:47:01 UTC
Execution time: 1.81 seconds

@sophiamersmann sophiamersmann merged commit af0cfc1 into master May 30, 2024
20 of 22 checks passed
@sophiamersmann sophiamersmann deleted the a11y-key-indicator-collection branch May 30, 2024 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants