### STR: 1. Ensure a screen reader is running 1. From any site, open a new `Report Broken Site` tool (i.e. via URL bar > Enhanced Tracking Protection > Report Broken Site) with keyboard 1. Fill in the form with test data 1. Navigate to and press `Send` button with `Enter` key 1. Observe the announcement of a screen reader * Repeat the steps above with keyboard alone (without a screen reader) ### Expected: 1. Screen reader is announcing that the report is successfully sent, the screen reader announces the success message, at minimum the text that is visually a title of the dialog: `Success: Your report has been sent` ### Actual: 1. Screen reader only announces the `Okay, button` (where the focus is placed), all of the above content that includes essential status data of the report is ignored and, unless the user would move the screen reader focus backwards (in browse mode, with arrow up), they would likely miss the status message altogether Maybe wrapping up the dialog in a landmark to ensure a screen reader announces the label of the dialog when the focus is placed elsewhere in the dialog would resolve the problem, but it's better to _also_ have the status message to be marked up with `role=status`
Bug 1856026 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
### STR:
1. Ensure a screen reader is running
1. From any site, open a new `Report Broken Site` tool (i.e. via URL bar > Enhanced Tracking Protection > Report Broken Site) with keyboard
1. Fill in the form with test data
1. Navigate to and press `Send` button with `Enter` key
1. Observe the announcement of a screen reader
* Repeat the steps above with keyboard alone (without a screen reader)
### Expected:
1. Screen reader is announcing that the report is successfully sent, the screen reader announces the success message, at minimum the text that is visually a title of the dialog: `Success: Your report has been sent`
### Actual:
1. Screen reader only announces the `Okay, button` (where the focus is placed), all of the above content that includes essential status data of the report is ignored and, unless the user would move the screen reader focus backwards (in browse mode, with arrow up), they would likely miss the status message altogether
Maybe wrapping up the dialog in a landmark to ensure a screen reader announces the label of the dialog when the focus is placed elsewhere in the dialog would resolve the problem, but it's better to _also_ have the status message to be marked up with `role=status`