Bug 1835361 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. On a translatable website, navigate to the awesomebar. Press `Tab` once to move the focus to PiP control and then press `Right Arrow` key to focus the `Translate this page` toggle
1. Press `Space` or `Enter` to open a Translations panel
1. When the panel is opened, locate the keyboard focus position

### Expected:
1. The focus is moved to the panel and the gear image button (`Manage translation settings`) is focused

### Actual:
1. The keyboard focus remains on the toggle button

### Notes:
1. pressing `Tab` once or pressing `Down Arrow` key would move the focus to the panel, thus the panel could be reached by a keyboard-only user, but this is a workaround and not an expected behavior, thus an a11y-S3 severity
2. Good example: Identity panel toggle (`View site information`)
### STR:
1. On a translatable website, navigate to the awesomebar. Press `Tab` once to move the focus to PiP control (if present) and then (if needed) use `Right Arrow` key to focus the `Translate this page` toggle
1. Press `Space` or `Enter` to open a Translations panel
1. When the panel is opened, locate the keyboard focus position

### Expected:
1. The focus is moved to the panel and the gear image button (`Manage translation settings`) is focused

### Actual:
1. The keyboard focus remains on the toggle button

### Notes:
1. pressing `Tab` once or pressing `Down Arrow` key would move the focus to the panel, thus the panel could be reached by a keyboard-only user, but this is a workaround and not an expected behavior, thus an a11y-S3 severity
2. Good example: Identity panel toggle (`View site information`)
### STR:
1. Ensure that Translations are activated via `browser.translations.enable=true`.
1. On a translatable website, navigate to the awesomebar. Press `Tab` once to move the focus to PiP control (if present) and then (if needed) use `Right Arrow` key to focus the `Translate this page` toggle
1. Press `Space` or `Enter` to open a Translations panel
1. When the panel is opened, locate the keyboard focus position

### Expected:
1. The focus is moved to the panel and the gear image button (`Manage translation settings`) is focused

### Actual:
1. The keyboard focus remains on the toggle button

### Notes:
1. pressing `Tab` once or pressing `Down Arrow` key would move the focus to the panel, thus the panel could be reached by a keyboard-only user, but this is a workaround and not an expected behavior, thus an a11y-S3 severity
2. Good example: Identity panel toggle (`View site information`)
### STR:
1. Ensure that Translations are activated via `browser.translations.enable=true`.
1. On a translatable website, navigate to the awesomebar. Press `Tab` once to move the focus to PiP control (if present) and then (if needed) use `Right Arrow` key to focus the `Translate this page` toggle
1. Press `Space` or `Enter` to open a Translations panel
1. When the panel is opened, locate the keyboard focus position

### Expected:
1. The focus is moved to the panel and the gear image button (`Manage translation settings`) is focused

### Actual:
1. The keyboard focus remains on the toggle button. Screen reader user may not be aware of the panel being opened (i.e. an NVDA screen reader on Windows does not announce anything)

### Notes:
1. pressing `Tab` once or pressing `Down Arrow` key would move the focus to the panel, thus the panel could be reached by a keyboard-only user, but this is a workaround and not an expected behavior, thus an a11y-S3 severity
2. Good example: Identity panel toggle (`View site information`)

Back to Bug 1835361 Comment 0