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

[BUG] Anchor tags in the cookbook are without proper accessible naming #3719

Open
1 of 9 tasks
Fuzzy3 opened this issue Nov 21, 2024 · 0 comments
Open
1 of 9 tasks

[BUG] Anchor tags in the cookbook are without proper accessible naming #3719

Fuzzy3 opened this issue Nov 21, 2024 · 0 comments
Labels
bug NOT Verified Applied to bug reports that have not been verified by a member of @kirbydesign/kirby-guild

Comments

@Fuzzy3
Copy link
Collaborator

Fuzzy3 commented Nov 21, 2024

Describe the bug

Currently most links (anchor tags) in the cookbook are not self-explaining - which is not a problem since they occur in a context that give them meaning. However when using a screen reader the user often traverses from link to link or even gets a complete overview of all the links shown without their surrounding context. This provides a poor experience for people using a screen reader.
This may easily be fixed by adding an aria-label to the anchor tags in the cookbook following the accessible naming convention.

Describe how to reproduce the bug

  1. Go to any page in the cookbook - could be the accessibility page: cookbook.kirby.design/#/home/accessibility-in-kirby
  2. Turn on voiceover and make it show the links overview
    Result: The links are shown but most without proper context to understand where they will take the user.

What was the expected behavior?

Each link should have an accessible name as described in the link - such that the intent of the link is clearly stated for people with disabilities.


Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Verification

To make sure the bug is not intended behaviour; it should be verified by a member of team Kirby before moving on to implementation.

  • Make sure the NOT verified label has been removed by a member of team Kirby; do not proceed until this is done.

Implementation

The contributor who wants to implement this issue should:

Review

Once the issue has been implemented and is ready for review:

@Fuzzy3 Fuzzy3 added bug NOT Prioritized Issue not yet prioritized and added to a Milestone 👶🏻 New For new issues before prioritisation and refinement NOT Verified Applied to bug reports that have not been verified by a member of @kirbydesign/kirby-guild labels Nov 21, 2024
@github-project-automation github-project-automation bot moved this to 📙 Backlog in Kirby Nov 21, 2024
@RasmusKjeldgaard RasmusKjeldgaard moved this from ⭐ Planned Work to 💌 Inbox in Kirby Nov 27, 2024
@RasmusKjeldgaard RasmusKjeldgaard moved this from 💌 Inbox to ⭐ Planned Work in Kirby Nov 27, 2024
@alxzak alxzak removed NOT Prioritized Issue not yet prioritized and added to a Milestone 👶🏻 New For new issues before prioritisation and refinement labels Nov 28, 2024
@alxzak alxzak moved this from ⭐ Planned Work to 💌 Inbox in Kirby Dec 2, 2024
@alxzak alxzak moved this from 💌 Inbox to 📙 Backlog in Kirby Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug NOT Verified Applied to bug reports that have not been verified by a member of @kirbydesign/kirby-guild
Projects
Status: 📙 Backlog
Development

No branches or pull requests

2 participants