Meeting minutes
mck: any agenda change?
Roadmap and meeting agenda planning
mck: we had some discussion and we would like to continue
mck: summary of the meeting last week.
… having a smaller meetings outside of APG - Slider example meeting led by Jon
<CurtBellew> Hi :)
mck: balance of discussion between technical vs prioritization for an instance
Quality of current content vs new content
mck: managing the PR and having adquate review
… PR and Issue burndown.
… leads to redesign and aria-at design
… trying to move APG forward
… open to the discussion
jon: I would recommend to have additional and designated reviewers.
… It takes so long to close the issue. waiting for a month for the review, once it was reviewed, usually significant changes are required.
mck: we can do bring more people for reviews
mck: we have different types of review so it is not necessary about accessiblity knowledge.
jamesn: visual review needs to be consistent, possibliy done by the same person.
… ARIA has the same problem in regards to review.
sarah: a good documenation may be helpful.
mck: do you think we are in good position to bring the people based on exisiting code documentation?
mck: for now, we need to bring W3C members only but I would like to fix that via community member.
sarah: regarding github assigment, the membership does not matter.
curt: call to review for the issue will be helpful?
mck: we can only do once a month
… bring new members and welcome them, or code review event?
curt: the reason for my question is that there are a number of people whose job is related to APG code and possibly we can invite them to work together.
mck: possibley organize a campaign to bring new people...
… I talked to Boaz, Bocuop about "program management" perspective and we need to have a clear scope on that
jamesn: if we bring a designated person, it become a whole project for that person.
… possibly side effect of (?)
jon: the biggest help will be accessiblity features - mobile device testing. we need to make sure "aria-right", sometimes aria example is sleeps away when we look into so much customization. widget library ...
jon: we may put a caution that APG examples are not a simpel widget library to be used right away. It will be more tool for understanding ARIA. helping to understand the issues is the core rather than building maintainale widget library. Focus on target and available resource will be beneficial. For example, we had a great contribution to slider example meeting who was not a regular member.
jon: I can reach out to people to review and leave the comments.
jamesn: we may able to ask people in slack channel too.
car: I support the idea, James.
mck: If we can coordinate the channel, ask specific questions, it would be good.
jamesn: I agree with getting useful info, rather than like or dislike of example
sarah: I am interested in coordinating slack feedback regarding APG example.
mck: we are on the map to setting up the community group. Items to keep in mind is that we can engage people via slack with specific framework.
jon: we can also create focused group for each example.
<carmacleod> https://
jon: summary of the meeting - don't add additional features.
… just replace my example with warning.
car: I can help with warning note
… with info to html range
mck: one of goal for redesign is also promoting related html example
… separate discusssion but aria value now vs aria value text is not clear.
jon: aria hidden for unused svg item was discussed.
… I need to test mobile touch
mck: more examples, Sarah?
sarah: usually keyboar and click. wonder how many drag action in the existing examples?
curt: pointer cancellation in wcag
… click is fine.
sarah: button.js use click funtion
<CurtBellew> wcag 2.5.2 : https://
<jongund> https://
mck: Jon's meeting brought a good point to look into mouse vs pointer event from the examples.
jon: focus styling - Focus border around thumb and Focus border around entire slider
mck: are you talking about adding more focus around the thumb?
jon: yes.
mck: high contrast issue - we should somehow pull together about HCM
mck: actually thinking about writing the HCM guideline.
… sarah can be a great to write that
car; how about media query for HCM?
group talk about different HCM configuration
Action: item: supporting high contrast setting in APG spec.
<trackbot> Error finding 'item'. You can review and register nicknames at <https://
in APG
james: how would this be related to ARIA closely?
future reference for Sarah's work https://
<sarah_higley> sarah: If you wanted to be pedantic, it has to do with ARIA in that native elements get high contrast mode adjustments automatically, but a <div role="link">, for example, would need manual color adjustments
car: sarah's menu example - it is not hidden on the load and it shows all the menu and hidden later. do we need to consider the js diabled situation?
sarah: we may need to worry more about js failing to load.
car: should we worry about "flash of unstyled content" regarding APG example?
sarah: sharing example of heavily relying on interent connection to load Js. - form of discrimintion
sarah: will do make change of "hidden unload"
rrsagents, make mintues
rrsagents, make minutes
<Jemma> s/action item: supporting high contrast setting. /
Action: Sarah will help to draft High Color Contrast Mode section in ARIA APG spec.
<trackbot> Created ACTION-2150 - Will help to draft high color contrast mode section in aria apg spec. [on Sarah Higley - due 2021-02-09].
<jamesn> https://
<Jemma> s/item:supporting high contrast setting/
mck: we need to take out "aria-own" because it is not supported nor consistent.