ADA Web Accessibility

Like UNF students, the web is full of potential. In order to make the most of that potential we aim to ensure that the web is accessible to individuals with disabilities. Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web as well. A key principle of Web accessibility is designing Web sites and software that are flexible to meet different user needs, preferences, and situations. Web accessibility is essential for people with disabilities and useful for all. Learn about the impact of accessibility and the benefits for everyone in a variety of situations by watching this video on web accessibility perspectives


A hand reaches toward a wide array of technologies.

 

Our Standard & Goal: WCAG 2.0 level AA Compliance

Introduction to WCAG 2.0

The Web Content Accessibility Guidelines (WCAG) were developed by the World Wide Web Consortium (W3C) to provide international protocols and guidelines in order to ensure the ongoing growth of the web. For more detailed information on WCAG 2.0 visit the W3C's guide to the Web Content Accessibility Guidelines (WCAG) 2.0

WCAG 2.0 Layers of Guidance Reference

W3C has specified several layers of guidance in order to meet the varying needs of its audience, an audience that includes web designers and developers, policy makers, purchasing agents, teachers, and students.

These layers of guidance include overall principles, general guidelines, and testable success criteria. Provided below is a map of the WCAG 2.0 guideline layout:

  • Principles – At the top are four principles that provide the foundation for Web Accessibility: perceivable, operable, understandable, and robust.
    •  Guidelines – under each principle are guidelines. These provide the basic goals that authors should work toward in order to make content more accessible to users with different disabilities. Guidelines are not testable, but provide the framework and overall objectives to help authors understand success criteria.
      • Success Criteria – set to meet guidelines. For each guideline, testable success criteria are provided to allow WCAG 2.0 to be used where requirements and conformance testing are necessary, such as in design specification, purchasing, regulation, and contractual agreements. In order to meet the needs of different groups and situation, three levels of conformance are defined: A (lowest), AA, and AAA (highest). Level AA is considered the minimum standard to meet as agreed by Web Accessibility Experts and the US Department of Justice.

WCAG 2.0 Checklist of Success Criteria

The following list is a list of all of the WCAG 2.0 level AA guidelines and their success criteria. If you'd like more information, each guideline's title links to its individual W3C reference page for guidance on passing that guideline's criteria. Note that the entire web page with all its component parts must be meet all of the following guidelines, a part of a web page that is not compliant results in the entire page being non compliant.


Guideline

Summary

1.1.1 – Non-text Content  

Provide alt text for all non-text content.

 

1.2.1 – Audio-only and Video-only (Pre-recorded) 

Provide an alternative to video-only and audio-only content.

1.2.2 – Captions (Pre-recorded)  

Provide captions for videos with audio.

 

1.2.3 – Audio Description or Media Alternative (Pre-recorded)  

Videos with audio have a second alternative such as a transcript.

1.2.4 – Captions (Live)  

Live videos have captions provided.

 

1.2.5 – Audio Description (Pre-recorded)  

Users have access to audio description for video content.

1.3.1 - Info and Relationships Information, structure, and relationships conveyed on the page can be programmatically determined or are available in text.

1.3.2 - Meaningful Sequence When a list is present, that list is programmatically set into the web page.

1.3.3 – Sensory Characteristics 

Instructions for operating or understanding content do not rely on only sensory characteristics such as shape, size, visual location, or sound.


1.4.1 – Use of Color 

Don’t use presentations that rely solely on color.

 

1.4.2 – Audio Control 

Don’t play audio automatically.

 

1.4.3 – Contrast (Minimum)

Contrast ratio between text and background is at least 4.5:1.

 

1.4.4 – Resize Text 

Text can be resized to 200% without loss of content or function.

 

1.4.5 – Images of Text 

Don’t use images of text instead of text.

 

2.1.1 - Keyboard All content is operable through a keyboard interface.

2.1.2 - No Keyboard Traps Do not trap keyboard users so that they cannot navigate.

2.2.1 - Timing Adjustable Provide user controls for any time limits. 

2.2.2 – Pause, Stop, Hide 

Provide user controls for moving content.

 

2.3.1 – Three Flashes or Below 

Ensure no content flashes more than three times per second.

 

2.4.1 – Bypass Blocks

Provide a ‘Skip to Content’ link on the page.

 

2.4.2 – Page Titled 

Use clear, informative, and precise page titles.

 

2.4.3 – Focus Order

Ensure the content order of the page is logical.

 

2.4.4 – Link Purpose (In Context) 

Ensure every link’s purpose is clear from its text context.

 

2.4.5 – Multiple Ways 

Offer several ways to find pages within a website. 

 

2.4.6 – Headings and Labels 

Use headings and labels that describe topic or purpose.

 

2.4.7 – Focus Visible

Ensure keyboard focus is visible and clear with indicators.

 

3.1.1 - Language of Page  The default human language of the page is programmatically determined.

3.1.2 – Language of Parts

Inform users when the human language on a page changes.

 

3.2.1 - On Focus When a page component receives focus, it does not initiate a change of context for the user.

3.2.2 - On Input Setting changes do not change automatically without informing users that a change will occur once prompted.

3.2.3 – Consistent Navigation

Use menu navigation and format consistently throughout the web site.

 

3.2.4 – Consistent Identification

Use and identify icons and buttons consistently.

 

3.3.1 - Error Identification When an input error is automatically detected, that error is identified and described to the user in text.

3.3.2 - Labels or Instructions Labels or instructions are provided when content requires user input.

3.3.3 – Error Suggestion

Provide suggested fixes when users make input errors.

 

3.3.4- Error Prevention (Legal, Financial, Data) 

Reduce the risk of input errors for sensitive data.

4.1.1 - Parsing Ensure there are no major code errors.

4.1.2 – Name, Role, Value 

Build all page elements for accessibility.

Web Accessibility Guides

There are people available who can and will help you with web accessibility; for Questions and Comments about ADA Web Compliance contact Either:
  • ADA Compliance by phone at (904) 620-2870 or by email at rrgonz@unf.edu
  • UNF's Webmaster by email at webmaster@unf.edu.

For more perspectives and tips on web accessibility visit the following.

General Tools and Guides

Testing for Compliance

Help with Meeting WCAG 2.0 level A & AA Success Criteria

The following are guides and tutorials to help you achieve web compliance.

Alternative Text

Captions & Transcripts

 

Change of Context (On Focus)

 

Color Contrast

 

Descriptive Link Text

Flash Content

Flashing & Flickering Content

Focus Indicators & Navigation

Fonts

Forms

 Page Structure & Logical Formats

 Screen Readers

Skip Navigation Links

Tables

Time Limits & Timed Content