Meeting minutes
<janina> Date 10 Dec 2025
<janina> /join #rqtf
<janina> Associate W3C and github here:
<Roy_Ruoxi> https://
Agenda Review & Announcements
janina: TPAC follow up will continue for coming weeks and months
janina: We do meet today and next week, then 2 week break, no 24th/31st. Back in 2026
TPAC 2025 Followup
matatk: For all APA impacted issues from TPAC, minutes and recordings are available.
ARIA & APA
<matatk> w3c/
matatk: Joint ARIA meeting, rebooted pronunciation task force. Focusing on use cases in recent weeks and have added a few. Doc is focusing on end user needs. Note that foreign/loan words can be problematic in that they can switch voice tones - which is jarring. Ongoing look for parallel pronunication issues.
<Fazio> Look at the Down Syndrome community about voice changing suddenly causing issues
<Fazio> Other Intellectual Developmental Disability communities as well
matatk: Meeting on bringing in expertise like ARIA to APA meeting. ARIA feels that different groups bring different strengths (technical, use cases) so there is consensus that more expertise in more areas is a good thing.
<Fazio> I have training documentation on trigger warnings
matatk: Trigger warnings from COGA - some future work is coming.
<Fazio> for instance needle images for vaccines
<Fazio> can trigger trauma responses
<Fazio> I'd love to do hardcore user research on trigger warnings
<Fazio> someone would need to fund it though
matatk: Two action items; if the action items are agreed to be reasonable, we'll mark them as in-scope for future work.
MEIG, TTWG, APA
<matatk> w3c/
<Fazio> Clarity on my Youtube captioning comment at TPAC: Manual editing captions in Youtube and lining up the timing is incredibly user friendly and a game changer. I use it to teach captioning
matatk: Meeting on media, APA related to topics such as DVB review (w/Andreas) - this is a taxonomy of media accessibility features, looking for buy in from the community (interoperability). They'll wait for comments until mid-January or so.
matatk: Looking for volunteers to review
<janina> Media User Accessibility Requirements (MAUR): http://
<janina> Note also WCAG3 Media list
matatk: Other items from that meeting; resolved IMSC spec concerns for now.
matatk: Also ARIA notify api discussion; in some circumstances, this will make better fit for areas not well covered by live regions
janina: Will do the read through.
Ttsaulter: Will also do the read through.
tsaulter: Will also do the read through
Janina: Side note, if you are dropped via the lounge, please email janina / roy your time of occurance and IP to help debug
New on TR
SHACL 1.2 Rules
<Roy_Ruoxi> spec: https://
<Roy_Ruoxi> tracking: https://
<matatk> SHACL 1.2 Overview: https://
Spec review requests
Web Sustainability Guidelines (meta-thread)
<matatk> w3c/
matatk: Web sustainability guidelines review, Glenda has items in the issue for discussion and the feedback format can be pushed over to that group. Matt has copied over a process about creating new tracking issue and getting approval for pushing those after APA review. This gives us a tracking issue number that we can follow as addressed.
<Fazio> Found one of the important documents I incorporate into trigger warning design training: https://
RDF 1.2 Reviews (meta-thread)
<matatk> w3c/
<Fazio> basically users will avoid a region of the screen where the trigger exists. so lets say vaccine image. Means user may not get a needed vaccine because they avoid the region that shows a syringe and never schedule
matatk: RDP review has Frederick to review. This is still in his priority queue within the next day or two.
matatk: Best place for comments are in the issue listed (278) in the IRC or follow the instructions if it would need APA consensus so we can collectively agree before submitting.
matatk: If anyone needs help, please ping the list.
Issue tracking
matatk: Items flagged by Paul - do we want to make a tracking issue.
CSS Content publishing without AAM
<matatk> w3c/
paulg: AAM mappings are not well mapped to CSS. Not that taken up yet so it isn't as widely used.
matatk: This is a large thread - there are additional concerns that we should link back up, maybe the ARIA repositories. Paul will research.
CSS Tables has risen from the dead
<matatk> w3c/
paulg: this is a spec for table like structure for table style layouts. May need more information as the use case where this would apply is not clear.
matatk: if paulg can create a tracking issue for this week or early next week, it can start to be reviewed quickly
`<meta name="text-scale" value="scale">`
<matatk> Explainer: https://
<matatk> Tracking issue for font keyword question: w3c/
matatk: purpose is to make base font size updates reflect more globally on a system in an opt-in basis.
matatk: Discussion is around breakage versus opting in to scaling. If anyone interested, please do feel free to review next week.