– DRAFT –
ARIA Authoring Practices Task Force

Setup and Review Agenda

<Jem_> jon: there is the bug on link checker

<Jem_> daniel: I could not find the issues of colon...most of them coming for w3c because we are updating cloud Infrastructure.

<Jem_> Matt: We can have the PR for the issue.

<Jem_> Jon: we have already the PR #3435

<Jem_> Link to errors in pull request #3216

<Jem_> Daniel: I will open the issue.

<Jem_> zakim. take up item 2

Publication planning

<Jem_> MK: Includes 5 Open PRs and 1 merged PR

<Jem_> Targeting Thursday June 25

<Jem_> Quick check of review status for:

<Jem_> PR 3445: Experimental Tabs with Actions Example: Clarify keyboard documentation for Tab key by mcking65

<Jem_> PR 3430: Editor Menu Bar Example: Implement optional spacebar behavior for radios and checkboxes by NakajimaTakuya

<Jem_> discussing Add Practice Page for Supporting Color Contrast Settings PR 2991

<Jem_> joe: I can review pr 2991.

<Jem_> Jon Gunderson will review #3430

PR 3372: Add Experimental Example of Scrollable Listbox with Actions on Options

<Jem_> github:PR 3372: Add Experimental Example of Scrollable Listbox with Actions on Options by mcking65

<Jem_> github:PR 3372: w3c/aria-practices#3372

<Jem_> github:w3c/aria-practices#3372

<Jem_> mk: we made great updates and good progress.

<Jem_> mk: Curt used notification API to fix live region issue. I will add some info about it to accessibility feature section.

<Jem_> ...Some observations from screen reader and keyboard testing:

<Jem_> Arrow keys are wrapping from last to first and vice versa; should not do that.

<Jem_> Home/end not working.

<Jem_> *Focus moves to listbox without being focused on an item when a button, e.g., move up, is disabled.

<Jem_> Accessible name of option does not reflect when item is favorited.

<Jem_> Curt:what would happen when they are focused on the action buttons? is it the same behavior - going to home or end -or does it stay inside of action?

<Zakim> Daniel, you wanted to say in the original vo actions implementation there is no concept of home/end

<Jem_> mk: what if you have used non voice over but to move the focus to one of the buttons control where the focus goes in the list options.

<Jem_> jon: there is a bug - if you are on the top, first list itme, hit up arrow, focus goes away

<Jem_> mk: when you tab in the list box, the focus is on the active element is the list box element and you have active dececendants set the option.

<Jem_> whnever you sanp back, focus back to the option that should be the active element becomes the list box. and aria active descentdant is pointing to the option

<Jem_> Curt can work on the example this week to continue testing.

<Jem_> when the favorite button is toggled on , I think we need to chante the name of the option, the accessible name of the option. I hope google can fix the accessible name bug.

Issue 3442: Guidance for the combobox - input click behavior

<Jem_> github:w3c/aria-practices#3442

<Jem_> https://www.w3.org/WAI/ARIA/apg/patterns/combobox/examples/combobox-autocomplete-list/

<Jem_> mk: the question is about mouse behavior.

<Jem_> when there is the value for the combo box, - let's say you chose Alaska - the focuase should be position the carrot and expand the list and show just alaska in the list or should it postion the carrot and expand the list and show all options in the list?

<Jem_> jon: We don't really talk about mouse behaviors...

<Jem_> mk: behavior of the keyboard user is equivalent to the behavior of the mouse user.

<Jem_> jon: people tend to think that mouse behavior is something to be followed.

<Jem_> mk: currenlty, if you tab into it you just give it focus to the combo box, not showing the expanded list.

<Jem_> joe: direct manupulation express an intent that user wants to make a change.

<Jem_> mk: do we want to have the exception for the filtering behavior?

<Jem_> mk: type-> filtering capability-> either edit to change and the filtering capability get overridden?

<Jem_> jon: you have to keep track of focus and if it does not have focus, you just don't apply the filter

<Jem_> mk: when you click the chevron when its collapsed should that always show the entire list and it would only filtering if you start doing typing in the edit box?

<Jem_> jon: it can be simpler - you click on the box and it has a valid value then you show the entier list and the selected item. if it is not a valide value, you show the filtered list.

<Jem_> it also work the exact same way with arrow keys, so we havew to revise arrow key documentation

<Jem_> we have to make sure it work for the mouse and keyboard behaviors ..same.

<Matt_King> present?