To fix this warning, you will need to remove the justified styling from the specified text elements. To do so, find the text elements that have been flagged, and remove the text justified tag.
Tool Tips
For every ARIA Hidden warning that is flagged on your page, assess the element and determine if it is truly correct to hide the element from assistive technology users. If it is appropriate to hide the element, then you can safely "ignore" the warning. If it is not appropriate to hide the element, then you will need to remove the ARIA hidden attribute from the element's code.
To fix underlined text, you will need to remove the underline element from the text or CSS styles that are making it underlined. Try using other stylization, such as italics, colored text, or bolding to emphasize or differentiate between words or phrases.
To fix this warning, you will need to rewrite the alternative text for any images that flagged the Low-Quality Alternative Text warning, ensuring the alternative text is accurate, unique, contextually appropriate, and does not contain redundant or unnecessary descriptors.
To resolve this warning, you will need to change the text of either one or both elements that flagged the Duplicate Alternative Text warning, ensuring that all images have unique alt text and that you are not repeating your alt text in your image titles and captions.
To fix text that is too small, you will need to ensure that all text elements on your website are at least 10 points. It may be larger, but keep in mind that text that is 20 points or bigger, or 16 points or bigger and bold and/or italicized may be flagged as a possible heading.
This warning shows up in Accessibility Checker when the logical tab order on the page has been changed, which can cause navigation issues for keyboard-only users.
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.
