{"id":27112,"date":"2024-02-08T11:20:27","date_gmt":"2024-02-08T11:20:27","guid":{"rendered":"https:\/\/reciteme.com\/au\/?p=27112"},"modified":"2024-09-24T08:32:03","modified_gmt":"2024-09-24T07:32:03","slug":"wcag-2-2-accessibility-standards","status":"publish","type":"post","link":"https:\/\/reciteme.com\/au\/news\/wcag-2-2-accessibility-standards\/","title":{"rendered":"Everything you need to know about WCAG 2.2 Accessibility Standards"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In our ongoing mission to create a more inclusive digital world, we are excited to announce the arrival of the latest version of the Web Content Accessibility Guidelines (WCAG). The release of WCAG 2.2 signifies a significant milestone in web accessibility, bringing forth new criteria and techniques to ensure equal access for all users. At Recite Me, an accessibility company committed to empowering individuals with disabilities, we welcome these updates and are thrilled to share their significant step forward to help people online.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Understanding Web Content Accessibility Guidelines (WCAG) 2.2<\/h2>

The\u00a0Web Content Accessibility Guidelines<\/a>\u00a0(WCAG) 2.2 builds upon its predecessors, WCAG 2.0 and WCAG 2.1, to provide an updated set of guidelines that further enhance digital accessibility. The WCAG 2.2 has advanced accessibility measures and has proposed new success criteria to address specific\u00a0accessibility barriers<\/a>\u00a0faced by people with disabilities. By adhering to these guidelines, organisations can\u00a0create accessible websites<\/a>, with multiple web pages that are more inclusive and accessible to a wider range of users.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Animation\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

New Success Criteria and Techniques<\/h2>

WCAG 2.2 introduces several new success criteria and techniques designed to address accessibility gaps and challenges that have emerged since the release of WCAG 2.1. Some of the key additions include:<\/p>

Improved support for users with cognitive and learning disabilities<\/h3>

The new success criteria in WCAG 2.2 specifically cater to individuals with cognitive impairments. These criteria emphasize the need for clear and consistent navigation, understandable instructions, and more intuitive user interfaces.<\/p>

Enhanced mobile accessibility<\/h3>

As mobile usage continues to grow, WCAG 2.2 acknowledges the unique accessibility challenges faced on mobile devices. It introduces success criteria that focus on touch target size, content readability, and mobile keyboard accessibility.<\/p>

Improved support for users with low vision and sight impairments<\/h3>

WCAG 2.2 includes new testable success criteria that address web accessibility issues related to visual presentation and content readability. Guidelines such as providing sufficient colour contrast<\/a> and ensuring text resizing compatibility will help users with low vision navigate the web more effectively.<\/p>

Accessibility considerations for users with disabilities using different technologies<\/h3>

The latest update also takes into account the needs of users who rely on assistive technologies<\/a>, such as voice-controlled assistants and augmented reality. It offers guidance on creating accessible experiences for these evolving platforms.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
success criteria<\/span><\/td>level<\/span><\/td>techn<\/span>ique<\/span><\/td>brief description<\/span><\/td><\/tr>
\u00a0<\/td>\u00a0<\/td>\u00a0<\/td>\u00a0<\/td><\/tr>
2.4.11<\/span><\/a><\/td>AA<\/span><\/td>C43<\/span><\/a><\/td>WCAG technique C43 for Success Criterion 2.4.11 involves using CSS to customise the appearance of focus indicators on web elements, making them more noticeable for users navigating with keyboards or other input methods, thereby enhancing accessibility for users with low vision or keyboard-based navigation needs.<\/span><\/td><\/tr>
2.4.12<\/span><\/a><\/td>AAA<\/span><\/td>C43<\/span><\/a><\/td>WCAG Technique C43 for Success Criterion 2.4.12 involves using ARIA – which stands for accessible rich internet applications properties and states to convey important information and user interface components that are not easily perceivable by screen readers. By utilising ARIA, web developers can enhance the accessibility of their content and ensure that users with disabilities can effectively understand and interact with the information presented on the website.<\/span><\/td><\/tr>
2.4.13<\/span><\/a><\/td>AAA<\/span><\/td>C41<\/span><\/a><\/td>WCAG Techniques C41, C40 and G195 are strategies to meet Success Criterion 2.4.13, which aims to make it easier to spot keyboard focus. C41 ensures that the border on a focused element has a thickness that makes it stand out from the background, as well as ensuring there is a visible contrast between the focused element and background. C40 is similar to C41 as it checks the element’s thickness, but it also ensures a two-colour focus indicator is created that stands out against the background of a page. G195 checks that the default focus styling given by a browser has been enhanced and made more suitable for the site. Sometimes the default styling provided by a browser can be incompatible with a site’s designs, making it hard for the user to distinguish which element is currently focused. All the techniques mentioned aim to eliminate that confusion by checking that the styling of an element makes it stand out when focused.\u00a0<\/span><\/td><\/tr>
C40<\/span><\/a><\/td><\/tr>
G195<\/span><\/a><\/td><\/tr>
2.5.7<\/span><\/a><\/td>AA<\/span><\/td>G219<\/span><\/a><\/td>WCAG Technique G219 is a strategy to meet Success Criterion 2.5.7. This success criteria ensures people with motor impairments who cannot carry out dragging movements have an alternative method which does not involve dragging. This is operative when a user must drag an item in a list of movable items, or move an item on a KANBAN board from \u201cTo Do\u201d to \u201cIn Progress\u201d. This technique will ensure that an alternative single pointer method is presented for a user to interact with draggable elements.<\/span><\/td><\/tr>
2.5.8<\/span><\/a><\/td>AA<\/span><\/td>C42<\/span><\/a><\/td>WCAG Technique C42 is a strategy to meet Success Criterion 2.5.8. This success criteria aims to make controls on a web page easier to activate and understand. C42 aims to ensure that controls are not bunched together on a page and are evenly spaced out, making it easier for the user to tell where each control is on the page. It does this by checking that the space around each control ensures that no external elements interfere with its readability and functionality. If there is not adequate spacing around controls, then other elements could obscure the control making it hard for users to find and use.<\/span><\/td><\/tr>
3.2.6<\/span><\/a><\/td>A<\/span><\/td>G220<\/span><\/a><\/td>WCAG technique G220 is a strategy to meet Success Criterion 3.2.6. This success criteria aims to have user help that is easily accessible, on a page. G220 aims to provide a link to a site’s contact details in a consistent location through the website. This will help a user as if they are navigating a collection of pages in a site and want to reach out, the contact details \/ button should be in a familiar place. This technique will stop users having to search around a page due to the layout of a site being inconsistent.\u00a0<\/span><\/td><\/tr>
3.3.7<\/span><\/a><\/td>A<\/span><\/td>G221<\/span><\/a><\/td>WCAG technique G221 is a strategy to meet Success Criterion 3.3.7. This success criteria aims to reduce the amount of redundant and repeating data when a user is required to complete a multi-step process. G221 aims to carry through data from a previous step where required. This will allow the user to have a steadier experience when completing a process, as they won’t have to keep stopping at every step to remember what they entered during the previous step. This will allow a smoother overall experience for users when they are completing forms and inputting data..\u00a0<\/span><\/td><\/tr>
3.3.8<\/span><\/a><\/td>AA<\/span><\/td>H100<\/span><\/a><\/td>WCAG Success Criteria 3.3.8 addresses logging in to websites and suggests a number of techniques you may wish to employ to make that process more accessible.<\/span>
<\/span>Technique H100\u00a0 encourages site owners to correctly mark up their login forms to make them as accessible as possible, while technique G218 focuses on the exchange process of creating an account or resetting your account details, and in particular that the emails sent via this process are themselves accessible.\u00a0<\/span><\/td><\/tr>
G218<\/span><\/a><\/td><\/tr>
\u00a0<\/td><\/tr>
3.3.9<\/span><\/a><\/td>AAA<\/span><\/td>G218<\/span><\/a><\/td>WCAG technique G218 is a strategy to meet Success Criterion 3.3.9. This success criteria aims to make the login process on a site rely less on cognitive and mental effort. For example, avoiding CAPTCHAs that include matching objects or words during the login process. G218 aims to verify a user’s identity during the login stage, by sending an email to the associated email address and having the user confirm the login using that email. This will mean that the login process is not as challenging as the user will not have to undergo any cognitive verification, they will only have to confirm their identity. This will speed up the login process and make it easier for users to login.<\/span><\/td><\/tr><\/tbody><\/table>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The Recite Me Accessibility Checker already successfully scans for techniques G195 and C42 providing fix support to users. In development, we are currently looking to cover Success Criteria 2.4.13, 2.5.8, 2.4.11, 2.4.12, and 3.2.6.<\/p>

Success Criteria 3.3.8 and 3.3.9 due to their nature ( pertaining to authorisation) may have to be checked by a human but the Recite Me Checker will be able to identify and highlight these for the user.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Benefits of Implementing WCAG 2.2 Web Accessibility<\/h2>

By embracing WCAG 2.2, organisations can experience a range of benefits:<\/p>