Bugzilla

Alex Arnaud (as a user depending on easy access), can you comment from accessibility point of view?

To improve ux-efficiency in message composition, we're introducing 3 new commands, "Show and focus To field", "Show and focus CC field", and "Show and focus BCC field". They come with international keyboard shortcuts, Ctrl+Shift+T, Ctrl+Shift+CC, and Ctrl+Shift+BCC. When a field isn't shown, the command will show and and focus them. When a field is shown, it will just focus them, which is especially convenient via keyboard shortcut. So the net result is always "Field shown and focused". We're currently discussing ways of making these new commands discoverable and accessible.

- In the main UI, the commands will be available from the address row disclosure buttons (CC/BCC) on top of the "To" address field. The "To" button will usually not be shown unless it's a News account. The buttons have a tooltip which mentions the respective keyboard shortcut.
- Alex and I have proposed to make these commands easily discoverable and accessible via the main menus: View > To field / Cc field / Bcc field. Using the menus (as explained above) will always show and/or focus the field. Hence the commands are never disabled, and do not have a checkmark as you cannot toggle them off like, for example, Contacts Side Bar.
- Magnus doesn't want to have these commands included in the menu as he believes that they are "not really a command at all" and he finds them "weird" because they work a bit different from the classic toggle buttons in the View menu.

Here's our question:
- How important is it for users depending on easy access (blind, autist and other special needs) to have these commands accessible in the View menu? Also considering that the shortcut to focus the "To" field will not be discoverable unless you've set up and are using a "News" identity.

For more background, you may want to read Anje's comment 47, my comment 48, and Magnus' comment 51.
Tia for assisting us with the accessibility evaluation.

Alex Arnaud (as a user depending on easy access), can you comment from accessibility point of view?

To improve ux-efficiency in message composition, we're introducing 3 new commands, "Show and focus To field", "Show and focus CC field", and "Show and focus BCC field". They come with international keyboard shortcuts, Ctrl+Shift+T, Ctrl+Shift+CC, and Ctrl+Shift+BCC. When a field isn't shown, the command will show and and focus them. When a field is shown, it will just focus them, which is especially convenient via keyboard shortcut. So the net result is always "Field shown and focused". We're currently discussing ways of making these new commands discoverable and accessible.

- In the main UI, the commands will be available from the address row disclosure buttons (CC/BCC) on top of the "To" address field. The "To" button will usually not be shown unless it's a News account. The buttons have a tooltip which mentions the respective keyboard shortcut.
- Alex and I have proposed to make these commands and their shortcuts easily discoverable and accessible via the main menus: View > To field / Cc field / Bcc field. Using the menus (as explained above) will always show and/or focus the field. Hence the commands are never disabled, and do not have a checkmark as you cannot toggle them off like, for example, Contacts Side Bar.
- Magnus doesn't want to have these commands included in the menu as he believes that they are "not really a command at all" and he finds them "weird" because they work a bit different from the classic toggle buttons in the View menu.

Here's our question:
- How important is it for users depending on easy access (blind, autist and other special needs) to have these commands accessible in the View menu? Also considering that the shortcut to focus the "To" field will not be discoverable unless you've set up and are using a "News" identity.

For more background, you may want to read Anje's comment 47, my comment 48, and Magnus' comment 51.
Tia for assisting us with the accessibility evaluation.

Alex Arnaud (as a user depending on easy access), can you comment from accessibility point of view?

To improve ux-efficiency in message composition, we're introducing 3 new commands, "Show and focus To field", "Show and focus CC field", and "Show and focus BCC field". They come with international keyboard shortcuts, Ctrl+Shift+T, Ctrl+Shift+CC, and Ctrl+Shift+BCC. On Mac, it's Command key instead of Control. When a field isn't shown, the command will show and and focus them. When a field is shown, it will just focus them, which is especially convenient via keyboard shortcut. So the net result is always "Field shown and focused". We're currently discussing ways of making these new commands discoverable and accessible.

