Skip to main content

ADA Technical Video

How you can help

  • Add descriptive alt text to images
  • Remove Flash files
  • Ensure links describe their purpose, i.e no ‘Read More’ alone as the link
  • Ensure color contrast is 4.5:1 for text on background colors (testing tools for Chrome and Firefox)
  • Remove pdfs or replace them with HTML content whenever possible
  • Remove any charts/graphs that rely on color to convey meaning
  • Use ol, ul and dl tags for lists or groups of links
  • Using h1-h6 to identify headings
  • Ordering the content in a meaningful sequence (i.e start with h2, then h3, then h4, etc)
  • Do not use tables for layout
  • No auto-playing audio or video
  • No images of text
  • Ensure there are no keyboard traps
  • Remove blink tags
  • If you create a non-English page or an English page that is partially non-English, encapsulate your content with the following code:
    <div xml:lang=”es”>…</div>
    The code above assumes the content is Spanish. You can find more language codes here.
  • Using table markup to present tabular information, i.e denote table headings with <th>, table data with <td>

What we do automatically

  • Basic alt text on images
  • ARIA landmarks on sections in the themes
  • Using label elements to associate text labels with their form controls
  • Labelling for controls
  • Using grouping roles to identify related form controls
  • Positioning labels to maximize predictability of relationships
  • Use CSS to include decorative images
  • Using CSS to control visual presentation of text
  • Using CSS margin and padding rules instead of spacer images for layout design
  • Grouping related links using the nav element
  • Making the DOM order match the visual order
  • Text can be resized without assistive technology up to 200 percent without loss of content or functionality.
  • All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes
  • Hidden skip to content link
  • Providing descriptive titles for Web pages
  • Placing the interactive elements in an order that follows sequences and relationships within the content
  • Create a logical tab order through links, form controls, and objects
  • More than one way is available to locate a Web page within a set of Web pages
  • Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
  • The default human language of each Web page can be programmatically determined.
  • When any component receives focus, it does not initiate a change of context.
  • Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated
  • If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
  • Labels or instructions are provided when content requires user input.
  • In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
  • For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

What we don’t do

  • Audio descriptions on video files
  • Text descriptions on audio files
  • Convert pdfs to make them accessible
  • Providing alternative content for iframes
  • Add fieldset/legends on forms