WTF: WCAG Technique Failure – Bad Page Title
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.
Elevage Digital articles on website accessibility and ADA-compliant website best practices.
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…
I recently created an accessible MailChimp signup form for WordPress with custom error handling that announces errors and status updates to screen reader users.
The popular Divi theme and page builder have some pretty significant accessibility issues. There are several strategies to improve Divi accessibility.
New accessibility rules for state and local governments will apply to websites, apps and social media content.
Build websites that are accessible by default. Don’t create roadblocks and special “vehicles” to interact with your website.