Meeting minutes
ARIA APG 1.2 retrospective
<Rich_Noah> Howard present+
https://
URL to preview the publication and as permanent record of the state of the pub branch for the CFC:
APG Redesign Project
https://
https://
this will be the last versioning for APG. redesign project will be new platform for APG document
Prototype: http://
jon: will aria apg 1.1 be deprecated?
mck: old version will get deprecation warning
Jemma will contact michael to place deprecation warning to 1.1
mck: still work to be done with education and outreach working group.
for apg redesign project
… we can aim for axecon as the deadline, fall back can be GAAD
"This publication is expected to be the final publication of WAI-ARIA Authoring Practices 1.2 as a Working Group Note. The content will continue to be updated as a resource outside of the formal document stream. To see plans for the complete guide, review the Authoring Practices Milestone Plan."
https://
https://
mck: we may need to rethink about milestone concept since we are not doing any versioning
james: we will work something out how to versioning the doc.
james: everything except ARIA will be ever green doc.
mck: we also add html exmaples - ex: slider with input and a lot more coming to incorporate to new design
… more cohesive doc for accessibility
… we will continue to work on slider, rating, accordion changes
jon: completing navigation menu guidance will be great.
… u of i campus developers are asking about this example
car: i am also wondering about navigation menu guidnace.
mck: we are getting cloes to finish.
car:
i like the intro section of menu bar and hope it can be part of spec
https://
https://
https://
jon: Example Disclosure Navigation Menu with Top-Level Links and Disclosure (Show/Hide) Navigation Menu can be very helpful
jon: mat and bryan, what do you think about separation link from button in top level links example?
mak/bryan: it is a good thing to separate link from button
jon: I am seeing the hybrid approach.
mck: that is aweful because it forces user to go through so many links
jon: shift tab moves the focus to top level link.
… links should be visible or hidden?
mck: there should be no links hidden from screen reader users.
brayn: there is different example in accordion case. but we suggest separate button to trigger visbility.
of hidden links
jon: display none for submenu items.
mck/bryan: that is ok.
james: are we planning to create web co? mpoent examples to apg
?
mck/james: we can offer vanila version of js and web component but people may abuse those without learning.
mck: we need to make sure that this is not production library.
people would use without learning
car: we need to provide guidances.
mck: we did a lot of work and improved on quality control and infrastructure.
… wondering about outcome
jon: it was worth to see all the updates and upgrade.
… adding accessibility features was good.
<carmacleod> car: we need to provide guidance for responsive design. i.e. how should things like tab component behave on smaller screens? Dropdown?
jon: comparing old example with new example shows that there are so much work to be done.
mck: we can organize project board to prioritize
rich: I see several different project boards.
mck: there is two types project boards -one is based on example pattern and compile all related issues.
… shows the bird view of a specific pattern
… the other is about code quality tracker project board.
it is more about auditing the examples
rich: showing the progress will be benficial.
car: question about region and section role discussion
… if we have div with region without accessible name, is it landmark or not?
mck: yes. it is landmark
james: region required to have accessible name.
form "role" will require accessible name, not form elemement.
car: banner in scope of body with role ban, it is landmark.