Karl Groves

I'm glad to see BIK taking a strong stance against accessibility overlays on websites. These overlays don't make websites more accessible. They end up offering a poorer user experience and makes debugging accessibility issues more challenging for developers as they unnecessarily add an additional layer of complexity. https://lnkd.in/eTBpNErY

15

Accessibility is often treated as a final polish step, but the latest discussions at axe-con 2026 that happened last week courtesy of Deque Systems, Inc suggest a much more powerful future. I just finished a compelling session with Jesse Beach, moderated by Jeremy Rivera, CPWA. The discussion was made fully inclusive through the ASL interpretation provided by the team at WAG (Workplace Accessibility Group). The core takeaway was simple: building with AI can actually make products more accessible, provided we train the systems on the right documentation. Jesse shared a perspective that perfectly captures why this shift matters: "Adding rules to the AI system turns your accessibility requirements from things we hope developers remember, into things that are automatically enforced." Here are three frameworks that set the standard for AI-ready documentation in addition to the work Jesse has built at Meta: W3C ARIA Patterns: The foundational logic for component behavior. https://lnkd.in/gjBQtwKd U.S. Web Design System (USWDS): The gold standard for structured accessibility rules. https://lnkd.in/gkbfd938 IBM Carbon: Detailed checklists that bridge the gap between design and development. https://lnkd.in/g6jnkKAy I have also gathered a list of accessible design systems that I’ll add in the comments. If you missed the live sessions, I highly recommend trying to register for axe-con to catch the on-demand recordings of the sessions: https://lnkd.in/g7rYSQWw Do you think we are close to a future where automatic enforcement of accessibility rules becomes the industry standard for all AI-generated code? #Accessibility #A11y #AxeCon #DesignSystems #GenAI #InclusiveDesign

11

4 Comments

🧩 The Accessibility Patterns I Live By: ARIA Authoring Practices Guide (APG) If you’re serious about building inclusive web experiences, you need to be familiar with the ARIA Authoring Practices Guide (APG). This is the gold standard I follow when developing accessible components—whether it’s in Webflow, custom code, or Figma handoff. 👉 https://lnkd.in/gtBaZmAB APG isn’t just a reference doc: it’s a living playbook of tested design patterns, best practices, and working examples that show you how to: 🔷 Use ARIA roles, states, and properties correctly 🔷 Build keyboard-accessible widgets (tabs, dialogs, sliders, and more) 🔷 Apply accessible names and descriptions 🔷 Structure content using landmarks and semantic regions 🔷 Avoid common accessibility mistakes before they reach production I use APG patterns to guide every project with complex components because conformance without usability is not enough. These patterns make accessibility practical, scalable, and human-centered. 💡 If you’ve ever wondered: What’s the right ARIA role for this custom component? How do I make this modal fully keyboard navigable? Am I naming and labeling my UI in a way screen readers understand? APG is where you get answers grounded in real accessibility thinking—not just surface-level fixes. 📌 Bookmark it: https://lnkd.in/gtBaZmAB 📣 And follow me for more deep dives into APG patterns coming soon! #Accessibility #ARIA #A11y #WebAccessibility #InclusiveDesign #WCAG #UXDesign #KeyboardNavigation #ARIApatterns #WebDev #GracefulWebStudio #DesignWithGrace #DigitalInclusion

23

4 Comments

Developing an extension, bookmarklet, or any dedicated resource takes many hours of work, research and development. Unnecessary or dismissive comments without offering constructive solutions risk discouraging those working to create free tools with the intent to promote accessibility and inclusion. #Accessibility #Inclusion #A11y #TechForGood #OpenSource

9

2 Comments