WCAG 2.2 and Academic Websites: Home: msstate

WCAG 2.2 and Academic Websites

Rich Text Content

While schools across the US have been returning to on-site learning modes in the past year, online methods play an increasingly important role in delivering learning content, both on- and off-campus. Digital accessibility ensures that learners, faculty, and administrators stay connected with each other and are able to participate in meaningful learning discussions.

The Web Content Accessibility Guidelines, or WCAG, are commonly accepted as the standard for digital accessibility in various sectors, including education. The WCAG is constantly evolving with the changing needs of different users. As a result, the World Wide Web Consortium is poised to announce WCAG 2.2, the latest version of the guidelines. Let’s take a closer look at WCAG 2.2 and how it will affect academic websites.

What is WCAG 2.2?

WCAG 2.2 is the long-anticipated successor to WCAG 2.1, which was announced in 2018. While the newer version is still being fine-tuned, it is expected to respond to an increased demand for online services among users with disabilities and the shift to mobile devices. The W3C aims to finalize and release WCAG 2.2 before the end of 2023. However, it’s much better to know more about WCAG 2.2 and implement its suggestions before they are formally announced as they greatly improve the user experience on academic websites.

What’s New In WCAG 2.2 – and How It Affects University Websites

Keyboard Control and Navigation

What’s New: WCAG 2.2 resolves a common issue where drop-down menu items and other elements are hidden by text typed in by users. It also sets size and contrast guidelines for keyboard focus indicators.

What This Means: Website developers need to ensure that web elements are always on top whenever they are in use. They also need to set a minimum size of two pixels and a contrast ratio of 3:1 for keyboard indicators to stay compliant. This also means that university websites and apps should start offering high-contrast themes to improve visibility. For example, Ohio University just announced that its SAP Concur web app is rolling out new themes, including two high-contrast options.

Drag And Drop

What’s New: The new WCAG 2.2 aims to make websites easier to navigate for those with motor impairments who are unable to click (or tap) and drag website elements, such as color pickers or sliders by requiring a single pointer instead.

What This Means: The days of dragging and dropping puzzle pieces as a form of user authentication are over. In addition, sliders might soon be a thing of the past if web developers don’t add point-and-click capabilities. To compensate for this, pointer inputs should be at least 24 by 24 pixels in size for improved visual and tactile feedback.

Help Features

What’s New: Help features such as self-help options, contact details, or feedback forms should maintain a consistent location across different web pages. For example, if the contact details are visible at the top of the home page, they should always be located at the top of the page, whether the user is looking at a sales page or an FAQ page.

What It Means: Users frequently complain that they have a hard time finding helpful information on websites, and it even gets even more confusing when the information changes locations across different pages. A consistent location for help features will ensure that the user will have quick and easy access to the assistance they need. The only exception to this is when the help features “float” on top of the website and the user is able to move them.

Redundant Entry

What’s New: Online forms should automatically reuse user inputs. Exceptions may be made for instances where the information should be reentered (such as passwords) or when the information is no longer correct or valid.

What It Means: Web developers should improve the way online forms store data so that the forms recognize identical fields and prepopulate them with data that has already been input by users. This will make forms more efficient and improve the overall user experience, especially for students with cognitive or motor issues. Course content developers could also take advantage of these new features to make tests and assessments more accessible.

WCAG 2.2: Improved Accessibility in the Academe

Like most academic papers, WCAG 2.2 is the result of years of research and testing. While it has not been formally announced, it is expected to change the landscape of digital accessibility for years to come. Academic institutions should be aware of WCAG 2.2 and start implementing the new guidelines in their websites to ensure a more inclusive environment for students, faculty, administrators, and the general public.

Allow Comments on this Page

Make Comments Public

HTML Editor

