Our Journey to Accessibility at Adobe Workfront
summary
Adobe Workfront takes a data-driven route: focus on top 10 pages (66% traffic), fix workflows, and move from 23 of 50 success criteria to 36 of 50 in the public ACR, a 13-point improvement. A seven-person accessibility team remediates eight of the top ten pages while organization-wide steps — UX mockup reviews, SDLC audits, onboarding training, monthly accessibility guilds, eslint-plugin-jsx-a11y and axe checks — push new features to be accessible. Biggest blockers are organizational buy-in and product compromises like restoring autofocus for existing users.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:37Speaker and talk intro
- 3:52Organizational challenges of accessibility
- 5:18Backstory of Workfront
- 9:10Why should we make our apps accessible?
- 11:24How do we get buy-in from management?
- 12:32Where do we start?
- 16:05Who's going to do the work?
- 18:07Pros and cons of a separate accessibility team
- 20:51Accessibility in the software dev lifecycle
- 26:00How do we make accessibility a sustainable practice?
- 27:56How is Adobe Workfront doing?
- 30:15Lesson learned and Q&A
related talks
38mMaking technology more equitable by shifting accessibility left
53mAccessing Accessible Accessibility
24mAccessibility needs better marketing
01h 02mAccessibility - how to get the job done in a highly collaborative manner
26mHow (Not) to Fail at Accessibility
06mAccessibility
54mAccessibility by everyone (and for everyone)
09m"How to bring accessibility into your teams."