Acquia Copilot is a conversational AI connected into our product documentation and knowledge base. Ask Copilot about product features, technical details, troubleshooting and how to get started with Acquia products.
Web Governance has performed a round of periodic updates to our accessibility checks to improve the overall quality of accessibility scans.
An email was sent to all users regarding this latest update. In case you did not receive the email, this is what was communicated:
Acquia is releasing a major upgrade to Web Governance accessibility checks, helping you create even more inclusive websites and apps.
What’s in the update?
Clearer Results: Access streamlined checks, reducing the number of "review" flags. Now, issues are categorized as errors or warnings, making it easier to prioritize fixes
Enhanced Accuracy: 36 checks have been added. These include entirely new checks and improved versions of existing ones. This means Web Governance can identify a wider range of accessibility issues with greater precision
Additionally, we are also removing checks that are no longer relevant as the internet evolves.
The WCAG has not changed but websites and programming languages have evolved in recent years. As a result, some checks that were relevant five years ago are now obsolete. New methods and features in HTML and CSS created a requirement to develop new checks to fulfill specific WCAG success criteria.
Indication
An orange line with the label "Accessibility checks update" on your charts and tables in the Accessibility module indicates when your domain started scanning with the updated versions of checks.
All checks are updated automatically and Web Governance users do not need to do anything in order to take advantage of the changes. However, as a consequence of the update, be aware that your accessibility compliance score may change.
Changes in accessibility scores are expected, due to more accurate and comprehensive assessment of website accessibility as well as the way Web Governance calculates accessibility scores.
Changelog: All of the details about what has changed
The following sections provide details about specific updates to the various accessibility checks that Acquia has made as part of this release. The checks are arranged in order based on Success Criterion numbers.
Removed checks
Removed checks related to Success Criterion 1.1.1
Check 58 All input elements with a type attribute value of "image" have an alt attribute.
Check 59 Alt text for all input elements with a type attribute value of "image" identifies the purpose or function of the image.
Check 64 All area elements have an alt attribute.
Check 65 Alt text for all area elements identifies the link destination.
Removed checks related to Success Criterion 1.3.1
Check 42 All h1 elements are not used for formatting.
Check 43 All h2 elements are not used for formatting.
Check 44 All h3 elements are not used for formatting.
Check 45 All h4 elements are not used for formatting.
Check 46 All h5 elements are not used for formatting.
Check 47 All h6 elements are not used for formatting.
Check 112 All data table summaries contain text.
Removed checks related to Success Criterion 1.3.2
Check 133 All layout tables make sense when linearized.
Replaced by check 398 (see previous release).
Removed checks related to Success Criterion 1.3.5
Check 316 The purpose of each input field collecting information about the user can be programmatically determined.
Removed checks related to Success Criterion 1.4.3
Check 302 Visited link text colour must contrast sufficiently with its background colour.
Check 303 Active link text colour must contrast sufficiently with its background colour.
Check 304 Selected link text colour must contrast sufficiently with its background colour.
Check 354 Link text colour must contrast sufficiently with its background colour.
Check 364 Text has minimum contrast
Removed checks related to Success Criterion 1.4.4
Check 116 b (bold) element is not used.
Check 117 i (italic) element is not used.
Check 176 basefont must not be used.
Check 177 font must not be used.
Check 351 Ensure pinch-to-zoom is enabled.
Removed checks related to Success Criterion 1.4.5
Check 11 Alt text for all img elements contains all text in the image unless the image text is decorative or appears elsewhere in the document.
Check 193 Alt text for all input elements with a type attribute value of "image" contains all non-decorative text in the image.
Check 194 Alt text for all area elements contains all non-decorative text in the image area.
Removed checks related to Success Criterion 1.4.6
Check 307 Visited link text colour must provide high contrast with its background colour.
Check 308 Active link text colour must provide high contrast with its background colour.
Check 309 Selected link text colour must provide high contrast with its background colour.
Check 356 The contrast between the colour of link text and its background is not sufficient to meet WCAG2.0 Level AAA.
Check 365 Text has enhanced contrast
Removed checks related to Success Criterion 2.1.4
Check 322 Keyboard shortcuts are implemented in a changeable and safe manner
Removed checks related to Success Criterion 2.4.1
Check 28 A "skip to content" link appears on all pages with blocks of material prior to the main document.
Check 31 All frames have a title attribute.
Check 32 All frame titles identify the purpose or function of the frame.
Check 84 ASCII art should have a skipover link.
Check 262 All groups of links with a related purpose are marked.
Removed checks related to Success Criterion 2.4.4
Check 19 Link text is meaningful when read out of context.
Check 173 Suspicious link text.
Check 174 Each source anchor contains text.
Removed checks related to Success Criterion 2.4.5
Check 184 Sites must have a site map.
Removed checks related to Success Criterion 2.4.8
Check 266 The document contains a breadcrumb trail if it is part of a collection.
Removed checks related to Success Criterion 2.4.10
Check 261 Each section of content is marked with a header element.
Removed checks related to Success Criterion 2.5.1
Check 311 Content can be operated using simple inputs on a wide range of pointing devices.
Removed checks related to Success Criterion 2.5.2
Check 321 Functionality that can be operated using a single pointer, is implemented in a safe manner.
Removed checks related to Success Criterion 2.5.3
Check 323 User interface components with labels that include text or images of text has the text that is presented visually contained in the name.
Removed checks related to Success Criterion 2.5.4
Check 326 Functionality that can be operated by device motion or user motion can also be operated by user interface.
Removed checks related to Success Criterion 2.5.5
Check 324 The size of the target for pointer inputs is at least 44 by 44 CSS pixels.
Check 362 Pointer-interactive elements, such as linked icons, must be easy to target (Enhanced)
Removed checks related to Success Criterion 2.5.6
Check 325 Web content does not restrict use of input modalities available on a platform.
Removed checks related to Success Criterion 3.1.1
Check 48 Document has required lang attribute(s).
Check 49 Document has a valid language code.
Check 273 Reading order direction is marked using the html element's dir attribute if the document's primary language is read right to left.
Removed checks related to Success Criterion 3.1.2
Check 110 Words and phrases not in the document's primary language are marked.
Removed checks related to Success Criterion 3.1.3
Check 179 Provide a reference to a glossary.
Removed checks related to Success Criterion 3.1.4
Check 98 Abbreviations must be marked with abbr element.
Check 99 Acronyms must be marked with acronym element.
Removed checks related to Success Criterion 3.2.1
Check 275 Loading the web page does not cause a new window to open.
Removed checks related to Success Criterion 3.2.2
Check 68 area should not open new window without warning.
Check 92 All select elements do not cause an extreme change in context.
Check 274 Change of context occurs only by user activation unless a warning is provided.
Removed checks related to Success Criterion 3.2.3
Check 263 Repeated blocks of content appear in the same frame within the frameset.
Check 276 Repeated components appear in the same relative order each time they appear.
Removed checks related to Success Criterion 3.2.4
Check 81 List items must not be used to format text.
Check 100 blockquote must not be used for indentation.
Removed checks related to Success Criterion 3.2.5
Check 274 Change of context occurs only by user activation unless a warning is provided.
Removed checks related to Success Criterion 3.3.1
Check 267 All form submission error messages identify any empty required fields.
Removed checks related to Success Criterion 3.3.2
Check 96 All textarea elements have a label that is positioned close to control.
Check 122 All input elements, type of "password", have a label that is positioned close to the control.
Check 123 All input elements, type of "checkbox", have a label that is positioned close to the control.
Check 124 All input elements, type of "file", have a label that is positioned close to the control.
Check 125 All input elements, type of "radio", have a label that is positioned close to the control.
Check 187 Each input element has only one associated label.
Check 205 All input elements, type of "file", have a label that describes the purpose or function of the control.
Check 209 All select elements have a label that is positioned close to the control.
Check 210 All select elements have a label that describes the purpose or function of the control.
Check 211 All input elements, type of "text", have a label that is positioned close to the control.
Check 217 All input elements, type of "password", have a label that describes the purpose or function of the control.
Check 218 All input elements, type of "text", have a label that describes the purpose or function of the control.
Check 219 All input elements, type of "checkbox", have a label that describes the purpose or function of the control.
Check 220 All input elements, type of "radio", have a label that describes the purpose or function of the control.
Check 246 All form fields that are required are indicated to the user as required.
Check 392 Each label associated with an input element contains text
Removed checks related to Success Criterion 3.3.3
Check 268 All form submission error messages provide assistance in correcting the error.
Removed checks related to Success Criterion 3.3.4
Check 269 Form submission data is presented to the user before final acceptance for all irreversible transactions.
Removed checks related to Success Criterion 4.1.1
Check 185 id attributes must be unique.
Removed checks related to Success Criterion 4.1.3
Check 327 Status messages can be programmatically determined through role or properties.
Added checks
New checks related to Success Criterion 1.1.1 (AAA)
Check 447 An image button has a name that describes its purpose.
Replaces check 59.
New checks related to Success Criterion 1.2.5 (AA)
Check 430 Video has audio description
New checks related to Success Criterion 1.3.1 (A)
Check 446 All heading elements are not used for formatting.
Replaces checks 42, 43, 44, 45, 46, 47.
New checks related to Success Criterion 1.3.4 (AA)
Check 452 Orientation of the page is not restricted using CSS transform property.
Replaces check 313.
New checks related to Success Criterion 1.3.5 (AA)
Check 431 Ensure input fields with autocomplete attributes align with their intended purpose.
Replaces check 316.
Check 455 autocomplete attribute has valid value.
New checks related to Success Criterion 1.4.3 (AA)
Check 438 Link text color must contrast sufficiently with its background color.
Replaces check 354.
Check 440 Text has minimum contrast.
Replaces check 364.
Check 442 Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast
Check 444 Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast
Check 478 Link text colour in user induced states must meet minimum contrast or better with its background colour.
Replaces checks 302, 303, and 304.
New checks related to Success Criterion 1.4.4 (AA)
Check 453 Meta viewport allows for zoom.
New checks related to Success Criterion 1.4.5 (AA)
Check 466 Images of Text.
Replaces checks 193 and 194.
New checks related to Success Criterion 1.4.6 (AAA)
Check 439 The contrast between the color of link text and its background is not sufficient to meet WCAG 2.0 Level AAA.
Replaces check 356.
Check 441 Text has enhanced contrast.
Replaces check 365.
Check 443 Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast
Check 445 Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast
Check 479 Link text colour in user induced states must meet enhanced contrast or better with its background colour.
Replaces checks 307, 308, and 309.
New checks related to Success Criterion 1.4.7 (AAA)
Check 449 Low or no background audio
New checks related to Success Criterion 1.4.8 (AAA)
Check 465 Text is Justified.
New checks related to Success Criterion 2.4.1 (A)
Check 423 Bypass Blocks.
Replaces checks 28, 31, 32, 84, and 262.
New checks related to Success Criterion 2.4.4 (AA)
Check 460 Links with identical accessible names and same context serve equivalent purpose
New checks related to Success Criterion 2.4.9 (AAA)
Check 476 Links with identical accessible names have equivalent purpose.
New checks related to Success Criterion 2.5.3 (A)
Check 470 Visible label is part of accessible name.
Replaces check 323.
New checks related to Success Criterion 2.5.5 (AAA)
Check 477 Pointer-interactive elements, such as linked icons, must be easy to target (extended).
Replaces checks 324 and 362.
New checks related to Success Criterion 3.1.1 (A)
Check 451 HTML page lang attribute has valid language tag.
Replaces check 49.
Check 434 Document has required lang attribute(s).
Replaces check 48.
New checks related to Success Criterion 3.1.2 (AA)
Check 454 Element with lang attribute has valid language tag.
Check 472 The local language attribute matches the actual language.
Replaces check 110.
New checks related to Success Criterion 3.1.4 (AAA)
Check 471 Abbreviations must be described.
New checks related to Success Criterion 3.3.1 (A)
Check 467 An input error is described to the user in text.
Replaces check 267.
New checks related to Success Criterion 3.3.2 (AAA)
Check 473 Labels or instructions are provided when content requires user input.
Replaces checks 96, 122, 123, 124, 125, 209, and 211.
New checks related to Success Criterion 3.3.3 (AA)
Check 468 All form submission error messages provide assistance in correcting the error.
Replaces check 268.
New checks related to Success Criterion 3.3.4 (AA)
Check 469 Form submission data is presented to the user before final acceptance for all irreversible transactions.
Replaces check 269.
New checks related to Success Criterion 3.3.5 (AAA)
Check 475 Context-sensitive help is available for forms.
New checks related to Success Criterion 4.1.3 (AA)
Check 448 Status messages can be programmatically determined through role or properties.
Replaces check 327.
Changelog: All of the details about what has changed (same information as above) arranged differently
The following sections provide details about specific updates to the various accessibility checks that Acquia has made as part of this release. The checks are arranged in order based on Success Criterion numbers.
Note
This section provides the same information as the previous section. However, the information in this section is categorized by criterion.
WCAG 2.0 Success criterion 1.1.1 Non-text Content (Level A)
Removed checks:
Check 58: All input elements with a type attribute value of "image" have an alt attribute
Check 59: Alt text for all input elements with a type attribute value of "image" identifies the purpose or function of the image
Check 64: All area elements have an alt attribute
Check 65: Alt text for all area elements identifies the link destination
New checks:
Check 447: An image button has a name that describes its purpose.
Web Governance has performed a round of periodic updates to our accessibility checks to improve the overall quality of accessibility scans.
An email was sent to all users regarding this latest update. In case you did not receive the email, this is what was communicated:
Acquia is releasing a major upgrade to Web Governance accessibility checks, helping you create even more inclusive websites and apps.
What’s in the update?
Clearer Results: Access streamlined checks, reducing the number of "review" flags. Now, issues are categorized as errors or warnings, making it easier to prioritize fixes
Enhanced Accuracy: 36 checks have been added. These include entirely new checks and improved versions of existing ones. This means Web Governance can identify a wider range of accessibility issues with greater precision
Additionally, we are also removing checks that are no longer relevant as the internet evolves.
The WCAG has not changed but websites and programming languages have evolved in recent years. As a result, some checks that were relevant five years ago are now obsolete. New methods and features in HTML and CSS created a requirement to develop new checks to fulfill specific WCAG success criteria.
Indication
An orange line with the label "Accessibility checks update" on your charts and tables in the Accessibility module indicates when your domain started scanning with the updated versions of checks.
All checks are updated automatically and Web Governance users do not need to do anything in order to take advantage of the changes. However, as a consequence of the update, be aware that your accessibility compliance score may change.
Changes in accessibility scores are expected, due to more accurate and comprehensive assessment of website accessibility as well as the way Web Governance calculates accessibility scores.
Changelog: All of the details about what has changed
The following sections provide details about specific updates to the various accessibility checks that Acquia has made as part of this release. The checks are arranged in order based on Success Criterion numbers.
Removed checks
Removed checks related to Success Criterion 1.1.1
Check 58 All input elements with a type attribute value of "image" have an alt attribute.
Check 59 Alt text for all input elements with a type attribute value of "image" identifies the purpose or function of the image.
Check 64 All area elements have an alt attribute.
Check 65 Alt text for all area elements identifies the link destination.
Removed checks related to Success Criterion 1.3.1
Check 42 All h1 elements are not used for formatting.
Check 43 All h2 elements are not used for formatting.
Check 44 All h3 elements are not used for formatting.
Check 45 All h4 elements are not used for formatting.
Check 46 All h5 elements are not used for formatting.
Check 47 All h6 elements are not used for formatting.
Check 112 All data table summaries contain text.
Removed checks related to Success Criterion 1.3.2
Check 133 All layout tables make sense when linearized.
Replaced by check 398 (see previous release).
Removed checks related to Success Criterion 1.3.5
Check 316 The purpose of each input field collecting information about the user can be programmatically determined.
Removed checks related to Success Criterion 1.4.3
Check 302 Visited link text colour must contrast sufficiently with its background colour.
Check 303 Active link text colour must contrast sufficiently with its background colour.
Check 304 Selected link text colour must contrast sufficiently with its background colour.
Check 354 Link text colour must contrast sufficiently with its background colour.
Check 364 Text has minimum contrast
Removed checks related to Success Criterion 1.4.4
Check 116 b (bold) element is not used.
Check 117 i (italic) element is not used.
Check 176 basefont must not be used.
Check 177 font must not be used.
Check 351 Ensure pinch-to-zoom is enabled.
Removed checks related to Success Criterion 1.4.5
Check 11 Alt text for all img elements contains all text in the image unless the image text is decorative or appears elsewhere in the document.
Check 193 Alt text for all input elements with a type attribute value of "image" contains all non-decorative text in the image.
Check 194 Alt text for all area elements contains all non-decorative text in the image area.
Removed checks related to Success Criterion 1.4.6
Check 307 Visited link text colour must provide high contrast with its background colour.
Check 308 Active link text colour must provide high contrast with its background colour.
Check 309 Selected link text colour must provide high contrast with its background colour.
Check 356 The contrast between the colour of link text and its background is not sufficient to meet WCAG2.0 Level AAA.
Check 365 Text has enhanced contrast
Removed checks related to Success Criterion 2.1.4
Check 322 Keyboard shortcuts are implemented in a changeable and safe manner
Removed checks related to Success Criterion 2.4.1
Check 28 A "skip to content" link appears on all pages with blocks of material prior to the main document.
Check 31 All frames have a title attribute.
Check 32 All frame titles identify the purpose or function of the frame.
Check 84 ASCII art should have a skipover link.
Check 262 All groups of links with a related purpose are marked.
Removed checks related to Success Criterion 2.4.4
Check 19 Link text is meaningful when read out of context.
Check 173 Suspicious link text.
Check 174 Each source anchor contains text.
Removed checks related to Success Criterion 2.4.5
Check 184 Sites must have a site map.
Removed checks related to Success Criterion 2.4.8
Check 266 The document contains a breadcrumb trail if it is part of a collection.
Removed checks related to Success Criterion 2.4.10
Check 261 Each section of content is marked with a header element.
Removed checks related to Success Criterion 2.5.1
Check 311 Content can be operated using simple inputs on a wide range of pointing devices.
Removed checks related to Success Criterion 2.5.2
Check 321 Functionality that can be operated using a single pointer, is implemented in a safe manner.
Removed checks related to Success Criterion 2.5.3
Check 323 User interface components with labels that include text or images of text has the text that is presented visually contained in the name.
Removed checks related to Success Criterion 2.5.4
Check 326 Functionality that can be operated by device motion or user motion can also be operated by user interface.
Removed checks related to Success Criterion 2.5.5
Check 324 The size of the target for pointer inputs is at least 44 by 44 CSS pixels.
Check 362 Pointer-interactive elements, such as linked icons, must be easy to target (Enhanced)
Removed checks related to Success Criterion 2.5.6
Check 325 Web content does not restrict use of input modalities available on a platform.
Removed checks related to Success Criterion 3.1.1
Check 48 Document has required lang attribute(s).
Check 49 Document has a valid language code.
Check 273 Reading order direction is marked using the html element's dir attribute if the document's primary language is read right to left.
Removed checks related to Success Criterion 3.1.2
Check 110 Words and phrases not in the document's primary language are marked.
Removed checks related to Success Criterion 3.1.3
Check 179 Provide a reference to a glossary.
Removed checks related to Success Criterion 3.1.4
Check 98 Abbreviations must be marked with abbr element.
Check 99 Acronyms must be marked with acronym element.
Removed checks related to Success Criterion 3.2.1
Check 275 Loading the web page does not cause a new window to open.
Removed checks related to Success Criterion 3.2.2
Check 68 area should not open new window without warning.
Check 92 All select elements do not cause an extreme change in context.
Check 274 Change of context occurs only by user activation unless a warning is provided.
Removed checks related to Success Criterion 3.2.3
Check 263 Repeated blocks of content appear in the same frame within the frameset.
Check 276 Repeated components appear in the same relative order each time they appear.
Removed checks related to Success Criterion 3.2.4
Check 81 List items must not be used to format text.
Check 100 blockquote must not be used for indentation.
Removed checks related to Success Criterion 3.2.5
Check 274 Change of context occurs only by user activation unless a warning is provided.
Removed checks related to Success Criterion 3.3.1
Check 267 All form submission error messages identify any empty required fields.
Removed checks related to Success Criterion 3.3.2
Check 96 All textarea elements have a label that is positioned close to control.
Check 122 All input elements, type of "password", have a label that is positioned close to the control.
Check 123 All input elements, type of "checkbox", have a label that is positioned close to the control.
Check 124 All input elements, type of "file", have a label that is positioned close to the control.
Check 125 All input elements, type of "radio", have a label that is positioned close to the control.
Check 187 Each input element has only one associated label.
Check 205 All input elements, type of "file", have a label that describes the purpose or function of the control.
Check 209 All select elements have a label that is positioned close to the control.
Check 210 All select elements have a label that describes the purpose or function of the control.
Check 211 All input elements, type of "text", have a label that is positioned close to the control.
Check 217 All input elements, type of "password", have a label that describes the purpose or function of the control.
Check 218 All input elements, type of "text", have a label that describes the purpose or function of the control.
Check 219 All input elements, type of "checkbox", have a label that describes the purpose or function of the control.
Check 220 All input elements, type of "radio", have a label that describes the purpose or function of the control.
Check 246 All form fields that are required are indicated to the user as required.
Check 392 Each label associated with an input element contains text
Removed checks related to Success Criterion 3.3.3
Check 268 All form submission error messages provide assistance in correcting the error.
Removed checks related to Success Criterion 3.3.4
Check 269 Form submission data is presented to the user before final acceptance for all irreversible transactions.
Removed checks related to Success Criterion 4.1.1
Check 185 id attributes must be unique.
Removed checks related to Success Criterion 4.1.3
Check 327 Status messages can be programmatically determined through role or properties.
Added checks
New checks related to Success Criterion 1.1.1 (AAA)
Check 447 An image button has a name that describes its purpose.
Replaces check 59.
New checks related to Success Criterion 1.2.5 (AA)
Check 430 Video has audio description
New checks related to Success Criterion 1.3.1 (A)
Check 446 All heading elements are not used for formatting.
Replaces checks 42, 43, 44, 45, 46, 47.
New checks related to Success Criterion 1.3.4 (AA)
Check 452 Orientation of the page is not restricted using CSS transform property.
Replaces check 313.
New checks related to Success Criterion 1.3.5 (AA)
Check 431 Ensure input fields with autocomplete attributes align with their intended purpose.
Replaces check 316.
Check 455 autocomplete attribute has valid value.
New checks related to Success Criterion 1.4.3 (AA)
Check 438 Link text color must contrast sufficiently with its background color.
Replaces check 354.
Check 440 Text has minimum contrast.
Replaces check 364.
Check 442 Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast
Check 444 Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have minimum contrast
Check 478 Link text colour in user induced states must meet minimum contrast or better with its background colour.
Replaces checks 302, 303, and 304.
New checks related to Success Criterion 1.4.4 (AA)
Check 453 Meta viewport allows for zoom.
New checks related to Success Criterion 1.4.5 (AA)
Check 466 Images of Text.
Replaces checks 193 and 194.
New checks related to Success Criterion 1.4.6 (AAA)
Check 439 The contrast between the color of link text and its background is not sufficient to meet WCAG 2.0 Level AAA.
Replaces check 356.
Check 441 Text has enhanced contrast.
Replaces check 365.
Check 443 Text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast
Check 445 Link text on top of image, gradient or backdrop-filter, or using Text Shadows, should have enhanced contrast
Check 479 Link text colour in user induced states must meet enhanced contrast or better with its background colour.
Replaces checks 307, 308, and 309.
New checks related to Success Criterion 1.4.7 (AAA)
Check 449 Low or no background audio
New checks related to Success Criterion 1.4.8 (AAA)
Check 465 Text is Justified.
New checks related to Success Criterion 2.4.1 (A)
Check 423 Bypass Blocks.
Replaces checks 28, 31, 32, 84, and 262.
New checks related to Success Criterion 2.4.4 (AA)
Check 460 Links with identical accessible names and same context serve equivalent purpose
New checks related to Success Criterion 2.4.9 (AAA)
Check 476 Links with identical accessible names have equivalent purpose.
New checks related to Success Criterion 2.5.3 (A)
Check 470 Visible label is part of accessible name.
Replaces check 323.
New checks related to Success Criterion 2.5.5 (AAA)
Check 477 Pointer-interactive elements, such as linked icons, must be easy to target (extended).
Replaces checks 324 and 362.
New checks related to Success Criterion 3.1.1 (A)
Check 451 HTML page lang attribute has valid language tag.
Replaces check 49.
Check 434 Document has required lang attribute(s).
Replaces check 48.
New checks related to Success Criterion 3.1.2 (AA)
Check 454 Element with lang attribute has valid language tag.
Check 472 The local language attribute matches the actual language.
Replaces check 110.
New checks related to Success Criterion 3.1.4 (AAA)
Check 471 Abbreviations must be described.
New checks related to Success Criterion 3.3.1 (A)
Check 467 An input error is described to the user in text.
Replaces check 267.
New checks related to Success Criterion 3.3.2 (AAA)
Check 473 Labels or instructions are provided when content requires user input.
Replaces checks 96, 122, 123, 124, 125, 209, and 211.
New checks related to Success Criterion 3.3.3 (AA)
Check 468 All form submission error messages provide assistance in correcting the error.
Replaces check 268.
New checks related to Success Criterion 3.3.4 (AA)
Check 469 Form submission data is presented to the user before final acceptance for all irreversible transactions.
Replaces check 269.
New checks related to Success Criterion 3.3.5 (AAA)
Check 475 Context-sensitive help is available for forms.
New checks related to Success Criterion 4.1.3 (AA)
Check 448 Status messages can be programmatically determined through role or properties.
Replaces check 327.
Changelog: All of the details about what has changed (same information as above) arranged differently
The following sections provide details about specific updates to the various accessibility checks that Acquia has made as part of this release. The checks are arranged in order based on Success Criterion numbers.
Note
This section provides the same information as the previous section. However, the information in this section is categorized by criterion.
WCAG 2.0 Success criterion 1.1.1 Non-text Content (Level A)
Removed checks:
Check 58: All input elements with a type attribute value of "image" have an alt attribute
Check 59: Alt text for all input elements with a type attribute value of "image" identifies the purpose or function of the image
Check 64: All area elements have an alt attribute
Check 65: Alt text for all area elements identifies the link destination
New checks:
Check 447: An image button has a name that describes its purpose.
Web Governance