[{:section_type=>"rich_text", :content=>"<p>While schools across the US have been returning to on-site learning modes in the past year, online methods play an increasingly important role in delivering learning content, both on- and off-campus. Digital accessibility ensures that learners, faculty, and administrators stay connected with each other and are able to participate in meaningful learning discussions.&nbsp;</p>\n<p>The Web Content Accessibility Guidelines, or WCAG, are commonly accepted as the standard for digital accessibility in various sectors, including education. The WCAG is constantly evolving with the changing needs of different users. As a result, the World Wide Web Consortium is poised to announce<span>&nbsp;</span><a href=\"https://userway.org/compliance/wcag/\">WCAG 2.2</a>, the latest version of the guidelines. Let’s take a closer look at WCAG 2.2 and how it will affect academic websites.</p>\n<h2>What is WCAG 2.2?</h2>\n<p>WCAG 2.2 is the long-anticipated successor to WCAG 2.1, which was announced in 2018. While the newer version is still being fine-tuned, it is expected to respond to an increased demand for online services among users with disabilities and the shift to mobile devices. The W3C aims to finalize and release WCAG 2.2 before the end of 2023. However, it’s much better to know more about WCAG 2.2 and implement its suggestions before they are formally announced as they greatly improve the user experience on academic websites.</p>\n<h2>What’s New In WCAG 2.2 – and How It Affects University Websites</h2>\n<h3>Keyboard Control and Navigation</h3>\n<p>What’s New: WCAG 2.2 resolves a common issue where drop-down menu items and other elements are hidden by text typed in by users. It also sets size and contrast guidelines for keyboard focus indicators.</p>\n<p>What This Means: Website developers need to ensure that web elements are always on top whenever they are in use. They also need to set a minimum size of two pixels and a contrast ratio of 3:1 for keyboard indicators to stay compliant. This also means that university websites and apps should start offering high-contrast themes to improve visibility. For example, Ohio University just announced that its SAP Concur web app is rolling out new themes, including two<span>&nbsp;</span><a href=\"https://www.ohio.edu/news/2023/09/new-visual-theme-concur-web-application\">high-contrast options</a>.&nbsp;</p>\n<h3>Drag And Drop</h3>\n<p>What’s New: The new WCAG 2.2 aims to make websites easier to navigate for those with motor impairments who are unable to click (or tap) and drag website elements, such as color pickers or sliders by requiring a single pointer instead.&nbsp;</p>\n<p>What This Means: The days of dragging and dropping puzzle pieces as a form of user authentication are over. In addition, sliders might soon be a thing of the past if web developers don’t add point-and-click capabilities. To compensate for this, pointer inputs should be at least 24 by 24 pixels in size for improved visual and tactile feedback.</p>\n<h3>Help Features</h3>\n<p>What’s New: Help features such as self-help options, contact details, or feedback forms should maintain a consistent location across different web pages. For example, if the contact details are visible at the top of the home page, they should always be located at the top of the page, whether the user is looking at a sales page or an FAQ page.</p>\n<p>What It Means: Users frequently complain that they have a hard time finding helpful information on websites, and it even gets even more confusing when the information changes locations across different pages. A consistent location for help features will ensure that the user will have quick and easy access to the assistance they need. The only exception to this is when the help features “float” on top of the website and the user is able to move them.</p>\n<h3>Redundant Entry</h3>\n<p>What’s New: Online forms should automatically reuse user inputs. Exceptions may be made for instances where the information should be reentered (such as passwords) or when the information is no longer correct or valid.</p>\n<p>What It Means: Web developers should improve the way online forms store data so that the forms recognize identical fields and prepopulate them with data that has already been input by users. This will make forms more efficient and improve the overall user experience, especially for students with cognitive or motor issues. Course content developers could also take advantage of these new features to make tests and assessments more accessible.</p>\n<h2>WCAG 2.2: Improved Accessibility in the Academe</h2>\n<p>Like most academic papers, WCAG 2.2 is the result of years of research and testing. While it has not been formally announced, it is expected to change the landscape of digital accessibility for years to come. Academic institutions should be aware of WCAG 2.2 and start implementing the new guidelines in their websites to ensure a more inclusive environment for students, faculty, administrators, and the general public.</p>"}]

Rich Text Content