WCAG Compliance Archives- Page 4 of 4/Category

Understanding WCAG for Better Digital Compliance
The World Wide Web is an interconnected network of knowledge accessible to anyone with an internet connection. However, the term ‘anyone’ isn’t always accurate. Some individuals, particularly those with disabilities, may find it challenging to access information and services online.

Fortunately, the Web Content Accessibility Guidelines (WCAG) are here to change this. WCAG can help websites follow the best practices of accessible design and eliminate accessibility barriers that could expose your business to the risk of legal action.

But what is WCAG — and how does it apply to your online business? In this post, we answer these questions and provide a few tips for making your web content WCAG-compliant.

The World Wide Web Consortium

The World Wide Web Consortium (W3C) is an international organization committed to improving the web. In 1997, the W3C launched the Web Accessibility Initiative (WAI) with the goal of providing strategies, guidelines, and resources to make the web accessible to people with disabilities. This initiative includes technical specifications for HTML, CSS, XML, and other technologies used to build websites.

Out of the WAI was born the Web Content Accessibility Guidelines or WCAG.

What is WCAG?

The Web Content Accessibility Guidelines, commonly known as WCAG, are a set of recommendations designed to make web content more accessible, primarily for people with disabilities. However, following these guidelines can also make your web content more accessible to all users, regardless of the device they’re using or their internet access circumstances.

The initial version of WCAG, WCAG 1.0, was released in 1999 with 14 guidelines. Since then, it has undergone significant revisions to better address the needs of various users and keep pace with rapidly evolving technologies. The most recent version at the time of this writing, WCAG 2.1, was published in 2021. However, the WAI plans to introduce WCAG 2.2 in the fall of 2023. Learn more about WCAG 2.2 and the future of accessibility standards.

WCAG Structure

WCAG is organized around four fundamental principles, which state that all content must be Perceivable, Operable, Understandable, and Robust (POUR). These four principles are expanded upon by supporting guidelines and further divided into distinct Success Criteria. These Success Criteria serve as precise and verifiable requirements for accessibility.

An Example of WCAG Success Criteria

Success Criterion 1.1.1 Non-text Content states: “All non-text content presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below…”

This Success Criterion is one of the Success Criteria under Guideline 1.1 Text Alternatives: “Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols, or simpler language.”

This Guideline is one of the Guidelines under Principle 1. Perceivable: “Information and user interface components must be presentable to users in ways they can perceive.”

WCAG Conformance Levels

WCAG success criteria are organized into three levels of conformance: Level A, Level AA, and Level AAA. Each Success Criterion is assigned a conformance level of A, AA, or AAA, with each Level including all success criteria from the lower levels.

For instance, Level AA includes all Level A success criteria, while Level AAA includes both Level A and AA success criteria. To qualify as meeting a certain conformance level, all content on a website must fully meet at least that Level.

While Level A conformance makes a website accessible, Level AA conformance of WCAG 2.0 or 2.1 is the most common. Websites that meet the Level AA requirements of the current version of WCAG are generally considered reasonably accessible to most users with disabilities.

Achieving Level AA conformance means satisfying all Level A and AA Success Criteria. However, it’s important to note that meeting Level AAA is optional as it’s impossible for some content to meet all Level AAA Success Criteria.

Understanding How WAI Maintains and Updates WCAG

The WAI regularly updates the WCAG to keep up with advancements in technology and user needs, ensuring the guidelines remain relevant and effective.

The WAI organizes this process through milestones, which are as follows:
1. Working Draft: The WAI team publishes the document as a Working Draft to ask for review and input from the community. The team updates the draft based on feedback. Usually, multiple Working Drafts of a technical report are published.
2. Wide Review Working Draft: Once all the comments and technical requirements have been addressed, it provides the complete document for community review. At this stage, members of the public are invited to leave comments.
3. Candidate Recommendations: The main purpose of the Candidate Recommendation is to ensure that the technical report can be implemented. At this stage, developers are encouraged to use the new version of WCAG in their projects.
4. Proposed Recommendation: After implementing each feature of the technical report, the W3C announces it as a Proposed Recommendation for W3C membership endorsement
5. W3C Recommendation: Once there is significant support for a new version of WCAG from the W3C Members, the W3C Director, and the public, it becomes an official W3C Recommendation.
It’s important to understand that WCAG is a living document, consistently updated to meet changing technology and digital accessibility needs. Hence, reaching each milestone takes time. WCAG needs to apply to different types of digital content and be reasonably future-proof.

But which version of WCAG should you use to test your content?

Which Version of WCAG Should I Use To Test My Content?

WCAG offers businesses a straightforward way to test their web content for accessibility issues. Each version of WCAG is designed for backward compatibility, including all previous guidelines and adding new ones. While recent versions of WCAG extend the requirements of older versions, the old standards still apply.

But which version of WCAG should you use for testing? When deciding which version of WCAG to use for testing your content, it’s generally recommended to use the latest version. Using the most recent version will ensure your website complies with the Americans with Disabilities Act (ADA) and other nondiscrimination laws, mitigating the risk of frivolous ADA lawsuits.

Is WCAG a Legal Requirement?

While WCAG is not legally binding in every country, many governments require compliance with its guidelines to ensure digital accessibility. For instance, in the US, federal websites must meet WCAG 2.1 Level A and AA requirements under Section 508 of the Rehabilitation Act.

Similarly, Title III of the ADA applies to private businesses but doesn’t explicitly mention WCAG or provide technical standards for online content. However, the Department of Justice (DOJ) published guidance in 2022 confirming its position that the ADA applies to business websites, stating:

“…the Department has consistently taken the position that the ADA’s requirements apply to all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web.”
– US Department of Justice | Guidance on Web Accessibility and the ADA (2022)

The Rise of ADA Web Compliance Lawsuits

