Talking Drupal: Talking Drupal #350 – Accessibility Scanning & Testing

Drupal CMS

Today we are talking about Accessibility Scanning & Testing with Mike Gifford & Daniel Mundra.

www.talkingDrupal.com/350

Topics Accessibility Scanning and Testing Goals Popular tools Drupal tools Storybook VPAT OpenACR How it replaces VPAT OpenACR and Drupal Tackling Accessibility Tools to use Automation CI/CD Issues that will not be caught Resources OpenACR https://github.com/GSA/openacr https://gsa.github.io/openacr-editor/ Accessibility Scanner Editoria11y Pa11y + Axe Cypress-axe Open source & accessibility (including list of open source tools) Site improve Purple hats WCAG-EM Fable tech labs Least accessible site Spoke truing tool GAAD Pledge Guests

Mike Gifford – mgifford.medium.com @mgifford Daniel Mundra – danielmundra.com

Hosts

Nic Laflin – www.nLighteneddevelopment.com @nicxvan John Picozzi – www.epam.com @johnpicozzi Mike Herchel – herchel.com@mikeherchel

MOTW

Editoria11y Editoria11y (“editorial accessibility”) is a user-friendly checker that addresses three critical needs for content authors

It runs automatically. Modern spellcheck works so well because it is always running; put spellcheck behind a button and few users remember to run it! It runs in context. Views, Layout Builder, Media and all the other modules Drupal uses to assemble a complex page means checkers that run on individual fields cannot “see” errors that appear on render. It focuses exclusively on content issues: things page editors can easily understand and easily fix. Editoria11y is meant to supplement, not replace, testing with comprehensive tools and real assistive devices.