So far you have been introduced to WCAG as the standard most accessibility audits will be based on. In most cases complying with WCAG accessibility requirements will be the goal. Many local accessibility requirements will be based on WCAG.  The activity this session will have you look at the accessibility requirements for your local city, state or province, or your country, and understand how, or if, those requirements are based on WCAG.

There are other accessibility standards to be aware of, that go beyond testing web content for accessibility.  There may be occasions when an evaluation needs one of these other standards. The ATAG standard will be used when evaluating authoring tools used to create content for the web. These tools might include a desktop HTML editor for creating web pages, or could be a WYSIWYG editor found in a web-based content management system (CMS), or it could be a multimedia authoring tool for arranging and editing video, among other types of authoring tools. ATAG describes what authoring tools need to provide in order to create content that complies with WCAG.

You will also be introduced to the UAAG Standard. This standard applies to technology like web browsers, media players, and assistive technologies, among others. It essentially describes how these types of tools, technically referred to as User Agents, should process content that complies with WCAG. We will touch on WAI-ARIA again, with a little more detail on how it should be used to make interactions on the Web accessible. And finally take a brief look at ISO-25751 (aka AccessForAll), used to guide the creation of content that adapts to individual learning needs. It would typically be used in educational contexts to guide and evaluate learning content that match learners' abilities, learning styles, and individual differences in the ways people learn.