Failure to meet these standards can expose businesses to legal challenges, as was the case with Domino’s Pizza in 2019. More recently, there has been a sharp increase in lawsuits related to website accessibility. For example, in 2022 alone, there were 2,387 web accessibility lawsuits filed in Federal Court and California State Court under the Unruh Act. This number doesn’t include the rising number of ADA legal complaints and ADA compliance demand letters sent to businesses with non-accessible websites.

While WCAG conformance might not be legally required elsewhere, it’s still considered a best practice and can significantly improve the user experience for all visitors.

Understanding What Conformance Means

WCAG conformance means that your website meets the criteria set by the WCAG guidelines. This involves more than just ticking off a list of guidelines; it means ensuring your website is accessible and usable for people with various disabilities.

W3C’s Understanding Conformance explains: “Conformance to a standard means that you meet or satisfy the ‘requirements’ of the standard.”

There are five requirements for conformance, per W3C:
1. Conformance Level: Websites must fully meet Level A, AA, or AAA levels.
2. Full Pages: Conformance and conformance levels account for the entire website or web page. It does not exclude a part of the website or a web page or evaluate each page individually.
3. Complete Process: If a web page is part of a multi-page process where a sequence of steps must be completed to accomplish an activity, all web pages must conform at the specified Level or better. Conformance can only be achieved if all pages in the sequence of steps conform at that Level or better.
4. Only Accessibility-Supported Ways of Using Technologies: Accessibility-supported technologies must be used to satisfy the success criteria. Any information or functionality not supported must also be available in a way that is accessibility supported.
5. Non-interference: If technologies are used in a way that is not accessibility supported, or if they are used in a non-conforming way, they must not prevent users from accessing the rest of the page. Additional requirements may also apply.
For more information, review W3C’s Understanding Conformance.

Building a Strategy for WCAG Conformance

Every online business should commit to web accessibility. Thankfully, WCAG makes this process more manageable. By planning to test your content against WCAG Level AA, you can find and address barriers affecting your users.

At 216digital, we’re dedicated to helping businesses achieve WCAG conformance. We can help develop a strategy to integrate WCAG 2.1 compliance into your development roadmap on your terms so you can focus on your other tasks.

Would you like to know where your business stands today? Schedule a complimentary ADA Strategy Briefing with 216digital to get a free scan of any URL and uncover accessibility issues on your site.
Greg McNeil

July 10, 2023

WCAG Compliance

Accessibility, ADA Compliance, ADA non-compliance, ADA Website Compliance, WCAG, Website Accessibility
5 Types of Assistive Technology Tools
The Internet is an essential resource for people worldwide. It provides access to information, entertainment, and services that make daily life easier. However, for people with disabilities, navigating the web can be a daunting task. That’s where assistive technology comes in. They help to bridge the gap and make the web more accessible for everyone.

So, what does your online business need to know about assistive technologies, and how can you make sure your website is compatible? In this post, we’ll break down the following:
- What Is Assistive Technology?
- What are 5 Types of Assistive Technology Tools?
- How Can I Make My Website Accessible?
What Is Assistive Technology?

Assistive technology(AT) is any tool or device that helps individuals with disabilities to access, navigate, and interact with web content. These tools can be hardware or software solutions that make it easier for people with various impairments to access and use websites and other digital resources. For example, a switch device using blinking or tapping can replace the need for a keyboard or mouse.

Typically, four main types of disabilities need to be considered.
- Visual: People who are blind, have low vision, or are color blind.
- Auditory: People who are hard of hearing or deaf.
- Motor: People who have limited fine motor control, muscle slowness, or tremors and spasms
- Cognitive: Cognitive disabilities hinder the behavior and intellectual development of a person. This includes a broad range of disabilities, from mental illnesses to learning disabilities or old age.
Different types of ATs are built to help each of these groups access web content. These tools are designed to bridge the gap between the users’ abilities and the demands of websites, making the web more accessible and inclusive.

What are 5 Types of Assistive Technology Tools?

With so many different types of assistive technology, it can be challenging to know where to start. So here are five of the most common types and how they help support people with disabilities browse the web:

1. Screen Magnification Software

Did you know that over 200 million people worldwide have a visual impairment that makes it difficult to read standard-sized text on a screen? Users with low vision often rely on magnification tools, such as screen magnifiers or browser zoom features, to make content legible or to reduce eye strain.

Most web browsers can “zoom in” on content, but screen magnification software works differently. Tools like MAGic, Windows Magnifier, and Apple’s Zoom magnify a part of the screen at a time, preserving the web page’s layout.

However, many users prefer to use the zoom function on their browsers. So don’t assume anyone with a visual impairment will only use screen magnification software when accessing your website.

The Web Content Accessibility Guidelines (WCAG) are a set of intentionally shared standards for website accessibility. For example, WCAG’s “Resize Text” guideline requires content to be zoomed in at least 200% before losing content or functionality.

2. Screen Readers

Screen readers are essential for users who are blind or have severe visual impairments. These software programs convert on-screen text into spoken words or braille output. As a result, users can navigate and interact with your website using only auditory feedback.

Popular screen readers include JAWS (Job Access With Speech), NVDA (NonVisual Desktop Access), and VoiceOver (for Apple devices). Each screen reader has its capabilities and limitations for carrying out tasks. However, screen readers only work if websites are compliant.

Here are a few examples of WCAG guidelines that are essential for screen readers:
- Providing all non-text content (images, form fields, video, audio, etc.) with alternative text descriptions. For example, images should have a text description that explains the image’s purpose on the page.
- Websites should use clear, descriptive headings and labels.
- Websites can be navigated with a keyboard or an alternate keyboard only.
3. Voice Recognition

One of the growing advances in AT is voice recognition. Voice recognition technology lets users control their browsers, dictate text, and interact with websites using only their voices. By enabling voice commands, users can navigate, click on links, fill out forms, and perform other tasks without using their hands.

