Creating Accessible Web Pages Using TerminalFour

Description

This article provides instructions on how to create accessible web pages using TerminalFour at Idaho State University (ISU).

Guide Navigation

Accessibility Laws and Standards

The Internet is one of the best things that has ever happened to people with disabilities. The web offers independence and freedom unavailable through any other medium. However, the web's greatest potential for people with disabilities remains largely unrealized when barriers to access are unintentionally created.. For example, some sites can only be navigated using a mouse, and some multimedia is not captioned. 

In the United States, applicable laws include The Americans with Disabilities Act (ADA) and the Rehabilitation Act of 1973. Because public universities are state-funded institutions, they fall directly under Title II of ADA. This rule extends beyond the University homepage. It covers:

  • Academic Environments: The Learning Management System (ISU Canvas), alongside course syllabi, PDFs, recorded lectures and digital textbooks.
  • Student Portals: Class registration tools, financial aid portals, mobile apps, and housing application software.
  • Internal Systems: Procurement tools, employee human resource platforms, and internal faculty directories.
  • Third-Party Vendors: Any external technology, licensed software, or library database embedded into the university's digital ecosystem.

Failure to maintain the laws and standards exposes the university to severe penalties. The Office for Civil Rights (OCR) under the U.S. Department of Education actively investigates student and staff complaints. Non-compliance can result in forced federal mediation, costly private class-action lawsuits, or the the withholding of federal funding. The deadline for compliance is April 24, 2027. 

Accessibility requirements include:

  • Alternative text for images
  • Captioning and transcripts for multimedia
  • Navigation via keyboards
  • Logical heading structures
  • Color contrast and readability
  • Accessible document formatting (PDFs, Word docs, PowerPoints, etc.)

Principles of Accessible Web Design

Provide Alternative Text

  • Alternative text provides a textual alternative to non-text content in web pages. It is especially helpful for people relying on screen reader technology to have the content of the website read to them. See CMS - TerminalFour Training: Image Description for more information.

Create Logical Document Structure

  • Headings, lists, and other structural elements provide meaning and structure to web pages. They can also facilitate keyboard navigation within the page. See CMS - TerminalFour Training: Headings for an explanation of headings and examples of heading hierarchy.

Provide Headers for Data Tables

  • Data tables need row and column header cells to programmatically associate them with their corresponding data cells, making it easier for screen reader users to navigate and understand the content in the table. See CMS - TerminalFour Training: Tables and Accessibility for rules and examples.

Ensure Users Can Complete and Submit all Forms

  • Every form element (text field, checkbox, dropdown list, etc.) needs a programmatifcally-associated label. Users must be able to submit the form and recover from errors.

Links that make sense out of context

  • Every link should make sense when read by itself. Certain phrases like "click here" and "more" must be avoided. See CMS - TerminalFour Training: Writing Link Text for rules and explanations.

Caption and/or provide transcripts for all multimedia

  • Videos must have captions and audio files must have a transcript.

Ensure accessibility of PDF, Word, PowerPoint and other non-HTML content.

Allow users to skip repetitive elements on the page

  • Each web page should provide a method to skip navigation or other elements that repeat on every page. This is usually accomplished by providing a "Skip to Main Content" or "Skip Navigation" link at the top of each page.

Do not rely on color alone to convey meaning

  • Color can enhance comprehension but cannot alone convey meaning. Certain combinations of ISU official colors do meet accessibility standards for color blindness  or oether visual impairments. See CMS - TerminalFour Training: Colors and web accessibility for official colors.

Ensure that content is clearly written and easy to read

  • Write clearly, use clear fonts, and use headings and lists logically.

Make JavaScript accessible

  • Ensure that JavaScript event handlers are device independent (e.g., they do not require the use of a mouse). Event handlers are triggered by a browser or user event such as when the page loads, when the user clicks the mouse or a keyboard key.

Web Content Accessibility Guidelines (WCAG)

WCAG provides an international set of guidelines. They are developed by the Worldwide Web Consortium (W3C), the governing body of the web. These guidelines, the basis of most web accessibility laws in the world, are based on four principles:

  • Perceivable: Content is available to the senses (vision and hearing primarily) either through the browser or through assistive technologies (e.g. screen readers, screen enlargers, etc.)
  • Operable: Users can interact with all controls and interactive elements using either the mouse, keyboard, or an assistive device.
  • Understandable: Content is clear and limits confusion and ambiguity.
  • Robust: A wide range of technologies (including old and new user agents and assistive technologies) can access the content.

For more information see, WebAIM: Constructing a POUR Website and WebAIM: Web Content Accessibility Guidelines.

Tools for Checking Accessibility

↑ Back to Top

Additional Resources

Print Article