Mike Gifford Says Accessibility Must Be Built Into Workflows Before AI Scales Bad Patterns

Drupal Core Accessibility Maintainer Mike Gifford said sustainable accessibility depends on embedding accessibility into workflows, design systems, and organisational culture from the beginning rather than treating it as a late-stage compliance process.

Speaking with The DropTimes as part of its continuing coverage following Global Accessibility Awareness Day, Gifford, who serves as Open Standards and Practices Lead at CivicActions, discussed how accessibility programmes become more resilient when integrated into development practices from the beginning. He also warned that AI-assisted development and automated publishing systems can rapidly amplify inaccessible practices when accessibility standards are poorly maintained or inconsistently applied across teams.

When asked what changes when accessibility becomes embedded into systems and workflows instead of remaining a reactive compliance layer, Gifford said:

“When you embed accessibility right into your design systems and workflows, it stops being a stressful, late-stage compliance checklist and naturally drives overall product quality. It also makes automation a whole lot easier to scale. By handling the baseline stuff early through infrastructure, you free up the necessary time and energy to focus on what really matters: manual testing and deeply engaging with people with disabilities.”

Gifford said the accelerating pace of AI-assisted development creates growing validation challenges for organisations already struggling to maintain accessibility standards consistently across teams and products. He warned that automated systems can rapidly amplify inaccessible practices when accessibility is not maintained as an ongoing priority throughout development workflows.

“Yes, absolutely. It has never been faster to produce content and code, but it has also never been harder to validate the quality of what we are putting out. Because automated development and AI can scale bad patterns instantly, taking the time to learn how to keep accessibility a priority and actually listening to our users is more important than it has ever been.”

Gifford said accessibility programmes frequently lose momentum because responsibility often remains concentrated around a small number of individuals personally committed to the work instead of being distributed structurally across organisations.

To reduce that long-term decay, he pointed to organisational incentives and frameworks designed to distribute accessibility responsibilities more clearly across teams and workflows. Gifford referenced the World Wide Web Consortium’s Accessibility Roles and Responsibilities Mapping (ARRM) framework as an example of a system that helps organisations align accessibility Success Criteria with specific operational roles.

“The biggest issue is that so often, change and momentum come from specific individuals who just care personally about the work. When they leave, the initiative stalls. To prevent that decay, you have to shift the culture so the system sustains itself. That means setting up long-term incentives that reinforce accessibility as part of the basic definition of doing a good job, and using frameworks like the W3C’s ARRM to effectively break up and assign Success Criteria across roles.”

Gifford also connected Drupal’s early accessibility culture to the project’s longstanding alignment with open web standards and standards-based development practices. He said accessibility became a natural priority within Drupal because the community already maintained a strong foundational interest in the broader principles of the open web.

“We were simply early to the game because Drupal already had a deep, foundational interest in web standards. That early momentum compounded thanks to strong, deliberate leadership from Dries and other key contributors who made it a priority. Ultimately, it fits our core philosophy: the Open Web only works if it is accessible to everyone.”

Looking ahead, Gifford said organisations will increasingly rely on AI-assisted testing and validation tools, but argued that leadership culture will remain more important than the technology itself. According to him, teams that prioritise learning, curiosity, and continuous improvement will be better positioned to maintain accessibility standards over time.

“Accessibility is a team sport, and some form of AI is going to be a part of most teams moving forward. The organizations that succeed will be the ones building AI assets that actively help them test to best practices and flag the right questions early. More than the technology, though, it will come down to leadership. The standout organizations will be led by people with a learning mindset who prioritize curiosity over just reacting to regulations and audits.”

Yesterday’s conversation with the A11yTalks team is available here: Accessibility Contributors Discuss Continuity, Governance, and AI Ahead of GAAD.