Meeting minutes
Trage
Triage
Matt_King: wow there's a lot!
Guidance on usage of Authoring Practices Guide vs. editor’s drafts
<jamesn> github: https://
Matt_King: 2 issues in this, one on the intro and one on the editor's draft
Matt_King: editor's draft part of this should be straightforward, eventually.
<jongunderson> https://
Matt_King: the rendering of the main branch (the current "editor's draft") will be replaced by our site here - when we update the main branch, it'll get pushed to the site by the W3C
jongunderson: how do we preview things?
Matt_King: PRs will have a netlify preview now
Matt_King: there's also a netlify preview for the main branch
Matt_King: not useful to point people to that though, it's only good for a day or two at atime
Matt_King: approximately this will all happen towards the end of june, but here's still planning to do
MarkMcCarthy: what about their introduction comment?
Matt_King: part of the plan is to create a TOC, separate the intro out, and make things a little more independent
carousel pattern should use localized "aria-roledescription"s for its elements
<jamesn> github: https://
jongunderson: is that just saying the documentation should make mention of being localized?
Matt_King: isn't that the same as aria-label?
jamesn: aria-labels are usually announced in the PAGE's language, but roles etc. are annouced in the USER's language
jamesn: for roledescription, it can't be automagically translated. it's an ongoing problem with roledescription
Matt_King: i always thought it was localized the same way the page was
jamesn: yes AND it's the best we can do, really
jongunderson: does the roledescription replace the original name?
jamesn: it's supposed to
jamesn: but depends on the implementation
jamesn: many AT speak both roledescription and name
Matt_King: which kind of defeats the purpose
Matt_King: should we do something different with roledescription vs label?
jamesn: i think we're doing things right, but we could be clearer on dev's instructions
Matt_King: so maybe a note about that somewhere?
jamesn: yeah
jongunderson: i can do that
jongunderson: is there an issue changing index to examples in the menubar?
jongunderson: seems like people are having some trouble finding examples
jamesn: going through the patterns section is the way to go right?
jongunderson: yeah, but when looking for certain things (like date picker) there's no pattern
Improve readability - Keep line lengths optimal
<jamesn> github: https://
jamesn: i kind of agree
MarkMcCarthy: it's very wall-of-text-y
jamesn: easily solved with CSS
jamesn: font could be bigger too
<siri> +1
s3ththompson: this might be from a page without a sidebar
s3ththompson: maybe needs a more consistent column, irrespective of the sidebar
Matt_King: i'll transfer this to the other repo
s3ththompson: this is probably part of the WAI template itself
Rich_Noah: it's not as apparent when there is a sidebar, but it's very noticable otherwise
jamesn: so we can file a bug vs. WAI template then?
group: oh yes
Matt_King: now issue 108 in the other repo
Matt_King: i'll ask Shawn about it in the issue
Matt_King: assign to Shawn?
jamesn: yep
Pattern page - add navigation for other patterns on the same level
<jamesn> https://
Matt_King: i love this suggestion
Matt_King: belongs in the other repo, solved on template level
<jamesn> github: https://
group: seems like a good plan
Matt_King: seems like a straightforward design enhancement
Matt_King: there's something similar in the WAI template, previous forward with a select box as well
<siri> love having select drop down
Matt_King: can Isaac work on this?
Rich_Noah: we'll get the issue into the backlog and schedule it
Matt_King: not urgent!
Matt_King: could be a Q3 change
Home page- The arialabel for the footer element is not descriptive.
<jamesn> github: https://
Matt_King: this is also a template issue
jamesn: does it really need an aria-label?
Matt_King: there's multiple contentinfos
jamesn: and they're both landmarks?
Matt_King: yes
Matt_King: page content info has last changed, updated by, etc. it COULD be complimentary, but it is content info, in my opinion
jamesn: i'd almost prefer a single footer with two regions inside it - two footers seems wrong
jongunderson: i think so too, there should be one footer, one banner, etc. if they have subsections, use regions
jongunderson: two contentinfos seems odd - it's against our landmark guidance, too
Matt_King: it says if there's multiple, label them, not sure it's broken.
Matt_King: it's not super easy to combine them
jamesn: i get that - i just don't think it's optimal
jongunderson: +1
Matt_King: from an SR user, it's nice to know the page contentinfo has last update ddate, the site one has general info, etc
jongunderson: why not call it a "last updated" Region?
jamesn: right - you generally ignore contentinfo landmarks because they're generally useless. how often is there anything other than a site level one? if you didn't write the site, would you expect another one?
Matt_King: the rest of the WAI site has page contentinfo that contains last updated, by who, and acknowledgements
Matt_King: that info gets mixed up with really important info on our pages, like last updated and changelogs
jamesn: generally, this sounds like a template issue. can we punt to them?
Matt_King: this hyperspecific label thing is a template issue
Matt_King: i'm okay with the current label, but the site label could be enhanced. we could drive it
Homepage- The header element is nested inside the main element.
<jamesn> https://
Matt_King: oh there's a header around an H1, which isn't needed. and yes, header inside a main element doesn't seem right
jongunderson: back in the XHTML days, the header element defined the heading structure itself
jongunderson: i think it's odd it's not being used to create a banner landmark though
jongunderson: i'd say move the header element to the top, leave the H1 alone
Matt_King: i think this belongs in the other repo too
jamesn: so what's the bug, then?
Matt_King: the H1 is wrapped in a header; exposed as a banner
jamesn: that's a firefox bug, it's scoped to main vs generic so it's not getting exposed right
<jamesn> A header element is intended to usually contain the section's heading (an h1–h6 element or an hgroup element), but this is not required. The header element can also be used to wrap a section's table of contents, a search form, or any relevant logos.
jongunderson: if they're using the headers this way, they're making banner landmarks
jongunderson: with voiceover and safari
Matt_King: chromium does not
Matt_King: so it's a gecko and webkit bug
jamesn: it's correct and allowed
jongunderson: it's allowed, but i don't think it's correct
jamesn: it contains the section's heading right?
Matt_King: main is a sectioning element right?
Matt_King: it conforms with the spec - Siri, what do you say?
siri: even though it conforms, but if it's not required i'd suggest removing it
jongunderson: +1
jamesn: i think we should also file bugs vs. the browsers, don't disagree about removing it
Matt_King: so could someone flag this with firefox and safari?
jamesn: browsers don't seem to expose it in the accessibility info - maybe it's NVDA and VoiceOver then?
Matt_King: maybe the accessibility tree itself has a bug then?
jamesn: remember - we're triaging :)
Meeting wrapup
jamesn: might not be as simple as filing bugs with the browsers
siri: i'll do some investigation
jongunderson: i cannot
Matt_King: sounds good - i'll move this to the other issue