Users should be able to use common commands such as “go to the homepage” to operate websites in predictable ways. However, web content must be designed and coded for users to use voice recognition tools.

Here are a few WCAG guidelines that can help improve the browsing experience for speech recognition users:
- Provide users with a clear visual indicator of which element is the current focus. Without focus indicators, users might not know what they’re controlling.
- Use labels and identifiers for interactive elements. Each element’s programmatic label should match its visual presentation. For instance, if a user sees a “submit” button on a page form, they should be able to say “submit” to activate the control and complete the form.
- Remove any keyboard traps that would prevent users from navigating your site after focusing on a certain element.
4. Switch Devices

A switch device is a specialized input tool that replaces the need for a keyboard or mouse. It is used by people with physical disabilities or fine motor impairments to access and control computers, smartphones, and other communication devices.

However, switch devices vary based on the user’s mobility, preferences, and settings. This can include pressing a button, blowing into a tube, or even moving an eyebrow. For example, users can press a large, round button with their hand, foot, or whatever is most comfortable. Then, on the screen, a focus indicator will automatically cycle through different elements on the site, and the user can click to activate the switch.

Like voice recognition AT, switch devices require similar WCAG standards to be implemented on a website for users to engage in the content.

5. Closed Captioning Services

Most of us are more familiar with closed captions, from streaming services and YouTube to video calls with Zoom. However, although it’s one of the more popular ATs, it is often overlooked.

Closed captioning services provide on-screen text corresponding to video and multimedia presentations’ audio content. By providing accurate and synchronized text captions for your multimedia content, you’re allowing users who are deaf or hard of hearing to understand and engage with your website. For this reason, WCAG requires all pre-recorded audio content to be clearly labeled, except for media with an alternative text option.

However, while automatic caption tools are available, they are far from perfect. For instance, we have all watched a YouTube video where captions do not always align with the speaker’s words. If it was not for our ability to hear, the message’s meaning would be different based on what the auto caption filled in. Therefore, it is highly recommended to use closed captioning services that employ human transcribers to make captions and transcripts more accurate.

How Can I Make My Website More Accessible?

With so many different types of AT available, it can be hard to know where to start. But regardless of where you are on your accessibility journey, we’re here to help. At 216digital, we can help develop a strategy to integrate WCAG 2.1 compliance into your development roadmap on your terms. Providing an accessible browsing experience to all your users, including those with disabilities.

To learn more about how the ADA experts at 216digital can help build an ADA WCAG 2.1 compliance strategy to achieve ongoing, real-world accessibility on your terms, schedule an ADA Strategy Briefing.
Greg McNeil

April 28, 2023

WCAG Compliance

Accessibility, ADA Compliance, ADA Website Compliance, Website Accessibility
What to Expect from WCAG 2.2
Are you an online business or website owner? If so, you must be aware of the critical changes in the Web Content Accessibility Guidelines (WCAG) 2.2! The World Wide Web Consortium (W3C) is expected to release the latest version of WCAG in May 2023. So stay ahead of the curve and ensure your website remains accessible to all users, including those with disabilities. Here’s what you need to know about the proposed changes — and how they will affect your current WCAG compliance. And remember, when WCAG 2.2 goes live, 216digital will be here to help.

Why is WCAG Changing?

WCAG is a set of guidelines designed to help make web content more accessible to people with disabilities. However, as technology and user preferences change, so must WCAG’s standards. Each new standard introduced is developed by the Web Accessibility Initiative (WAI). In 2021, WAI announced they were starting to work on the draft for WCAG 2.2, which is finally expected to be released sometime next month.

WCAG can be changed to add new success criteria or to change a current guideline’s conformance level. But, it will not remove any guidelines or change any language. Currently, WCAG 2.2 is based on the same three conformance levels as the previous versions: Level A, AA, and AAA.

Level A

Level A is the lowest level of conformance and the easiest to achieve with minimal impact on a website’s structure or design. It allows websites to be broadly accessible as it addresses the most basic access issues.

Level AA

By meeting the success criteria for Level AA, websites are considered reasonably accessible as they offer a higher level of conformity than Level A. AA is most often used as the compliance standard in lawsuits and is usable for most people.

Level AAA

Level AAA is the highest level of conformance and the most difficult to achieve. It is not often used as a goal to strive toward since it is not feasible for most websites to have the resources to meet this level.

What’s Changing In WCAG 2.2?

WCAG 2.2 introduces nine new success criteria along with minor changes to the instructions accompanying several established guidelines. However, each of these criteria is still up for feedback and changes, so there’s no guarantee that all of them will make it into the final version of WCAG 2.2.

Here’s a quick overview of the new guidelines — and how each one can help address web accessibility issues:

Guideline 2.4 Navigable

2.4.11 Focus Appearance (Minimum)

Level AA

Focus Appearance builds on two existing WCAG criteria, specifying the minimum requirements for focus indicators. The new guideline ensures that keyboard focus indicators are visible and easily distinguishable. They must have a clear border, are not obscured by other content, and have at least a color contrast ratio of 3:1 against the unfocused state and all adjacent colors.

The intent of WCAG 2.4.11 is to help low-vision users who use a keyboard for navigation. Users can quickly tell where they are on a page by ensuring the current focus point is visible.

2.4.12 Focus Not Obscured (Minimum)

Level AA

Knowing the current focus point is essential for sighted users who use a keyboard or keyboard-like device. However, sticky headers, pop-ups, and other content can sometimes obscure focused elements while a user is browsing.

However, Criterion 2.4.12 requires user interface components not to be entirely hidden from other content on the page. This lets users easily track the current focus point and avoid confusion.

2.4.13 Focus Not Obscured (Enhanced)

Level AAA

Similar to 2.4.12, 2.4.13 requires that no part of the focus indicator is hidden by other content.

