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

Route accessibility announcer #14673

Closed
3 of 4 tasks
Tracked by #23255
sanjaiyan-dev opened this issue Aug 22, 2022 · 3 comments · Fixed by #25741
Closed
3 of 4 tasks
Tracked by #23255

Route accessibility announcer #14673

sanjaiyan-dev opened this issue Aug 22, 2022 · 3 comments · Fixed by #25741

Comments

@sanjaiyan-dev
Copy link
Contributor

Describe the feature

Adding Route Announcer to Nuxt js for better accessibility.
Inspired by https://nextjs.org/docs/accessibility#route-announcements.

Additional information

  • Would you be willing to help implement this feature?
  • Could this feature be implemented as a module?

Final checks

@sanjaiyan-dev
Copy link
Contributor Author

Related PR-: nuxt/framework#6847

@danielroe
Copy link
Member

Off the bat, I love this idea. I think we should be providing tools to make it as easy as possible for developers to add essential accessibility features to their apps. Note that there are some judgement calls on how this is best implemented.

Related:

@pi0 pi0 changed the title Route Announcer for Nuxt js 📢 Route accessability announcer Aug 23, 2022
@pi0 pi0 changed the title Route accessability announcer Route accessibility announcer Aug 23, 2022
@danielroe danielroe added the 3.x label Jan 19, 2023
@danielroe danielroe transferred this issue from nuxt/framework Jan 19, 2023
@danielroe danielroe added the a11y label Sep 17, 2023
@ivan-kalachikov
Copy link
Contributor

ivan-kalachikov commented Feb 2, 2024

Is anybody working on it?
If no could I be assigned on the issue? @danielroe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants