WAS Credential Content Outline

Web Accessibility : Form Labels, Instructions, and Validation

Need help to conduct accessibility audits to improve form and web application usability?

Web Accessibility, Part 7: Form Labels, Instructions, and Validation

53 Input Purposes for User Interface Components

Semantic Markup for input fields reminds me of microformats

Input Purposes for User Interface Components

This section contains a listing of common user interface component input purposes. The terms below are not keywords that must be used, but instead represent purposes that must be captured in the taxonomy adopted by a webpage. Where applicable, authors mark up controls with the chosen taxonomy to indicate the semantic purpose. Reminds me of microformats.

Accessible Rich Internet Applications (WAI-ARIA) 1.1

Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. T...

WAI-ARIA Overview

Currently certain functionality used in Web sites is not available to some users with disabilities, especially people who rely on screen readers and people who cannot use a mouse. WAI-ARIA addresses these accessibility challenges, for example, by defining new ways for functionality to be provided to assistive technology. With WAI-ARIA, developers can make advanced Web applications accessible and usable to people with disabilities.

WAI-ARIA Authoring Practices 1.1

This document provides readers with an understanding of how to use WAI-ARIA 1.1 [WAI-ARIA] to create accessible rich internet applications. It describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. This document is directed primarily to Web application developers, but the guidance is also useful for user agent and assistive technology developers.

Authoring Tool Accessibility Guidelines (ATAG) 2.0

How to Meet WCAG (Quickref Reference)