Meeting minutes
<Rich_Noah> Howard present+
<Jem> meeting agenda: https://
Setup and Review Agenda
scribe
New APG Issue Triage
<Jem> github:https://
James: changes done for combobox 1.2 are reflected
Support the changes made to the aria-spec
MK: It is addressed
It is addressed in the pattern too
JN: Second point, value is calculated as child
The value of the combobox is either (1) the same as the value of the element with combobox role (such as the value of the input) or (2) if that element doesn't have a value then it is the "name" of the element calculated as if the element is a button
MK: There is no explicit statement in the example that says the content like that.
Content of the <div> represents the value
like don't put anything in the <div> that becomes the value
James: Good to put that info so that people won't put wrong info
Jon: Can we change and make it make explicit the content regarding the <input>
James: Waiting for core AAM issues are solved 1.2 is ready to publish
MK: issue #2287
<Matt_King> github: https://
<jamesn> github:https://
Two-state checkbox
<jamesn> github: https://
github: https://
MK: About the tab target size at a certain break point
Jon: we are developing a responsive library
Jon: we are not developing responsive library
<Jem> https://
James: In 1.2 this is changed
The hit point includes the label and checkbox
MK: Jem is updating the issue with the updated example
checkbox and datepicker-dialog have tables with empty headers #2285
https://github.com/w3c/aria-practices/issues/2285
Mk: this is an editorial issue
MK: change <th> to <td>
Jem: 1.2 looks correct
It is maintaining checkbox and ddialog
<siri_> s/ ddialog /dialog
Jon will fix the issue
James: The first and second are blank then they need to be blank
MK: there will no <th> but will be empty <td>
MK: roles can be implicit or explicit. We have explicit roles
James: It is 4 column table, the first cell be non-blank
If you move down the row, some marked as heading and some not, will that not be confusing
James: either row column jumping around or empty <td> will create confusion
Jon is in process of fixing issue
Remove JsDocs Warnings #2039
<jamesn> github: https://
Rich: Js.doc, is warning about blank *, white space, as discussion few days ago about auto fixes
MK: They were showing up on the files tab, hope everyones comments are wrt JS.doc
Howard has no questions
Menubar PR
<Jem> https://
MK: Getting authentication issue when pushing to repo
<Jem> github:https://
MK: The content is not clear about tab moves in and out of menubar
Matt made changes to the content and when it is pushed, ask people for review
MK: Don't know if these are APG issues
<Jem> Matt has made some slight revision to make it clear.
Vnu-jar issue
<Jem> https://
<Jem> https://
<Jem> error: The “role” attribute must not be used on a “tr” element which has a “table” ancestor with no “role” attribute, or with a “role” attribute whose value is “table”, “grid”, or “treegrid”.
MK: Putting roles on Tree grid
role= row, there is no way to satisfy this linter and hope Michael will change it
Comments from Zoe in the issue: It seems as though the error is correct? The treegrid example has <table role="treegrid"> and <tr role="row">. According to ARIA in HTML the <tr> shouldn’t have that role? The validator is merely showing that? Am I misunderstanding the issue? Digging a bit further: <table role="treegrid"><tr role="row"><td>test</td></tr></table> results in: error: The “role” attribute must not be used on a “tr” elemen[CUT]
if you remove role=row, validator throws error as <tr> has no aria-posinset or aria-setsize
<Jem> aria-level="1" aria-posinset="1" aria-setsize="1" aria-expanded="true
<jamesn> "Therefore, authors MUST NOT apply aria-expanded, aria-posinset, aria-setsize, and aria-level to a row that descends from a table or grid, and user agents SHOULD NOT expose any of these four properties to assistive technologies unless the row descends from a treegrid."
James: This is validator bug, when row is within the tree grid aria-posinset , aria-setsize, aria-expanded, aria-level
If the context of <tr> in the grid then validator should support these 4 attributes
Mk: aria-posinset , aria-setsize,aria-expanded are supported only on tree grid
not on grid
If <tr> element is child of tree grid , it can have aria-expanded, aria-posinset, aria-setsize, and aria-level
Jon will raise issue for validator
Mk: remaining all warnings
MK: remaining all are warnings
rsagent, make minutes