What it checks
31 checks mapped to 15 WCAG 2.2 success criteria. Checks marked flagged for review are ones no tool can decide alone — they are surfaced with the evidence, and a person decides.
| Check | Severity | WCAG 2.2 | Result |
|---|---|---|---|
| Text contrast is below the WCAG AA minimum Low-contrast text is unreadable for many people with low vision, and for anyone on a dim screen or in sunlight. |
critical | 1.4.3 AA | Decided automatically |
| Image has no alternative text Screen-reader users get nothing but the word "image" where this picture is, so any information it carries is lost. |
critical | 1.1.1 A | Decided automatically |
| Link has no readable text A link with no text is announced only as its URL, or skipped entirely. |
critical | 2.4.4 A 4.1.2 A |
Decided automatically |
| Bold text used instead of a heading Bold text looks like a heading but is not one, so it never appears in the heading list a screen-reader user navigates by. |
serious | 1.3.1 A | Flagged for review |
| Heading has no text An empty heading is announced as a heading with nothing in it, which breaks navigation by headings. |
serious | 1.3.1 A 2.4.6 AA |
Decided automatically |
| Heading level is skipped Screen-reader users navigate by heading level; a jump from H2 straight to H4 makes the page look like it has missing sections. |
serious | 1.3.1 A | Decided automatically |
| Alternative text does not describe the image Alt text like "image1.png" or "screenshot" tells a screen-reader user nothing about what the image shows. |
serious | 1.1.1 A | Decided automatically |
| Link text does not say where it goes Screen-reader users often pull up a list of every link on the page; a list of "click here" entries is unusable. |
serious | 2.4.4 A | Decided automatically |
| Status lozenge has no readable text A lozenge is announced by its text; with none, its colour is the only thing carrying the meaning and a screen reader conveys nothing. |
serious | 1.4.1 A 1.1.1 A |
Decided automatically |
| Table has no header row Without header cells a screen reader reads a wall of values with no way to tell which column each one belongs to. |
serious | 1.3.1 A | Decided automatically |
| Instructions rely on colour alone A reader who cannot distinguish the colour, or who is using a screen reader, has no way to tell which items you mean. |
moderate | 1.4.1 A | Flagged for review |
| Embedded content has no accessible name Embedded frames are announced by their title; without one, a screen-reader user hears only "frame". |
moderate | 4.1.2 A 2.4.1 A |
Flagged for review |
| Collapsible section has no label An unlabelled expand is announced only as a button, so a keyboard user cannot tell what opening it will reveal. |
moderate | 2.4.6 AA 4.1.2 A |
Decided automatically |
| Dashes or numbers used instead of a list A hand-typed list is read as loose sentences, so a screen-reader user never hears how many items there are or where the list ends. |
moderate | 1.3.1 A | Flagged for review |
| H1 used inside the page body Confluence already renders the page title as the only H1, so a second H1 in the body gives the page two competing titles. |
moderate | 1.3.1 A | Decided automatically |
| Same link text points to different pages Two links reading "guidelines" that lead to different pages are indistinguishable in a screen reader’s link list. |
moderate | 2.4.4 A 2.4.9 AAA |
Decided automatically |
| Bare URL used as link text A screen reader reads a raw URL character by character, which is slow and tells the listener very little. |
moderate | 2.4.4 A | Decided automatically |
| Video or audio may need captions or a transcript Pre-recorded audio and video need captions and a text alternative, and a page cannot prove it has them on its own. |
moderate | 1.2.1 A 1.2.2 A |
Flagged for review |
| Passage in a different script A screen reader keeps using the page language, so text in another script is read with the wrong pronunciation rules. |
moderate | 3.1.2 AA | Flagged for review |
| Page title does not describe the page The title is the first thing a screen reader announces and the label the page carries in search, tabs and link lists. |
moderate | 2.4.2 A | Decided automatically |
| Header cell is empty An empty header leaves every cell in that column without a label when it is read out. |
moderate | 1.3.1 A | Decided automatically |
| Table uses merged cells Merged cells break the grid a screen reader uses to pair each value with its header, so the reading order can come out scrambled. |
moderate | 1.3.1 A | Flagged for review |
| Table nested inside another table Nested tables are very hard to navigate with a keyboard or screen reader, which usually announces them as one confusing grid. |
moderate | 1.3.1 A | Decided automatically |
| Long run of capital letters Some screen readers spell out all-caps words letter by letter, and blocks of capitals are slower for everyone to read. |
advisory | 3.1.5 AAA | Flagged for review |
| Two headings have the same text Screen-reader users navigate by jumping between headings; identical headings are impossible to tell apart in that list. |
advisory | 2.4.6 AA | Decided automatically |
| Heading reads as a paragraph Long headings are hard to scan in a screen reader’s heading list, which is how many users find their way around a page. |
advisory | 2.4.6 AA | Decided automatically |
| Alternative text starts with "image of" Screen readers already announce that the element is an image, so the prefix is read out twice. |
advisory | 1.1.1 A | Decided automatically |
| Alternative text is very long A screen reader reads alt text in one uninterrupted run, so anything past roughly 150 characters is hard to follow. |
advisory | 1.1.1 A | Decided automatically |
| Text is justified Justified text creates uneven rivers of white space that people with dyslexia find hard to track. |
advisory | 1.4.8 AAA | Decided automatically |
| Very long paragraph A screen reader reads a paragraph as one unbroken block, and long blocks are hard to follow or re-find. |
advisory | 3.1.5 AAA | Flagged for review |
| Another page in this space has the same title Identical titles are impossible to tell apart in search results, breadcrumbs and link lists. |
advisory | 2.4.2 A | Decided automatically |
| Blank lines used for spacing A screen reader announces every empty line, so stacks of them are read out as meaningless pauses. |
advisory | 1.3.1 A | Flagged for review |
| Table appears to be used for layout A table announces rows and columns that carry no meaning here, which slows a screen-reader user down for no benefit. |
advisory | 1.3.1 A | Flagged for review |
Severity, and what it means for the score
Every page gets a score out of 100. A critical issue costs 15 points, serious 8, moderate 3, and advisory 1. A page is reported as conforming when it has no critical or serious failure at your target level — advisory findings never block a conformance claim.