See also: IRC log
<scribe> scribe: jongund
<jamesn> scribe: jongund
JN: If it is done, just close
MK: It is a branch we don't need
MK: I reviewed based on our
guidelines, you can see my last to commit comments....
... editorial changes in description
... Changed radio group to radio button
... Other changes based on editorial guidelines
... Please read now and see if it is OK
... Name required is true in the spec
JN: It doesn't seem correct
MK: Do you want to raise a spec issue in ARIA 2.0
JN: Why does ARIA require a label
for the group if HTML5 doesn't
... The majority of the time it should have a label, it is an
edge when it doesn't
MK: Is the way that I worded it ok
<jamesn> https://github.com/w3c/aria-practices/commit/bab23225c3059da615afc7d2cde9993691d16da5
<Matt_King> http://w3c.github.io/aria-practices/#radiobutton
AA: Accessible name is required
JN: I am going to log an issue,
it should be optional
... The spec says it is required so we need to tell people to
do it
MK: We could adjust it based on an ARIA 2.0 draft
AA: I have one suggestion
... Under ARIA, roles, states properties... elements owned by a
radio group, move to up after that
MK: We address roles first in
other patterns, then properties and states in order of relative
importance
... We would need to change alot of other patterns if we do
that
AA: never mind
MK: I am closing issue 696
MK: I started from the according
pattern in the edeleted file
... It is in the editors draft
<jamesn> fyi logged aria issue https://github.com/w3c/aria/issues/427
MK: This is the first draft, I
don't have anything to say about the overall, after reading
quite a bit, there is no single according pattern
... I tried to pick out the most popular pattern
JG: When focus is on headers you didn't include arrow keys by themselves
MK: I was worried about browser scrolling the window
JG: What about adding control to the home and end keys
JN: I am thinking, I mostly tab
through them, I am not concerned about scrolling since
... I don't think people need the up and down arrow keys
MK: I deleted most of the previous stuff
JN: Often the implementation of
these things are the according code is different than the code
in container
... The stuff in the according pane is content, not part of
accordion pattern
... If we include it it should be there all the time
MK: If you make the accordion
widget it should do it all the time
... Bubbling will take care of precidence
... It is important to document some way to get to the
header
... We need some level of consistency
... I chose that one because of broser support
JN: You are not worried about
stealing control+page up and control+ page down
... Firefox and chrome do, IE doesn't
MK: On the mac most people do not
even know where the page down key is
... We can see if we get feedback
... In general we should be making the content more important
than the chrome/OS
JN: What we need is a new key on keybopards
MK: What we expect keys to go to the operating system, the browser is equivalent to the operating system
JN: I agree with you as long as I don't wany to use those keys
MK: We should change to control+Home and control+End
JG: I vote for consistency
MK: I am incline to include up and down arrow keys
JN: I definitely see people using the down arrow key
MK: You use home and end in the key as well
JN: Don't take space
MK: If you tab off the header then the scrolling works
JN: Assuming there is something to move focus to
MK: Do we want to make the panel focusable
JG: We want to make sure peope know they exist
MK: We can mark them as
optional
... Any comment on the first section
JK: I like it
JG: Button inside header?
MK: Yes
... JG: what about document order issue? Is that a problem?
JK: Collapse and expand I don't see a header
MK: Some have a expand/contract button, in the example we use CSS
JK: What is the order?
MK: The panel would always follow
the header
... I am not worried about that issue
... Go on to issue 67
https://github.com/w3c/aria-practices/issues/67
http://w3c.github.io/aria-practices/examples/accordion/accordion1.html
JN: I have a comment, can we get
rid of the web fonts
... I don't think we need them
<jemma_ku> https://cdn.rawgit.com/w3c/aria-practices/master/examples/accordion/accordion1.html
AA: Who's idea is the dark gray background
MK: How do I delete the files
JN: I can look at them and see if they are being used
MK: I do not pay attention to fonts...
JK: I do not see them being used
<jemma_ku> https://cdn.rawgit.com/w3c/aria-practices/master/examples/accordion/css/global.css
MK: They were in his zip file
AA: Will it get rid of the dark gray background?
JN: We need to work on the visual
styling
... It doesn't look like he is using the fonts
<jemma_ku> legend { font: normal 1.5em/1 antonregular, Frutiger, "Frutiger Linotype", Univers, Calibri, "Gill Sans", "Gill Sans MT", "Myriad Pro", Myriad, "DejaVu Sans Condensed", "Liberation Sans", "Nimbus Sans L", Tahoma, Geneva, "Helvetica Neue", Helvetica, Arial, sa
JK: I found where the fonts are
used
... web font discussion related to accordion example ...
JN: It needs some styling work....
MK: Can you work on the CSS this week?
JN: Yes I can do it
MK: I am adding a comment to the
issue, issue 67
... discussion about closing issue 56 on revising the pattern
...
... discussion about closing issue 53 on revising the pattern
...
... I am going to close issue 53
... we can discuss the example on september 9th
<jemma_ku> https://github.com/w3c/aria-practices/pull/98
Next meeting is September 12th
JG: I created pull request for 4 tree view examples
MK: We can look at that on september 12th
JG: I may have combobox examples
MK: I wonder if .... APG
1.1
... We can mark in the top table... reviews and edits
done
... review of implementation table ...
JK: layout grid question, grid
and treegrid
... never mind I was thinking about table
MK: We will start out with a data grid
JK: Is landmark example done
AA: yes
JN: We moved the one we are not going to get done into that table
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/gird/grid/ Found Scribe: jongund Found Scribe: jongund Inferring ScribeNick: jongund Present: jongund JamesNurthen JaEunKu AnnAbbott WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 29 Aug 2016 Guessing minutes URL: http://www.w3.org/2016/08/29-aria-apg-minutes.html People with action items:[End of scribe.perl diagnostic output]