Meeting minutes
/join #rqtf
Agenda Review & Announcements
Maturity Model Wide Review
<Fredrik> Wowowowowowowowowow!
Fazio: Maturity Model out for wide review.
<matatk> https://
<stevef> may be of interest: Screen Reader HTML Support – Lookup https://
janina: Not reviewing on GitHub. Reason we're out for wide review preparatory for us to say we're done. We all need to vote on it when it's time to publish. If you want an early peek, can find in following link.
Screen Reader HTML support
<matatk> HT SteveF may be of interest: Screen Reader HTML Support – Lookup https://
Maturity Model Wide Review Announcement: https://
stevef: WIP demonstration of HTML support for screen readers.
Horizontal review process - for us
matatk: Documentation mostly complete for our procedures
matatk: Thinking of APA's real value about what we add regarding technical stuff, but we think about use cases others don't
… There are a number of new members who can bring new perspectives to that work. Might be helpful to point to collection of use cases we've already got and can expand upon.
… Give guidance to spec authors so that we don't need to take on as much effort as we do now. Some pointers will be helpful.
janina: This is absolutely important and contribute to. Doesn't normally come to us as a use case. We see from horizontal reviews that something is missing and that's very valuable to specify and elucidate.
Horizontal review process - for spec authors
<matatk> Matthew explaining the gist of this, but here are some totally optional to read, and very deep in thread details of the very latest ideas around how to make it easier for groups to contact APA (posting in case you want to see TAG and APA interacting): https://
matatk: Number of things we're working on with TAG and FAST to make spec authoring much quicker.
matatk: TAG has a screener (questionnaire) to help authors identify accessibility gaps
matatk: Make the process easier for all to participate. More info coming later but consult previous link for info
TPAC 2025
New charters
Web & AI Interest Group
<Roy_Ruoxi> - charter: https://
<Roy_Ruoxi> - issue: w3c/
Roy_Ruoxi: Wide program to involve the community in discussing AI
janina: Not too concerned given Roy's involvement.
Roy_Ruoxi: Involve some of RQTF's work.
matatk: Accessibility is mentioned in this charter.
matatk: Makes sense to add privacy and accessibility to this, given nature of AI at the moment
Roy_Ruoxi: Want to find a place to have research on AI in W3C. Maybe I will add one of two (security and privacy) to this
New on TR
Spec review requests
IMSC Text Profile 1.3
<matatk> due: 2025-09-12
<matatk> tracking issue: w3c/
matatk: Talked recently about Jen's idea to have a tracking issue
matatk: [reads Tiffany's comment from GitHub]
matatk: Think that accessibility of these characters is important. I think we should write back and ask Tiffany to suggest some text as an example
janina: Will be good to specify how to do this before suggesting
Neha: They have not added super- and subscript text. The issue list mentions these but not elsewhere. I couldn't find anything on the page, had to read into the spec
matatk: Could you try the process of leaving a comment as specified in the APA outline.
Neha: Sure.
DID Resolution
<matatk> due: 2025-09-25
<matatk> public request: w3c/
matatk: Make sure there are alternative representations of data as specified at the previous link.
janina: Can add me, Matthew. Not sure we'll find anything that's not text-related.
Screen Orientation
<matatk> due: 2025-10-16
<matatk> public request: w3c/
matatk: Specifise types and angles of screen orientation and a means of locking and unlocking it.
matatk: They have an a11y considerations section already. Some stuff mentioned there that immediately comes to mind.
Neha: Please add me to that, Matthew.
Dubbing and Audio description Profiles of TTML2 (DAPT)
<matatk> due: 2025-10-18
<matatk> public request: w3c/
matatk: Very well written spec. They are into accessibility considerations.
matatk: [Janina and Fredrik volunteer]
Issue tracking
WebDriver commands to enable and disable full accessibility support in browser
<matatk> tracking: w3c/
matatk: About programmatic control of browser. No way to enable or disable accessibility support from within browser. [Proceeds to summarize the issue from the previous link]
Badging API - Add Accessibility considerations section
<matatk> tracking: w3c/
matatk: a11y considerations section needed.
matatk: Will add you Jon.
Giving ::scroll-marker-group a name (and optionally text)
<matatk> tracking: w3c/
matatk: Issue wants to add label but role not possible yet. [Summarizes Paul's comment]
matatk: About pseudo element related to scroll markers group that gives it a label and semantics in CSS
matatk: Will add you, Steve.
[Range] What is the label?
<matatk> tracking: w3c/
matatk: Imagine a fieldset for ranges. Imagine range of time. This is semantically grouping those. Not sure why fieldset or nested fieldset isn't suggested.