If you're simultaneously boring the experts and losing the beginners, congratulations! You're in a special kind of meeting I call one size fits nobody.
During these meetings, half the room rolls their eyes during basic explanations while the other half glazes over when things get technical.
You've got legal teams who need high-level compliance overview sitting next to developers who want specific implementation details. Marketing needs to understand alt text basics while the accessibility specialist wants to discuss dynamic ARIA states.
So you end up with the worst of all worlds. Twenty minutes explaining what WCAG stands for while your senior developer checks email. Then straight into DOM manipulation discussions that leave your content team completely lost.
The questions I see in these meetings range from "what's a screen reader?" to "how do we handle live regions in single-page applications?" The accessibility expert sits there dying inside during screen reader explanations while the project manager frantically googles semantic HTML.
At the end, everyone leaves frustrated. The experts learned nothing new. The beginners understood nothing at all. Decisions got made without proper input because half the room was either bored senseless or completely confused.
Accessibility spans multiple disciplines, including legal, design, development, content and UX. And technical depth varies wildly between all these roles. So everyone needs different information to do their jobs properly.
The solution is to split meetings by technical level when possible. When you can't, use progressive disclosure. You cover basics first, then offer technical deep-dives for those who need them.
There's no need to educate everyone about everything. Give people just enough information they actually need for their role.
Not too much. Not too little. Just enough. Think of Goldilocks.