Web Accessibility Specialist Body Of Knowledge
IAAP WEB ACCESSIBILITYSPECIALIST (WAS)Body of KnowledgeOctober 2020United in Accessibilitywww.accessibilityassociation.org
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility Professionals2020 Co-Editors:Rosemary Musachio, CPWA & Richard StreitzContributors: Dr. Paul Bohman, CPWAPina D’Intino, CPACCSamantha EvansKatie Haritos-Shea, CPWAEric Hind, CPACCDavid McDonald, CPACCRosemary Musachio, CPWARadek Pavlíček, CPWAAllison Ravenhall, CPWAPaul RayiusDamian Sian, CPWAStacy Iannaccone, CPACCEdited: September 2019 to include WCAG 2.1First Draft Edit Version v1.10 October 2020B IAAP
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility ProfessionalsTable of ContentsA.B.C.D.The Purpose of this Document . 5IAAP Exam Preparation Resources .6About the WAS Designation .6The WAS Exam Content at a Glance . 81. Creating Accessible Web Content . 111.1. Understand and interpret accessibility specifications and techniques. . 111.1.1. Overview . 111.1.2. The W3C . 111.1.3. Web Content Accessibility Guidelines (WCAG) 2.1 . 121.1.4. W3C overview of the Web Content Accessibility Guidelines . 121.1.5. WCAG Versioning . 131.1.6. Accessible Rich Internet Applications (WAI-ARIA) 1.1 . 131.1.7. Authoring Tool Accessibility Guidelines (ATAG) 2.0 . 141.1.8. Normative versus non-normative documents: . 141.2. Create accessible JavaScript, AJAX, and interactive content . 161.2.1. Support for JavaScript in accessibility APIs and assistive technologies161.2.2. Study topics related to JavaScript, AJAX, and Interactive Content. 161.3. Integrate accessibility into the quality assurance process. . 171.3.1. Study topics related to accessibility quality assurance . 181.4. Choose well-supported accessibility techniques . 181.4.1. Study topics related to accessibility support . 191.5. Create interactive controls/widgets (standard or custom) based onaccessibility best practices . 201.5.1. Study topics related to interactive controls/widgets . 201.6. Create accessible single-page applications (SPAs). . 211.6.1. Study topics related to single-page applications . 211.7. Create web content that is compatible with the strategies used by personswith disabilities to access web content. . 221.7.1. Vision . 221.7.2. Blind users . 221.7.3. Blind users with a touch screen . 231.7.4. Screen reader and browser combinations . 231.7.5. Recommended combinations to guarantee better compatibility: . 241.7.6. Screen reader considerations . 241.7.7. Low vision users . 251.7.8. Reading . 261.7.9. Cognition .271.7.10. Motor . 281.7.11. Hearing . 30IAAP C
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility Professionals2. Identify accessibility issues/problems . 312.1. Identify interoperability and compatibility issues. . 312.1.1. Study topics related to strategies used by people with disabilities . 312.1.2. Keyboard accessibility. 312.1.3. Touch device accessibility . 312.2. Determine conformance to accessibility specifications based on accessibilityissues found. . 322.2.1. Identify the success criterion for every accessibility failure. 322.2.2. Differentiate between WCAG 2.0, WCAG 2.1 . 322.2.3. Distinguish between failures (of success criteria) from optional bestpractices. 322.2.4. Study topics related to determining the level of conformance toaccessibility specifications . 332.3. Test with assistive technologies. 332.3.1. Study topics related to testing with assistive technologies . 342.4. Test for end-user impact . 352.4.1. Study topics related to testing the end-user impact. 352.5. Use accessibility testing tools effectively. 362.5.1. Automated Testing . 362.5.2. Manual Testing Tools. 372.5.3. Study topics related to accessibility testing tools: . 383. Remediate (fix) accessibility issues .393.1. Prioritize accessibility issues based on the level of severity. . 393.1.1. Study topics related to prioritizing accessibility issues based on the levelof severity . 393.2. Recommend strategies and/or techniques for fixing accessibility issues. .403.2.1. Study topics related to recommending strategies and/or techniques forfixing accessibility issues .404 IAAP
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility ProfessionalsA. The Purpose of this DocumentThis Body of Knowledge document outlines the skills expected of candidates seeking toobtain the Web Accessibility Specialist (WAS) designation. The IAAP Web AccessibilitySpecialist (WAS) exam is a technical knowledge exam.WAS knowledge includes comprehending web accessibility theory, principles, andfundamental information appropriate to an intermediate level of skills and experience.The IAAP WAS designation requires three to five years of hands-on work experience inor with a web accessibility team.Specifically, the three main purposes of this document are as follows:1. List the categories of information covered in the exam2. Present general information about each category3. List additional resources to help test takers prepare for the examThe Body of Knowledge is designed to be a starting point when studying for the WASexam. It is not intended to be an exhaustive explanation of every concept or questionon the exam. Please note that the use of this guide does not guarantee successfulcompletion of the exam.As of the WAS BOK Update from June 2020, the WAS BOK covers concepts fromWCAG 1, WCAG 2.0, and WCAG 2.1. Unless specific information is discussed about acertain version, “WCAG” will be used.If you discover any broken links, please .IAAP 5
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility ProfessionalsB. IAAP Exam Preparation ResourcesTest-takers can study resources available anywhere in preparation for the exam.IAAP lists a collection of WAS Exam resources for preparation that are both free andfor purchase. You can find these resources on the IAAP Prepare for the WAS Examwebpage.Candidates should review each section of the WAS Content Outline to determinewhere they have the most background, where they have some knowledge, and identifysections that are less familiar where they will spend most of their time studying toprepare for the WAS Exam. Candidates may also utilize the WAS BOK for more detailedreview and study preparation. All WAS Exam items are written from content contained inthis WAS BOK.C. About the WAS DesignationThe IAAP Web Accessibility Specialist credential is intended for accessibilityprofessionals who are expected to evaluate the accessibility of existing content orobjects according to published technical standards and guidelines and provide detailedremediation recommendations.The WAS exam allows individuals to certify their skillset in the specialized professionaldiscipline of web accessibility. Individuals who pass the Certified Professional inAccessibility Core Competencies (CPACC) and the Web Accessibility Specialist (WAS)exams are eligible to carry a higher-level credential called the Certified Professional inWeb Accessibility (CPWA).The WAS credential represents an ability to express technical proficiency for someonewith at least an intermediate level of experience designing, developing, implementing,and evaluating accessible web-based content, projects, and services. This exam is notintended for beginners or those without regular hands-on experience in remediating oridentifying accessibility issues in code. The WAS Exam is not intended to illustrate orassess the ability to write code. Knowledge of HTML programming alone will not providethe background necessary to achieve the WAS credential successfully. Hands-onexperience and knowledge of programmatic code elements, WCAG 2.1 standards, andcontextual implications for end users of assistive technology are all required.Web Accessibility Specialists are expected to know and use the relevant technologies,not merely be aware of them. Relevant domains for the WAS designation include: 6 IAAPcreating accessible web contentidentifying accessibility issues/problemsremediating (fixing) accessibility issues
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility Professionals Web accessibility refers to the inclusive practice of making the web usable bypeople of all abilities and disabilities.Expected results from WAS exam:The following knowledge will be demonstrated in the exam:An understanding of general ICT accessibility principles based on the needs of personswith disabilities and how they use the Internet, the tools they can use, and the creationor support of an accessible ICT ecosystemHow to create accessible digital contentGeneral principles on how to implement ICT accessibility activities/projects for personswith disabilitiesHow to contribute to the creation of an inclusive societyAdditional Information IAAP homepage General information about IAAP certification WAS Exam Content Outline WAS Frequently Asked Questions WAS Preparation ResourcesIAAP 7
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility ProfessionalsD. The WAS Exam Content at a GlanceCreating Accessible Web Solutions(40% of the exam)1. Guidelines, principles, and techniques for meeting success criteria (including WCAG,WAI-ARIA, ATAG, basic concepts, limitations of the specific guidelines, principles,and techniques, what is normative vs. non-normative; what is included in the differentlevels (A, AA, AAA))2. Basic knowledge of programming (at a conceptual level; principles and conceptsrelated to programming; the impact of specific coding practices on web solutions vs.writing specific code)3. Accessibility quality assurance (i.e., assuring the quality of accessibility throughoutthe development life cycle, difference and overlap between user experience andaccessibility)4. Accessibility supported technologies (including user’s assistive technologies andaccessibility features; a combination of assistive technologies and users agent;design decisions in choosing technologies that support accessibility; e.g., notchoosing Flash when something else has better accessibility support, differences inassistive technology supports and behaviors, differences in support for touch when ascreen reader is on vs. off)5. Standard controls vs. custom controls (e.g., using standard controls when possible, ifusing custom controls build them using WAI-ARIA best practices)6. Single-page applications (e.g., focus control, delays for AJAX-screen readercompatibility, live announcements)7. Strategies of persons with disabilities in using web solutions (e.g., navigation ofscreen reader users, headings and landmarks, coping strategies, user-preferredmethods vs. website specific methods, using keyboard vs. mouse)8 IAAP
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility ProfessionalsIdentify accessibility issues in web solutions(40% of the exam)1. Interoperability and compatibility issues (e.g., works with JAWS, Chrome, Safari,etc )2. Identifying guidelines and principles regarding issues (including WCAG, WAIARIA, ATAG, basic concepts, limitations of the specific guidelines, principles, andtechniques, what is normative vs. non-normative; what is included in different levels(A, AA, AAA))3. Testing with assistive technologies (e.g., navigation of screen reader users, headingsand landmarks, screen magnifiers, high contrast, using keyboard vs. mouse)4. Testing for end-user impact (e.g., low vision, cognitive, mobile/touch)5. Testing tools for the web (both automated and manual tools, i.e., what they areand what are their limitations, e.g., unit testing, browser-based tools, spider tools,bookmarklet, automated tools used to monitor site vs. external tools)Remediating issues in web solutions(20% of the exam)1. Level of severity and prioritization of issues (e.g., cost-benefit, legal risk, user impact,what is the problem, what to focus on first)2. Recommending strategies and/or techniques for fixing issues (i.e., the best solution,a solution that is most widely useful, feasibility of the solution, fixing vs. redesign, howto fix it)IAAP 9
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility Professionals10 IAAP
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility Professionals1. Creating Accessible Web Content1.1. Understand and interpret accessibilityspecifications and techniques.1.1.1.OverviewThis competency focuses on designing and creating web content in accordance with thefollowing W3C accessibility specifications: Web Content Accessibility Guidelines (WCAG) 2.1 Understanding WCAG 2.1 (non-normative)Techniques for WCAG 2.1 (non-normative)How to Meet WCAG 2.1 (non-normative)Accessible Rich Internet Applications (WAI-ARIA) 1.1 WCAG 2.1 (normative)WAI-ARIA 1.1 (normative)WAI-ARIA 1.1 The Roles Model (non-normative)WAI-ARIA Authoring Practices 1.1 (non-normative)Accessible name and description computation 1.1 (non-normative)Authoring Tool Accessibility Guidelines (ATAG) 2.0 ATAG 2.0 (normative)Implementing ATAG 2.0 (non-normative)1.1.2.The W3CThe W3C is an internationally recognized web standards body that identifies itsapproved technical specification standards as “W3C Recommendations” (such asHTML, CSS, etc.). The consortium has several Accessibility specifications that haveachieved W3C Recommendation status, including WCAG, ATAG, and WAI-ARIA. Otheraccessibility related W3C recommendations, such as the User Agent AccessibilityGuidelines (UAAG), are out of the scope of the IAAP WAS certification.IAAP 11
IAAP Web Accessibility Specialist (WAS)International Association of Accessibility Professionals1.1.3.Web Content Accessibility Guidelines (WCAG) 2.1The international standard, WCAG 2.1, covers a wide range of recommendations formaking Web content more accessible. Following these guidelines will make contentmore accessible to a wider range of people with disabilities, including accommodationsfor blindness and low vision, deafness and hearing loss, limited movement, speechdisabilities, photosensitivity, and combinations of these, and some accommodation forlearning disabilities and cognitive limitations; but will not address every user need forpeople with these disabilities. WCAG is device-agnostic to address the accessibilityof web content on desktops, laptops, tablets, and mobile devices. Following theseguidelines will also often make Web content more usable to users in general.Web Content Accessibility Guidelines (WCAG) is developed through the W3C processin cooperation with individuals and organizations around the world, sharing the goalto provide a single shared standard for web content accessibility that meets the needsof individuals, organizations, and governments internationally. The WCAG documentsexplain how to make web content more accessible to people with disabilities.1.1.4.W3C overview of the Web Content AccessibilityGuidelinesThe WCAG document is organized into principles, guidelines, and success criteria. Thefour POUR principles are: Perceivable: Information and user interface components must be presentableto users in ways persons with disabilities can perceive (including blindness, lowvision, deafness and hearing loss, limited movement, and cognitive limitations). Operable: User interface components and navigation must be operable(functionality from keyboard). Understandable: Information and the operation of user interface must beunderstandable. Robust: Content must be robust enough that it can be interpreted reliably by awide variety of user agents, including assistive technologies.WCAG 2.1 has 13 guidelines within these principles, while WCAG 2.0 has 12. InputModalities is the new guideline added to WCAG 2.1. This additive approach helps tomake it clear sites that conform to WCAG 2.1 also conform to WCAG 2.0.Each guideline has at least one or more success criteria. Each success criterion isassigned a level: A, AA, or AAA. A site that meets all the success criteria at level A issaid to “conform to” level A. A site that meets all the success criteria of both level Aand level AA conforms to level AA. A site that meets all the success criteria at all levelsconforms to level AAA.Most laws and policies that reference either WCAG 2.0 or WCAG 2.1 focus on12 IAAP
IAAP Web Accessibility Specialist (WAS)In
IAAP Web Accessibility Specialist (WAS) International Association of Accessibility Professionals. 1. Creating Accessible Web Content. 1.1. Understand and interpret accessibility specifications and techniques. 1.1.1. Overview. This competency focuses on designing and creating web content in accordance with the following W3C accessibility .
I. Creating Accessible Web Content A. Understand and interpret accessibility specifications and techniques. Overview This competency focuses on designing and creating web content in accordance with the following W3C accessibility specifications: Web Content Accessibility Guidelines (WCAG) 2.1 ס WCAG 2.1 (normative)
Web Accessibility @ W3C "Before and After" demonstration Web sites W3C's Web Accessibility Initiative Web Content Accessibility Guidelines 1.0 Web Content Accessibility Guidelines 2.0 Multi-stakeholder development of int'l standards Content, authoring tools, user ag
"Techniques for Web Content Accessibility Guidelines 1.0". Status of this document This is a W3C Working Draft for review by the Web Content Accessibility Guidelines Working Group and other invited parties. It should eventually supersede the current W3C Note Techniques for Web Content Accessibility Guidelines 1.0. This is a draft
Administer accessibility supports during instruction and assessment. 5. Evaluate and improve the use of accessibility supports. Intended Audience and Recommended Use The Georgia Department of Education [s Accessibility & Accommodations Manual is intended for use in administering accessibility supports for those students who need them.
DOR Document Accessibility Standards Page 2 . Accessibility Testing Accessibility testing should be conducted on all created documents and forms that will be submitted for review as well as distributed to the public. A designated person within the unit or division should ensure the documents and forms meet DOR Document Accessibility Standards.
Bluetooth Switch or Hook iOS Switch Interface with these steps. STEP 1: SET UP YOUR ACCESSIBILITY SHORTCUT The Accessibility Shortcut gives you the ability to easily turn Switch Control on or off by triple clicking the home or power button on your device. 1. Go to Settings App Accessibility Accessibility Shortcut 2. Select Switch Control
The basic goal of this paper is to answer the question to what extent Responsive Web Design has a beneficial impact on Web Accessibility and the other way around. In this context, it will also be examined to what extent Responsive Web Design strategies and best practices have a positive or negative impact on the implementation of accessibility
and hold an annual E-Safety Week. Our Citizenship Award. 4 Through discussion in all our history themes – the rule of law is a key feature. RE and citizenship/PSHEE lessons cover religious laws, commandments and practices. In RE we encourage pupils to debate and discuss the reasons for laws so that all pupils understand the importance of them for their own protection. As part of the .