Guideline 2.5 Input Modalities

2.5.7 Dragging Movements

Level AA

Drag and drop movements can be difficult and error-prone for many website users. Therefore, WCAG 2.5.7 requires that any functionality that uses a dragging movement for operation can also be achieved in other ways, like clicking. For example, a user could use a single tap, double tap, long presses, or path-based gestures instead of dragging an item. However, a dragging action is allowed when it is essential to the functionality of the content.

2.5.8 Target Size (Minimum)

Level AA

When buttons and other clickable elements are small, they can be challenging to interact with for people with fine motor impairments. The purpose of 2.5.8 is to ensure that when users select a target with a mouse or other device, they can do so easily without activating other nearby targets. Therefore, all clickable elements, such as links, must be at least 24 by 24 CSS pixels in size and spacing between adjacent targets.

2.5.8 provides a level AA alternative to 2.5.5: Target Size (Enhanced), which was introduced as part of WCAG 2.1. However, 2.5.5 requires the target size for all clickable elements to be at least 44 by 44 CSS pixels.

Guideline 3.2 Predictable

3.2.6: Consistent Help

Level A

The goal of 3.2.6 is to ensure that all users can easily find help when completing tasks on a web page. For example, suppose a help feature — such as search bars and help buttons — is available on multiple pages of a website. In that case, it must appear in the same relative place an order on each of the pages where it appears. This is particularly beneficial for users with cognitive disabilities or limited web experience, as they can quickly access help when needed.

Guideline 3.3 Input Assistance

3.3.7 Redundant Entry

Level A

For people with cognitive disabilities, logging into a website or mobile app can be challenging. The 3.3.7 level AA guideline tackles authentication processes that require the user to remember, manipulate, or transcribe information. Websites that use cognitive function tests must provide at least one other authentication method.

For instance, asking users to remember a password is a standard cognitive function test. But suppose the website allows entries from password manager browser extensions. In that case, the website has provided them with a mechanism to complete the process.

3.3.8 Accessible Authentication (Minimum)

Level AA

3.3.8 takes 3.37 further by not allowing any exceptions for cognitive function tests. For multi-step processes, 3.3.8 requires websites to auto-populate fields or enable users to select the information that they’ve previously entered. For example, suppose a website’s form requires the user to enter their address multiple times. In that case, the second field should either provide users with an option to select their address from the previous entry or auto-populate.

3.3.9: Redundant Entry ( Enhanced)

Level AAA

Similar to 3.3.7 and 3.3.8, 3.3.9 applies to the authentication process. However, 3.3.9 is a Level AAA guideline that does not require an authentication process unless that step provides an alternative authentication process or auto-populate.

Getting Ready for WCAG 2.2

While the full implementation of WCAG 2.2 may still be on the horizon, it’s never too early to start preparing. Here are some steps you can take to ensure a smooth transition:
1. Familiarize yourself with the new success criteria and understand their implications for your website.
2. Conduct an accessibility audit to identify areas that need improvement and align with WCAG 2.2 requirements.
3. Update your website’s design, content, and functionality to address the new criteria and improve accessibility.
4. Train your team on the importance of web accessibility and the new guidelines to ensure consistent implementation.
How Will the Revisions Affect My Current WCAG Compliance?

The transition from WCAG 2.1 to 2.2 will require some adjustments to your website, particularly in the areas of navigability, input modalities, predictability, and input assistance. However, these updates are designed to build upon the existing guidelines, so your current efforts will not be wasted. By proactively addressing these changes, you’ll ensure that your website remains compliant and accessible to all users.

When WCAG 2.2 Goes Live, We’ll Be Here to Help

When WCAG 2.2 goes live, you can count on 216digital to help you navigate the changes and maintain an accessible website. Our expert team will assess your website, provide recommendations, and implement the necessary adjustments to ensure your website meets the latest accessibility standards. Reach out to us today by scheduling a complementary ADA Strategy Briefing so that you can embrace the future of web accessibility with confidence.
Greg McNeil

April 28, 2023

WCAG Compliance

Accessibility, ADA Compliance, ADA Website Compliance, WCAG, WCAG 2.2, Website Accessibility
Do PDFs Need To Be Web Accessible?
PDFs have become a content staple for online businesses. From brochures and forms to e-books and reports, everyone uses PDFs, and with good reason. They’re compatible with most online content and are the ideal way to share and view information online.

But have you ever considered how accessible these documents are for disabled users? Despite their many advantages, PDFs often remain a closed book for people with disabilities.

Read on to learn what an accessible PDF is, how it will benefit your online business, and how to make your PDF files accessible to everyone.

The Popularity of PDF Documents

It’s not surprising that PDFs are used so much in the workplace. They are the perfect medium for presenting different types of information in a single document. Text, photos, charts, logos, and other items become fixed in a PDF, so the end-user can’t delete or reorder page elements.

PDFs also preserve the original formatting, fonts, and layout across different devices and operating systems. This ensures that your documents look the same to all users, regardless of their device.

Today, PDFs are the most widely used online document format. However, not all PDFs are made with accessibility in mind. While they may appear visually perfect, they can pose challenges for people with disabilities. But why are web-accessible PDFs important?

Why is PDF Accessibility Important?

While many businesses use PDFs for essential purposes, it’s important to remember that all online content must be fully accessible. Title III of the Americans with Disabilities Act (ADA) requires businesses open to the public to provide complete and equal access to people with disabilities. Moreover, the Department of Justice (DOJ) has continuously taken the position that the ADA does apply to all online content, including PDFs.

When authoring your online documents, you must avoid creating barriers for individuals with disabilities. For example, many PDFs need the appropriate tags to define their structure and non-text content. These issues can create barriers for people who use screen readers and other assistive technologies. In that case, you may expose yourself to legal implications and accessibility-related lawsuits. So don’t take the risk; ensure that your PDFs are accessible.

