<aside> ⚠️

Study tasks from domain 2D and 2H are the exact same in the BoK. I have deduplicated the list already.

</aside>

• Understand the needs of users of different types of disabilities
• Identify issues for the methods, technologies or strategies used by people with disabilities
• Become familiar with the specifications (WCAG, WAI-ARIA, and ATAG), and know which Success Criteria apply to which conformance level.
• Understand the WCAG conformance requirements.
• Understand the evaluation process of the WCAG-EM methodology.
• Be able to distinguish between failures of accessibility criteria versus other bad accessibility practices that are not covered in the specifications.
• Identify Issues for Screen reader users
• Identify Issues for Users who use a keyboard or alternative input device
• Identify Issues for Users with Auditory Disabilities
• Identify Issues for Users with Low Vision
• Identify Issues for Users with Cognitive or Learning Disabilities
• Identify Issues for Touch Users
• Understand the purpose of ACT Rules.
• Know the strengths and limitations of automated testing tools.
• Differentiate between the kinds of accessibility issues that can be found with automated tools and issues that require manual testing.
• Understand how accessibility software tools can be used at various stages in the web development process (e.g., design/develop/test).
• Be familiar with the types of software tools available (site-wide scanning, server-based analysis, unit testing, integration testing, browser developer tools, browser add-ons, simulators, guided manual testing, etc.).
• Know how to use the keyboard and screen readers to navigate ARIA custom widgets.
• Be familiar with standard keystrokes for interaction with interactive elements in native HTML.
• Know how to use the browser's built in Development Tools to inspect source code.
• Understand how accessibility software tools can be used at various stages in the web development process (e.g., design/develop/test).
• Characterise and differentiate between the disciplines of Agile and Waterfall project management methodologies and compare the approaches each methodology would have for accessibility quality assurance.
• Demonstrate an understanding of the benefits of designing digital content with accessibility in mind as opposed to remediation.
• Characterise and differentiate between the disciplines of accessibility and user experience design and compare assumptions of each discipline.
• Understand how accessibility needs to be integrated into the entire product life cycle, including concept, requirements, design, prototyping, development, quality assurance (QA), user testing, support, and regression testing.
• Identify ways in which each person’s role in the product life cycle can include some aspect of accessibility.
• Know which combinations of assistive technologies work best with which browsers.
• Know how to use screen readers to navigate content via landmarks and headings, use forms, and read content, including data tables. Be aware that mechanisms often differ between desktop (mostly keyboard-based: tab and arrow keys) and mobile (often gesture-based).
• Be aware that users of AT often use their tools in very different ways. For example, while screen readers offer various navigation modes for expert users, many actual users do not know or use these modes.
• Understand the different screen reader modes for interacting with different types of page content (Windows screen reader: read/browse mode, forms mode, application mode, VoiceOver rotor, TalkBack menu).
• Be familiar with standard keystrokes for interaction with interactive elements in native HTML
• Be familiar with conventions for keyboard interaction within ARIA widgets.
• Know the limitations of your assistive technology knowledge. If you are not experienced, do not assume something is an error. It may be that you do not know how to use the assistive technology correctly. Output anomalies or gaps could indicate a partial lack of screen reader support or bugs.
• Demonstrate an understanding of user testing and compare it to accessibility testing.
• Understand the value of user testing by users with various types of disabilities.
• Consider the consequences of certain types of accessibility flaws. Some flaws are more critical than others.
• Demonstrate an understanding of the design’s usability versus accessibility and the conformance to accessibility specifications.
• Understand the value of user testing by users with a variety of types of disabilities.
• Think through the consequences of certain types of accessibility flaws. Some flaws are more damaging than others are.
• Consider the usability of the design, not just the accessibility or conformance to the specifications. For further information, go to: W3C’s Involving Users in Evaluating Web Accessibility.