{"id":1544,"date":"2018-04-27T17:51:14","date_gmt":"2018-04-27T17:51:14","guid":{"rendered":"http:\/\/pressbooks.library.ryerson.ca\/pwaa\/?post_type=back-matter&#038;p=1544"},"modified":"2019-11-15T17:30:23","modified_gmt":"2019-11-15T17:30:23","slug":"book-recap","status":"publish","type":"back-matter","link":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/back-matter\/book-recap\/","title":{"raw":"Content Recap","rendered":"Content Recap"},"content":{"raw":"<strong>Congratulations!<\/strong> You have reached the end.\r\n\r\nThe goal of Professional Web Accessibility Auditing Made Easy has been to build your knowledge and develop your skills so you will be able to:\r\n<ul>\r\n \t<li>Audit the accessibility of websites<\/li>\r\n \t<li>Report issues and make informed recommendations<\/li>\r\n \t<li>Understand thoroughly the aspects of web accessibility<\/li>\r\n<\/ul>\r\n<h2>Unit 1: Aspects of Web Accessibility Auditing<\/h2>\r\n<strong>Unit 1 <\/strong>provided <strong>an overview<\/strong> of the many aspects of web accessibility auditing, creating a foundation that the rest of the materials here are built upon. You started assembling your <strong>Web Accessibility Auditing Toolkit<\/strong>, which would grow into a collection of tools, references, and resources to support your accessibility auditing activities.\r\n<h2>Unit 2: Introduction to WCAG 2.0<\/h2>\r\n<strong>Unit 2<\/strong> introduced you to the W3C Web Content Accessibility Guidelines (WCAG 2.0). First the <strong>four principles<\/strong> were introduced, which state that web content must be: Perceivable, Operable, Understandable, and Robust. You were also introduced to <strong>conformance levels<\/strong> and <strong>success criteria<\/strong>: Level A are criteria that <strong>must<\/strong> be addressed or barriers will be created; Level AA are criteria that <strong>should<\/strong> be addressed or content will be difficult to use for some; and Level AAA are criteria that <strong>could <\/strong>be addressed to improve usability further. With that in mind, the <strong>10 Key Guidelines<\/strong> were introduced to familiarize you with the more common accessibility issues found in web content.\r\n<h2>Unit 3: Automated Testing Tools<\/h2>\r\n<strong>Unit 3<\/strong> covered a variety of automated tools that support web auditing activities. First, the AChecker and WAVE <strong>accessibility checkers<\/strong> were compared, and a variety of other similar tools were introduced for you to explore. You were also introduced to tools for <strong>evaluating colour contrast<\/strong>, for <strong>validating HTML markup<\/strong>, and for determining the<strong> reading level\u00a0<\/strong>that visitors to a website would need to effectively understand the content.\r\n<h2>Unit 4: Manual Testing Strategies<\/h2>\r\n<strong>Unit 4<\/strong> introduced a number of <strong>manual test strategies<\/strong> that complement automated tests, and assistive technology reviews. You were introduced to the <strong>Tab Navigation<\/strong> and the <strong>Select All <\/strong>tests, useful for quickly identifying keyboard accessibility issues and other potential barriers. Tools such as <strong>Developer Tools<\/strong> were introduced as a means of <strong>examining HTML markup<\/strong> to help identify specific issues in the code of a website.\r\n<h2>Unit 5: Assistive Technology Testing<\/h2>\r\n<strong>Unit 5<\/strong> looked at <strong>Assistive Technologies<\/strong> <strong>(AT)<\/strong>, focusing on getting set up with <strong>ChromeVox <\/strong>as a tool for doing day-to-day screen reader testing. You also learned about other popular screen readers like<strong> JAWS, NVDA, and VoiceOver<\/strong>, as well as other types of AT such as <strong>magnification<\/strong> programs, <strong>voice recognition<\/strong>, and <strong>alternative input devices<\/strong>.\r\n<h2>Unit 6: User Testing<\/h2>\r\n<strong>Unit 6<\/strong> showed us aspects of web accessibility that go beyond the typical web accessibility audit, addressing considerations associated with <strong>user testing<\/strong>. User testing can provide valuable information about the <strong>usability of web content<\/strong>, though there are a number of\u00a0<strong>considerations<\/strong> that must be addressed when <strong>selecting user testers<\/strong> (such as <strong>experience with web content<\/strong> and level of <strong>assistive technology expertise<\/strong>) to ensure results are meaningful. Strategies were also introduced for developing <strong>user testing protocols<\/strong>, and <strong>observing and recording<\/strong> testers' behaviours during user testing sessions.\r\n<h2>Unit 7: Web Accessibility Audit Reporting<\/h2>\r\n<strong>Unit 7<\/strong> explored the next step in the auditing process after testing: <strong>accessibility reporting<\/strong>. Different <strong>types of audit reports<\/strong> were covered, including Informal, Template, General, and Detailed reports, each of which serve different purposes depending on the needs of the organization and the type of web content being reviewed. You took a <strong>tour of the Canvas 2012 General Review<\/strong>, which introduced the elements of an accessibility audit report.\r\n<h2>Unit 8: Other Accessibility Standards<\/h2>\r\n<strong>Unit 8<\/strong> built on what you learned about accessibility guidelines in Unit 2, introducing<strong> international standards and regulations based on WCAG 2.0<\/strong>. You were also introduced to other types of accessibility standards for <strong>authoring tools<\/strong> <strong>(ATAG 2.0)<\/strong>, <strong>user agents<\/strong> such as browsers and assistive technologies <strong>(UAAG 2.0)<\/strong>, and <strong>WAI-ARIA<\/strong>, which provides tools developers can use to create accessible custom web interactions.","rendered":"<p><strong>Congratulations!<\/strong> You have reached the end.<\/p>\n<p>The goal of Professional Web Accessibility Auditing Made Easy has been to build your knowledge and develop your skills so you will be able to:<\/p>\n<ul>\n<li>Audit the accessibility of websites<\/li>\n<li>Report issues and make informed recommendations<\/li>\n<li>Understand thoroughly the aspects of web accessibility<\/li>\n<\/ul>\n<h2>Unit 1: Aspects of Web Accessibility Auditing<\/h2>\n<p><strong>Unit 1 <\/strong>provided <strong>an overview<\/strong> of the many aspects of web accessibility auditing, creating a foundation that the rest of the materials here are built upon. You started assembling your <strong>Web Accessibility Auditing Toolkit<\/strong>, which would grow into a collection of tools, references, and resources to support your accessibility auditing activities.<\/p>\n<h2>Unit 2: Introduction to WCAG 2.0<\/h2>\n<p><strong>Unit 2<\/strong> introduced you to the W3C Web Content Accessibility Guidelines (WCAG 2.0). First the <strong>four principles<\/strong> were introduced, which state that web content must be: Perceivable, Operable, Understandable, and Robust. You were also introduced to <strong>conformance levels<\/strong> and <strong>success criteria<\/strong>: Level A are criteria that <strong>must<\/strong> be addressed or barriers will be created; Level AA are criteria that <strong>should<\/strong> be addressed or content will be difficult to use for some; and Level AAA are criteria that <strong>could <\/strong>be addressed to improve usability further. With that in mind, the <strong>10 Key Guidelines<\/strong> were introduced to familiarize you with the more common accessibility issues found in web content.<\/p>\n<h2>Unit 3: Automated Testing Tools<\/h2>\n<p><strong>Unit 3<\/strong> covered a variety of automated tools that support web auditing activities. First, the AChecker and WAVE <strong>accessibility checkers<\/strong> were compared, and a variety of other similar tools were introduced for you to explore. You were also introduced to tools for <strong>evaluating colour contrast<\/strong>, for <strong>validating HTML markup<\/strong>, and for determining the<strong> reading level\u00a0<\/strong>that visitors to a website would need to effectively understand the content.<\/p>\n<h2>Unit 4: Manual Testing Strategies<\/h2>\n<p><strong>Unit 4<\/strong> introduced a number of <strong>manual test strategies<\/strong> that complement automated tests, and assistive technology reviews. You were introduced to the <strong>Tab Navigation<\/strong> and the <strong>Select All <\/strong>tests, useful for quickly identifying keyboard accessibility issues and other potential barriers. Tools such as <strong>Developer Tools<\/strong> were introduced as a means of <strong>examining HTML markup<\/strong> to help identify specific issues in the code of a website.<\/p>\n<h2>Unit 5: Assistive Technology Testing<\/h2>\n<p><strong>Unit 5<\/strong> looked at <strong>Assistive Technologies<\/strong> <strong>(AT)<\/strong>, focusing on getting set up with <strong>ChromeVox <\/strong>as a tool for doing day-to-day screen reader testing. You also learned about other popular screen readers like<strong> JAWS, NVDA, and VoiceOver<\/strong>, as well as other types of AT such as <strong>magnification<\/strong> programs, <strong>voice recognition<\/strong>, and <strong>alternative input devices<\/strong>.<\/p>\n<h2>Unit 6: User Testing<\/h2>\n<p><strong>Unit 6<\/strong> showed us aspects of web accessibility that go beyond the typical web accessibility audit, addressing considerations associated with <strong>user testing<\/strong>. User testing can provide valuable information about the <strong>usability of web content<\/strong>, though there are a number of\u00a0<strong>considerations<\/strong> that must be addressed when <strong>selecting user testers<\/strong> (such as <strong>experience with web content<\/strong> and level of <strong>assistive technology expertise<\/strong>) to ensure results are meaningful. Strategies were also introduced for developing <strong>user testing protocols<\/strong>, and <strong>observing and recording<\/strong> testers&#8217; behaviours during user testing sessions.<\/p>\n<h2>Unit 7: Web Accessibility Audit Reporting<\/h2>\n<p><strong>Unit 7<\/strong> explored the next step in the auditing process after testing: <strong>accessibility reporting<\/strong>. Different <strong>types of audit reports<\/strong> were covered, including Informal, Template, General, and Detailed reports, each of which serve different purposes depending on the needs of the organization and the type of web content being reviewed. You took a <strong>tour of the Canvas 2012 General Review<\/strong>, which introduced the elements of an accessibility audit report.<\/p>\n<h2>Unit 8: Other Accessibility Standards<\/h2>\n<p><strong>Unit 8<\/strong> built on what you learned about accessibility guidelines in Unit 2, introducing<strong> international standards and regulations based on WCAG 2.0<\/strong>. You were also introduced to other types of accessibility standards for <strong>authoring tools<\/strong> <strong>(ATAG 2.0)<\/strong>, <strong>user agents<\/strong> such as browsers and assistive technologies <strong>(UAAG 2.0)<\/strong>, and <strong>WAI-ARIA<\/strong>, which provides tools developers can use to create accessible custom web interactions.<\/p>\n","protected":false},"author":56,"menu_order":1,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"back-matter-type":[],"contributor":[],"license":[],"class_list":["post-1544","back-matter","type-back-matter","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/back-matter\/1544","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/back-matter"}],"about":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/types\/back-matter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/users\/56"}],"version-history":[{"count":17,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/back-matter\/1544\/revisions"}],"predecessor-version":[{"id":2501,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/back-matter\/1544\/revisions\/2501"}],"metadata":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/back-matter\/1544\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/media?parent=1544"}],"wp:term":[{"taxonomy":"back-matter-type","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/back-matter-type?post=1544"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/contributor?post=1544"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/license?post=1544"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}