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

Spike - Investigate options for updating a11y props being required or not #9816

Open
thatblindgeye opened this issue Nov 9, 2023 · 0 comments

Comments

@thatblindgeye
Copy link
Contributor

Describe the enhancement or change
Spike for a discussion to have regarding #5397

Basically we need to decide whether:

  • we want to update certain a11y props to either be required (if currently optional) or make them optional (if currently required)
  • we want to add console warnings when an optional a11y prop is not passed in, but ideally should be (e.g. if an element doesn't have a visible text label, typically we should want an aria-label added somewhere)
  • leave things as-is - props will remain optional or required as they already are
  • some combination of all of the above

Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?

Any other information?

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

No branches or pull requests

4 participants