[Athen] Agenda for January 10 ATHEN-MICROSOFT Meeting

Anita Mortaloni anitase at microsoft.com
Thu Jan 4 18:23:18 PST 2018


Hi ATHEN,

Sharing out the agenda for the upcoming ATHEN meeting next Wednesday 1/10 at 9am. In addition you will find details on the Ribbon Experience that we would like feedback on this month.

If you have additional items that you would like to discuss, send them prior to the meeting to add them to the agenda.

Talk to you all next week!
Anita Mortaloni

Agenda for 01/10 ATHEN-Microsoft Meeting

* Summary of last month's scenarios
* Comments feature in WXP across mobile, Win32, Mac & web'. Contact: Kathleen Cachel
* Mac Word scenarios. Contact: Cathy Harley
* Feedback request
* Ribbon Experience. Contact: June Lee
* Open Discussions
* Bug Updates
* Windows 10 issues
* Future topics?

Keyboard Interactions and Assistive Technology Announcements in the Ribbon for Office Online
Contact: June Lee (junele at microsoft.com)
Background
Office Online is working on a simpler ribbon to reduce the perception of complexity that our product currently has. We are leveraging this opportunity to revisit our earlier decisions around keyboard (KB) interactions and assistive technology (AT) announcements to improve our products' experience for all users. One challenge we face is that as an Office product hosted online, we sit at the intersection of several and sometimes different standards - Office, the web, and other online Microsoft products.

The questions this week focus on core controls in the ribbon. We'd like to converge on these interaction patterns before moving on to navigating to/from/within the ribbon.

Thank you in advanced for your feedback and help!

Questions about core controls in the ribbon
Below are questions about what you would expect from specific core controls in the ribbon based on their AT announcement. Questions are number as Q1, Q2, etc. and bolded. Note: Not all core controls or all keyboard interactions are included for brevity.


1. Flyout anchor - A button that drops a menu.

Q1. Do you expect to be able to drop a menu from a control with the AT announcement "<label> button collapsed?"

1. Preview gallery - A gallery is a list control that provides a rich visual preview of the options available. This control is excellent for selecting an option based on an image as opposed to a text label (i.e. easier to insert a square via a picture than the text "square"). A gallery control can be placed in a Menu or directly in the Ribbon. Examples of preview galleries are:
* The Font Styles gallery in the Home tab

[a. Font Styles gallery in the Home tab]

* The Picture Styles gallery in the Picture Tools Format contextual tab.

[b. Picture Styles gallery in the Picture Tools Format contextual tab]
There are 2 schools of thought for navigating within a preview gallery:

1. The first is to give keyboard users the same experience as mouse users by making each preview gallery item focusable, and therefore interactable via keyboard.
2. The second is to give keyboard users the most efficient experience by only allowing focus on the preview gallery's button that drops the Menu, so a user must drop the menu before interacting with each gallery item.

Q2. Which do you expect/prefer?

Q3. If each preview gallery item can receive keyboard focus, do you expect it to be marked up as a button or a list item?

1. Split button - A split button is made up of 2 parts. The larger part is a button and the smaller part is a button with a collapsed menu. Its AT announcement is "<label> button collapsed"
Q4. Do you expect to be able to tab to each part of a split button, or for the whole control be 1 tab stop?
Q5. If a split button is 1 tab stop, do you expect to be able to arrow between each part to execute the part in focus via enter/space, OR
Q6. If a split button is 1 tap stop, do you expect enter/space to execute the 1st part (execute button) and alt+down to execute the 2nd part (drop the menu)

1. Toggle button - A button that has an on and off state (i.e. "Bold"). Its AT announcement is "on <label> button" or "off <label> button," depending on its state.
Q7. After updating the state of a toggle button via space or enter, do you expect focus to stay on the control or for it to return to the canvas?

1. Combo boxes

Q8. If you keep hitting 'Arrow Right' when focus is inside the menu, do you expect to eventually leave the combo box and into the next control to the right of the combo box (and vice versa)? If not, do you expect 'Tab' to take you to the next control when focus is inside a combo box?

1. Disabled controls
Q9. Do you expect disabled controls to be focusable even though they are not executable, or do you expect to skip over disabled controls?
Questions about core controls in menus
Below is the behavior you'll experience on Word Online today. I've called out notable differences by adding a sub-bullet to specify such differences. Please comment on the control descriptions you disagree with or have further questions on.

1. Button

Q10. After executing a button in a menu via space or enter, do you expect (1) focus to stay on the control, (2) close the menu and put focus on the flyout anchor, or (3) close the menu and put to the canvas?

1. Checkbox
Q11. After toggling a checkbox in a menu via space or enter, do you expect (1) focus to stay on the control, (2) close the menu and put focus on the flyout anchor, or (3) close the menu and put to the canvas?

1. Combo box

Q12. After updating the value of a combo box in a menu by dropping the combo box's menu, arrowing through menu items, and hitting enter on the focused menu item, do you expect (1) focus to stay on the control, (2) close the menu and put focus on the flyout anchor, or (3) close the menu and put to the canvas?

1. Spin button

Q13. When you hit arrow down to the next menu item and land on a spinner, do you expect another arrow down to (1) update the value of the spinner or (2) take you to the next menu item?

Q14. After updating the value of a spinner via typing in the textbox and hitting enter, do you expect (1) focus to stay on the control, (2) close the menu and put focus on the flyout anchor, or (3) close the menu and put to the canvas?

1. Toggle button

Q15. After updating the state of a toggle button in a menu via space or enter, do you expect (1) focus to stay on the control, (2) close the menu and put focus on the flyout anchor, or (3) close the menu and put to the canvas?

1. Disabled controls
Q16. Do you expect disabled controls to be focusable even though they are not executable, or do you expect to skip over disabled controls?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20180105/424f35e5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 17963 bytes
Desc: image005.jpg
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20180105/424f35e5/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 19373 bytes
Desc: image006.jpg
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20180105/424f35e5/attachment-0001.jpg>


More information about the athen-list mailing list