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

Heading semantics in Timeline Navigation available to VoiceOver be separate from control #864

Open
Tanvez opened this issue May 7, 2024 · 0 comments

Comments

@Tanvez
Copy link

Tanvez commented May 7, 2024

Issue Description WCAG Criteria Status Category Example Notes
Heading semantics in Timeline Navigation available to VoiceOver be separate from control Enhancement Identified Screen reader <div class="tl-timemarker tl-timemarker-with-end" tabindex="-1" id="ada-lovelace-marker" aria-label="Ada Lovelace, from December 10, 1815 to November 27, 1852, press space to show">…<div class="tl-timemarker-content-container tl-timemarker-content-container-long tl-timemarker-content-container-small"><div class="tl-timemarker-content">…<div class="tl-timemarker-text"><h2 class="tl-headline tl-headline-fadeout">Ada Lovelace</h2></div></div></div></div> VoiceOver can navigate by headings in the Timeline Navigation but then must navigate "up" to the named div with the click behavior.A structure more like this could be cleaner:<h2 aria-label="Ada Lovelace, from December 10, 1815 to November 27, 1852">  <button tabindex="-1" aria-describedby="tl-timemarker-description">    <div class="tl-timemarker-media-container" aria-hidden="true"><span class="tl-icon-image"></span></div>    Ada Lovelace</button></h2>…<div hidden id="tl-timemarker-description">press space to show</div>
@JoeGermuska JoeGermuska added this to the Accessibility 2024 milestone May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants