Meeting minutes
<janina> /join #rqtf
Agenda Review & Announcements
janina: TPAC planning continues, there's more work to do, but the agenda should be ready in 2 weeks
APA re-charter
janina: re-chartering is in process. We're looking for votes from members. We're currently at 11 and we need another dozen or so.
… many orgs have not yet voted so please have your reps cast their votes
<janina> ghttps://
<matatk> Voting on APA charter: https://
janina: we have until the end of July to get this done
Horizontal Review process update
matatk: recap: we are improving the horizontal review process. We're close to the first major change which is the HTML version of the self-review checklist.
<matatk> Process for raising issues as part of spec review: https://
matatk: the improvements for folks doing reviews from APA includes raising issues
… I want to add a couple of things to these instructions. You can follow this process and raise comments as part of an a11y review.
… We'd like people to use this process when you do your next review.
… We can adjust the process based on feedback.
… There's an issue template that we're happy with.
… There's a couple of reviews outstanding so we can use this process for those as well (e.g., web neural network, etc.)
… any questions?
(crickets0
matatk: If there's anything you want to see more of in the documentation, let us know.
janina: We think it will make our lives easier
New on TR
Digital Credentials
<Roy_Ruoxi> https://
Roy_Ruoxi: there is an accessibility considerations section but it has no content. This is a first public working draft
… someone could start looking into this one
janina: In the past we've had Lionel look at this but anyone can look into it.
matatk: it's very specific, it relates to digital versions of physical credentials such as government ids.
… it's related to verifiable credentials. But not completely because of the analog to physical documents.
janina: we're early in the process so we want to get on this while we have plenty of time. I'd like to assign Lionel and myself.
matatk: some additional background, various government groups are discussing this issue in a conference: trust, verifiability, security, etc.
… W3C is involved because there's a big push right now.
… it's something for RQTF but we should also consider various mailing lists to get many eyes on it.
Neha: I'd be happy to contribute to this.
janina: it will be at least 2 weeks before we come back to this
Charter review requests
Web Applications Working Group Charter
<Roy_Ruoxi> https://
<Roy_Ruoxi> https://
janina: it's a busy group, we've worked with them often. Is there anything new in the charter?
Roy_Ruoxi: they didn't mention any liaison with us
janina: we haven't had a problem working with them when we need to, so not sure it's needed.
Roy_Ruoxi: there are some new concepts in their charter
matatk: devices and sensors has a collaboration spec for device orientation and motion
janina: I'm inclined to say we can sign off on this, I have no concerns
matatk: agreed
Spec review requests
matatk: we don't have Jen on the call and we have a lot of CSS to get to. The Web Neural Networks API, where we published our comment last week, we also discussed some other issues.
… Paul raised a good point that we can raise issues with other groups like audio description and ensure the ideas get into other areas like VTT (unsure of minuting).
… I'd like to have someone follow our new process to make these comments.
I can try to make a comment about audio description.
matatk: I'm happy to help and we can look at it again next week
Comment review requests
Canvas Text Metrics for Editing, Art and Design
<matatk> source: w3ctag/design-reviews#1095
<matatk> tracking: w3c/
matatk: this is about putting text on the canvas in artistic ways
… this could involve fallback content as well as live regions if it was dynamic in nature
PaulG: My main concern is that <canvas> itself is like 3 raccoons in a trenchcoat; it doesn't really have a good fallback. COGA reasons (e.g. dyslexia); reading order could be a mess; ...
mike_beganyi: to echo Paul, changing direction and flow and making that available to AT is an issue. I mentioned skew, kerning, but not dyslexia specifically.
matatk: Jeffery Askin suggested that references to the elements could have fallbacks.
PaulG: Non-text content needs a text description if you want to meet the spirit of WCAG. Having artistic text floating around in a canvas was not anticipated by WCAG.
janina: Canvas came along in HTML as a method to provide bits on screen.
PaulG: What I'm guessing is that even though AG may be aware of it, they may think it's not an evolving area.
janina: Concern around an area of the page having its own ecosystem.
PaulG: Whole thing needs role=image and a text description at a minimum.
janina: The idea of mapping the API to elements sounds interesting to me. I like the subversive implications of putting it into an API.
matatk: this is an active TAG review and will probably be asked for my thoughts on it.
HTML in Canvas: WICG/
matatk: there's something called HTML in canvas which is new APIs for rendering 2d and webGL. It would be in the DOM but it would be rendered in the canvas.
… they mention accessibility improvements and they mention the fallback and better support for it.
janina: That sounds like a good approach
PaulG: +1
<mike_beganyi> +1
[css-overflow-5] Discrete versus navigation scroll marker mode
source: w3c/csswg-drafts#12122
tracking: w3c/
matatk: Concern about overreach, CSS imparting roles and behavior.
PaulG: Concern that this conflicts with named anchors.
janina: What he said!
<mike_beganyi> +12
Add hover/focus/long-press triggering delays to CSS
source: w3c/csswg-drafts#9236
tracking: w3c/
PaulG: This is something that most devs are already trained to do.
… Have two concepts: throttle and debounce.
… Those two mechanisms for adding a slight delay - either for perceived improved performance, or preventing someone from moving their pointer across the screen and being bombarded by pop-ups - could be useful.
… Seems compatible with WCAG - don't hide stuff whilst someone's using it, for example.
… the appearance of it can be delayed slightly, that's fine, and it can animate out - doesn't affect the WCAG angle.
… Doesn't use JavaScript, so that's good, though custom tooltips not really needed. But it's OK.
Triage
PaulG: Pointer Animations - if it respects reduced motion should be OK
PaulG: interactivity needs discussion - see Patrick Lauke's point that it will affect discoverability - e.g. if you look for other slides, and they're not in the accTree, you won't find them.
Paul's comment: w3c/
Patrick's comment: w3c/
Scott O'Hara's comment: w3c/
This was the other issue Patrick wanted interest on