Washington State University (WSU) is dedicated to creating an inclusive and accessible environment for everyone involved in its programs or services, including students, staff, faculty, and visitors, as outlined in the University Accessibility Statement. This commitment includes ensuring that all WSU websites and web applications are accessible to users with disabilities. Guidance on achieving this accessibility is provided by WSU policy, Washington state law, and federal regulations. To comply, developers and web content creators must adhere to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA.
Follow this step-by-step process to make your website accessible.
- Learn the Core Concepts of digital accessibility and how they address many barriers to accessing digital content.
- Download and use the Core Concepts (PDF) check sheet as a guide to creating accessible content.
Review current WSU, Washington state, and federal policies. Make sure you know the guidelines and are familiar with WCAG 2.1. These guidelines provide the necessary framework for making your web content accessible.
What are the policies?
The following policies provide the standards for creating accessible digital content and technology.
Americans with Disabilities Act Title II Regulations
This rule requires WSU to give people with disabilities an equal opportunity to benefit from all their programs, services, and activities. On April 24, 2024, the Federal Register published the Department of Justice (DOJ) final rule updating its regulations for Title II of the Americans with Disabilities Act (ADA). The final rule has specific requirements (WCAG 2.1 AA) for how to ensure that web content and mobile applications (apps) are accessible to people with disabilities.
Washington State USER-01 Accessibility Policy
This policy, formerly known as 188, establishes the expectation for state agencies that people with disabilities have access to and use of information and data and be provided access to the same services and content that is available to persons without disabilities. The technical standard for compliance with accessibility is WCAG 2.1. Review the full Accessibility Policy on the Washington Technology Solutions website.
WSU Policies
The following policies help WSU comply with Title II of the Americans with Disability Act and Washington state’s USER-01 Accessibility Policy.
BPPM 10.45 – Electronic and Information Technology (EIT) Accessibility
Washington State University (WSU, University) is committed to providing equal access to electronic and information technology (EIT) for all students, staff, faculty, and others with disabilities. This includes but is not limited to accessibility of instructional materials, documents, media, and other information provided through WSU’s telecommunication products, websites, online learning services, software systems, and information kiosks. Review the full BPPM 10.45 policy on the Office of Policies, Records, and Forms website.
WSU Accessibility Statement
Washington State University is committed to fostering an inclusive and accessible environment for all students, staff, faculty, and visitors who participate in WSU’s programs or services. WSU will ensure that students, faculty, staff, and visitors have access to university facilities, technology, and information needed to have an equal opportunity to succeed in their education, employment, and community activities.
Read the full University Accessibility Statement on the Access at WSU website.
What is WCAG 2.1?
WCAG stands for Web Content Accessibility Guidelines. The guidelines are created by the World Wide Web Consortium (W3C) and help make web content accessible to all users, including those with disabilities. They are organized under the four principles of accessibility. Below is a simplified list of the requirements organized under the principles.
Perceivable
Review WCAG 2.1 Principle 1- Perceivable
- Text Alternatives: Provide text descriptions for images and other non-text content.
- Time-based Media: Offer captions for videos and transcripts for audio.
- Adaptable: Ensure content can be presented in different ways without losing meaning.
- Distinguishable: Make it easy to see and hear content, like using good color contrast and allowing text to be resized.
Operable
Review WCAG 2.1 Principle 2 – Operable
- Keyboard Accessible: Make sure everything can be used with a keyboard.
- Enough Time: Give users enough time to read and use content.
- Seizures and Physical Reactions: Avoid content that can cause seizures, like flashing lights.
- Navigable: Help users navigate and find content, such as using clear headings and labels.
Understandable
Review WCAG 2.1 Principle 3 – Understandable
- Readable: Make text readable and understandable.
- Predictable: Ensure web pages appear and operate in predictable ways.
- Input Assistance: Help users avoid and correct mistakes, like providing clear error messages.
Robust
Review WCAG 2.1 Principle 4 – Robust
- Compatible: Ensure content works well with current and future technologies, including assistive technologies.
There are many free evaluation tools available to help you test and identify existing accessibility issues on your website. A comprehensive Web Accessibility Evaluation Tools List can be found on the W3C website.
WSU Web Design System (WSU WDS) Accessibility tool
The WSU WDS was built with accessibility in mind. If your website is in the WSU WDS, you have access to the WSUWP Gutenberg Accessibility plugin. The plugin adds an accessibility and usability checker panel to the Gutenberg editor. It checks for some errors (must be fixed), alerts (should be fixed), and warnings (may need fixed). A link is provided to review your webpage through WAVE (Web Accessibility Evaluation Tools) for you to check for additional accessibility errors and alerts.
It’s important to note that this tool only identifies approximately 25% of possible issues. It does not scan the documents on our website. You still need to manually check your website using additional tools.
Learn how to use the Accessibility & Usability Panel.
Automated Testing
Here is a list of useful tools to help you evaluate the accessibility of our website.
- WAVE (Web Accessibility Evaluation Tool: This tool provides visual feedback about the accessibility of your web content using icons and indicators on your page. It provides details about what the indicators mean, why it matters, and what to do to fix the issue. It also provides links to the Standards and Guidelines associated with the issue. The WAVE tool will identify when PDFs are present on your site, but it will not scan them for accessibility. All documents must be checked for accessibility using other tools (Adobe, Microsoft, etc.).
- Axe DevTools: A browser extension that helps developers find and fix accessibility issues directly within their development environment.
- Lighthouse: An open-source, automated tool for improving the quality of web pages. It has audits for performance, accessibility, progressive web apps, SEO, and more.
Common issues identified by automated testing include, but are not limited to:
- Missing alternative text on images or other non-text elements.
- Lack of heading structure or incorrect heading order
- Empty or invalid links
- Ambiguous or lengthy link text
Manual Testing
Test your website using a keyboard only. Make sure all interactive elements can be navigated and used with a keyboard. Interactive elements include links, buttons, and forms.
Resources for manual testing
- Review this helpful video by PopeTech to learn how to perform a keyboard accessibility test.
- Review WCAG 2.1, Guideline 2.1 – Keyboard Accessible.
Test with Assistive Technologies
Use a screen reader or other assistive technology to test your site. Keep in mind that not all assistive technologies work the same, so avoid using one technology exclusively. A comprehensive Web Accessibility Evaluation Tools List can be found on the W3C website. Some commonly used tools include:
- VoiceOver (macOS/iOS) – a built–in screen reader for Mac computers.
- NVDA (available for PCs) – a free screen-reading tool built for PCs running Windows 8.1 or later.
- Windows Narrator – a screen-reading application built into Windows 11
- JAWS (paid) – a screen reader for Windows
Identify and Evaluate all Documents on your Website
All electronic documents (PDF, Word, PPT, Excel) posted on a WSU website must be assessable and are considered electronic information technology. Consider avoiding adding documents to your website whenever possible. In most cases, a web page can replace a document.
Note: Before launching a new site in the WSU WDS, you must confirm that you have reviewed and fixed all accessibility issues on your site, including documents. Sites with identified errors will not be made public.
Here are some resources to help you make your documents and presentations accessible.
Once you identify all accessibility issues on your site, begin prioritizing what to fix and how to fix them. Make sure to download and use the Core Concepts (PDF) check sheet as a guide for fixing issues.
- Start with Errors and Alerts. Errors and Alerts are identified within WSU WDS. You can access the Accessibility & Usability dropdown panel within the page editor. Errors and Alerts are also identified using the WAVE tool. Errors and Alerts are the most critical and create significant barriers for people with disabilities.
- Review and manually check all Warnings.
- Remove all unneeded documents and have them replaced with web pages if appropriate. Documents can create barriers for all users. There are many reasons why PDFs and other documents should not be posted online including the following:
- A web page or online form is almost always a better option
- They hinder web performance in search, which is bad for Search Engine Optimization (SEO)
- Additional steps and even software may be necessary to access their content
- They are not mobile friendly
- They are harder to track in analytics unless special reports are developed
- They cause difficulty in navigation, affecting the user experience
- They are less likely to be kept up to date because it takes extra steps to update the file, export, then reupload
- If you can’t fix the issue yourself, reach out for help.
- Submit a Web Support Form
- Attend Open Lab with the CAHNRS Web team on Wednesdays at 11
- Attend Open Lab with the Central Web team on Fridays at 9:30
- Schedule a one-on-one or department/unit training with the CANNRS web team
- Perform regular checks, utilizing the provided and available accessibility tools to find and fix issues quickly.
- Attend regular training to ensure you are aware of current best practices and new/existing requirements.
- Make sure all contributors to your website follow the required guidelines.