We all wear a lot of hats as digital web and app professionals. Depending on the client or company you work for, you may have multiple roles and responsibilities. How can we possibly add the digital accessibility hat on top of all that? What accessible pieces should we focus on? What do we do when a project does not have a lot of time or budget to include accessibility? One way we can tackle these issues is by using an accessible component-driven approach. By thinking about inclusiveness from the start, we can get a head start on accessibility while still building the required site components.
In late 2016, I developed an open-source KSS node style guide demonstrating good accessibility practices call the A11y Style Guide. The style guide comes with pre-populated accessible components that include helpful links to related tools and articles to make your site more inclusive. These components also serve as a guide for both HTML markup and CSS code, to inform designers, front-end and back-end developers at every stage of the website’s creation.
During this session, we will cover some generals about accessibility, what roles are responsible for accessibility, how to be inclusive in your design and development, then we will review some accessible patterns using the A11y Style Guide and others!