Meeting minutes
<janina> Meeting APA Weekly Teleconference
Agenda Review & Announcements Spring, Md 20906 To Fairways North Mon, Aug 14, 2023 at 12:43:40PM EDT
janina: Invited Experts (IEs) have to be re-invited, but APA will not do that since APA has no new reg track deliverables
Charter Update https://www.w3.org/2002/09/wbs/33280/apa-wg-recharter/results
TPAC 2023 Planning - https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2023
matatk: The APA chairs are doing extensive pre-planning for TPAC
… a lot of internal APA work planned
… the Wiki page (cited) is up to date, https://
… notice a few significant specs are moving towards new versions, e.g., ARIA, ePUB
… the ARIA notification proposal should be reviewed by us, link on the wiki is https://
… since ARIA is generally focused on screen reader, APA's contribution should be to focus on non-screen reader use cases
Fredrik: Let's look to the WhatWG Notifications API as well.
… https://
Semantic headings in embedded media
janina: APA may be interested in defining semantics within an embedded object
… for example, an embedded Music XML on a page may want its own H1, H2, H3
… and not only be subject to the hierarchy of the host page
… same with embedded media, as the user agent continues to be a primary technology for access to content, media, etc
… we can imagine that the embed would even use its own user-agent
… requiring handoffs between the embed and the host
Lionel_Wolberger: When considering this embed/host issue, we will likely want to look at the decisions made regarding iFrames
RQTF Resolution re Symposium Report
janina: CTAUR (https://
… has new focus, partially due to the news that Red Hat is dropping Libre Office
… from the net, 'Red Hat's Matthias Clasen has let it be known that LibreOffice will be dropped from a future Red Hat Enterprise Linux release, and the future of its support in Fedora is unclear as well.'
… RQTF spoke with COGA regarding collaboration on Google Docs
… COGA cited that they prefer inline comments to the comments-on-the-side user interface on Google Docs
… which also require their own keystrokes
… FYI, COGA finds GitHub quite challenging to use, both UI and command line
… with usability challenges that map into the API itself
… MAUR has received input from the W3C Media and Entertainment Interest Group
… the chair notes that the *AUR series (accessibility user requirements) originated with our engagement with HTML5
matatk: We see developers redoing experiences within Canvas elements
… so when people for example use a WebTV in Canvas
… the developers find themselves reinventing all the accessibility support
PaulG: It's not quite as stark as that, canvas supports HTML fallbacks which have sell known accessibility features
… WhatWG needs to solidify this and indicate that this will not be deprecated
janina: This HTML fallback needs to be documented better
PaulG: Like the JS <noscript> section
TPAC 2023 Planning - https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2023
CSS Update (Paul) https://github.com/w3c/css-a11y/issues
PaulG: There was a light/dark color contrast discussion, but mostly about what to call it, nothing directly addressing accessibility
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
<matatk> A list of comment review requests that are both pending and closed (i.e. high priority): https://
matatk: A list of comment review requests that are both pending and closed (i.e. high priority): https://
<matatk> Here's a list of actions:
<matatk> es
<matatk> (for WG and TFs - oops URL too long!)