Using the accessibility checker | Civio CMS Knowledge Base [ ![Civio Knowledge Base](/storage/branding/01KP4QF0THM695BDF2MG6TX3CY.svg) ](https://nginx.deploy-lagoon-production.districtcms-docs.dh1.amazee.io) [Articles](/articles) [Releases](/releases) [Home](/) [Knowledge base](/articles) [Page building & display](/articles?category=6) Using the accessibility checker =============================== Updated 1 week ago Search Go Overview -------- The accessibility checker is built into the content editor. It reviews your content for common accessibility issues as you work, helping ensure your pages are usable by everyone, including people who rely on assistive technology such as screen readers. Opening the accessibility checker --------------------------------- Select the accessibility checker button in the editor toolbar. The checker inspects the content you're editing and reports any issues it finds without leaving the page. ![](/storage/TPbYZjePckSDomkVY9NZnmUSh1M8tAF96JAxWeBD.png) Reviewing issues ---------------- Issues are shown in a balloon panel attached to the relevant part of your content, each with plain-language guidance explaining the problem and how to address it. Checks are run against established accessibility testing libraries and cover common problems, such as images without alternative text, inconsistent heading structure, vague link text like "click here", and tables missing header cells. Each alert includes buttons to jump straight to the relevant place in the editor and to dismiss the alert (see below). If an alert points to content tucked inside a tab or accordion, use the next and previous buttons to step through each issue in turn. ![](/storage/hJ659wz9zJ1U9HoUgRsPoYj6248cDmdAVtyp4Y1B.png) Errors and manual checks ------------------------ The checker flags two kinds of issue. **Errors** are clear problems that should be fixed, such as an image with no alternative text. **Manual checks** (sometimes shown as warnings) are items the checker can't judge on its own — for example, whether a link's wording makes sense out of context — and need a person to review and confirm. ![](/storage/X0NcqfwcqqxgYkVsVaqwYNLgubNCJiwlyMeJkl3q.png) Fixing issues ------------- For many common problems, the checker offers a quick fix that corrects the issue in a single step. Where an issue needs your judgement, follow the guidance shown in the panel and adjust the content manually, then re-run the check to confirm it's resolved. Dismissing alerts ----------------- Once you've reviewed a manual check and you're satisfied the content is fine, you can dismiss it from the bottom of the tooltip: - **Ignore** hides the alert for you only. Use this for something you've checked but other editors may still want to review. - **Mark OK** hides the alert for everyone. Use this when the content is correct and no one else needs to action it. Only dismiss an alert once you've actually checked it — dismissing is not the same as fixing. If the same alert appears many times, often because it comes from a shared template or component, the tooltip may offer to dismiss it across the whole page or site in one step. What the checker can and can't catch ------------------------------------ The checker is an automated safety net for common, machine-detectable problems. It can tell when alternative text is missing, but it can't tell whether the text you've written is meaningful. It also can't judge things like whether colour alone is being used to convey meaning, or whether your content reads in a sensible order. Treat it as a helpful first pass that complements — rather than replaces — writing accessible content and any formal accessibility review. Checking content on published pages ----------------------------------- As well as running in the editor, the checker can appear on your published pages when you view them while signed in, if your site is configured to show it there. When it is, you can review issues in the context of the live page and jump back into editing to fix them. If you don't see it on published pages, your site may only run the checker inside the editor. If you don't see the checker ---------------------------- Accessibility checking is configured per content type by an administrator, and the options to dismiss alerts ("Ignore" and "Mark OK") are controlled by your user permissions. If the button isn't available where you're editing, or you can't dismiss an alert you've reviewed, ask your site administrator, or contact the District support team. See also: [Using the WYSIWYG editor](/articles/using-the-wysiwyg-editor), [Applying basic and custom styles](/articles/applying-basic-and-custom-styles) [ Back to articles ](/articles) Table of contents ----------------- © 2026 [District](https://www.district.au)