Bug 1941630 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.

### Prerequisites:
1. Ensure a screen reader is running, i.e. NVDA on WinOS

### STR:
1. In Firefox, locate and focus with keyboard the hamburger menu and observe the screen reader announcement
    1. you'd need to press `Tab` key until you get to the last group of toolbar controls, by default in release starting with "Save to Pocket" button, then press `Right Arrow` key to move the focus through the tools to the hamburger menu

### Expected:
1. Menu button has a clear accessible name that concisely describes the functionality of this control, i.e. "Application menu" or "Firefox menu"

### Actual:
1. `Firefox` is the label of the menu button. It has a description `Open application menu` that is often skipped and should not be relied on to provide an accessible name and communicate the functionality of the control

This is an [access-S3 issue](https://wiki.mozilla.org/Accessibility/Triage) because it relies on assistive technology users to guess what this button would do. It really is close to `access-S2` issue because at the moment the `Firefox` label is meaningless within the Firefox application.

Screen reader users in the recent user interviews (4 of 4) missed this button or did not really need what to expect in it. Note that while users did find an alternative ways to the actions requested via the ribbon menu, not all functionality is provided in there and could only be accessed via the main menu or a direct URI "about:" which is not widely known by users.
### Prerequisites:
1. Ensure a screen reader is running, i.e. NVDA on WinOS

### STR:
1. In Firefox, locate and focus with keyboard the hamburger menu and observe the screen reader announcement
    1. you'd need to press `Tab` key until you get to the last group of toolbar controls, by default in release starting with "Save to Pocket" button, then press `Right Arrow` key to move the focus through the tools to the hamburger menu

### Expected:
1. Menu button has a clear accessible name that concisely describes the functionality of this control, i.e. "Application menu" or "Firefox menu"

### Actual:
1. `Firefox` is the label of the menu button. It has a description `Open application menu` that is often skipped and should not be relied on to provide an accessible name and communicate the functionality of the control

This is an [access-S3 issue](https://wiki.mozilla.org/Accessibility/Triage) because it relies on assistive technology users to guess what this button would do. It really is close to `access-S2` issue because at the moment the `Firefox` label is meaningless within the Firefox application.

Screen reader users in the recent user interviews (4 of 4) missed this button or did not really need what to expect in it, i.e.:
> Firefox Button - application button. I do not know what it does, honestly.
Note that while users did find an alternative ways to the actions requested via the ribbon menu, not all functionality is provided in there and could only be accessed via the main menu or a direct URI "about:" which is not widely known by users
### Prerequisites:
1. Ensure a screen reader is running, i.e. NVDA on WinOS

### STR:
1. In Firefox, locate and focus with keyboard the hamburger menu and observe the screen reader announcement
    1. you'd need to press `Tab` key until you get to the last group of toolbar controls, by default in release starting with "Save to Pocket" button, then press `Right Arrow` key to move the focus through the tools to the hamburger menu

### Expected:
1. Menu button has a clear accessible name that concisely describes the functionality of this control, i.e. "Application menu" or "Firefox menu"

### Actual:
1. `Firefox` is the label of the menu button. It has a description `Open application menu` that is often skipped and should not be relied on to provide an accessible name and communicate the functionality of the control

This is an [access-S3 issue](https://wiki.mozilla.org/Accessibility/Triage) because it relies on assistive technology users to guess what this button would do. It really is close to `access-S2` issue because at the moment the `Firefox` label is meaningless within the Firefox application.

Screen reader users in the recent user interviews (4 of 4) missed this button or did not really need what to expect in it, i.e.:
> Firefox Button - application button. I do not know what it does, honestly.

Note that while users did find an alternative ways to the actions requested via the ribbon menu, not all functionality is provided in there and could only be accessed via the main menu or a direct URI "about:" which is not widely known by users

Back to Bug 1941630 Comment 0