You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Annual Review: Community Group's Work on Accessibility in Overlay Technology
Agenda:
Year-in-Review: Our Achievements
Deep Dive: Guided Reading of the Capabilities Draft Report
Getting on the Same Page: Terminology Discussion
Looking Forward: Next Steps
Details:
Year-in-Review:
We'll discuss the major milestones and progress we've made in the past year.
Deep Dive:
Highlighting Key Capabilities: Understand the capabilities present in COTS (commercial off the shelf) products. These are essential in evaluating and contrasting current technologies.
Future Potential: We'll discuss aspirational capabilities that hold promise for advancing accessibility, especially when implemented as edge technology.
Getting on the Same Page:
Let's dive deep into the vocabulary we've come across. We'll carefully explore terms like "overlay", "user agent", "assistive technology", "browser extensions", and other edge-located add-ons to ensure a shared understanding.
@JaninaSajka, note I updated the description structure slightly to ease integration in the TPAC calendar: our code gets lost when it bumps on h1, h2, or h3 headings in the description of a session for now.
Session description
Annual Review: Community Group's Work on Accessibility in Overlay Technology
Agenda:
Details:
Link to the Capabilities Draft Report
Looking forward to an insightful session. See you there!
Session goal
Provide an update and transparency.
Additional session chairs (Optional)
@lwolberg
IRC channel (Optional)
#a11yedge
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
#48, #31
Estimated number of in-person attendees
Don't know (Default)
Instructions for meeting planners (Optional)
No response
Agenda, minutes, slides, etc. (Optional)
The text was updated successfully, but these errors were encountered: