Meeting minutes
<janina> /join #rqtf
Agenda Review & Announcements
janina: Standard agenda, some additional items
Charter review
<matatk> AC reps' survey on the charter - please vote if you can! https://
<matatk> Proposed charter (full): https://
janina: Voting expires in about a week, 24th, middle of the night, Boston time
<matatk> Proposed charter (diff): https://
<matatk> s//join #rqtf//
janina: Right now, we don't have enough positive feedback, need still more to feel confident. I will go through our member list
Upcoming presentation on Accessibility Compatibility Data
matatk: This is about the Base Line Initiative. So about the "safe" features, that you as a web content developer can rely on, that the browser supports these. The problem is: It doesn't consider how well AT supported theses features are.
matatk: This has been a known issue and they want to fix it. At the moment, work is being done, by Lola Odelola. She will join in August this call and give us a presentation. We want to make sure, we get as many people as possible to this call.
janina: As this is a really important topic, we will probably record the presentation but not the discussion following it so we are free to share our ideas and comments
New on TR
Roy_Ruoxi: Nothing new
Spec review requests
matatk: No spec review at the moment
Comment review requests
matatk: We have a few, some old, some new, so I grouped them in the agenda. We will do them in order here:
<PaulG> this loads a blank page for me (?)
Proposal: New attribute alt-origin to indicate provenance of alt text (machine vs. human authored)
<matatk> source: whatwg/html#11448
<matatk> tracking: w3c/
matatk: Did someone look through this, any thoughts?
Dr_Keith: Why would we want to include whether alt text is machine generated of human generated versus just wondering if it's correct?
<JenStrickland> Some of us got in queue to respond to the question.
matatk: Good question. Looking though the GitHub Issue a few people have the same question.
<matatk> Credible Web CG: https://
mike_beganyi: Yeah, I agree with the comments by Steve and and Leonie, who had good points.
JenStrickland: Same, the idea is nice but I think it's off track.
<Zakim> matatk, you wanted to plus-one Jennifer
PaulG: Another point: A visual indicator would also be necessary and not only a disclaimer for robots and AT users
<Fazio> It's akin to automated testing vs manual
matatk: The Credible group is doing important work in this context, see the link above if you are interested.
<Fazio> I think its useful
matatk: I wonder if we could come to consensus on this and write an APA comment, not just from individual members
<Fazio> all companies want scale. This allows scale
<Neha> +1 Fazio
Add showValidationMessage() method for validation without focus management
<matatk> source: whatwg/html#11416
<matatk> tracking: w3c/
matatk: The current reportValidity function auto refocuses the invalid element. So trapping focus, bad UX, accessibility problems
<JenStrickland> I also agree with you and Paul. It's a valuable fix.
matatk: Paul and I both think this proposal is a good idea. Someone from WHATWG added a "maybe" comment. Could help with a11y but also backfire in some cases
<PaulG> bit.ly/a11yform
matatk: I can draft something in our tracking thread and later post the comment, when there is no disagreement
PaulG: Pauls presentation is really useful and will us it in the comment
… sorry comment from Matthew
[css-env][css-fonts] New `<meta text-scale>` tag to make UA initial font size respond to OS text scale setting
<matatk> source: w3c/csswg-drafts#12380
<matatk> tracking: w3c/
matatk: My initial thought is fantastic
PaulG: I agree, that's why I added it
matatk: Any objections if we say APA likes this
matatk: (No objections) Awesome will do it
[css-anchor-position-1] Improve accessibility guidance
<matatk> source: w3c/csswg-drafts#10311
<matatk> tracking: w3c/
matatk: We talked about this before. They asked for a11y guidance, because they wanted better examples as to how to use it and maybe not to use it
matatk: Paul and Neha added ideas and examples to our tracking issue. We still need a tooltip and a disclosure example that uses anchor positioning and a bit of ARIA
matatk: Once we've got the missing examples, I'm happy to write some text and maybe Paul can check it
Neha: I will write the missing examples
(end of meeting)