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

[P2][Sourcing] JAWS 2024 screenreader not reading the header for the popover opened for fd-popover component. #12716

Open
OneEyedOwl123 opened this issue Nov 11, 2024 · 0 comments · May be fixed by #12907
Assignees
Labels
accessibility use this label for any issue or enhancement related to screenreader/keyboard/etc support

Comments

@OneEyedOwl123
Copy link

OneEyedOwl123 commented Nov 11, 2024

Is this a bug, enhancement, or feature request?

Bug

Describe your proposal.

JAWS 2024 screenreader not reading the header for the popover opened for fd-popover-body component.
Using fd-popover component, for fd-popover-body-header , it should read the header when the popover opens giving information about the popover header.

Can you handle that on the application side

No

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.)

Angular 15, version: 0.43.47

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

  1. Turn on JAWS 2024 screen reader.
  2. Navigate to popover control for a fd-popove component using keyboard tabbing.
  3. Hit enter/space to open the popover.
  4. No information about the popover header is being read to convey to the user what popover has been opened. It should read the popover header defined using fd-popover-body-header.
Screenshot 2024-11-11 at 3 21 02 PM

Please provide relevant source code (if applicable).

Please provide stackblitz example(s).

https://stackblitz.com/edit/angular-a6mrnw?file=src%2Fapp%2Fpopover-complex-example.component.html

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

Yes, the screen reader should read the header of the popover being opened to give users the context of what was opened. It should read the header defined using fd-popover-body-header directive or some other way to make the screen reader announce the popover header.

Did you check the documentation and the API?

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.

@OneEyedOwl123 OneEyedOwl123 changed the title [P2][Sourcing] [P2][Sourcing] JAWS 2024 screenreader not reading the header for the popover opened for fd-popover-body component. Nov 11, 2024
@OneEyedOwl123 OneEyedOwl123 changed the title [P2][Sourcing] JAWS 2024 screenreader not reading the header for the popover opened for fd-popover-body component. [P2][Sourcing] JAWS 2024 screenreader not reading the header for the popover opened for fd-popover component. Nov 11, 2024
@droshev droshev added the accessibility use this label for any issue or enhancement related to screenreader/keyboard/etc support label Nov 15, 2024
@droshev droshev added this to the Sprint 140 - November 2024 milestone Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility use this label for any issue or enhancement related to screenreader/keyboard/etc support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants