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

Screen reader does not announce the associate text message for the delete confirmation. #210

Open
javierbo1989 opened this issue Nov 30, 2022 · 1 comment

Comments

@javierbo1989
Copy link

User Experience:
Users dependent on screen-reader to navigate the page will face difficulty in navigating the page if the screen reader does not announce the confirmation text information for the delete section, hence user will face difficulty in navigating the page efficiently

Repro-Steps:

  1. Open Azure portal with valid credentials and create a API Management.
  2. Click Developer Portal button to navigate to the portal.
  3. Wait portal to load in design mode.
  4. Navigate to the Left nav and select Pages button.
  5. Navigate to the "Pages" window and select "Add page" button.
  6. Select delete page button.
  7. A confirmation dialogs will appear on the page.
  8. Verify whether, screen reader announces the confirmation text or not.

Actual Result:
Screen reader does not announce the associate text message for the delete confirmation.
When focus reach out to the delete pop-up then, Narrator does not announce the confirmation text like, "Are you want to sure to delete". It is announcing as yes button.

Expected Result:
Screen reader should announce the associate text message for the delete confirmation as, "Are you want sure to delete 'Yes' button or No Button".
Ex: This can we have done from "aria-describedby="
This link might help: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-describedby#example

Screenshots
image

MAS Reference:
MAS 1.3.1 – Info and Relationships

Reference Links:
Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
External Bug Process: If this bug belongs to external team, mark it resolved/done and assign it back to the tester with notes on where to file/route the bug. For more information, please use this External Bug Process (sharepoint.com) “HCL Staff should not log any third-party external bugs. Should be routed to EDAD team”.
Please reach out to C&AI Teams channel for any process related queries.

@msftedad
Copy link

Hi Team
any update on this ticket?

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

No branches or pull requests

2 participants