Baking In Accessibility: A Recipe for Better Compliance
Finding accessibility issues is the easy part. Fixing them, preventing them from coming back, and doing it consistently across a large portfolio of sites and technologies is considerably harder. Accessibility works best when it isn't a final check, but is baked into the tools, workflows, and components we use every day.
At UCLA Digital Technology Solutions (DTS), we've been tackling accessibility remediation across dozens of sites, multiple platforms, and years of existing content. Tools like Siteimprove help identify problems, but an audit is only the beginning.
This session explores the different layers we've used to address accessibility: Editoria11y to guide content editors, Drupal HTML filters to clean up problematic markup, end-to-end testing to catch issues in design components, and AI-assisted tools for tasks like generating alt text and remediating content at scale.
We'll share what worked, what didn't, and where human judgment is still essential. There may not be a perfect recipe for accessibility, but baking it into your content, code, and processes makes it much harder to leave out.
At UCLA Digital Technology Solutions (DTS), we've been tackling accessibility remediation across dozens of sites, multiple platforms, and years of existing content. Tools like Siteimprove help identify problems, but an audit is only the beginning.
This session explores the different layers we've used to address accessibility: Editoria11y to guide content editors, Drupal HTML filters to clean up problematic markup, end-to-end testing to catch issues in design components, and AI-assisted tools for tasks like generating alt text and remediating content at scale.
We'll share what worked, what didn't, and where human judgment is still essential. There may not be a perfect recipe for accessibility, but baking it into your content, code, and processes makes it much harder to leave out.