W3C

- DRAFT -

ARIA APG TF

03 Oct 2016

See also: IRC log

Attendees

Present
JamesNurthen, JaEunJemmaKu, MichielBijl, jongund, AnnAbbott, Bryan_Garaventa
Regrets
Chair
JamesNurthen
Scribe
MichielBijl, AnnAbbott

Contents


<MichielBijl> scribe: MichielBijl

Issue 109: Develop example of the tree view design pattern (Jon/Jemma) https://github.com/w3c/aria-practices/issues/109

JN: John, any updates on tree view?

JG: code example you mean?

JN: yeah.

<jamesn> http://w3c.github.io/aria-practices/#TreeView

MK: did merge in the pull request.

JN: Should we review this?

MK: Sure

JG: Sounds like we need some changes something in menubar returns false

JN: We’re looking at tree view first
... Are we okay with it? Have people tested it?

MK: There are four examples

JN, MK: haven’t tested them yet

JN: Should we say “have them tested by next week?”
... Log issues to github.

MK: yeah that sounds good.
... Firefox is doing the computation correctly
... I’ll check Chrome

AA: Matt, did you say Firefox did it correctly for aria-posinset, setsize, etc?

MK: Yes
... Firefox 49 is better

JN: Worth discussing during call?

MK: Guidance question, should authors set posinset etc?

JN: Only if DOM structure doesn’t allow it to be computed.

AA: Do we have to test across browsers?

JN: No, APG is best practices, doesn’t have to work everywhere

MB: That’s correct

MK: Should fail ARIA tests
... script and CSS should work
... but screen readers don’t necessarily have to wrok.

*long discussion about whether to include posinset, setsize, etc.*

JN: If everyone can test treeview before next week and file bugs

Issue #12: code review guide (Ian) https://github.com/w3c/aria-practices/issues/12

MK: Is on the agenda to provide group an update where we are with the code guide

IP: Jesse Beach did a lot of work getting some code review software in place
... Basically can see if any submitted code meets our standards
... Need to incorporate those rules into the guide
... Things like number of space, indentation etc.
... Pretty straight forward to edit that
... Were do you want this to live?

MB: root master branch.
... sub dir called docs

MK: Sounds good to me
... Issue with auto update
... Running both auto generate and JS lint

MB: Need status icon for travis/JSCS

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

JN: Don’t want to make it to difficult to contribute

<jongund> what is the url to the requirements?

JK: I agree

https://github.com/w3c/aria-practices/blob/master/.jscsrc

MB: more a job for the editors, shouldn’t make it more difficult to contribute

IP: Agree, makes it easier on our side to review

http://jscs.info

<jamesn> http://jscs.info/


.jscsrc

<jamesn> https://github.com/w3c/aria-practices/blob/master/.jscsrc

JK: What should we do about the errors in the PR?

MB: Ideally, fix them.

JN: JSCS can fix most of them automatically

Call duration

MB: Did we officially shorten it to 60 minutes?

JN: No not yet
... You, Matt, and I can discuss afterwards
... Don’t need CfC

Issue 109: Develop example of the tree view design pattern (Jon/Jemma) https://github.com/w3c/aria-practices/issues/109

Issue 110: Develop example of menu or menubar design pattern (Jon/Jemma) https://github.com/w3c/aria-practices/issues/110

JN: Hasn’t passed travis test

IP: Passing the travis test is irrelevant to functionality

JN, MB: Agree

JN: It’s in the APG
... Think Bryan had a comment on the list

<jamesn> https://github.com/w3c/aria-practices/pull/119

<jamesn> https://github.com/a11ydoer/aria-practices

<jemma_> https://github.com/a11ydoer/aria-practices/tree/menubar

<jamesn> http://jongund.github.io/oaa-examples/examples/menubar/menubar-1/menubar-1.html

<jemma_> http://jongund.github.io/oaa-examples/examples/menubar/menubar-2/menubar-2.html

JN: Do we want to review them here, or do that off call and get back to it next week?

<annabbott> scribe: AnnAbbott

JN: example menu doesn't open on Enter

because menu/menuitems are links

<jemma_> in the spec, "Enter and optionally Space: activate the menu item with focus (perform the command or open the submenu associated with the menu item)."

<jemma_> https://cdn.rawgit.com/w3c/aria-practices/master/aria-practices.html

AA: defer mega menu discussion until Matt is on call due to his experience

JN & Jemma: spec should state clearly what is expected

JN: will log issue

<jamesn> https://github.com/w3c/aria-practices/issues/120

zakim: next item

Review status of current example development work https://github.com/w3c/aria-practices/wiki/Design-Patterns-Status

JN: any updates?
... anyone can take any unassigned
... let's end here & may/may not have call next week

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/10/03 18:22:23 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/??/something in menubar/
Succeeded: s/etc./etc.*/
Succeeded: s/NJ/JN/
Succeeded: s/MC/JN/
Found Scribe: MichielBijl
Inferring ScribeNick: MichielBijl
Found Scribe: AnnAbbott
Inferring ScribeNick: annabbott
Scribes: MichielBijl, AnnAbbott
ScribeNicks: MichielBijl, annabbott
Present: JamesNurthen JaEunJemmaKu MichielBijl jongund AnnAbbott Bryan_Garaventa
Got date from IRC log name: 03 Oct 2016
Guessing minutes URL: http://www.w3.org/2016/10/03-aria-apg-minutes.html
People with action items: 

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


[End of scribe.perl diagnostic output]