WCAG Archives /Tag - 216digital dev

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

216digital, ADA Web Accessibility, Website Accessibility

Accessibility, ADA Compliance, ADA non-compliance, ADA Website Compliance, WCAG, 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

216digital, ADA Compliance, ADA Web Accessibility, Uncategorized

Accessibility, ADA Compliance, ADA Website Compliance, WCAG, WCAG 2.2, 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

216digital, ADA Compliance, Website Accessibility

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

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

What Are the Levels of WCAG Compliance?

What are the WCAG Levels?

WCAG Foundation Principles

Perceivable

Operable

Understandable

Robust

What Do the Different WCAG Conformance Levels Mean?

WCAG 2.0 Level A: Minimal Compliance

WCAG 2.0 Level AA: Acceptable Compliance

WCAG 2.0 Level AAA: Completely Compliant

Can You Partially Meet a WCAG Level?

What WCAG Level to Aim For

Closing