Accessibility is now and has been a hot topic for many years. Web projects come in all sizes as well does team support. From small startups, all the way to entrenched enterprise solutions, addressing accessibility continues to be a challenge. TBH, HTML and CSS by itself is 100% accessible. But as soon as we start to add complex layouts and interactive elements, things breakdown fast.
Of the 10 most common accessibility issues #4 jumps out at me as a complex issue wrapped up in a mosaic of issues.
Missing WAI-ARIA attributes
The Web Accessibility Initiative – Accessible Rich Internet Applications (WAI-ARIA) is a technical specification used by developers to build accessible interactive content. Interactive content includes elements like drag-and-drops, accordions, or sliders. Unfortunately, these types of interactive content interfere with users who rely on screen readers or speech instructions if they’re not implemented properly.
The web today and the web of the future is complex and it will get even more complex. Users are demanding more and more complexity as far as interactive elements and immersive experiences all at the same time, we can not leave people with disabilities behind.
It is here where we have the challenge. Stipulating that all the devs in an org will be 100% fluent in accessible code is a bar that few will set. All the documents and lunch-n-learns will not solve this either. In this talk I will go over modern strategies for how we can all ship accessibility.
Attendees of this talk will learn how a team of dedicated engineers with full knowledge of accessibility standards can set web dev teams up for success. Leveraging modern HTML tools developers can solve these issues and ship consistent experiences that can be used in any modern development framework with accessibility rules made available via a declarative API.