Meeting minutes
Continued Capabilities Reorganization Discussion (Figjam)
Lionel_Wolberger: We did the manual work of compying out the FigmaJam stickies, and translating them into markdown text
Lionel_Wolberger: We did the manual work to copy the Figjam stickies and create a TOC from them
… we preserved as best as possible the semantic heading order that was strongly implied by the visual grouping
Lionel_Wolberger: Perhaps I can render locally and screen share so we can discuss ...
[we're walking through our TOC and tweaking]
janina: Perhaps 'accessible interactivity?'
Jason: In looking at interaction, there is a difference between content and apps
… Automation tends to focus on the aspects of the content
… accessibility automation modifies these types of semantics
… On the other hand, accessibility automation rarely modifies the interactions themselves, which might be coded in React, Angular, etc
jason: Suggests two H1's -- Content & Presentation; Accessible Interaction
Lionel_Wolberger: It is a classic computer science architecture that application and presentation are distinguished.
Lionel_Wolberger: We started wrangling with headers: they need representing as a top level.
Lionel_Wolberger: ... are they presentation? Or are the functional?
… They resemble links
Jason: Disagree. They are not like links as they are not interactive in that way
Lionel_Wolberger: I meant, screen readers offer navigation by headers, links, buttons...
janina: We are out of time, let's pick this up next time.