Aren’t all PDFs Web Accessible?

Contrary to popular belief, PDFs are not automatically web-accessible. While all PDFs are created using standard desktop publishing tools, they are not explicitly designed with accessibility in mind. As a result, many PDFs contain severe obstacles that can be difficult for users with disabilities to navigate or understand.

For example, suppose someone with low vision or who is legally blind uses a screen reader. In that case, they won’t be able to read a standard PDF if it lacks alternative text descriptions for images. This is because assistive technology tools like screen readers are not automatically compatible with PDFs.

In order to make PDFs truly accessible, additional efforts must be taken to address these concerns.

How are Accessible PDFs Different?

The fundamental difference between an accessible and inaccessible PDF file is that one can be accessed, viewed, and interacted with by everybody. For a PDF to be considered accessible, it must meet a set of accessibility guidelines:
1. Web Content Accessibility Guidelines (WCAG): WCAG is the set of guidelines created by the World Wide Web Consortium (W3C) to make web content more accessible to people with disabilities. They provide pass-or-fail success criteria with recommendations that can be applied to web-delivered documents.WCAG 2.1 is the current standard, including specific guidelines for PDF accessibility.
2. PDF/UA 1 (ISO 14289-1) This is an international standard for accessible PDFs, which provides detailed technical specifications for creating accessible documents.
What Are Tag Trees, and How Do They Help Make PDFs Web Accessible?

Tagged trees, or “tag trees,” are the main elements for making a PDF accessible. These tags tell assistive technologies how to read the PDF content and identify headings, paragraphs, sections, and tables.

They ensure that assistive tech tools move from section to section in the correct order without skipping non-text items like graphs or images. By doing so, tag trees can help convey information about the document’s layout, reading order, and organization to assistive technologies.

Tag trees help make a PDF accessible in several ways:
1. Reading Order: Properly tagged PDFs define the correct reading order for the content, ensuring that the text is presented in a logical sequence that makes sense to the user. This is especially important for screen reader users who rely on a linear reading experience.
2. Alternative Text: Tags can include alternative text descriptions for non-text elements, such as images or charts. This allows screen readers to convey the purpose or meaning of these elements to users who cannot see them.
3. Navigation: Proper tagging enables users to navigate between different sections or elements of the document easily. For example, the user wants to move from one heading to another or jump to a specific list or table, proper tagging makes this possible.
To make PDFs accessible, they must be appropriately tagged. This can be done using various tools and software, such as Adobe Acrobat Pro, which allows you to add, edit, or validate tags in a PDF. By making PDFs accessible through the use of tag trees, you help ensure that people with disabilities can access, navigate, and understand your documents more effectively.

How to Make Your PDF Accessible

PDFs can be made accessible if you structure and tag them correctly to meet accessibility standards. However, creating your document with accessibility in mind from the beginning is much easier than editing it once it has been made!

Here are some tips to make your PDFs more accessible:
- Add descriptive text for images, charts, and other non-text elements.
- Ensure that your document follows a clear hierarchy with headings, lists, and tables (i.e., H1, H2, H3)
- Choose fonts that are easy to read and ensure sufficient contrast between text and background colors.
- If interactive form fields need to be completed, ensure the user can enter values and move from one field to the next logically using the keyboard.
Some tools like Adobe Acrobat Pro and Acrobat DC add tags automatically with the “save as accessible PDF” function. However, they are not perfect. You’ll still need to check tags manually to ensure they match the content and are ADA-compliant.

How to Check PDFs for Web Accessibility

Every organization needs to consider accessibility from the first stages of document creation. PDFs are not only a legal requirement in many jurisdictions but also a smart business strategy. By making your PDFs accessible, you can reach a larger audience, improve your SEO, and demonstrate your commitment to inclusivity. Start implementing web accessibility into your PDF documents today by scheduling a complementary ADA Strategy Briefing with 216digital. Unlock the full potential of your online business.
Greg McNeil

April 10, 2023

Legal Compliance, WCAG Compliance

Accessibility, ADA Compliance, ADA Website Compliance, Website Accessibility, Website Accessibility Tools
What’s the Difference Between Usability and Accessibility?
Imagine surfing the internet and being unable to read the text due to size. Or not being able to enjoy video content because it has low volume and lacks closed captions. That’s where web usability and accessibility come into play. These two concepts might seem the same at first, but usable content isn’t always accessible. So, what exactly do these terms mean, and how do they affect your online experience?

In this post, we’ll explore the differences between web usability and accessibility and how they work together to create an optimal user experience. Let’s look at each concept in more detail.

Understanding Usability

Website usability helps us understand the user’s needs. It applies a user-centric design process to make sure that websites are efficient, easy to use, and satisfy users. In other words, a website should be easy to navigate, have a clear layout, and include a responsive design.

For example, a website with excellent usability will make it simple for users to find information, complete tasks, and engage with the site’s content.

Some key principles of web usability include:
- Ease of learning: How easily can users accomplish basic tasks when encountering a website for the first time?
- Efficiency: Once users have learned the workings of a website, how quickly can they perform tasks?
- Recognition: When previous users return to a website, how easily can they remember what and how to do something?
- Errors: How often do users make errors, and how easily can they recover from them?
- Satisfaction: How pleasant is the website in terms of design and layout?
While usability is based on user experience, it doesn’t focus on users with disabilities. Web accessibility, on the other hand, does.

What is Web Accessibility?

Web accessibility is the practice of making websites usable by people with disabilities. It aims to remove barriers preventing these users from accessing, navigating, and interacting with the content. Allowing them to perceive, understand, navigate, and interact with websites and tools equally.

