Nomensa Accessible Media Player

Initial configuration

Download the Library

The library can be downloaded directly from GitHub, and should be placed within you sites/all/libraries/nomensa_amp directory.

Providing Useful Alternative Text for Images

For screen reader users and SEO, it is important to put in alternative text for images that convey the meaning that the visual represents. In most cases this is fairly straight forward, but it is a very common source of web accessibility problems in Drupal sites.

There are a number of great resources on when and how to provide alt text for images:

Accessibility

The Drupal community has adopted an Accessibility Statement that sets goals for both the software we produce as well as websites managed by the Drupal Association. Although there are a lot of standards, the most widely adopted internationally is the World Wide Web Consortium's (W3C) Web Content Accessibility Guidelines (WCAG) 2.0 AA.

Drupal 8 Accessibility Features

More Semantic

There are many instances in Drupal 8 where we have been able provide more semantic HTML5 elements which assistive technology will be able to leverage. We have extended this further by adding WAI-ARIA landmarks, live regions, roles & properties.

Accessibility tools for JavaScript in Drupal 8

These tools are under active development in Drupal 8. This documentation page may be out of date

Announce page updates aurally

Many page updates are expressed visually through color changes and animations. In order to make page updates apparent in a non-visual way, Drupal provides the Drupal.announce JavaScript method. This method creates an aria-live element on the page. Text appended to this node is read by a screen-reading user agent.

Drupal.announce accepts a string to be read by an audio UA. You can also set a second parameter: the priority. Here are a couple examples:

Drupal.announce('Entering edit mode');
Drupal.announce('Please fill in your user name', 'assertive');
Drupal.announce('You look beautiful today.');

The two accepted priority values are polite and assertive. polite is the default.

Contributor task: Manually do accessibility testing of a patch for a Drupal issue

On this page:

To get help completing this task, see the Getting help completing your task page. The #drupal-accessibility irc channel might have people in it to chat with about coding and accessibility issues and extensions in Drupal.

Goal

From an accessibility point of view, manually test a patch (software fix) for a reported Drupal issue to verify that it resolves the issue and does not cause other regressions (new bugs). The Accessibility section of the core gates documentation page has more information.

Skills needed

Some familiarity with the module, theme, or task is helpful, but not required. You will also need to apply a patch to a test site.

Pages

Subscribe with RSS Subscribe to RSS - accessibility