https://github.com/w3c/aria-practices/wiki/December-1%2C-2020-Agenda

<scribe> scribe:Jemma

Next meeting date - December 15

Wrapping up 1.2 release

s/release /release 1

Review actions to complete 1.2 in November:

discussion about ARIA publication schedule - still wating for the horizontal review to be done from other group

MCK: hopefully we can wrap up all APG issues at next meeting.

Issue: Navigation Treeview Example: Convert to single page example with functionality equivalent to disclosure navigation example by jongund · Pull Request #1558 · w3c/aria-practices

<trackbot> Created ISSUE-1055 - Navigation treeview example: convert to single page example with functionality equivalent to disclosure navigation example by jongund · pull request #1558 · w3c/aria-practices. Please complete additional details at <https://www.w3.org/WAI/ARIA/track/issues/1055/edit>.

https://github.com/w3c/aria-practices/pull/1558\

https://github.com/w3c/aria-practices/pull/1558#pullrequestreview-534904388

comment from Valerie - "And the code looks great as well except the css is not showing up in the "Open In Codepen" button, and this should be fixed before merging. I can spend a bit more time trying to figure out why it's not working."

<jongund> https://raw.githack.com/w3c/aria-practices/update-tree-nav/examples/treeview/treeview-navigation.html#current-statistics

<MarkMccarthy> +1, also dislike moving focus James

carolyn: it is domain specific decision

mck: MS does move focus to right.

James: Mac does not

MCK: This is designer specific decision.

I will write a note about different implementation by different domain in the example

james: the requirments for screen reader user and keyboard users are different.

mck: I think it is still a design decision by domain.

mark/james: focus should not move to right section because users tend to explore different menu items before they actually move the focus to read the contents.

mck: single page app does not work for browsablity.

another topic discussed is tension between keyboard user vs screen reader users.

the group is talking about different apps' use cases - ms outlook and more.

james: As far as there is a clear instruction about two different focus managments, it will be fine.

action items - carolyn will make CSS style change for "caution" on the top, Matt for writing the note for two different focus managemene depending on domains.

<trackbot> Error finding 'items'. You can review and register nicknames at <https://www.w3.org/WAI/ARIA/track/users>.

https://github.com/w3c/aria-practices/pull/1607

we agree to add note and it is done.

we are making fabulous progress on codepen button

<mck> https://github.com/w3c/aria-practices/pull/1584/files

https://w3c.github.io/aria-practices/examples/dialog-modal/datepicker-dialog.html

<carmacleod> https://raw.githack.com/w3c/aria-practices/update-tree-nav/examples/dialog-modal/datepicker-dialog.html

<jamesn> https://raw.githack.com/w3c/aria-practices/update-tree-nav/examples/combobox/combobox-datepicker.html

combo box help info for date format looks better

we can make it consistent for date picker dialog example

combox example has a few pixels overlapwith pop up calendar.

<jamesn> https://raw.githack.com/danieldafoe/aria-practices/fix/date-picker-dialog-overlaps-help-text/examples/dialog-modal/datepicker-dialog.html

https://github.com/w3c/aria-practices/issues/1531

color slide example issue

https://github.com/w3c/aria-practices/pull/1472

mck: I am wondering whether we need to add multiple buttons to make a slider. furthermore, this is also not compatible with mobile.
... this example makes screen reader be verbose like 12 steps to go through.
... the goal is to dispaly aria slider pattern in the way that Aria intends to work.

Jon and Matt will work together to add one more version of slider.

color picker will have two versions - one without button and the other with buttons.

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/December 165/December 15/
FAILED: s/release /release 1/
Succeeded: s/overap  /overlap/
Present: mck Jemma jongund MarkMccarthy Carolyn_MacLeod JamesN
Regrets: Bryan_Garaventa Curt_Bellew Sarah_Higley
Found Scribe: Jemma
Inferring ScribeNick: Jemma

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)