--- # Web Accessibility Workshop Pablo Tamarit 2024-08-12 --- **What do these 3 things have in common?** * Security * Performance * Accessibility --- They are **non-functional software requirements** * <!-- .element: class="fragment" data-fragment-index="1" --> Not always directly perceivable * <!-- .element: class="fragment" data-fragment-index="2" --> Often forgotten in initial design/implementation * <!-- .element: class="fragment" data-fragment-index="3" --> Not as easy to fix afterward --- ## Not as easy to fix afterward  <small>[Source](https://9gag.com/gag/5182500)</small> --- ### Are we building inaccessible websites on purpose?  <small>[Source](https://en.wikipedia.org/wiki/File:Disaster_Girl.jpg)</small> --- ### Are we too inexperienced on the topic?  <small>[Source](https://theoffice.fandom.com/wiki/Michael_Scott?file=YoungMichaelScott.jpg)</small> --- ### Are we a bit scared of web accessibility?  <small>[Source](https://knowyourmeme.com/memes/awkward-look-monkey-puppet)</small> --- ## Low hanging fruits > 96.4% of all errors detected fall into [...] six categories. These most common errors have been the same for the last 5 years. **Addressing just these few types of issues would significantly improve accessibility across the web.** — [The WebAIM Million 2024 accessibility report](https://webaim.org/projects/million/#errors) --- # [Workshop time](https://web-accessibility-workshop.web.cern.ch/) ---  <small>[Source](https://devblogs.microsoft.com/premier-developer/microsoft-inclusive-design/)</small> --- **Accessibility:<br>essential for some,<br>useful for all.** ---