See also: IRC log
<mck> METTING: ARIA APG Task Force July 31, 2017
<mck> zakimg, make log public
scibe: jongund
<scribe> scribe: jongund
<mck> Projec page https://github.com/w3c/aria-practices/projects/5
AA: On the last call JN was going to assign some reviews, but I did not get an assignment
MK: I didn't see anything in the
notes about assignments
... I did not seen anything in the last meeting about the
project pages for each widget
... Not all the features of the project pages are
accessible
... There a opportunities for working group members to help
withproject related tasks
<sirib> everything for this project shown as Zero
MK: I want this to be a place for
people to see what we discussed about a widget without having
to search the discussion
... There are about 43 issues in this space, but ost are
closed
... I need help, since drag and drop is the way this page
works
<mck> https://github.com/w3c/aria-practices/projects/5
MK: discussion of github project
features ...
... discussion of being to update and edit project information
...
... I will discuss with MC and JN the ability for people to
edit project information
... I cannot edit the projects until Github fixes the keyboard
access issue
MK: What did you mean?
... The pull message was not clear
... It looks like the changes, removing JS that does not do
anything
JG: There was a couple issue, including looking at the wrong place for the labels
MK: For the purpose of teaching
<mck> example page: http://w3c.github.io/aria-practices/examples/menubar/menubar-1/menubar-1.html
AA: This is a pull request, what is the issue
JG: There was a bug in the code
MK: I don't want the javascript
to not create the label
... I am concerned the second example is more complicated and
may confuse people
... If you compare the the source code of the two examples you
see the roles in the right places
... Take out example 2 and simplify the JS code to not put the
ARIA in
... It also sets up one example per page ideal
JG: We need labels on the MENUs?
MK: Currently only touch based screen readers take advantage of the labels
MC: On desktops like JAWS and NVDA do not use the labels on the menu
MK: I will raise this issue with
screen reader companies
... From a best practices we should include them
... Are there any objects to simplifying this example page
AA: Fine with me
Siri: Fine with me
<mck> https://github.com/w3c/aria-practices/issues/410#issuecomment-313885943
MK: The ARIA spec does not allow
aria-expanded on menuitem
... In the desktop world this problem did not exist
Siri: When you use aria-controls ...., it won't see the parent role
MK: in native operating systems
they don't see the parent
... The validator chock on this practice, we raised issue 454
against aria
... We have a couple choices
... Change the examples to remove aria-expanded, this has a big
down side, and we might add it in later
... Another approach is to put notes in the document about this
issue and to ignore this validation error
... I don't think the validator will change before the spec
changes, but we hope to get a commitment on the change
Siri: Agree with MC on the later
MK: I am going to add issues to the ARIA spec and discuss resolution with chairs
MK: The HTML validator for
HTML5
... It allows us a process to check our code against the W3C
validator
AA: Is this why we got the all checks failed?
MK: The reason is the respec
javascript and it changes the shortcut code into fully resolved
URL
... in our build we are getting a timeout on our curl
script
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: AnnAbbott matt_king ShirishaBalusani JonGunderson Found Scribe: jongund Inferring ScribeNick: jongund Agenda: https://github.com/w3c/aria-practices/wiki/July-31%2C-2017-Meeting Got date from IRC log name: 31 Jul 2017 Guessing minutes URL: http://www.w3.org/2017/07/31-aria-apg-minutes.html People with action items:[End of scribe.perl diagnostic output]