Web Accessibility

Overview

Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with websites and web applications. At Cal State Ä¢¹½ÊÓÆµ, web content must conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and CSU policy so that everyone can use campus websites, including people who rely on assistive technologies.

Why web accessibility matters

Accessibility helps ensure that the same information and services are available to everyone. It benefits people with disabilities and also many others who use features such as captions, larger text, or keyboard navigation for convenience or preference. Accessible web content makes it easier for assistive technologies to present information clearly and consistently.

For example, screen readers read the content of a web page out loud for people who are blind, have low vision, or have certain cognitive or learning disabilities. Keyboard navigation supports people who cannot use a mouse. When pages are built accessibly, these users can find, understand, and use the same content as those who do not use assistive technology.

Instructions

Star Icon
  • Start with a few basics that make the biggest difference:

    These steps will improve usability for everyone and make it easier to address more detailed accessibility checks later.

  • Before you publish or update a page, check the following:

    • Structure: The page has a clear heading structure and uses meaningful HTML markup (headings, lists, paragraphs).
    • Text alternatives: All meaningful images have appropriate alternate text or are marked as decorative.
    • Links: Link text clearly describes the destination (avoid “click here” and “read more” without context).
    • Media: Videos have captions and transcripts if needed.
    • Keyboard access: All interactive elements can be reached and activated using only the keyboard.
    • Color and contrast: Text has sufficient contrast and does not rely on color alone to convey meaning. See Color and Styling.
  • For images:

    • Provide concise, accurate alternate text for meaningful images.
    • Mark purely decorative images so they are skipped by screen readers.
    • Avoid putting important text inside images when you can use real HTML text instead.

    For audio and video:

    • Provide captions for video and transcripts for audio content.
    • Make sure captions are accurate and synchronized with the audio.
    • Follow campus captioning guidance so media is prioritized and captioned appropriately.
  • Many users navigate with a keyboard or assistive technologies such as screen readers. To support them:

    • Insert a working “skip to main content” link on every page so users can bypass repeated navigation.
    • Follow good heading structure so screen reader users can jump between sections.
    • Ensure all interactive elements (links, buttons, menus, forms) are keyboard accessible and have visible focus indicators.
    • Use meaningful link text that makes sense out of context.

    Avoid “keyboard traps,” where users can move focus into a component but not back out again without a mouse.

  • Simple checks can catch many issues before your page goes live:

    • Keyboard test: Use the Tab, Shift+Tab, and Enter/Space keys to move through the page and activate links and buttons. Make sure you can reach everything and that focus is always visible.
    • Screen reader spot-check: If you have access to a screen reader (such as NVDA on Windows or VoiceOver on macOS), try navigating the page by headings and links to see how it reads.
    • Automated check: Run the page through an automated accessibility checker to flag common issues such as missing alt text, contrast problems, and heading order.

    For more detailed guidance, see the developer quick tips on the topics listed above or contact the ATI team for an accessibility review.

  • If you would like more in-depth training on web accessibility and universal design, you can explore:

    • CSU and CSU Northridge training materials on web accessibility, document design, and universal design.
    • Guides that explain web accessibility criteria in more detail (for example, text alternatives, multimedia, navigation, and user interface requirements).

    See the “Resources” section at the bottom of this page and on the ATI home page for links to external training and reference materials.

Understanding Accessibility

Accessibility is not only about disability; it is about ability and removing barriers so that it is easy for everyone to use our information and services.

Accessible technology enables people to:

  • Acquire the same information,
  • Engage in the same interactions, and
  • Enjoy the same services,

in an equally effective and equally integrated manner, with substantially equivalent ease of use.

Principles for Information and Communication Technology (ICT)

  1. Perceivable: Information and user interface components must be presented in ways that users can perceive (for example, text alternatives for images and captions for audio and video).
  2. Operable: Users must be able to navigate and operate the interface in multiple ways (for example, by keyboard as well as mouse or touch).
  3. Understandable: Information and the operation of the interface must be clear and predictable so that people with different learning styles and cognitive abilities can use it.
  4. Robust: Content and interfaces should work reliably with current and future assistive technologies and user settings.
Digital accessibility means everyone can perceive, understand, navigate, and interact with Cal State Ä¢¹½ÊÓÆµâ€™s websites, courses, and technologies—on any device, with or without disabilities, and without barriers.

Universal Design Principles

Universal design is the concept of designing products, environments, and technologies so they can be used by as many people as possible, regardless of age, size, or ability. In the digital world, this means websites, online courses, and tools that work well for a wide range of users from the start—not just retrofitting for accessibility later.

The original seven principles of universal design are:

  • Flexibility in Use
  • Simple and Intuitive Use
  • Perceptible Information
  • Tolerance for Error
  • Low Physical Effort
  • Size and Space for Approach and Use

These principles align closely with web accessibility and the Web Content Accessibility Guidelines (WCAG). Ä¢¹½ÊÓÆµing them during design helps reduce barriers for students, employees, and visitors—with and without disabilities.

Flexibility in use means providing choices in how people access and interact with content. Different users have different needs and preferences.

  • Offer content in multiple formats (for example, text, audio, and video).
  • Allow users to adjust text size or zoom without breaking the layout.
  • Support both mouse and keyboard input, and work well on touch devices.
  • Provide alternatives for time-limited tasks whenever possible.

When websites and tools are flexible, more people can participate in ways that work best for them.

Simple and intuitive use means that people can understand how to navigate and use a site without needing special instructions or technical knowledge.

  • Use clear, consistent navigation and labels.
  • Group related information together and avoid clutter.
  • Write in plain language and define technical terms when needed.
  • Make important tasks (such as applying, logging in, or contacting you) easy to find.

