Divi5 Accessibility: Links and Buttons
To resolve accessibility issues in Divi5 related to links and buttons, you must apply ARIA roles correctly and use semantically correct HTML when possible.
Elevage Digital articles on website accessibility and ADA-compliant website best practices.
To resolve accessibility issues in Divi5 related to links and buttons, you must apply ARIA roles correctly and use semantically correct HTML when possible.
A review of GoDaddy Airo websites uncovered critical or high-severity WCAG failures that could significantly impact users who rely on assistive technologies.
WCAG Failure F89 applies when a linked image does not include text that describes the purpose of the link
An accessible website that meets WCAG requirements combines good code, design, and content. A failure in any one of these areas is a failure for the whole site.
Failure for WCAG 2.4.2 Page Titled where a title is provided, but it does not accurately describe the contents or purpose of the page.
Version 1.2 includes a significant update to menu styling to better support combinations of links and buttons within dropdown menus.
Three specific failures for WCAG 1.1.1 Non-Text Content where alt text and the ALT attribute are used incorrectly
I’m not comparing the pros and cons of Divi vs. KadenceWP to build websites, that’s been done. My personal preference is to build sites using KadenceWP because it provides better accessibility, page speed and flexibility than Divi. Instead, this post is about using KadenceWP Blocks within a Divi theme to compensate for many accessibility issues…