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

🚀 - [Skeleton] Accessibilty enhancements (aria) for notifying screen-readers #8999

Open
ajitzero opened this issue Sep 12, 2024 · 0 comments
Labels
contributions welcome Architecture is clear and community can help P3 This issue has low priority

Comments

@ajitzero
Copy link
Contributor

Description

Enhancement for: https://taiga-ui.dev/directives/skeleton

Brief:
We should consider using one or more of the following aria attributes to inform assistive technologies regarding the current state of skeleton loaders:

  • aria-busy: Most relevant.
  • aria-hidden: Technically correct, but is likely not applicable. (Mentioning it here for posterity. I'm not an expert.)
  • aria-live: Disrupts the user's focus on status change, either immediately (default) or when the user is idle (polite). This is good, unless there are multiple notifications for a group of skeleton loaders.

Problems:

  • aria-live is important, but difficult to assign to a group of skeleton elements. We may need to introduce a [tui-skeleton-group] directive for the parent, which solves this issue but is also easy for developers to forget to use, even if it exists.
  • Is it possible to apply it only to the parent element and not recursively to the children? I may be misunderstanding how the component works, so this may be a non-issue. aria-atomic may help solve the issue if this is a problem.
@waterplea waterplea added P3 This issue has low priority and removed state: need triage labels Sep 26, 2024
@waterplea waterplea added contributions welcome Architecture is clear and community can help and removed feature labels Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contributions welcome Architecture is clear and community can help P3 This issue has low priority
Development

No branches or pull requests

2 participants