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

A11y: ToC Block links are not marked as ToC links #6082

Closed
Tishasoumya-02 opened this issue Jun 7, 2024 · 2 comments · Fixed by #6084
Closed

A11y: ToC Block links are not marked as ToC links #6082

Tishasoumya-02 opened this issue Jun 7, 2024 · 2 comments · Fixed by #6084
Assignees
Labels
99 tag: UX Accessibility Accessibility issues

Comments

@Tishasoumya-02
Copy link
Contributor

Problem: Every ToC-Link are not labeled as such. Whenever a screenreader is used, it doesn't tell the user that the link is a ToC-Link. The link seems to be linking to another page, but that is not the case. It's always an anchor link. This might confuse the user.

Proposed Solution: Mark the links as table-of-contents-links with alt-tags or ARIA-labels. A screenreader should read "Title-of-the-link, table-of-content-link" or something similar.

Steps to reproduce:

  • Create Table-of-Contents block in page and populate it.
  • Inspect Table-of-Contents-Links or use a screenreader
  • Link is not shown as ToC-Link, no aria label, no alt tag

Expected result:

  • The link should be marked as Table-of-Contents-Link

WCAG - 2.1:

BIK BITV-Test (Web):

@ichim-david
Copy link
Member

ichim-david commented Jun 7, 2024

I left a review on the pull request #6084 (review)
From my point of view this proposed solution does more harm than good and although we can improve the toc accesibility by ensuring we have good markup this solution will not improve the accessibility but decrease it.

@Wagner3UB Wagner3UB added the 99 tag: UX Accessibility Accessibility issues label Sep 13, 2024
@sabrina-bongiovanni sabrina-bongiovanni self-assigned this Sep 26, 2024
@sabrina-bongiovanni
Copy link
Contributor

If the other PR is going to solve this issue, do we still need to change the markup on this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
99 tag: UX Accessibility Accessibility issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants