Meeting minutes
<janina> Date 28 Jan 2026
<janina> Date 28 Jan 2026
<Mike> Mike Paciello is inviting you to a scheduled Zoom meeting.
Accessibility At the Edge Meeting
<Mike> Time: Jan 28, 2026 02:30 PM Eastern Time (US and Canada)
<Mike> Every week on Wed, 110 occurrence(s)
<Mike> Changed occurrence(s):
<Mike> Feb 11, 2026 02:30 PM (updated)
<Mike> Feb 25, 2026 02:30 PM (updated)
<Mike> Mar 4, 2026 02:30 PM (updated)
<Mike> Mar 11, 2026 02:30 PM (updated)
<Mike> Apr 22, 2026 02:30 PM (updated)
<Mike> Please download and import the following iCalendar (.ics) files to your calendar system.
<Mike> Join Zoom Meeting
<Mike> https://
<Mike> Meeting agenda
<Mike> https://
<Mike> Meeting ID: 839 5240 3240
<Mike> ---
<Mike> One tap mobile
<Mike> +13092053325,,83952403240# US
<Mike> +13126266799,,83952403240# US (Chicago)
<Mike> Join instructions
Administratrivia
Mike: I will be sending an updated meeting, please use that Zoom link
Jason's Emails
Lionel_Wolberger: I read 3 ARIA post-source remedations examples from Jason's email of 3 December 2025
… In the real world, accessibility enhancements—especially ARIA attributes—are often introduced after a website is built.
… These are not theoretical patterns. Governments, Fortune-100 companies, agencies, and SaaS platforms all use “post-source accessibility layers” to retrofit ARIA without rewriting original code.
… Example 1: GOV.UK: Injecting aria-live and Fixing Conditional Reveals
… Example 2: Enterprise AEM Site (Fortune 100): Accessibility Overlay Layer
… Example 3: Agency Case Study (BakkenBæck / Phantom): ARIA Roles Added Post-Build
Mike: We will need citations.
… if this is Jason's own work, then it will not be as powerful as having evidence from a 3rd party
<Mike> https://
<Mike> I think this is an important post that we should take into consideration.