Designing With Purpose

Information and user interface components must be presentable to users in ways they can perceive. This means that users must be able to perceive the information being presented. User agents, like screen readers, require clearly defined HTML elements within a structured web page. The ARIA (Accessibility Rich Internet Application) Landmarks and a hierarchy of Headers should be used to define page regions and content context. The Banner, Navigation panel, Main section, and Footer are visually perceivable on a standard computer screen, but not necessarily on a screen reader device.

User interface components and navigation must be operable. This means that users must be able to operate the interface. All web page elements must be operable by a keyboard, speech input, and other non-mouse devices. Some of the Java scripts may not be keyboard accessible, and preventing non-mouse users from performing some functions. Many people do not use the mouse and rely on the keyboard to interact with the web. This requires keyboard access to all functionality, including form controls, input, and other user interface components.

Information and the operation of user interface must be understandable. This means that users must be able to understand the information as well as the operation of the user interface. Page Titles must be unique and meaningful. Links and Buttons must have concise and clearly marked text labels. Images must have descriptive alternative text. The page foreground and background ? and icons ? must have contrasting colours for low vision users. The web page must have clearly defined user instructions, and a separation of information content.

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, like browsers and assistive technologies. This means that users must be able to access the content as technologies advance. Meeting this requirement helps maximize compatibility with current and future user agents, like screen readers. In particular, it enables assistive technologies to process the content reliably, and to present or to operate it in different ways. This includes non-standard (scripted) buttons, input fields, and other controls. To deliver a desirable user experience, there must be a separation between web page design and user content. The web page may not render as expected in all browsers, and will not perform as expected in differing screen readers. A design utilizing Java Scripts and widgets may require ARIA coding to achieve a robust implementation.

Conformance to a standard means that you have satisfied the requirements of the standard. To conform to the WCAG standard, you need to satisfy the Success Criteria. In order to accommodate different situations that may require or allow greater levels of accessibility than others, WCAG has three levels of conformance: A, AA, AAA.

Equitable Use means everyone uses the same website, without a separate accessible site or an accessibility mode.

Flexibility in Use means people can operate websites using different input methods, such as touch, speech, gaze, a mouse, or a keyboard.

Simple and Intuitive Use means websites are straightforward, with clean layouts, consistent interaction, and clear information.

Perceptible Information means content is provided in text as well as visually or audibly, so that the information is accessible using different senses.

Tolerance for Error means interactions are designed to promote success and minimize risks, for example, by providing confirmations and feedback.

Low Physical Effort means people can efficiently operate websites using their preferred input device (such as a keyboard).

Size and Space for Approach and Use means the necessary tools to operate a website interface are visible and readily available.