Understanding accessible procurement and applying AS EN 301 549
summary
Public procurement must require testable accessibility not vague promises citing AS EN 301 549 which now embeds WCAG 2.1 and maps criteria to hardware, web, documents and kiosks including dimensions, audio output and privacy needs. Real harms reported include qualified candidates knocked out of recruitment by inaccessible application portals, doubled captioning demand during COVID, and high remediation costs for inaccessible HR systems. Actionable steps are to include pass/fail criteria in RFQs, require vendor evidence and usability testing and follow ISO 30071.1 processes.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:38Outline
- 1:09Public procurement
- 1:46ICT Procurement
- 2:32Exclusion
- 8:50Additional Costs
- 9:49Missed Opportunities
- 11:12Status
- 12:05Functional performance
- 13:45Testable criteria for accessible ICT
- 15:32Working with AS EN 301 549
- 17:51Procurement matters
related talks
45mAccessibility beyond WCAG: EAA & EN 301 549
52mShop Accessible: Concrete Strategies for Procuring Accessible/Inaccessible Solutions
33mThe Digital Accessibility Legal Landscape – why it matters for developers
43mWhat is accessibility, and why I should care?
38mAccessibility 101-102: What every tester should know about digital accessibility
44mHow to Build Accessible Products
26mHow to become an accessibility advocate
01h 02mAccessibility - how to get the job done in a highly collaborative manner