Meetings/TPAC 2023
Meeting and Next Steps Summaries
Monday
COGA and I18N
This meeting helped us understand the work that COGA would like to do with i18n, which relates to translating the language advice in Content Usable, and proposed/exploratory similar work being doing in a WCAG 3 subgroup, to other languages.
- Minutes
- COGA and I18N
- Next steps
- TBD
- Slides
- Developing an internationalization plan for WCAG 3’s Clear Language Guidelines
Prep for inter-group meetings
Here, we discussed internally issues that formed the agenda for inter-group meetings later in the week.
- Minutes
- Prep for ARIA meeting
- Prep for EPUB meeting: expert handlers and decorative images
- Prep for EPUB meeting: interlinear text
Tuesday
Devices and Sensors: Compute Pressure API
- Minutes
- Compute Pressure API
- Next steps
- Send the draft AC section to the group
- TBD
- Agenda
- Slot
- Tuesday 1000-1100, in APA space
Internationalization
- Minutes
- Internationalization
- Next steps
- Make an interlinear text prototype
- TBD
- Agenda
- Interlinear text synchronisation for accessible user agents (we know of some obvious synchronisation issues, such as different writing directions/systems).
- i18n blue sky projects.
- [addition] COGA request for ongoing review of language guidance
- Slot
- Tuesday 1130-1200, in APA space
EO
- Minutes
- EO - Maturity Model and Adapt
- Next steps
- TBD
- Agenda
- Major messaging for Maturity Model
- Actively advertising Adapt
- Need to determine size of audience
- Slot
- Tuesday 1200-1300, in APA space
EPUB 3
- Minutes
- Next steps
- Update issues filed:
- TBD
- TBD
- TBD
- TBD
- Review guidance vs current status quo (George, RQTF)
- Get examples of questions on images from publishers (from Charles, Avnessh)
- Produce responses to those questions
- Ascertain if the guidance needs to be changed
- Matthew to document technique of focusing an element to move the SNFSP (tabindex="-1")
- Matthew found this issue that may be of interest: How to include MusicXML #1227
- Agenda
- Forthcoming projects
- Needs we have identified for markup in chapter titles.
- Interlinear publications
- Embedded media (like MusicXML)
- Multiple tracks of sign language
- Making UAs better UAs
- Footnotes
- Dual text tracks
- Existing work to pick up
- images that are described in surrounding text and alt="" (from George)
- Slot
- Tuesday 1415-1630, in APA space
ARIA
- Minutes
- ARIA
- Next steps
- Engage with ARIA to review the guidance (APG?) on SR announcements
- Collect COGA etc. use cases
- Agenda
- Notifications
- Proposal document
- Here's a direct link to the discussion board: ARIA Notification Proposal Discussion Points #1958
- Proposal document
- ARIA "blue sky" plans
Thursday
Web Application Security WG
- Minutes
- Here are some rough notes; this was an informal meeting. Many thanks to Mike West for his input on architectural issues:
- There is scope here for creating a namespace of well-known URLs for structural destinations on the site (wider than accessibility)
- The root of the namespace can provide the manifest
- The manifest should point to well-known URIs, not the actual URIs—for reasons of caching and accuracy over time (and ensuring updates don't break things)
- Content negotiation is appropriate
- We probably don't need parameterised URIs, because these are global ones.
- In the cases where parameterised URIs may've been used, we should consider instead links on the local page that use the @rel attribute.
- The @rel attribute could be considered too.
- Advantage: easier to implement
- Disadvantage: doesn't give the overview of destinations supported by the whole site.
- Next steps
- Write the spec!
- Run it by WebAppSec (specifically Mike, Theresa and Ricky)
- Keep EO updated
- Keep the people behind the proposal sent to EO updated
- Keep Adapt updated
- Keep a11yEdge CG updated
- Agenda
- Well-known URLs for common destinations (COGA; external proposal)
- Discovery mechanism
- Slot
- 0930-1000 on Thursday, in APA space (meeting Mike West, chair)
Tencent's work on haptics
- Minutes
- Tencent's work on haptics
- Next steps
- Investigate the Vibration API for fidelity
- Consider rebooting the CG
- TBD
- Slot
- 1130-1200 on Thursday, in APA space
- Agenda
- We will be talking with the team behind this work: "How Haptic Technology Empowers the Visually Impaired"
- There will also be a breakout session on this work, but the APA discussion will allow us more opportunity to ask questions and discuss the topic in more detail.
- For reference: the proposed breakout session.
MEIG + Timed Text
- Minutes
- MEIG + TT
- Next steps
- Start work on MAUR update
- Look into cross-cutting navigation issues (across EPUB and Media)
- TBD
- Agenda
- MEIG TPAC 2023 agenda issue
- Slot
- 1430-1630 on Thursday, in APA space
Web of Things
- Minutes
- Web of Things
- Next steps
- Use Cases
- TBD
- Agenda
- WoT agenda
- Slot
- 1730-1830, Thursday, WoT (or maybe APA) space (see status note).
Friday
WHATWG
- Minutes
- TBD—may find them via the WHATWG chat page?
- heading level start issue
- SFNSP issue
- Next steps
- Talk with CSS about using CSS speech—now done: CSS does not feel this is appropriate
- Investigate ruby for positioning symbols
- Investigate having a core set of attributes as separate attributes, which are exposed "together" in the accessibility tree for ATs (Simon Pieters)
- TBD
- Agenda
- Update on Adapt attributes.
- Pronunciation update. Alternative plans:
- From feedback from AT vendors: JSON in attributes
- Alternative: SSML as first-class citizen (no rendering needed)
- Future plans (arising from the MEIG et al conversation):
- Needs we have identified for markup in chapter titles.
- Interlinear publications
- Embedded media (like MusicXML)
- Multiple tracks of sign language
TAG
- Minutes
- TBA
- Next steps
- APA to collab on TAG accessibility checklist
- Use GitHub to talk with the TAG
- FAST checklist
- Decide if using as a second-stage checklist
- Improve along the lines already suggested, and discussed, e.g. with examples, clearer terminology
- Decide if demarcating/separating from FAST TF stuff
- Continue FAST development as planned
- APA to seek review on upcoming specs as and when needed, via GitHub
- Slot
- 1430-1500 on Friday in TAG space
CSS
- Minutes
- TBD!
- Issues discussed:
- Next steps
- Investigate focusing issues
- Read the doc on proposals for making <details> and <summary> more accessible
- TBD
- Slot
- 1700-1800 on Friday, in CSS space (latest email: 2023-08-28)
- Agenda
- Enquiry as to the status of CSS Speech
- Also any "blue sky" plans
- TBD - other issues that were discussed
- Homework
- Review specs:
- https://drafts.csswg.org/css-view-transitions-1/
- https://drafts.csswg.org/css-anchor-position-1/
- https://fantasai.inkedblade.net/style/specs/css-anchor-exploration/
Meetings with other groups to be arranged
This lists the groups (by h3) and rough planned agenda (not yet discussed with the other groups).
MNX (Music Notation) CG
Status: MNX is not meeting at TPAC, but we've been having a great discussion with them. Need to invite them to an APA call after TPAC?
Duration: 60mins
- General challenges, opportunities
- Embedding MusicXML
Internal meetings
Note: These were the plans—see above for the actual!
Horizontal review activities
- Triage accessibility comment review requests
- Sweep for accessibility-related active CGs
Review developments from CGs
- a11yEdge
- IA
- Accessibility for Children
TF time
- FAST
- Maturity
Homework for APA members
Note: This was the pre-TPAC work.
This list provides an overview of the things we need to do to prepare; each item has a link to the relevant meeting below.
- ARIA
- Read the ARIA notification proposals and discuss on APA list
- Collect use cases (e.g. from COGA)
- CSS: Read the "blue sky" specs from CSS that have been highlighted for potential accessibility considerations
- Well-known URLs
- Details TBA, pending meeting organisation
- Learning about Tencent's work on haptics
- Read the article before we talk with the team behind it
Links
- Main W3C TPAC 2023 site
- APA calendar: Monday the 11th
- APA calendar: Tuesday the 12th
- APA calendar: Thursday the 14th
- W3C calendar: Joint meeting with accessibility groups and the Web Payment Security IG on Thursday the 14th
Internal private group-apa-chairs email archive links (may be out-of-date):