|
What is Compliance?
WCAG Summary
Since the mid-90s, the Department of Justice (DOJ) has applied the Americans with Disabilities Act (ADA) to “websites of covered entities”. At the time, there were many organizations publishing guidelines for digital accessibility. Over time, however, the Worldwide Web Consortium (W3C), a non-profit international community devoted to making the internet accessible to
people with disabilities, developed the Web Content Accessibility Guidelines (WCAG), which has become the most common standard for web accessibility. In April of 2024,
the DOJ published Nondiscrimination on the Basis of Disability; Accessibility of Web Information and
Services of State and Local Government Agencies, which finally established WCAG 2.1 level AA as the official standard for digital
accessibility.
To learn more about the Web Content Accessibility Guidelines, specifically how it is organized and what we mean by “level AA,” please visit DLI’s WCAG Summary page.
Basic Four
Even a cursory look at WCAG will reveal that it is a very technical document with many layers. In fact, there are many pieces of WCAG addressed within the applications we use or the settings that UITS administrators establish for us that typical content creators may never need to consider.
For that reason, we recommend thinking of WCAG and digital accessibility as a type
of grammar. It is a set of habits we develop to help us consider when we write a piece
of text or create a piece of media, ensuring that content can be accessed by someone
with limited vision, hearing, or movement and is optimized for people who use assistive technology to access the web. We’ve narrowed all these habits into a set of practices we call the Basic Four of Accessibility. The Basic Four website has more detail, but the Basic Four can be summarized like
this:
- Document Structure: “Documents” here refers to many types of content from HTML pages (the website) to Word documents, PowerPoint presentations, PDFs, etc. It infers many elements of documents including:
- Proper Semantic (Heading) Structure: This allows non-sighted readers to browse content using headings the same way a sighted
reader does.
- Use of List Styles: Properly formatted lists are used for sequences or bullets.
- Table Structure: Proper table headings are used so that assistive technology can provide proper context
for data in the table.
- Proper Color Contrast: Use of different colors of text may make reading more difficult for people who cannot
differentiate between colors.
- Descriptive Links: Full URLs are typically ignored by sighted readers but can be tedious for someone
listening to a document using assistive technology.
- Alternative Text: Descriptive text written for images that tell a reader who cannot see the image what they need to know about it.
- Media Accessibility: Closed captioning, audio descriptions, and transcripts ensure access to our video
and audio content.
- Accessible Third-Party Applications: When working with or acquiring an application or using a resource from another institution,
it is important to be able to tell whether that application or resource is compliant.
|