Developers love Angular.js for its ease of development, documentation and community support. For all of its benefits, it’s easy to overlook some of the nuances that can make an application inaccessible. We’ll walk through the issues and discuss some of the finer points of Angular development.
Abstract
Developing accessible Angular.js applications is fairly easy to do once you make a few consolations. Initially the project must determine whether or not a dependency on JavaScript is acceptable as single-page applications frameworks like Angular.js do not adhere to progressive enhancement. The project must also consider the browser requirements of Angular.js which, as of version 1.3, requires IE9+. Once the initial requirement hurdles overcome, developers must understand the implications of Angular’s built-in directives, as well as those of 3rd party modules, might have on their application. During this talk, we will walk through the implications of developing in Angular.js and how developers can overcome each of them.
Keypoints
Aside from JavaScript and browser dependencies, Angular.js is not inherently inaccessible.
Angular’s ngAria module help overcome many of the issues that can arise during Angular development.
Utilize unit and functional testing to ensure that levels of accessibility are maintained.
Speaker Bio(s)
Justin Stockton
Justin began creating accessible Web applications after reading an interview with Tim Berners-Lee on how he was upset with how information on the Web was slowly becoming available to only a few. Since then he has worked on several government projects, including several versions of Disability.gov, to create Web sites that remove the barriers to information and provide people with disabilities access to the information they deserve. Justin currently resides in Boulder, CO with his family and enjoys getting up to the mountains every chance he gets.
Handout(s)
Manage Cookie Consent
We use cookies to give you the best experience and to help improve our website.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.