Most accessibility tools tell you what is broken. Limena helps teams understand which accessibility barriers are disrupting valuable customer journeys, what those failures may be costing the business, and who owns the fix.

Ryan Short, founder of Limena, joins Chris Bryce to explain how accessibility intelligence turns a long list of WCAG failures into business priorities. Limena connects accessibility barriers to customer journeys, conversion points, organizational ownership, and continuous verification.

They discuss:

• Why accessibility work keeps losing to the product backlog
• How to connect accessibility barriers to customer journeys and revenue
• How Limena prioritizes issues by business impact
• Why closing a development ticket does not prove the barrier is gone
• Why widgets and point-in-time audits are not enough
• Where accessibility overlaps with SEO, AEO, and content quality
• How Limena fits into Git-based and composable delivery workflows

Watch the episode: YouTube

Learn more about Limena: limena.app
Connect with Ryan: LinkedIn
Learn more about Dotfusion: dotfusion.com

McGill University runs a thousand sites on its central platform, 500 more custom builds, and tracks 6,000 to 8,000 content edits a week. Joyce Peralta, Manager of Digital Communications at McGill, joins Chris Bryce to talk about the content model project addressing all of it.

The number that anchors this conversation: 61 different terms used across the university for the exact same program component. Joyce's central point is that AI does not cause content inconsistency, it amplifies inconsistency that already exists. The inaccuracy people see in AI answers comes from information presented differently across websites, not from information that is wrong.

McGill looked at building a separate content repository just for AI and turned it down, because a second repository means a second governance and synchronization problem. Joyce points to Dries Buytaert's markdown experiment, which found AI bots still hit the website itself the majority of the time.

The content model work is federated across about 50 subject matter experts from departments across the university. Rollout runs concept by concept, with a timeline Joyce estimates at five years or more. Her real point on success: this cannot be a Communications project or an IT project alone, it has to be both working as one team, with alignment across the whole institution.

Also in this one: the student usability panel that tracks how AI use among students changes year over year, why Drupal and the Drupal EDU Slack group are a real source of leverage, and what a taxonomy problem looks like at university scale.

Chapters

0:00 Welcome to Episode 48
1:05 Meet Joyce Peralta, McGill University
1:38 The velocity of change since Beyond the CMS launched
2:35 Inside McGill's web services team: comms and IT as one team
4:12 Who owns the university's content model
5:56 The vision behind McGill's content transformation
9:34 Taxonomy at scale: a thousand sites, 500 custom builds, 6,000 to 8,000 edits a week
14:33 Federated with 50 subject matter experts: the 61-term problem
16:19 AI amplifies inconsistency, it does not cause it
17:19 Why McGill rejected a separate AI-only content repository
19:10 How McGill actually uses AI in the content model project
21:35 Concept by concept: a rollout Joyce estimates at five years or more
24:02 Open source, Drupal, and the Drupal EDU Slack group
26:49 Three feedback groups, including the student usability panel
29:50 The human side of technology as AI reshapes expectations
31:32 Lessons for higher ed teams just starting this work
33:38 Where to find higher ed thought leadership
34:52 Wrap-up

Click here to watch a video of this episode.

Links
Joyce Peralta on LinkedIn
Dotfusion headless CMS services
Chris Bryce on LinkedIn

Click here to view the episode transcript.

Enterprise content supply chains run 15 to 19 steps. Joel Varty, CTO of Agility CMS, thinks AI can get that down to six, so people are the only bottlenecks left. Chris Bryce and Joel dig into the MCP server that connects Claude directly to your CMS and kills the copy-paste layer of content operations.

Joel has spent 21 years building Agility, the Canadian headless CMS behind Cineplex, Scotiabank country sites, school boards, and higher education. He explains why Agility deliberately did not build an AI agent inside the CMS, and instead meets teams inside the AI they already use: Claude, Copilot, or Gemini.

The MCP server now runs the full loop: content models for developers, a content pipeline that pushes up to 250 items per batch, and bulk publish, unpublish, and delete. Plus metadata vs JSON-LD schema in plain language, AEO, blogging from a phone with a Claude project, and content ops through a CLI for regulated industries that need sign-off and audit logs.

Click here to watch a video of this episode.

Links: Agility CMS: https://agilitycms.com Connect your AI agent to Agility: https://mcp.agilitycms.com Dotfusion (Agility Partner): https://dotfusion.com/services/agility-cms-development-agency Chris on LinkedIn: https://www.linkedin.com/in/cbryce Joel Varty on LinkedIn: https://www.linkedin.com/in/joelvarty/

Creators & Guests

• Chris Bryce - Host
• Joel Varty - Guest

Click here to view the episode transcript.