WAS Credential Content Outline
I. Creating Accessible Web Solutions -- 40%
A. Guidelines, principles and techniques for meeting success criteria (including WCAG 2.0, WAI-ARIA, ATAG, basic concepts, limitations of the specific guidelines, principles, and techniques, what is normative vs. non-normative; what is included in different levels (A, AA, AAA))
B. Basic knowledge of programming (at a conceptual level; principles and concepts related to programming; impact of specific coding practices on web solutions vs. writing specific code)
C. Accessibility quality assurance (i.e., assuring the quality of accessibility throughout the development life cycle, difference and overlap between user experience and accessibility)
D. Accessibility supported technologies (including user's assistive technologies and accessibility features; combination of assistive technologies and users agent; design decisions in choosing technologies that support accessibility; e.g., not choosing Flash when something else has better accessibility support, differences in assistive technology supports and behaviors, differences in support for touch when screen reader is on vs. off)
E. Standard controls vs. custom controls (e.g., using standard controls when possible; if using custom controls build them using WAI-ARIA best practices)
F. Single page applications (e.g., focus control, delays for AJAX-Screen Reader compatibility, live announcements)
G. Strategies of persons with disabilities in using web solutions (e.g., navigation of screen reader users, headings and landmarks, coping strategies, user preferred methods vs. website specific methods, using keyboard vs. mouse)
II. Identify accessibility issues in web solutions -- 40%
A. Interoperability and compatibility issues
B. Identifying guidelines and principles regarding issues (including WCAG 2.0, WAI-ARIA, ATAG, basic concepts, limitations of the specific guidelines, principles, and techniques, what is normative vs. non-normative; what is included in different levels (A, AA, AAA))
C. Testing with assistive technologies (e.g., navigation of screen reader users, headings and landmarks, screen magnifiers, high contrast, using keyboard vs. mouse)
D. Testing for end-user impact (e.g., low vision, cognitive, mobile/touch)
E. Testing tools for the web (both automated and manual tools, i.e., what they are and what are their limitations; e.g., unit testing, browser based tools, spider tools, bookmarklet, automated tools used to monitor site vs. external tools)
III. Remediating issues in web solutions – 20%
A. Level of severity and prioritization of issues (e.g., cost benefit; legal risk, user impact, what is the problem, what to focus on first)
B. Recommending strategies and/or techniques for fixing issues (i.e., best solution, solution that most widely useful, feasibility of solution, fixing vs. redesign, how to fix it)
What will make our profession strong is having you as a member. Regardless of your knowledge level in accessibility, we all play a role in growing this profession. Help guide us to being a great professional association serving our diverse needs.
Through use of IAAP Connections, you can join an existing discussion or even start your own. You can also blog, upload resources to libraries and join some of our committees.
Get involved today.
Make IAAP a strong community.