Meeting minutes
Issue 240, w3c/adapt#240
Lionel_Wolberger: Email sent to Russel to remind him regarding issue #240
<ghurlbot> Issue 240 Could we build symbolic annotations with existing Web standards? (DuncanMacWeb) i18n-tracker
TPAC prep (break-out, hand-out, authoring tool) - https://www.w3.org/2023/09/TPAC/
janina: A breakout on Verifiable Credentials and Accessibility. TPAC is a good place to move forward on the concept we have been discussing
… regarding Verifiable Credentials, privacy-preserving profiles, and trust brokers
… trust brokers in this space may be a great curb-cut as well
janina: Let's set a breakout regarding Matt's tool that enables authoring and rendering
janina: Suggest Adapt curate a one pager regarding AAC and its potential applications.
Lionel_Wolberger: I will draft that one pager
Roy: Deadline for signing up for breakout sessions is 3 Sept 2023
janina: Let's sign up sooner to ensure that we get good slots
Lionel_Wolberger: For the record, here is the link to TPAC breakout sessions: https://
… Note that all breakout sessions will have both a physical and a virtual component this year (like last year)
… Breakouts that are public (the default) will be open to anyone to join remotely, free of charge, without a TPAC registration.
… To propose a session: https://
A11y4Children follow-ups
Lionel_Wolberger: Last email from Maud on 20 June 2023 said
… "We will work on use cases related to AAC imagery to the Web in our next meetings."
janina: Regarding trigger warnings, David may have some updates.
Lionel_Wolberger: I pinged him.
janina: Let's touch base with a11y4children and see if they had any discussion regarding Adapt
Lionel_Wolberger: Sent
Demo page that can be printed out as a one-pager
Lionel_Wolberger: Already discussed
Track "Adapt dash" WHATWG status, https://github.com/whatwg/html/issues/9084agenda+ Gap Analysis, https://github.com/w3c/adapt/wiki/Gap-Analysis Lionel_Wolberger]
Lionel_Wolberger: Wait for update from APA chairs
janina: We need to clarify that Adapt could be released first as a browser extension
… then later in future, it would need to be built into browsers
… the use case of the embedded video is a good example
… an embedded video cannot currently accept an <H1>
Lionel_Wolberger: I believe you can have multiple H1's but there is division in the WCAG communities on whether only a single H1 is desired
janina: The main point is, we'd like video chapter headings to be in semantically nested structures
… to reduce the friction around discovery and exploration of video chapter headings
… since video has become a dominant form of multi-modeal information sharing, publication and distribution
… the web page and the media object itself should support the inherent structure of the media that it encapsulates
Lionel_Wolberger: This may be another breakout: the semantics of video chapter headings
… expecially for longer format media content such as lectures, howto videos, movies