Accessibility Resources

H. Conrad Cunningham

13 April 2019

Accessibility Resources

I initially prepared this page as a handout for the Spring 2019 offering of CSci 487, Senior Project, in Computer and Information Science at the University of Mississippi.

What is Accessibility

To comply with legal expectations such as the Americans with Disabilities Act of 1990, the Rehabilitation Act of 1973, and other laws, court rulings, and international conventions, we must make our electronic documents, websites, software applications (mobile, desktop, web, etc.), video, audio, and hardware accessible to persons with a wide range of abilities and disabilities. This, of course, applies to materials for our courses, whether online or in the classroom.

As examples, consider users who have:

It is usually better to treat accessibility as a design concern from the beginning rather than an add-on feature at the end of development.

Online Resources

Web Content Accessibility Guidelines

Note: I adapted this section from a draft paper by Hao Zhou and H. Conrad Cunningham.

To clarify what is meant by accessibility in Web pages, the W3C standardized the Web Content Accessibility Guidelines (WCAG). WCAG 2.1 is organized according to thirteen technology-independent guidelines grouped according to the following four principles. Accessible documents must be [WCAG 2.1]:

  1. perceivable
  2. operable
  3. understandable
  4. robust

The guidelines are not testable, but WCAG also associates one or more testable success criteria with each each of thirteen guidelines. For a criterion to be testable, it should be possible for either a program or a human reader to determine unambiguously whether the criterion is satisfied for a specific Web page.

Using the WCAG and its success criteria, WebAIM provides the web accessibility evaluation tool WAVE to help authors and publishers develop compliant Web pages.

Perceivable

The user must be able to perceive both the content and the user interface controls. To be perceivable, an accessible document must [WCAG 2.1]:

As an example of a testable success criterion for the “provide text alternatives for any non-text content” guideline, WCAG requires any essential “non-text content that is presented to the user” to have “a text alternative that serves the equivalent purpose”. For instance, an image (i.e. HTML <img> element) conveying essential information must include an alternative (i.e. alt) text attribute.

Operable

The user must be able to operate and navigate through the user interface. To be operable, the user interface of an accessible document must [WCAG 2.1]:

As an example of a testable success criterion for the “help users navigate” guideline, WCAG requires the content to be organized using section headings arranged into a logical hierarchy (such as <h1>, <h2>, … without skipping levels.

Understandable

The user must be able to understand both the content and the user interface operation. To be understandable, the presentation of an accessible document must [WCAG 2.1]:

As an example of a testable success criterion for the “make text readable” guideline, WCAG requires that it be possible for a program to determine the default human language for each Web page. For instance, a Web page should declare the default language using the lang attribute of the page’s <html> element.

Robust

A wide variety of “user agents” (both human users and assistive technologies) must be able to interpret the content reliably. To be robust, an accessible document must [WCAG 2.1]:

As an example of a testable success criterion for this guideline, WCAG requires that a page’s markup meet the specification for the markup language. For example, all HTML elements must have start and end tags, be validly nested, and not contain any duplicate attributes. All identifiers should be unique except in circumstances where duplication is allowed.