Some key principles of web accessibility include:
- Providing all non-text content (images, form fields, video, audio, etc.) with a text alternative that serves the equivalent purpose
- Making sure everything on the website can be done through keyboard navigation
- Using webpage titles that describe each page’s topic or purpose.
- Ensure the site’s navigational elements are consistent and predictable across every page.
- Allowing users with visual impairments to adjust the text size and contrast on a website.
Web Accessibility is a Part of Usability

While web accessibility focuses on ensuring that people with disabilities can use websites, web usability is about making a website easy to use for everyone. Although these concepts have different goals, they do share some similarities. For instance, both require clear navigation, readable text, and a logical structure.

However, it’s important to remember that a usable site and an accessible site are not always the same, and vice versa. For example, a website can be usable if it works well for everyone. Still, it could be inaccessible if it creates barriers for those with disabilities. On the other hand, a website can be accessible but not usable if it is designed for people with disabilities but lacks user-friendly features.

The goal is to create a website or tool that is both web accessible and usable, benefiting the widest range of users possible.

Web Accessible Design

There are guidelines and techniques for web accessibility. The Web Content Accessibility Guidelines (WCAG) is a set of recommendations created by the World Wide Web Consortium (W3C) to ensure web accessibility. These guidelines are organized under four main principles: perceivable, operable, understandable, and robust (POUR).

However, designers, developers, and business owners often only approach web accessibility as a checklist of standards to meet. As a result, the user’s interaction is often lost, and accessibility is not achieved.

Only by combining the accessibility standards and usability process can we make sure a website is technically and functionally usable by people with disabilities. This process is often referred to as usable accessibility or accessible user experience.

Testing for Web Accessibility and Usability

Testing is an essential step in making sure that your website is accessible and usable. For web accessibility, you can use automated testing tools like Lighthouse, WAVE, and Firefox Inspector. Automated audits scan your website for accessibility barriers, such as missing alt text, improper header structures, and broken links. These tools provide quick insights into potential problems, such as missing alt text, improper heading structures, and broken links. However, automated testing is not enough.

For web usability, it’s helpful to conduct a manual audit. Manual reviews are more thorough, providing a more accurate assessment of how people with disabilities experience and engage your website. A web accessibility expert assesses your website using tools and human judgment. This includes screen readers, keyboard navigation, and magnifiers.

Web Accessibility and Usability

Web accessibility and web usability are two different yet interconnected concepts that help create a better online experience for all users. By understanding and implementing both, you can create a website that is inclusive, user-friendly, and compliant with accessibility standards.

As you become aware of the importance of web accessibility and its impact on your users, it is important to know you are not alone. 216digital is here to help regardless of where you are in your web accessibility journey. Schedule a complementary ADA Strategy Briefing today to find out how we can help.
Greg McNeil

April 10, 2023

WCAG Compliance

Accessibility, ADA Compliance, ADA Website Compliance, Website Accessibility
Debunking Common Web Accessibility Myths

“Web accessibility is too expensive.“

“There’s no real business value to making my website accessible.“

These are just a few of the concerns we hear when talking to organizations about web accessibility for the first time. And while it’s easy enough to poke holes in each one, it’s worth mentioning these myths are one of the many reasons digital accessibility lags so far behind.

To better understand why online businesses are slow to build accessible experiences, let’s debunk some of these myths and explain why web accessibility is essential for your business.

Common Myths in Website Accessibility

Common misconceptions about web accessibility have impacted the way organizations approach any accessibility initiative — particularly when it comes to time, cost, and compliance. Here’s what we learned.

Myth: There Are No Benefits to an Accessible Website

Why is digital accessibility so important? We can all agree that delivering an equal browsing experience to every user is the right thing to do. However, there are other benefits, like improved search engine optimization (SEO).

Many of the same principles for good SEO overlap with web accessibility best practices. Companies spend tens of thousands of dollars every year to improve their searchability. Search engines rank websites based on the content and user experience.By working on one, we enhance the other. After all, a better user experience for your visitors also offers a better understanding to search crawlers.

Myth: Web Accessibility Only Affects Those Who Are Blind or Have Low Vision

Most believe visual impairments are the most prominent disability an inaccessible website can impact. However, web accessibility can benefit several impairments, including hearing, cognitive, and motor. In fact, mobility and cognitive impairments affect a higher percentage of the population than visual.

That means digital accessibility is essential for people who cannot move their limbs and require a switch device. Similarly, people with dyslexia need the option to change fonts or line spacing.

The bottom line is an accessible website benefits users of all abilities. And your website’s design doesn’t have to suffer in the process.

Myth: Web Accessibility Means Redesigning My Entire Website

Most online business owners believe that providing an accessible online experience means starting from scratch — redesigning and developing the entire site. That, without exception, sounds both time-consuming and expensive. While we agree that it’s ideal to design an accessible website from the first line of code, it’s not feasible for the millions of existing sites.

However, it is often possible to make a website accessible by making minor adjustments, such as adding alternative text to images, adding focus outlines on interactive elements, and ensuring that videos have closed captions. These changes can significantly improve the website’s accessibility without requiring a complete redesign.

Myth: Using Automated Tools On My Site is All I Need to Make It Accessible

Automation is a powerful tool that is getting better all the time. But automation alone cannot identify and fix every accessibility error. In fact, automated scans can only detect 30% of barriers for users with disabilities. The limited scope of even the most advanced automation will leave many compliance issues unresolved and your company at risk.

That’s not to say automated tools are not a great starting point. However, it’s essential to think of them as a tool in a more extensive toolkit, including regular monitoring, manual testing, and reporting.

At 216digital, we believe in a hybrid approach. That combines the speed of automation with the precision of manual auditing to achieve and maintain an accessible website.

For more information about automated tools and ADA web compliance, check out the article, Are Web Accessibility Testing Tools Enough to Ensure Compliance.

Myth: Screen overlays can make my website compliant and protect me from an ADA lawsuit

