Accessibility HELPS

Basic method for ensuring your content is accessible

Accessibility HELPS

The fundamentals of accessibility are consistent across different formats. While comprehensive lists like the guidelines ensure full accessibility, most people do not need to understand that level of detail. Typically, content is developed in a word processor or on a website with an accessible theme. Assuming the theme is accessible, HTML or word processor documents (e.g., Microsoft Word .docx files) have fewer considerations. When checking a document for accessibility, you can use the following acronym, HELPS. 

  • Headings
  • Explain (audio-visual content)
  • Language
  • Presentation
  • Structure

When to Use This Acronym

This acronym provides a basic understanding of common accessibility issues that content creators can resolve. It covers many criteria but not all. As your freedom to develop the look and feel of your content expands, the complexity of accessibility compliance will increase.

It is your responsibility to ensure your content fully complies with . However, we can help. Please reach out to the ATI Team for accessibility review or assistance planning projects.

How to Use This Acronym

The acronym is organized so that the most impactful practices for simple documents are at the top, while more technical issues are towards the bottom. Presentation and Structure are often resolved by templates in the 窪蹋勛圖 web environment or default settings in word processors.

Examples

  • Simple Document: For a two-page document with no visuals, your language will be concise, and presentation and structure will rely on basic document structure. Including headings for different sections is helpful. In this case, the primary way to increase accessibility is by providing Headings.
  • Document with Visuals: If you include an image or video in the above document, ensure the non-text content has a text alternative. Add alt text, closed captions, and audio descriptions as necessary. If your Language remains simple and you do not add color design or advanced structures, you only need to worry about Headings and Explain.
  • Complex Document: For a course syllabus, consider your audience and message to ensure clarity. Present steps and parallel content in a list, use simplified language, and provide definitions. Headings, Explain and Language are very important here, however unless you use advanced structures like tables, design with colors, or include text that is in images, you can likely ignore the Presentation and Structure advice.

For typical documents developed in a word processor or on the 窪蹋勛圖 Drupal template, Presentation and Structure are rarely considered due to accessible templates and design limitations. For personal domains, graphic design or PDF output, you need to consider Presentation and Structure.

Headings

Consider for: All documents

Headings provide structure and assist all readers. Ensure headings are accessible by using appropriate tags or styles:

  • Use proper tags or styles for the format.
  • Avoid pseudo-headings (text decoration instead of proper headings).
  • Use clear and concise language.
  • Use searchable keywords.
  • Use parallel syntax to help your content flow together.
  • Maintain a logical hierarchy.
  • Avoid using headings for emphasis.

Explain (Audio-visual Content)

Consider for: Any pages with media

Audio-visual content includes media like images, audio, video, and multimedia. Ensure you use the proper access method for each type:

  • Images: Use alt text for descriptions.
  • Decorative Images: Mark the image as decorative. In HTML this means using an empty string, signified by two double quotes as your alt text (). Other interfaces include a mark as decorative checkbox.
  • Audio Only: Provide transcripts.
  • Video Only: Provide text alternative.
  • Audio-Visual Content: Use closed captions and audio descriptions.

Language

Consider for: Most documents, especially those benefiting from organization or optimizing for scanning.

Language considerations for content creators include:

  • Use simple language (6th grade level for public content, 9th grade for student content).
  • Provide definitions for uncommon terms.
  • Use lists and structures to enhance understanding.
  • Make link text actionable.

Presentation

Consider for: Documents not developed using word or on a CMS and any document that uses color.

Presentation involves the use of colors and sensory characteristics:

  • Color Contrast: Meet WCAG standards (4.5:1 or 3:1 for large fonts).
  • Sensory Characteristics: Use at least two sensory characteristics to differentiate content.
  • Color for Emphasis: Avoid using color alone to convey information.
  • Font Decorations: Avoid using font decorations for emphasis.
  • Fonts: Use simple serif or sans-serif fonts; avoid long passages of script or embellished fonts.

Structure

Consider for: Documents with tables or non-standard layouts such as columns or accordions. Also consider for all content outside a CMS.

Proper structure utilization includes:

  • Use tables only for data with headers.
  • Implement accessible columns.
  • Use accordions logically.
  • Ensure forms and semantic HTML meet accessibility requirements.