Tom Resing

Accessibility audits help ensure your product and website are usable by everyone, not just compliant on paper. This guide explains what an accessibility audit is, when and why to conduct one, and how to run it step by step. It covers key standards, practical audit methods, common issues to watch for, and how to turn findings into meaningful improvements. If accessibility is part of your UX or product responsibility, this is a must-read. 👉 Read the full blog: https://lnkd.in/gn7jAFA2 #AccessibilityAudit #InclusiveDesign #UXResearch #UXDesign #UserExperience #UXArmy

6

This blog post from MHCLG about switching from an over-architected collection of microservices to a single monolinth is great! Sometimes simpler is better, and faster. 👏

3

So You Want to Implement AI-Driven Functional UI Testing? Read This First. If you’re considering AI-driven functional UI testing: -Start by stabilizing your environments and strategy -Don’t over-automate or blindly trust AI results -Avoid tools that can’t evolve with your application  (and also there’s an ad) https://lnkd.in/gtixwdMq

2

An Accessibility Conformance Report (ACR), more commonly referred to as a VPAT® (Voluntary Product Accessibility Template), is a report that’s typically completed by an Accessibility Professional. It’s an important document to have, and companies should understand what they are and what they are not. https://lnkd.in/e7x5nhgA #Accessibility #A11y #Process

39

1 Comment

A quick thought on makers and takers that I've been sitting on for awhile, especially given that #DrupalConVienna is this week. As it's framed, there are two sides. Yet, we are one #Drupal community. To me, that is the story of open source, especially after being in it for 17+ years. ↳ I have seen the #Drupal community grow from a handful of dreamers to a global force. ↳ I have watched as some build, code, and give their time for free. ↳ I have seen others use, benefit, and sometimes never give back. But here’s something to consider: ↳ Both makers and takers are needed. ↳ Makers of #Drupal push the limits, create new tools, and keep the engine running. #Drupalcon Vienna is a testament to that. ↳ Takers spread the word, use the tools, and show the world what’s possible. Is this is a battle? Perhaps it's a strive for balance. Here’s what I’ve learned after years in open source: 1. Makers are the heartbeat: ↪ We write code, fix bugs, and answer late-night calls for help. 2. Takers are the proof: ↪ They use what’s built, find the gaps, and show what works in the real world. 3. Both sides teach us: ↪ Makers learn what people need. Takers learn how things are made. 4. Growth comes from both: ↪ When makers and takers talk, share, and listen, the whole #Drupal community gets stronger. 5. Investment is key: ↪ Time, money, and care must flow both ways. We must invest in local #Drupal communities, their ecosystems, and in each other. 6. The microcosm matters: ↪ Every open source project is a small world. What works here can work anywhere. 7. The future is shared: ↪ The best ideas come from many hands, not just a few. I have seen projects fail when one side is missing. I have seen magic happen when both sides show up. Open source is not just about code. It’s about people. It’s about building together, using together, and growing together. If we want #Drupal — and any open source project — to thrive, we must keep investing. To me, this looks like a more robust connection with the local #Drupal communities in the U.S., like Pacific Northwest Drupal Summit, MidCamp, BADCamp, Florida DrupalCamp, Drupal Camp Chattanooga, Drupal 4 Gov, etc. Keep investing in the technology. And in each other. That’s how we get through the storm. That’s how we all win.

7

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

The 2025 Governmentwide Section 508 Assessment has been released. The results revealed that agencies earned a low governmentwide average for accessibility conformance, at 1.96 on a 5-point scale, with wide variation across agencies. The report also included clear, actionable recommendations for improvement. Three of the most notable: 🌟 Treat ICT accessibility as an integral part of agencies’ already established security, privacy, and risk management lifecycles. 🌟 Reject contract deliverables that fail to meet Section 508 requirements to ensure agencies only pay for ICT products and services that meet federal standards and contractual obligations. 🌟 Consider oversight and enforcement approaches used in cybersecurity, such as risk-based authorization to operate, continuous monitoring, and mandatory reporting. Have you read the report? What were your key takeaways? https://lnkd.in/g2ZNRetm

17

1 Comment

I have seen this problem repeatedly when talking to developers, maintainers, and accessibility practitioners: projects often lack a clear, living statement of how accessibility is handled. That gap is why I drafted ACCESSIBILITY.md guidance: https://lnkd.in/gpRZqKfS Why should projects have an ACCESSIBILITY.md? Because it makes a project’s accessibility commitments explicit, discoverable, and actionable for contributors and users. How can it help both humans and machines? For humans, it clarifies expectations, processes, and responsibilities. For machines, having a consistent, structured file enables automation, tooling, and compliance scanning to integrate accessibility into workflows rather than leave it to chance. This is a community effort. The initial draft was created with AI under my direction; I shaped the intent, structure, and editing. I want practical feedback. What’s missing? What should be clearer? What formats or examples would make this genuinely useful for real projects?

74

12 Comments

Is your design workflow feeling sluggish? The integration of generative AI, like ChatGPT, into tools like Figma isn't just hype—it's a fundamental shift in design productivity. 🧠 This marriage of language models and visual design promises to streamline early-stage ideation and iteration in powerful ways. We're moving beyond manual mockups. Here’s what this means for designers today: * **Rapid Prototyping:** Generate initial layout concepts or user flow scripts instantly based on text prompts. * **Content Population:** Instantly fill wireframes with realistic, context-aware placeholder text. * **Accessibility Checks:** Use AI to analyze designs against WCAG guidelines faster than ever before. According to recent industry analysis, AI adoption in design is expected to drastically reduce time spent on repetitive tasks ([Design Future Report](https://lnkd.in/eG8nzVze)). This frees us up for higher-level strategic thinking. Embracing these tools isn't optional; it’s necessary for staying competitive. Start experimenting with how conversational AI can augment your creative process now! What use case are you most excited about? 👇 *Source Example (Illustrative): McKinsey Global Institute research often highlights productivity gains from AI integration across professional services.*

8

W3C WAI invites you to comment on new W3C Group Note Drafts. Cognitive Accessibility Research Modules is an overview document found at https://lnkd.in/gxSEM6FM. It introduces the following modules: (1). Voice Systems and Conversational Interfaces: https://lnkd.in/gkRRBW4Z (2). Technology Assisted Indoor Navigation / Wayfinding: https://lnkd.in/gV5VfrJ7 (3). Online Safety and Wellbeing (Algorithms and Data): https://lnkd.in/gvTnbXv3 (4). Supported Decision-Making Online: https://lnkd.in/gVzWwan2 Information on related work can be found on the Cognitive Accessibility page at W3C https://lnkd.in/gDwMrEB6. Overview: These Cognitive Accessibility Research Modules are early, in-progress drafts. They cover research on accessibility for people with cognitive and learning disabilities. They address user needs, accessibility issues, directions for solutions, and areas for further research. These research documents are intended to inform W3C work. They are also useful for researchers, policy makers, developers, designers, and content creators. We welcome all input on these early drafts. We particularly seek input on what might be appropriate to add to these documents, including, other relevant research, additional user needs, and connections between research and priorities for new work in W3C groups. To comment, please open a new issue in the COGA GitHub repository. Create a separate GitHub issue for each topic, rather than commenting on multiple topics in a single issue. If it's not feasible for you to use GitHub, please email your comments to public-coga-comments@w3.org. Because this is a list email address, please put your comments in the body of the message and not as an attachment. Thanks for your help with this!

65

1 Comment

Role-playing rule books are being designed to be more experimental and unique. Here’s how they can be designed for accessibility, too. https://lnkd.in/euuqYUSA #design #accessible #tabletop #rpg

1