Web Accessibility Standards

Ensuring web accessibility is our obligation so that everyone can fully engage with and benefit from GCUs bright past and brilliant future. Accessible sites reach a bigger and more diverse audience, are easier for everyone to use, and comply with GCU’s Accessibility policy.

Using GCU-branded themes

The standard GCU Sites (WordPress Theme called Campus Flex) Theme has been created with accessibility in mind, and accessibility continues to improve through a close collaboration of University Marketing and Communications, and Campus Technology Services. GCU departments are required to use this theme.

WCAG

Web Content Accessibility Guidelines (WCAG) 2.0 were created as part of the Web Accessibility Initiative (WAI), a working group of World Wide Web Consortium (W3C) to ensure that web content is accessible to everyone.  Section 508 of Rehabilitation Act outlines many of these requirements.

Web accessibility guidelines and standards

Web accessibility is standardized by the Web Content Accessibility Guidelines (WCAG 2.1), published by the World Wide Web Consortium (W3C). WCAG 2.1 is organized into the following four key concepts:

• Web content must be perceivable
• Web content must be operable
• Web content must be understandable
• Web content must be robust

Within each of these four concepts, WCAG 2.1 includes a variety of specific success criteria for measuring websites’ accessibility. Each of the success criteria is labeled with a level (A, AA, and AAA) that is a rough indicator of how critical the issue is.Our goal at the Grand Canyon University, as stated in the Grand Canyon University IT Accessibility Guidelines, is to work toward meeting WCAG 2.1 at Level AA. To help the GCU community to attain this goal, we have developed an IT Accessibility Checklist, designed to present WCAG principles in ways that are easy to understand and apply. Many of the WCAG principles apply to a variety of information technologies (IT), not just websites. Therefore, our checklist does as well. However, it especially applies to websites and offers a great way to learn more about web accessibility or to research specific techniques.

GO TO THE IT ACCESSIBILITY CHECKLIST

Accessibility Categories

WCAG 2.0 has many requirements that fall under four basic principles:

• Perceivable – All information and user interface must be perceivable. Make sure that your audience can access, recognize and understand content through all assistive technology.
• Operable – Some users are unable to use a mouse and rely on keyboard controls or other tools to navigate. In order to fully interact with a website, content needs to be operable no matter what accommodation tools users are employing.
• Understandable – Understandable websites use clear, concise language and offer functionality that is easy to interpret. If a user navigates around your website, the connection between the functionality and the result should be obvious.
• Robust – Robust websites work across operating systems, different browsers, and on tablet/mobile devices. Users should be able to choose their own technologies to access, read and interact with your site.

Levels of Standards

The Web Content Accessibility Guidelines 2.0 are organized into three levels of standards:

1. Level A – the most basic web accessibility features
2. Level AA – deals with the biggest and most common barriers for disabled users
3. Level AAA – the highest (and most complex) level of web accessibility

At GCU, we aim to meet many of the standards associated with A-level and AA-level accessibility. Although we strive to meet some AAA standards, not all Level-AAA guidelines are applicable to web content.

Siteimprove Digital Accessibility Metric

Siteimprove is a cloud service that enables you to systematically review your sites for accessibility. Sites are crawled on a regular basis – every five days – and reports identifying accessibility errors and how to fix them are issued to the site owner.

GCU websites are part of the everyday experience of employees, students, and community members. Given the importance of these sites, it is vital for them to be accessible for people with disabilities.

Accessible websites are designed well for everyone. All images have tags identifying their content. Videos have captions that allow people to view them in loud environments. Webpages have headings that allow for easy and efficient navigation.

GCU offers Siteimprove free of charge to help GCU web designers and departments make their sites accessible and allows us a means of setting standards. After an easy registration process, Siteimprove will crawl a website and present the designer with a list of issues to fix. Web designers can also set Siteimprove to provide regular updates showing any changes in accessibility. While Siteimprove is an automated system with limitations in what it can detect, this service makes maintaining website accessibility substantially easier.

If you are interested in using Siteimprove, please contact Campus Technology

Recommended but not required standards:

In addition to the required scores above, the following optional standards are available to further increase accessibility:

• WCAG 2.1 AAA
• WAI-ARIA

The application of design standards is what creates accessibility. Consider seeking input from people with different disabilities.

See our Siteimprove page for more information and troubleshooting

Checking a website for accessibility

You can go a long way toward assuring your website is accessible by following these simple steps:

1. Validate your HTML. If HTML is used incorrectly, assistive technology can have problems interpreting the page content, which can result in access problems for users. Use a free HTML validator to check your code, or try Siteimprove for GCU developers.
2. Test with a keyboard. Set your mouse aside and use the tab key to navigate through your web pages. You should be able to access all interactive features (e.g., menus, links, form fields, buttons, controls) and operate them by pressing Enter, space, arrow keys or other intuitive keystrokes. If you are unable to access some of your site’s features, your site is likely to have accessibility problems.
3. Use an accessibility checker. There are several free online tools that will check your web pages for accessibility.  See our Tools and resources (need to build it later) page for an annotated list.
4. Test with users. You can test your site by simply recruiting and observing users as they interact with your site. To test for accessibility, recruit users who have a variety of skill levels and characteristics, such as those listed below under the heading What Is Accessibility?
5. Ask for help. The GCU community is actively working toward the goal of full accessibility for all visitors to its websites. Since we’re all working together toward this goal, there are many in the community who are happy to help. See Help (need to build it later) for more information.

What is web accessibility?

People who use the web have a growing variety of characteristics. As web developers, we can not assume that all our users are accessing our content using the same web browser or operating system as we are, nor can we assume they’re using a traditional monitor for output, or keyboard and mouse for input. Consider these user characteristics:

• Unable to see. People who are blind use either audible output (products called screen readers that read web content using synthesized speech) or tactile output (a refreshable Braille device).
• Has dyslexia. People with learning disabilities such as dyslexia may also use audible output, along with software that highlights words or phrases as they’re read aloud using synthesized speech.
• Has low vision. People with low vision may use screen magnification software that allows them to zoom into all or a portion of the visual screen. Many others with less-than-perfect eyesight may enlarge the font on websites using standard browser functions, such as Ctrl + in Windows browsers or Command + in Mac browsers.
• Has a physical disability. People with physical disabilities that affect their use of hands may be unable to use a mouse, and instead may rely exclusively on the keyboard or use assistive technologies such as speech recognition, head pointers, mouth sticks, or eye-gaze tracking systems.
• Unable to hear. People who are deaf or hard of hearing are unable to access audio content, so video needs to be captioned and audio needs to be transcribed.
• Using a mobile device. People who are accessing the web using a compact mobile device such as a phone face accessibility barriers, just like people with disabilities do. They’re using a small screen and may need to zoom in or increase the font size, and they are likely to be using a touch interface rather than a mouse. Also, Apple’s iPhone and iPad do not support Adobe Flash.
• Limited bandwidth. People may be on slow Internet connections if they’re located in a rural area or lack the financial resources to access high-speed Internet. These users benefit from pages that load quickly (use graphics sparingly) and transcripts for video.
• Limited time. People who are very busy may have too little time to watch an entire video or audio recording, but can quickly access its content if a transcript is available.

An accessible website works for all of these users, and countless others not mentioned.

The following video, produced by W3C Web Accessibility Initiative (WAI), discusses the importance of creating websites that are accessible to all users.