Screen overlay products, also known as accessibility widgets or plugins, can help make a website more accessible to users with disabilities. Still, they do not guarantee that a website will fully comply with the Americans with Disabilities Act (ADA) or other accessibility guidelines.

These products typically provide a range of accessibility features, such as increasing text size, changing the background color, and providing alternative text descriptions for images. However, they do not address all of the accessibility issues that a website may have. For example, they may not address issues related to the structure and organization of content, or the use of appropriate headings and labels.

Additionally, these products do not address the issue of accessibility for users who are using assistive technologies such as screen readers. These technologies rely on the underlying code of the website, and a screen overlay does not address these barriers.

While these products can be a helpful tool for improving accessibility, they should not be considered a substitute for a comprehensive accessibility audit and remediation process to mitigate ADA lawsuit risk. Approximately 600 companies with an accessibility widget installed on their websites were hit with ADA accessibility lawsuits in 2022.

Myth: Web Accessibility Litigation is Frivolous and Invalid

Shockingly, most online companies believe accessibility lawsuits have no merit. Yet huge brand-named companies, such as Domino’s, have also been targeted with frivolous ADA lawsuits.

But huge name brands aren’t the only ones. Thousands of small and mid-size businesses face legal action. If you think your business is small enough to fly under the radar and avoid litigation, you’re wrong. Many mom-and-pop restaurants and small stores have recently fought and lost website accessibility lawsuits.

Failure to provide an accessible website can result in legal action and potentially significant financial penalties. Therefore, it’s crucial to take web accessibility seriously and ensure your website is accessible to everyone.

Fact: Web Accessibility is Smart Business

You’re not alone if you’ve fallen victim to believing some of these common myths and misconceptions. In ethical terms, individuals of all abilities deserve the right to barrier-free web use. And as we’ve seen, there are strong legal incentives for ensuring that your website is as accessible as possible. But you can take action.

216digital has made it easier to achieve website accessibility compliance without breaking your budget, taking all of your time, or completely redesigning your website. We can help develop a strategy to integrate WCAG 2.1 compliance into your development roadmap on your terms.

To learn more about how the ADA experts at 216digital can help build an ADA WCAG 2.1 compliance strategy to achieve ongoing, real-world accessibility on your terms, schedule an ADA Strategy Briefing.

Greg McNeil

March 14, 2023

Legal Compliance, Testing & Remediation, WCAG Compliance

ADA Compliance, ADA Website Compliance, Website Accessibility
What Are the Levels of WCAG Compliance?
When it comes to accessibility compliance, the Web Content Accessibility Guidelines (WCAG) version 2.0 is the most widely used standard worldwide. WCAG has set internationally shared standards for web content accessibility to meet the needs of individuals, organizations, and governments. Web Content applies to all content on a web page or application, including text, images, sounds, code, or markup that define a website’s structure or presentation.

There are three levels of WCAG compliance: A, AA, and AAA. Although this distinction is essential, it can be baffling. Therefore, we will discuss what WCAG A, AA, and AAA are, what they mean for your site, and which compliance level to aim for when becoming accessible.

Learn more about WCAG and ADA Web Accessibility Standards

What are the WCAG Levels?

There are three compliance levels within WCAG 2.0: A, AA, and AAA. For a website to be accessible for all users, each level’s requirments must be met. The distinction between conformance levels gives an organized structure requiring an increasingly higher standard of accessibility. The three levels provide flexibility upon different situations. For example, in complex websites or advancing technologies, to maintain a minimum level of compliance.

WCAG Foundation Principles

Each level of compliance is based on the same four principles of web accessibility. These principles are the foundations for content on the web and anyone wanting to use it. WCAG 2.0 guidelines follow these four principles: perceivable, operable, understandable, and robust, referred to as POUR. Therefore, to understand each WCAG level, it is essential to start with their foundation.

Perceivable

A website’s information and elements must be apparent to the user, leaving nothing undetectable or invisible. Most users perceive content and elements on a website through visuals. However, sound or touch are used alternatively for those unable to.

Operable

A website’s interactive elements such as controls, buttons, and navigations should be operable by all users. Users must operate the interface elements by first identifying those elements and selecting those options. Most users can interact by clicking, tapping, swiping, or rolling. However, users who cannot physically click require voice commands or other assistive devices to engage with interactive elements.

Understandable

Websites must be clear and concise in presenting predictable patterns for interaction and design. Users should have no issue comprehending the meaning or purpose of the presented information, including the function of buttons or other elements on a website. Everything should have a purpose and should be recognizable to all users.

Robust

Content must be robust enough for users to understand the function and reliably use various assisting technologies.

What Do the Different WCAG Conformance Levels Mean?

As previously mentioned, WCAG 2.0 A, AA, and AAA all have specific criteria to be met. The requirements for a website include all interactive elements, content, and presentation following four principles of POUR. WCAG does provide guidelines for each level for what an accessible website should do, each level building upon the next. However, the specific actions each website must take to be considered accessible or reach a certain level of compliance are not outlined. The most significant difference between conformance levels A, AA, and AAA is what they mean for the users of each website.

WCAG 2.0 Level A: Minimal Compliance

Level A covers the basic requirements and is the minimum degree of accessibility for a website to be accessible. Basic requirements to meet Level A do not impact the design or structure of the website. Failure to fulfill will result in an inaccessible website and will be impossible or exceedingly difficult for users with disabilities to use.

Notable WCAG 2.0 Level A success criteria include:
- All non-text content such as audio, video, or images must have a text alternative such as an alt text within the website’s code or captions to serve as an equivalent source for information and context.
- Users can effectively navigate the website using only keyboard inputs.
- Time-based media or video content must have a media alternative for text.
- Content and interface elements conveyed through presentation can be extracted and presented to the user in different modalities through assistive technologies or user agents.
- Color is not used as the only visual means of conveying information, prompting a response, distinguishing an element, or indicating an action by the user.
WCAG 2.0 Level AA: Acceptable Compliance

