Brian Kardell (@briankardell) joins Erik, Justin, and Danny on the panel along with our guest Marcy Sutton (@MarcySutton) in a discussion on WAI ARIA attributes & how we should or shouldn’t be using these in the context of our applications.


Direct download: episode-106_aria-for-developers.mp3
Category:web-accessibility -- posted at: 3:15pm EST

34: & Web Accessibility

Accessibility for web applications typically gets added at the end of development cycles with different tools and low priority. This ruins the experience for many users and generally causes a huge impact on the quality of code. Because many companies are not held to supporting the standards of Section 508, Web AIM best practices, and WCAG by their clients and the impact in ROI is hard to measure it usually doesn’t happen.


Karl Groves (@karlgroves), Accessibility Consultant at The Paciello Group , creator of, & viking web developer leads by example, being an unstoppable developer community advocate for integration of accessibility over supplementation. Tenon takes a very interesting approach in that it integrates with tools we already use. Karl goes through developer resources. Tenon, and how we can make Web Accessibility a ‘first class’ citizen in our applications by making it part of our workflow and a fully integrated part of our process.



Direct download: episode-34_tenon-and-web-accessibility.mp3
Category:web-accessibility -- posted at: 9:59am EST

9: Web Accessibility for JavaScript Components and Custom Elements

In Episode 9, ‘Web Accessibility for JavaScript Components and Custom Elements’. Steve Faulkner (@stevefaulkner) from The Paciello Group and Marcy Sutton (@marcysutton) from Substantial discuss the lack of focus in product development today in building accessible applications & services. Many times web accessibility becomes an afterthought in creating a software product, having little prioritization from the business side until it is a problem. Retrofitting such an important part of our development can make web accessibility seem more like a chore with low ROI for the the time taken to implement it. It can be easy if developers know how to do it and hardly any work when it is successfully incorporated into a development process and it’s valued at the business level.


With recent advances in the past few years in JavaScript MV* frameworks like Angular, React, & Ember we are seeing the need for web accessibility more and more. Heavy JavaScript applications tend to provide little or wrong functionality for things we take for granted like keyboard access. Examples on modifying these to better attend to user experience traditionally meant lots of overhead in development by forking the framework and updating it constantly. Based on the resources developers typically find in online searches & Roles the lack of good developer examples, WAI ARIA & even simple accessibility is easy to misunderstand.


Many newer client side frameworks focus on componentization of HTML elements. Angular Directives, Ember Components, React Classes and Web Components. Componentization gives developers a chance to build much faster and easier Web Accessibility using various tools like WAI ARIA roles at a much more focused & reusable level. What is the future of Web Accessibility with these technologies? Why are we so concerned about Web Accessibility?