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

Segmented-button Accessibility when switching between disabled/enabled #12675

Open
aflalves opened this issue Oct 30, 2024 · 0 comments · May be fixed by #12808
Open

Segmented-button Accessibility when switching between disabled/enabled #12675

aflalves opened this issue Oct 30, 2024 · 0 comments · May be fixed by #12808
Assignees
Labels
bug Something isn't working

Comments

@aflalves
Copy link
Contributor

aflalves commented Oct 30, 2024

Is this a bug, enhancement, or feature request?

bug

Describe your proposal.

When the segmented-button becomes disabled, it is not possible to focus on it anymore - this is expected
But when the button becomes enabled, it is still not possible to focus on it.

We are using reactive forms, but the same happened with template driven

Can you handle that on the application side

We couldn't find a way to hack it. Is there a component method or service we could call to refresh things up?

Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)

ng 17 + fd 48
ng 18 + fd 53

If this is a bug, please provide steps for reproducing it; the exact components you are using;

There are 2 ways to reproduce:

  1. Component is initialized as disabled and becomes enabled - focus not possible
  2. Component is initialized as enabled, becomes disabled and enabled again -> focus not possible

Please provide relevant source code (if applicable).

Please provide stackblitz example(s).

the stackblitz crashes when I try to open it. It is simple to reproduce by just taking the last example in the docs with reactive forms and do:

setTimeout(() => {
  this. customForm.controls['basic'].disable()
  this. customForm.controls['basic'].enable()
}, 2000)

In case this is Accessibility related topic, did you consult with an accessibility expert? If not, please do so and share their recommendations.

Did you check the documentation and the API?

yes

Did you search for similar issues?

yes

Is there anything else we should know?

IMPORTANT: Please refrain from providing links or screenshots of SAP's internal information, as this project is open-source, and its contents are accessible to anyone.

@droshev droshev self-assigned this Dec 3, 2024
@droshev droshev added the bug Something isn't working label Dec 3, 2024
@droshev droshev added this to the Sprint 141 - December 2024 milestone Dec 3, 2024
@droshev droshev linked a pull request Dec 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants