Skip to main content Skip to main navigation Skip to footer content

Accessibility at Fresno State

Accessibility Testing

Accessibility testing helps identify barriers that prevent people with disabilities from using Fresno State websites and digital content. Effective testing combines automated tools with manual review so that common issues can be identified, verified, and prioritized for remediation.

Recommended Testing Workflow

  1. Run an automated scan with WAVE.
  2. Review broader patterns and repeated issues with PopeTech.
  3. Test the page using only a keyboard.
  4. Check headings, landmarks, links, images, forms, and tables manually.
  5. Test zoom and reflow to make sure content remains usable.
  6. Use a screen reader on key tasks and important pages.

Automated Testing

WAVE

WAVE is useful for page-level testing. It can help identify issues such as missing alternative text, color contrast concerns, empty links or buttons, and heading structure problems. It is especially helpful when reviewing a single page during content creation or troubleshooting. WebAIM recommends the WAVE browser extension for more complete testing, especially for dynamic or non-public pages.

Open WAVE

PopeTech

Fresno State uses the PopeTech accessibility platform to monitor and report accessibility issues across university websites. PopeTech helps identify common patterns, recurring issues, and areas that may require remediation.

The Web Services team runs monthly scans through PopeTech across Fresno State websites to identify accessibility issues and address common problems where possible.

If you are a site owner and would like an accessibility report for your website, please create a ticket by clicking the button below. The Web Services team can provide reports and help interpret the results.

Request an Accessibility Report (Web Services)

Important Limitation of Automated Tools

Automated tools can only detect some accessibility issues. They cannot reliably determine whether alternative text is appropriate, whether link text is meaningful, whether the reading order makes sense, or whether a complete task is usable with assistive technology. For that reason, automated scans should always be followed by manual testing.

Keyboard Testing

Keyboard testing checks whether a page can be used without a mouse. Use the Tab, Shift + Tab, Enter, Spacebar, and arrow keys to move through the page.

  • Can all links, buttons, menus, and form fields be reached by keyboard?
  • Is keyboard focus always visible?
  • Does focus move in a logical order?
  • Can dropdowns, accordions, dialogs, and other controls be opened and closed by keyboard?
  • Is there a keyboard trap anywhere on the page?
  • Does the “Skip to main content” link work properly?

What to Check on Every Page

Headings and Structure

  • Make sure the page has one clear <h1>.
  • Check that headings follow a logical order without skipping levels unnecessarily.
  • Verify that landmarks and page regions make sense.

Images and Alternative Text

  • Make sure informative images have meaningful alternative text.
  • Confirm that image links and image buttons have accessible names.

Links and Buttons

  • Link text should make sense out of context.
  • Buttons and linked icons should have clear labels.
  • Avoid empty links, empty buttons, and vague text such as “click here.”

Tables

  • Use tables only for data, not for layout.
  • Make sure header cells are identified correctly.
  • Check that table structure remains understandable when read linearly.

Color and Contrast

  • Text and interface elements should have sufficient contrast.
  • Do not rely on color alone to communicate meaning.

Media and Embedded Content

  • Videos should include accurate captions.
  • Audio content should have a transcript when needed.
  • Embedded content such as iframes, maps, and third-party tools should also be reviewed for accessibility.

Documents

  • Check linked PDFs, Word documents, and other files for accessibility.
  • Do not assume a linked document is accessible just because the web page is accessible.

Screen Reader Testing

Screen reader testing helps verify how a page is announced to users who rely on assistive technology. Even a brief review of important pages and common tasks can reveal issues that automated tools do not catch.

  • Check that the page title and heading structure are clear.
  • Verify that landmarks and regions are announced meaningfully.
  • Confirm that links and buttons have understandable names.
  • Check that form labels, instructions, and errors are announced correctly.
  • Listen for reading order problems or missing context.

When to Ask for Help

Contact the Web Services team for accessibility issues related to Fresno State websites. For broader digital accessibility concerns (documents, software, or other digital tools), contact the Office of Digital Accessibility (ODA).

When possible, include the page URL, a short description of the issue, screenshots, and notes about how the issue was found (such as WAVE, keyboard testing, or screen reader testing).

Submit a Work Order to Web Services (Website Support)

Submit Accessibility Support Request (ODA)

Additional Resources