Meeting minutes
<shawn> ( kudos for Lounge improvements also go to Ken F https://
Agenda Review & Announcements
FAST demo
<shawn> [ screen sharing does not work well for Shawn. hopefully you can share the presentation separately?]
<alastairc> URL for the record: https://
<Eric_hind> matatk: FAST; update on Framework for Accessible Specification of Technologies. Currently has complex taxonomy, user needs like perception of content, functional needs like limited color perception. Issue is that there are empty sections - we need to collect advice and context. May help to think of functional by user needs as rows and columns on
<Eric_hind> a sheet.
<Eric_hind> matatk: Looking for advice on what the spec needs to provide, what the author/content creator needs to make, and the user agent and Assistive Technology related to them. This can be done in GitHub and then a generated table style format might be generated- or alternatively, like the FAST document itself
<Eric_hind> matatk: Hope is that GitHub will be source of truth, then TR style document to be created from that.
FAST plans
<Eric_hind> Fredrik: Want to get as much expert knowledge as possible into these cross points. Already reaching out to the right people but any proposal of help is welcome. A coordinated matrix will be a result with the content added. This will be a dynamic, updated document - we know that we don't know everything so this will be a living document.
<Eric_hind> Fredrik: Ask is, how may we support and be supported?
<Eric_hind> Dr_Keith: Confirm that GitHub will be source of truth. Fredrik: Yes, but there will be a linear TR format - and it will be searchable.
<Eric_hind> Dr_Keith: Is this a conventional search or potentially going to an LLM or other method? Fredrik: We haven't settled on anything yet TBD. Gathering info is first priority
<Eric_hind> Chuck: Expect chairs to have discussions and give opinions.
<alastairc> AT for authoring tool or assistive tech?
<Zakim> alastairc, you wanted to comment on matrix and intersectional needs confusion
<Eric_hind> Shawn: To step up a level, regarding shared purpose, audience, etc. What are the foundational goals or research? Matatk: This will be in the document and this might be a good topic for future meeting (to settle these foundational issues)
<Eric_hind> Alastairc: Intersectional needs are mathematical or no? Matatk: Term used in mathematical approach like crosspoints.
<Eric_hind> Alastairc: In v3, doing things top down is occasionally showing gaps. What we're discussing would be positive for requirement coverage for our group
<Francis_Storr> +1 to chuck
<Eric_hind> matatk: Is there chair interest in helping out? Chuck: This would be helpful and would be best started out after CSUN
<alastairc> +1, also happy to catchup at CSUN if you are there.
<Eric_hind> Matatk: We will definitely revisit this.
<Eric_hind> matatk: Returning to APA - note that Todd is present and available.
<Eric_hind> Matatk: And welcome to Chiara too.
<Eric_hind> Matatk: Now onto Zakim 7, new on TR.
<Eric_hind> Matatk: Introductions to Chiara and Todd to group
Spec review requests
WebCodecs
Due: 2025-02-28
<Eric_hind> Matatk: Web codecs use cases are not yet finalized per issue 97 link. Two issues; looking for a11Y considerations, as well as streaming out different channel and route them to different devices.
<Eric_hind> Matatk: Asking for more use cases, looking to get this to the explainer level. Any thoughts or contributions around this kind of routing/streaming?
<Eric_hind> mike_beganyi: Existing tech related to channel splitting might be applicable to this kind of question.
<Eric_hind> David Fazio: this has the potential to be very complicated.
Next time...
Re-chartering! https://