WordPress
Sample: Sentinela scan of our owner's site
Published 11 Oct 2026
This is a sample, not a client case study. shandongtire.com belongs to Sentinela’s owner, who agreed to publish the result. It shows what a report looks like; it is not a testimonial, and no fixes have shipped yet.
What was tested
- Site: shandongtire.com, a WordPress site for a tire brand.
- Scan: a Monitoring scan on the Starter plan, started by hand on 11 October 2026 at 11:23 UTC. It finished in about 6 minutes, including the AI-assisted review.
- Target: WCAG 2.2 level AA.
- Pages: 10, each rendered at a desktop and a mobile width: the home page, the about page, the contact page, the news page, two product listings (at an English and a Vietnamese address) and four product pages. The contact page is also published at a second address with the same content; the scan tested it once and the results apply to both.
- Purchase flow: the keyboard purchase flow was not part of this scan, so the score counts those 10 pages only. That flow runs on Shopify and WooCommerce stores, from a product’s add-to-cart button to the start of checkout; this site has no shop, so the flow did not run.
- Checks: axe, Sentinela’s keyboard test and accessibility-tree check, then an AI-assisted review of every page. A person has not reviewed the findings yet.
These results come from automated testing, which detects only some accessibility issues. They are not a full audit and do not determine legal conformance. A full audit adds a person who reviews every finding and runs the manual checks listed on our method page.
The score: 81.1 out of 100
Each page starts at 100 and each distinct issue subtracts its severity weight times our confidence in it; the site score is the average of the pages (score version 3, as described on /method). The dashboard shows it rounded to 81. It is not a percentage of WCAG conformance.
Only the automated checks count toward the score. AI-assisted suggestions are shown separately and do not change it until a person confirms them.
What the scan found
24 open issues from the automated checks. One issue is one problem on one element: the same issue found at both widths counts once, and an issue found on most pages, such as one in the header, counts once for the whole site.
| Severity | Open issues |
|---|---|
| Critical | 4 |
| Serious | 17 |
| Moderate | 3 |
| Minor | 0 |
| Total | 24 |
What the 24 issues are:
| Problem | Issues | Where |
|---|---|---|
| Low text contrast in the header (site-wide) | 1 | 10 of 10 pages |
| Menu links that do not say whether their submenu is open (site-wide) | 3 | 10 of 10 pages each |
| Images without a text alternative | 4 | One on each product page |
| Low text contrast on the news cards | 8 | 4 on the home page, 4 on the news page |
| Keyboard focus that is not visible | 7 | 5 contact form fields, and the search box on both product listings |
| A video that may have no captions | 1 | The home page |
Four of them are site-wide issues, each found on 10 of 10 pages: the phone number in the header, whose text is too light against its background, and three main-menu links that open a submenu.
AI-assisted suggestions, shown apart
The AI-assisted review added 13 suggestions. They are not part of the 24 and do not count toward the score, because a person has not reviewed them yet. All 13 are marked serious, with a confidence between 0.5 and 0.8. For example: the map image on the contact page has alt text in Vietnamese on an English page; a specification table is published as a picture; names and titles look like headings but are not marked up as headings; and the product search field relies on placeholder text, with no visible label.
WCAG criteria
The report marks 7 of the 55 WCAG 2.2 level A and AA criteria with issues: 5 as Issues found and 2 (1.3.1 and 3.3.2) as Issues found (AI suggestion):
| Criterion | Found by |
|---|---|
| 1.1.1 Non-text Content | Automated checks and AI-assisted suggestions |
| 1.2.2 Captions (Prerecorded) | Automated checks |
| 1.3.1 Info and Relationships | AI-assisted suggestions only |
| 1.4.3 Contrast (Minimum) | Automated checks |
| 2.4.7 Focus Visible | Automated checks |
| 3.3.2 Labels or Instructions | AI-assisted suggestions only |
| 4.1.2 Name, Role, Value | Automated checks and AI-assisted suggestions |
AI-assisted suggestions are pending review by a person. Of the other 48 criteria, the report marks 19 “No issues detected by automated checks” and 3 “Needs human review”; the remaining 26 are not tested automatically. None of this is a statement that a criterion is met.
What to fix first
In the order the report gives:
- Images without a text alternative (critical, WCAG 1.1.1). On each of the four product pages, the main specification image has no alt text, so screen readers skip it and its specifications are lost. Fix: alt text that summarizes the key specifications, or the same data in an HTML table beside the image.
- Low text contrast in the header (serious, WCAG 1.4.3), site-wide on 10 of 10 pages. The phone number is too light against its background to read easily. Fix: darken the text or its background.
- Low text contrast on the news cards (serious, WCAG 1.4.3), on the home page and the news page. Light text such as dates and labels. Fix: darken the text or its background.
- Keyboard focus that is not visible (serious, WCAG 2.4.7), on the contact form’s fields and the product search box. When you move through the page with the Tab key, nothing shows where you are. Fix: a visible focus style on every control.
- A video that may have no captions (serious, WCAG 1.2.2). The home page video has no captions track. Captions may be part of the video itself, which a person needs to check. Fix: a captions track, or captions in the video.
- Menu links that do not say whether their submenu is open (moderate, WCAG 4.1.2),
site-wide on 10 of 10 pages. “Products” and two of its sub-items open a submenu but do not
expose an expanded state, so a screen reader cannot tell whether it is open or closed. Fix:
set
aria-expandedon the link and update it when the submenu opens or closes.
What happens next
Against the previous scan, this one found 0 new issues; all 24 are still open. The site is on a monthly schedule. When fixes ship and a later scan confirms them, this page gets a before-and-after section with the numbers from that scan.