Level A conformance is an excellent starting point. However, Level AA goes further by ensuring a website must be deemed usable and understandable for most people, regardless of ability. For this reason, level AA compliance has been the standard for accessibility and web accessibility laws globally, including the ADA and Section 508 in the United States.

Notable WCAG 2.0 Level AA success criteria include:
- Text for content, captions, and text images can be resized without assistive technology up to 200% without loss of range of function.
- Text or alt text is used to convey information or content rather than images with text.
- More than one way to locate a web page within a website except when the web page is the result of a process or steps
- Navigation elements are consistent throughout the site
- Form fields have accurate labels
WCAG 2.0 Level AAA: Completely Compliant

Compliance at WCAG 2.0 is the highest level of accessibility and accommodates the maximum number of users. Unfortunately, it is also the most challenging level to achieve. While this level of compliance would be ideal, it is not necessary., W3 states they do not recommend or require Level AAA compliance for an entire website since it is impossible to achieve Level AAA from some content.

Notable WCAG 2.0 Level AAA success criteria include:
- Sign language interpretation for audio or video content
- Visual presentation of text and images has a contrast ratio of at least 7:1 except for large text, logo, or visual decorative components with no significance to the content.
- Timing is not an essential part of any activity on the website.
- The website does not contain anything that flashes more than three times in any one second.
- Context-sensitive help is available.
Can You Partially Meet a WCAG Level?

A website must meet all of the accessibility compliance level’s guidelines. To state that a website is Level AA compliant, it must meet every requirement for both Level A and the Level AA guidelines. Therefore, if you meet the24 out of 25 requirements for Level AA, your site will still be deemed only a Level A. However, please do not use this not to try to aim for higher levels of compliance. The more accessible your site is, the better the user experience is for your users regardless of their abilities.

What WCAG Level to Aim For

Most websites and development teams aim to meet Level AA. The legally required level for legislation for specific sites is Level AA, including the ADA and Section 508. Suppose you want to strengthen your existing website by making it ADA compliant. In that case, it is best to accomplish the Level A criteria first before progressing to Level AA. A Level A compliance level is still more accessible than an inaccessible website.

Closing

Understanding the different levels of WCAG 2.0 and their requirements can serve as a guide when implementing accessibility into your website. Take the first steps towards becoming accessible. Testing and correcting accessibility issues will help better your business and mitigate expensive ADA lawsuits.

Integrating accessibility can seem intimidating at first, but 216digital is here to help. If you would like more information on web accessibility or how to make your website accessible today, schedule a 15-minute complimentary consultation with our experts.
Greg McNeil

January 27, 2022

WCAG Compliance

Accessibility, WCAG, Website Accessibility, Website Accessibility Tools

Understanding WCAG for Better Digital Compliance

The World Wide Web Consortium

What is WCAG?

WCAG Structure

An Example of WCAG Success Criteria

WCAG Conformance Levels

Understanding How WAI Maintains and Updates WCAG

Which Version of WCAG Should I Use To Test My Content?

Is WCAG a Legal Requirement?

The Rise of ADA Web Compliance Lawsuits

Understanding What Conformance Means

Building a Strategy for WCAG Conformance

5 Types of Assistive Technology Tools

What Is Assistive Technology?

What are 5 Types of Assistive Technology Tools?

1. Screen Magnification Software

2. Screen Readers

3. Voice Recognition

4. Switch Devices

5. Closed Captioning Services

How Can I Make My Website More Accessible?

What to Expect from WCAG 2.2

Why is WCAG Changing?

Level A

Level AA

Level AAA

What’s Changing In WCAG 2.2?

Guideline 2.4 Navigable

2.4.11 Focus Appearance (Minimum)

Level AA

2.4.12 Focus Not Obscured (Minimum)

Level AA

2.4.13 Focus Not Obscured (Enhanced)

Level AAA

Guideline 2.5 Input Modalities

2.5.7 Dragging Movements

Level AA

2.5.8 Target Size (Minimum)

Level AA

Guideline 3.2 Predictable

3.2.6: Consistent Help

Level A

Guideline 3.3 Input Assistance

3.3.7 Redundant Entry

Level A

3.3.8 Accessible Authentication (Minimum)

Level AA

3.3.9: Redundant Entry ( Enhanced)

Level AAA

Getting Ready for WCAG 2.2

How Will the Revisions Affect My Current WCAG Compliance?

When WCAG 2.2 Goes Live, We’ll Be Here to Help

Do PDFs Need To Be Web Accessible?

The Popularity of PDF Documents

Why is PDF Accessibility Important?

Aren’t all PDFs Web Accessible?

How are Accessible PDFs Different?

What Are Tag Trees, and How Do They Help Make PDFs Web Accessible?

How to Make Your PDF Accessible

How to Check PDFs for Web Accessibility

What’s the Difference Between Usability and Accessibility?

Understanding Usability

What is Web Accessibility?

Web Accessibility is a Part of Usability

Web Accessible Design

Testing for Web Accessibility and Usability

Web Accessibility and Usability

Debunking Common Web Accessibility Myths

Common Myths in Website Accessibility

Myth: There Are No Benefits to an Accessible Website

Myth: Web Accessibility Only Affects Those Who Are Blind or Have Low Vision

Myth: Web Accessibility Means Redesigning My Entire Website

Myth: Using Automated Tools On My Site is All I Need to Make It Accessible

Myth: Screen overlays can make my website compliant and protect me from an ADA lawsuit

Myth: Web Accessibility Litigation is Frivolous and Invalid

Fact: Web Accessibility is Smart Business

What Are the Levels of WCAG Compliance?

What are the WCAG Levels?

WCAG Foundation Principles

Perceivable