Notice Type: Error Did a “Zooming and Scaling Disabled” error appear in an Accessibility Checker audit of one of your WordPress posts or pages? Read below for an explanation of […]
WCAG Level AA
Notice Type: Error Did an “Improper Use of Link” error appear in an Accessibility Checker audit of one of your WordPress posts or pages? Read on below for an explanation […]
To fix a Missing Language Declaration error, you will need to edit your theme files to add the missing language attribute to the HTML tag at the very top of your website header. If you're using a theme that receives updates, then you'll need to make the change in a child theme to ensure the fix does not get overwritten when you next update your theme.
To resolve this warning, you need to review any GIFs that are present to ensure that they meet all applicable guidelines for accessibility and then either "Ignore" the warning in Accessibility Checker or remove the GIF from your page or post if it is not accessible.
To resolve this warning, you need to visit the front end of your website and fully ensure that any videos on the page or post are accessible. Once you have fully tested your videos for accessibility, you need to resolve any accessibility errors that may be present and then can "Ignore" the warning in Accessibility Checker for that post or page.
To fix empty or missing form label errors, you'll need to determine how the field and form were created and then either add text to your existing field label or add field labels if they are missing completely.
To fix an Insufficient Color Contrast error, you will need to ensure that flagged elements meet the minimum required ratio of 4.5:1. To do so, you will need to find the hexadecimal codes of your foreground and background color, and test them in a color contrast checker. If these color codes have a ratio of 4.5:1 or greater, or you can confirm that they meet one of three exceptions, you can "Ignore" this error. If the color codes do not have a ratio of at least 4.5:1, you will need to make adjustments to your colors.
To resolve a Link to a Non-HTML File Warning, you need to ensure a direct link to view or download the document is present, warn users it is a link to a document by displaying the specific file extension in the link anchor, and est and remediate your file for accessibility errors.
To resolve a Link to PDF Warning, you need to Make sure that any PDF documents can be accessed natively. If you're using a WordPress plugin that allows you to embed PDFs on your website, you need to ensure a direct link to view or download the document is present, warn users it is a link to a document by displaying the specific file extension in the link anchor, and test and remediate your PDF for accessibility errors.
To resolve a Link to MS Office File Warning, you need to ensure a direct link to view or download the document is present, warn users it is a link to a document by displaying the specific file extension in the link anchor, and est and remediate your MS Office file for accessibility errors.
To fix a Possible Heading warning, you will need to determine if the flagged text is indeed intended to be a heading. If so, you need to change it from a paragraph to a heading at the proper level. If it is not supposed to be a heading then you can safely "Ignore" the warning.
To fix a page with no headings, you will need to add heading elements. At a minimum, every page should have one H1 tag. Add additional subheadings as appropriate for your content. If you have determined that headings are definitely not needed on the page, then you can "Ignore" the warning in Accessibility Checker.