Clear design helps everyone, and it is especially important for users with cognitive, learning, or language disabilities.

Perceptible information means that important content and cues can be perceived by users in more than one way.

  • Provide text alternatives for images and icons so screen readers can describe them.
  • Add captions to videos and transcripts for audio content.
  • Make sure color is not the only way information is conveyed; use text or symbols as well.
  • Ensure sufficient color contrast between text and background.

When information is available through sight, sound, and text, more people can access it.

Tolerance for error means designing pages and processes so that mistakes are less likely, and easier to recover from when they happen.

  • Provide clear error messages that explain what went wrong and how to fix it.
  • Allow people to review and confirm important information before submitting forms.
  • Avoid time limits when possible, or allow users to extend them.
  • Prevent accidental activation of destructive actions (for example, use confirmation dialogs for deletions).

Building in tolerance for error supports users who may have cognitive, motor, or attention-related disabilities—and reduces frustration for everyone.

Low physical effort means that people can use a site efficiently and comfortably, without unnecessary strain.

  • Ensure all tasks can be completed with a reasonable number of keystrokes or clicks.
  • Support full keyboard access so users do not need fine motor control with a mouse.
  • Avoid interactions that require dragging, precise movements, or holding down keys for a long time.
  • Make interactive targets (buttons, links) large enough to activate easily.

Reducing physical effort helps users with mobility impairments, repetitive strain injuries, and people using mobile devices.

Size and space for approach and use is often discussed for physical environments, but it has digital parallels as well.

  • Ensure touch targets and clickable areas are large enough and well spaced so users do not activate the wrong control.
  • Avoid layouts that require precise pointing or very small click areas.
  • Make sure content reflows properly when people zoom in or view pages on small screens.
  • Avoid horizontal scrolling where possible, especially on mobile devices.

Thoughtful layout and spacing make interfaces easier to approach and use for people with mobility or vision impairments and for anyone on a small or touch-based device.

Best Practices for Accessibility

Star Icon
  • Size and space for approach and use is often discussed for physical environments, but it has digital parallels as well.

    • Ensure touch targets and clickable areas are large enough and well spaced so users do not activate the wrong control.
    • Avoid layouts that require precise pointing or very small click areas.
    • Make sure content reflows properly when people zoom in or view pages on small screens.
    • Avoid horizontal scrolling where possible, especially on mobile devices.

    Thoughtful layout and spacing make interfaces easier to approach and use for people with mobility or vision impairments and for anyone on a small or touch-based device.

  • Alternative text (“alt text”) allows people who cannot see images to understand their purpose and content.

    • Describe the meaning of the image, not its appearance (“Students studying in a library” rather than “three people at a table”).
    • Keep alt text concise—usually a short phrase or one sentence is enough.
    • Do not repeat nearby caption text unless it is needed for context.
    • Mark purely decorative images as decorative so screen readers skip them.

    See Alternate Text for examples and more tips.

  • Color choices affect readability and whether people with low vision or color blindness can use your content.

    • Do not use color alone to convey meaning (for example, avoid instructions like “items in red are required”). Add text or symbols as well.
    • Ensure sufficient contrast between text and background. Aim for at least 4.5:1 for normal text and 3:1 for large text.
    • Keep link text visually distinct using more than color alone (for example, color plus underline or bold).
    • Avoid putting important text inside images when you can use real HTML text instead.

    For more guidance, see Color and Styling.

  • Many users navigate using only a keyboard or assistive technology, and many others use touch screens. Pages must work well without a mouse.

    • Make sure all interactive elements (links, buttons, menus, form fields) can be reached and activated using only the keyboard.
    • Provide a visible focus indicator (outline or highlight) so users can see where they are.
    • Include a working “skip to main content” link so users can bypass repeated navigation.
    • Avoid interactions that rely on hover only; ensure the same action can be performed with keyboard and touch.

    See Keyboard Accessibility and Navigation for more details.

  • Link text should clearly describe where the link goes or what it does, even when read out of context.

    • Use meaningful link text such as “Accessibility Services” instead of “click here” or “read more.”
    • Make each link text unique when linking to different destinations on the same page.
    • Avoid using full URLs as link text unless necessary; use human-readable text instead.
    • If a link opens in a new window or tab, let users know in the link text or nearby text when appropriate.

    Good link text helps screen reader users who navigate by links and benefits all users who skim pages.

How to Evaluate Accessibility Based on Four Principles

When you review a page for accessibility, use the four WCAG principles as a quick checklist. Ask yourself:

  1. Perceivable
    Can everyone see or hear the content?
    • Is the font style and size easy to read?
    • Is there enough color contrast between text and background?
    • Do images have appropriate alternative text?
    • Do audio and video have captions or transcripts?
  2. Operable
    Can everyone operate the page controls?
    • Can a user move through links and controls using only the keyboard (Tab, Shift+Tab, Enter/Space)?
    • Are menus, buttons, and forms reachable and usable without a mouse?
    • Can users pause, stop, or hide any moving or auto-updating content?
  3. Understandable
    Is the content and navigation clear?
    • Is the language plain and consistent?
    • Are headings and labels descriptive?
    • Do error messages explain what went wrong and how to fix it?
  4. Robust
    Does the page work with different devices and assistive technologies?
    • Does the page still work when users zoom in or increase text size (for example, Ctrl +)?
    • Does it behave correctly with screen readers and on mobile devices?

ATI Resources

Resources

Other Videos and Resources

Need help?

If you have questions about web accessibility or would like an accessibility review of your site, please contact the Accessible Technology Initiative (ATI) team or Accessibility Services.

Last updated: December 2025