- In the main UI, the commands will be available from the address row disclosure buttons (CC/BCC) on top of the "To" address field. The "To" button will usually not be shown unless it's a News account. The buttons have a tooltip which mentions the respective keyboard shortcut.
- Alex and I have proposed to make these commands and their shortcuts easily discoverable and accessible via the main menus: View > To field / Cc field / Bcc field. Using the menus (as explained above) will always show and/or focus the field. Hence the commands are never disabled, and do not have a checkmark as you cannot toggle them off like, for example, Contacts Side Bar.
- Magnus doesn't want to have these commands included in the menu as he believes that they are "not really a command at all" and he finds them "weird" because they work a bit different from the classic toggle buttons in the View menu.

Here's our question:
- How important is it for users depending on easy access (blind, autist and other special needs) to have these commands accessible in the View menu? Also considering that the shortcut to focus the "To" field will not be discoverable unless you've set up and are using a "News" identity.

For more background, you may want to read Anje's comment 47, my comment 48, and Magnus' comment 51.
Tia for assisting us with the accessibility evaluation.

Alex Arnaud (as a user depending on easy access), can you comment from an accessibility point of view?

To improve ux-efficiency in message composition, we're introducing 3 new commands, "Show and focus To field", "Show and focus CC field", and "Show and focus BCC field". They come with international keyboard shortcuts, Ctrl+Shift+T, Ctrl+Shift+CC, and Ctrl+Shift+BCC. On Mac, it's Command key instead of Control. When a field isn't shown, the command will show and and focus them. When a field is shown, it will just focus them, which is especially convenient via keyboard shortcut. So the net result is always "Field shown and focused". We're currently discussing ways of making these new commands discoverable and accessible.

- In the main UI, the commands will be available from the address row disclosure buttons (CC/BCC) on top of the "To" address field. The "To" button will usually not be shown unless it's a News account. The buttons have a tooltip which mentions the respective keyboard shortcut.
- Alex and I have proposed to make these commands and their shortcuts easily discoverable and accessible via the main menus: View > To field / Cc field / Bcc field. Using the menus (as explained above) will always show and/or focus the field. Hence the commands are never disabled, and do not have a checkmark as you cannot toggle them off like, for example, Contacts Side Bar.
- Magnus doesn't want to have these commands included in the menu as he believes that they are "not really a command at all" and he finds them "weird" because they work a bit different from the classic toggle buttons in the View menu.

Here's our question:
- How important is it for users depending on easy access (blind, autist and other special needs) to have these commands accessible in the View menu? Also considering that the shortcut to focus the "To" field will not be discoverable unless you've set up and are using a "News" identity.

For more background, you may want to read Anje's comment 47, my comment 48, and Magnus' comment 51.
Tia for assisting us with the accessibility evaluation.

Alex Arnaud (as a user depending on easy access), can you comment from an accessibility point of view?

To improve ux-efficiency in message composition, we're introducing 3 new commands, "Show and focus To field", "Show and focus CC field", and "Show and focus BCC field". They come with international keyboard shortcuts, Ctrl+Shift+T, Ctrl+Shift+CC, and Ctrl+Shift+BCC. On Mac, it's Command key instead of Control. When a field isn't shown, the command will show and and focus them. When a field is shown, it will just focus them, which is especially convenient via keyboard shortcut. So the net result is always "Field shown and focused". We're currently discussing ways of making these new commands discoverable and accessible.

- In the main UI, the commands will be available from the address row disclosure buttons (CC/BCC) on top of the "To" address field. The "To" button will usually not be shown unless it's a News account. The buttons have a tooltip which mentions the respective keyboard shortcut.
- Alex and I have proposed to make these commands and their shortcuts easily discoverable **and accessible** via the main menus: View > To field / Cc field / Bcc field. Using the menus (as explained above) will always show and/or focus the field. Hence the commands are never disabled, and do not have a checkmark as you cannot toggle them off like, for example, Contacts Side Bar.
- Magnus doesn't want to have these commands included in the menu as he believes that they are "not really a command at all" and he finds them "weird" because they work a bit different from the classic toggle buttons in the View menu.

Here's our question:
- How important is it for users depending on easy access (blind, autist and other special needs) to have these commands accessible in the View menu? Also considering that the shortcut to focus the "To" field will not be discoverable unless you've set up and are using a "News" identity.

For more background, you may want to read Anje's comment 47, my comment 48, and Magnus' comment 51.
Tia for assisting us with the accessibility evaluation.