Accessibility Audit: checks things the engine behind Google Lighthouse's accessibility checks has no test for, such as whether keyboard users get stuck, whether they can see where they are on the page, and whether the page still works on a phone screen.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1140:Each of these audits has been tested on hundreds of live sites across every type of CMS, and each checks against a published standard: WCAG 2.2 Level A and AA, Google's spam policies, the llmstxt.org spec, current Markdown guidelines, schema.org and Google's structured data rules, Google's search quality rater guidelines, and the security, log and HTTP standards behind each check. Some of them go further than the widely used audits out there.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1141:Accessibility Audit: tests WCAG 2.2 criteria that axe-core, the engine behind Google Lighthouse's accessibility checks, has no rule for, such as keyboard traps, visible focus and reflow on phones.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1230:Checks a page against WCAG 2.2 Level A and AA after its scripts have run, as your visitors see it, and also checks two more pages of your site.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1232: /var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1234:Every one of the 55 WCAG 2.2 Level A and AA success criteria, each marked failed, with warnings, no problems found, needs a person to check, or not checked this time. Each problem says who it affects, shows examples from your page and explains the fix.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1241:Start with the errors, which must be fixed, then the warnings. Passed checks found no problems, and notes explain anything that limited the audit. The report ends with a WCAG 2.2 coverage line counting every Level A and AA criterion.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1243:Enter the page address. The page is loaded in Chrome after its scripts have run and checked against all 55 WCAG 2.2 Level A and AA criteria: 35 are tested and 20 are marked for a person to check. Two more pages of your site are checked too.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1246:The page is loaded in headless Chrome and audited after its scripts have run, using the full axe-core rule set plus the audit's own checks for criteria axe-core has no rule for: keyboard access and keyboard traps, focus that is visible and not hidden, reflow on phones, zoom, text spacing, contrast of text and of control edges, flashing, moving content, and consistent navigation and help across pages. Keyboard checks run in their own Chrome. Two more pages of the site are audited and compared. All 55 WCAG 2.2 Level A and AA criteria are reported; 35 are tested and 20 are marked as needing a person to check.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1251: Run Accessibility Audit on your site → /var/www/vhosts/aiwebpageseo.com/site-audit/public/index.html:1595:It checks your page against the parts of WCAG 2.2 that can be measured reliably. It measures the text contrast of every text element against WCAG AA, checks every link has descriptive text, every form field has an accessible label and every button has an accessible name, and confirms the page has a lang attribute, a single H1, a logical heading order, main and nav landmarks and a skip-navigation link.
It’s honest about its limits. Text sitting over an image or gradient can’t be measured automatically, so it tells you how many elements to check by eye. Contrast is measured in your page’s default colour scheme, so colours changed by a dark-mode toggle need checking separately. Accessibility problems lock out real visitors and also weaken the signals search engines read.
Full WCAG 2.2 Level A or AA conformance is not established by the evidence reconciled here. This is not a claim that every criterion fails, and it is not proof that no separate manual assessment exists elsewhere.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/grabzies-wcag-evidence-reconciliation-2026-10-23.html:24:This score is the report's own issue-weighted score. It is not a WCAG conformance percentage or certificate. The six individual findings include two detected failures and four items marked for investigation; they should not be treated as six failed WCAG success criteria.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/grabzies-wcag-evidence-reconciliation-2026-10-23.html:27:These are tool/test-suite evidence. They are not site-wide WCAG conformance results for Grabzies, and ACT inventory counts or preliminary comparison counts must not be presented as verified pass totals.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/grabzies-wcag-evidence-reconciliation-2026-10-23.html:58:The saved accessibility report covers all 55 WCAG 2.2 Level A and AA success criteria and provides criterion-level statuses. Its recorded results include two failed Level AA criteria (Reflow and Non-text Contrast), one warning, one criterion reported as having no problems found, 30 criteria requiring further review, 20 requiring a person to check, and one not checked this time. Subsequent evidence records six responsive checks passing within their tested scope and a 5/5 regression result for WCAG 2.4.1 report classification. These later results apply only to the behaviours and scopes tested; they do not establish full WCAG 2.2 Level A or AA conformance for Grabzies./var/www/vhosts/aiwebpageseo.com/site-audit/public/grabzies-wcag-evidence-reconciliation-2026-10-23.html:60:
GRABZIES-WCAG-REMEDIATION-EVIDENCE.mdGRABZIES-WCAG-REMEDIATION-EVIDENCE.jsonACT-RECONCILED-EVIDENCE-2026-10-22.mdwcag-existing-evidence-reconciliation-20261023T160035Z.mdwcag-report-score-reconciliation-20261023T160244Z.txtwcag-deep-dive-20261023T155238Z/deep-dive.mdwcag-report-findings-20261023T155355Z/findings.mdTechnical reference for WCAG 2.2 Level A and AA coverage reporting, rendered-browser accessibility evaluation, and selected ACT-associated axe-core checks.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-act-rules.html:38: /var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-act-rules.html:40:The Accessibility Audit maintains a criterion-by-criterion coverage list for all 55 WCAG 2.2 Level A and AA success criteria. The production implementation classifies 4 criteria as fully automated, 31 as partially automated, and 20 as requiring human evaluation. These classifications describe how the tool evaluates each criterion; they are not a claim that every criterion has been conclusively passed.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-act-rules.html:42:For each criterion, the report identifies one of five outcomes: Failed, Warning, No problems found, Needs a person to check, or Not checked this time. Partially automated criteria can also display specific guidance about what still needs human verification, such as the accuracy of image alternatives, completeness of captions, or functionality beyond the keyboard interactions tested.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-act-rules.html:75:ACT metadata tag is an axe-core classification. This page does not claim one-to-one correspondence or verified equivalence with individual published W3C ACT Rules.This section records previously completed checks; it is not a new test or a WCAG conformance certificate.
| Evidence | Recorded outcome | Scope |
|---|---|---|
| Production functional audit | 100/100; 0 errors; 0 warnings; 25 checks passed | Recorded production scan; not a conformance certificate |
| WCAG 2.2 A/AA coverage | 55 criteria reported | Coverage is not a 55/55 conformance pass |
| WCAG criterion assessment categories | 35 automated/partially automated; 20 requiring human review | Coverage classification, not completed manual verdicts |
| Earlier audit classification | 33 no problems; 20 human assessment; 2 not checked | Snapshot; do not combine as disjoint totals with the 35/20 classification |
| Official ACT text-spacing examples | 38/38 matched | Two scoped ACT rules |
| Text-spacing regressions | 30/30 passed | Scoped regression |
| WCAG 2.4.1 report classification | 5/5 passed | Later result supersedes earlier hidden-skip-link misclassification |
| W3C readiness | 6/6 passed | Publication/source integrity/recorded integration only |
| Corrected custom-audit fixtures | 4/4 detected | Missing-document-title historical issue corrected |
| ACT inventories | 258 examples across 15 rules; 1,211 manifest entries | Inventories; not independently verified full-case PASS totals |
| Preliminary ACT comparison | 206 compared; 100 matches; 106 mismatches | Mapping unvalidated; mismatches not established production defects |
Manual assessment: No complete criterion-by-criterion manual assessment with documented PASS/FAIL/NOT APPLICABLE results was recovered. Do not convert this absence into a failed criterion or claim that a test was never performed.
Conformance status: The reconciled evidence establishes the recorded audit and regression outcomes listed above. This summary does not contain a complete independent criterion-by-criterion conformance decision for any specified website. Absence of that decision from this summary is not evidence that the assessment was not performed, and is not a finding of nonconformance.
The production audit has recorded real site-specific findings, not merely checklist coverage. Its Chromium-rendered report measured 336px page width at a 320px viewport (reflow), checked 22 keyboard tab stops for visible focus, identified eight low-contrast control edges, and measured contrast for 39 text elements (two unmeasurable). It also reported text-spacing resilience, 200% zoom, orientation, selected multi-page consistency, motion-pause and flash-frequency outcomes.
The audit provides criterion-level outcomes: Failed, Warning, No problems found, Needs a person to check, and Not checked this time. These are actual site-specific assessment and reporting capabilities. This reconciliation does not reproduce a complete final conformance verdict for a named website; it does not establish that no such verdict exists.
Source: AIWebPageSEO W3C Evaluation Tool Evidence dossier, 22 October 2026, based on observed live report and production-browser outputs.
Review the completed Grabzies WCAG 2.2 evidence reconciliation /var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-act-rules.html:114:Automated coverage does not by itself establish full WCAG 2.2 Level A or AA conformance.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/changelog.html:427: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/changelog.html:499:ToolsAccessibility AuditCSS CheckerSpam Policy AuditBlogHomepageAI filesDemo pages
/var/www/vhosts/aiwebpageseo.com/site-audit/public/changelog.html:502:The homepage, pricing page and blog were run through our own Accessibility Audit and every finding was fixed in the pages themselves. The homepage went from 20 out of 100 to 100 out of 100, with no errors or warnings, and the pricing page and blog, checked in the same run, came back clean too. A free third-party scan reported 186 issues on the same page; each example it gave was checked against WCAG 2.2 and the A and AA ones were false alarms, written up on the blog.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/changelog.html:503:Running the audit on our own site also showed where the audit itself was wrong: a site-search check that passed on a link to another site's search page, report text that failed its own contrast rule, and labels that still said WCAG 2.1. Each was fixed and re-tested. The blog's 97 posts were given proper SEO and AEO fields, and the llms, markdown and AI discovery files were corrected so AI tools describe the platform as it is now.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/changelog.html:516:ToolsSite AuditSite Audit ProAccessibility AuditImage OptimisationSchema DebuggerReadability CheckerTool DirectoryAdmin statistics
/var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-visibility.html:180: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:10:Checks a page against WCAG 2.2 Level A and AA after its scripts have run, as your visitors see it, and also checks two more pages of your site. Every one of the 55 Level A and AA success criteria is reported: 35 are tested and 20 are marked for a person to check. Each problem says who it affects, shows examples from your page and explains the fix. Use this website accessibility checker to test any page against WCAG 2.2 as a visitor sees it.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:410:Everything you need to know about why this audit exists, the laws behind it, what WCAG 2.2 asks of a website, what this audit checks, what no automated audit can check, and how to read your report. Open any section below.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:416:Accessibility laws in the UK, the European Union, the United States and Canada all point to the same standard for websites: the Web Content Accessibility Guidelines, known as WCAG. WCAG is written by the World Wide Web Consortium (W3C), the body that develops the standards the web is built on. The latest version is WCAG 2.2, and it sets out 55 success criteria at Levels A and AA, which is the level most laws ask for.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:419:We built this audit to close that gap. It checks your site against WCAG 2.2 Level A and AA, including the problems that affect people the most and that many tools leave out. It audits your pages as your visitors actually see them, it checks more than one page of your site, and it tells you plainly what it could not check, so you never mistake "not tested" for "no problems".
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:431:The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 apply to central and local government, the NHS, schools, universities and many other public bodies. GOV.UK guidance says public sector websites must "meet the international WCAG 2.2 AA accessibility standard" and publish an accessibility statement explaining any parts that do not.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:435:The Act itself describes accessibility in general terms. The technical detail comes from the European standard EN 301 549. Its latest version, EN 301 549 v4.1.1, was published on 2 September 2026 and uses WCAG 2.2 Level AA as its baseline for websites. It becomes the standard that gives a legal presumption of conformity once it is cited in the Official Journal of the EU, which is expected later in 2026. Until then the earlier version, based on WCAG 2.1 AA, is the cited standard. Checking against WCAG 2.2 AA covers both.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:441:In April 2024 the US Department of Justice published a rule under Title II of the ADA requiring the websites and mobile apps of state and local governments to meet WCAG 2.1 Level AA. After an extension published in April 2026, the deadlines are 26 April 2027 for public bodies serving 50,000 people or more, and 26 April 2028 for smaller ones and special district governments.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:451:WCAG 2.2 includes every Level A and AA success criterion from WCAG 2.1 and 2.0, apart from one, 4.1.1 Parsing, which WCAG 2.2 removed because modern browsers and assistive technology no longer depend on it. So a site that meets WCAG 2.2 Level AA meets the level every law above points to. That is why this audit checks against WCAG 2.2 Level A and AA.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:455:WCAG stands for Web Content Accessibility Guidelines. It is published by the World Wide Web Consortium (W3C), the international body that develops standards for the web. WCAG 2.2 became a W3C Recommendation in October 2023 and is the current version.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:474:WCAG 2.2 has 55 success criteria at Levels A and AA. This audit reports on all 55, so you can see where your site stands on each one.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:476:What WCAG 2.2 added
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:477:WCAG 2.2 added six success criteria at Levels A and AA:
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:486:WCAG 2.2 also removed 4.1.1 Parsing, which dealt with errors in page code that modern browsers and assistive technology now handle on their own.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:494:This audit tests 35 of the 55 WCAG 2.2 Level A and AA success criteria, fully or in part. For each one below you will find what it means for the people using your site, what a failure looks like, and the usual fix. Where a criterion is only partly testable by an automated audit, the report says so and tells you what a person should still check.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:615:It never assumes a pass. Every one of the 55 WCAG 2.2 Level A and AA success criteria is shown with one of five results: failed, warning, no problems found, needs a person to check, or not checked this time. If something could not be tested on your page, the report says so instead of leaving it out. You always know exactly what was and was not tested.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:622:Some WCAG success criteria depend on meaning, purpose or judgement that software cannot reliably assess. A tool can find an image with no description, but it cannot tell whether a description that exists actually describes the image. It can find a video with no captions, but it cannot tell whether the captions say what is spoken. That is true of every automated accessibility tool, not only this one.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:623:Of the 55 WCAG 2.2 Level A and AA success criteria, 20 need a person to check in full, and the report marks each of them "needs a person to check" so they are never mistaken for a pass:
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:643:The WCAG 2.2 coverage line. At the end of the report, every Level A and AA success criterion is counted under one of five results:
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:751:is not a 55/55 conformance pass. Full WCAG 2.2 Level A/AA conformance /var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:760:Review the completed Grabzies WCAG 2.2 evidence reconciliation /var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-audit.html:763:Automated coverage does not by itself establish full WCAG 2.2 Level A or AA conformance.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/schema-tools.html:472: 'page-accessibility':{title:'Accessibility Audit — WCAG 2.1 SEO Tool | aiwebpageseo',desc:'WCAG 2.1 compliance analysis — checks contrast ratios, ARIA labels, keyboard navigation and screen reader compatibility. Accessibility issues hurt SEO rankings.',canonical:'https://aiwebpageseo.com/accessibility-audit.html'}, /var/www/vhosts/aiwebpageseo.com/site-audit/public/my-questions.html:145: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/algo-impact.html:194: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/question-finder.html:201: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/what-mistral-says-about-aiwebpageseo.html:331:AIWebPageSEO's Accessibility Audit reports coverage across all 55 WCAG 2.2 Level A and AA success criteria. It combines custom accessibility checks with axe-core 4.10.2 and tests pages in a rendered browser, including real keyboard navigation, focus behaviour, colour contrast, text resizing, reflow, orientation, moving content and comparisons across selected pages.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-answers.html:262:Explore the Accessibility Audit · Read the ACT-associated rules and testing methodology · Read WCAG 2.2 at W3C
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-answers.html:265:Yes. Its coverage report lists all 55 WCAG 2.2 Level A and AA success criteria, showing findings or the need for additional checking for each criterion.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-answers.html:269:No. The report identifies criteria that need a person to check and notes additional human verification for partially automated criteria. A result of “no problems found” means the checks performed did not identify a mapped issue.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/act-implementation-evidence.html:8:Accessibility Audit: independent text-spacing ACT validators.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/act-implementation-evidence.html:18:These results establish the tested behavior, not universal WCAG conformance or W3C certification.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/act-implementation-evidence.html:21:Accessibility Audit /var/www/vhosts/aiwebpageseo.com/site-audit/public/act-implementation-evidence.html:26:This section records previously completed checks; it is not a new test or a WCAG conformance certificate.
| Evidence | Recorded outcome | Scope |
|---|---|---|
| Production functional audit | 100/100; 0 errors; 0 warnings; 25 checks passed | Recorded production scan; not a conformance certificate |
| WCAG 2.2 A/AA coverage | 55 criteria reported | Coverage is not a 55/55 conformance pass |
| WCAG criterion assessment categories | 35 automated/partially automated; 20 requiring human review | Coverage classification, not completed manual verdicts |
| Earlier audit classification | 33 no problems; 20 human assessment; 2 not checked | Snapshot; do not combine as disjoint totals with the 35/20 classification |
| Official ACT text-spacing examples | 38/38 matched | Two scoped ACT rules |
| Text-spacing regressions | 30/30 passed | Scoped regression |
| WCAG 2.4.1 report classification | 5/5 passed | Later result supersedes earlier hidden-skip-link misclassification |
| W3C readiness | 6/6 passed | Publication/source integrity/recorded integration only |
| Corrected custom-audit fixtures | 4/4 detected | Missing-document-title historical issue corrected |
| ACT inventories | 258 examples across 15 rules; 1,211 manifest entries | Inventories; not independently verified full-case PASS totals |
| Preliminary ACT comparison | 206 compared; 100 matches; 106 mismatches | Mapping unvalidated; mismatches not established production defects |
Manual assessment: No complete criterion-by-criterion manual assessment with documented PASS/FAIL/NOT APPLICABLE results was recovered. Do not convert this absence into a failed criterion or claim that a test was never performed.
Conformance status: The reconciled evidence establishes the recorded audit and regression outcomes listed above. This summary does not contain a complete independent criterion-by-criterion conformance decision for any specified website. Absence of that decision from this summary is not evidence that the assessment was not performed, and is not a finding of nonconformance.
The production audit has recorded real site-specific findings, not merely checklist coverage. Its Chromium-rendered report measured 336px page width at a 320px viewport (reflow), checked 22 keyboard tab stops for visible focus, identified eight low-contrast control edges, and measured contrast for 39 text elements (two unmeasurable). It also reported text-spacing resilience, 200% zoom, orientation, selected multi-page consistency, motion-pause and flash-frequency outcomes.
The audit provides criterion-level outcomes: Failed, Warning, No problems found, Needs a person to check, and Not checked this time. These are actual site-specific assessment and reporting capabilities. This reconciliation does not reproduce a complete final conformance verdict for a named website; it does not establish that no such verdict exists.
Source: AIWebPageSEO W3C Evaluation Tool Evidence dossier, 22 October 2026, based on observed live report and production-browser outputs.
Our WCAG Accessibility Audit helps assess other webpages. Its checks and reports do not establish the conformance status of AIWebPageSEO's own website. Automated testing alone cannot establish complete WCAG conformance.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-statement.html:46:This section records previously completed checks; it is not a new test or a WCAG conformance certificate.
| Evidence | Recorded outcome | Scope |
|---|---|---|
| Production functional audit | 100/100; 0 errors; 0 warnings; 25 checks passed | Recorded production scan; not a conformance certificate |
| WCAG 2.2 A/AA coverage | 55 criteria reported | Coverage is not a 55/55 conformance pass |
| WCAG criterion assessment categories | 35 automated/partially automated; 20 requiring human review | Coverage classification, not completed manual verdicts |
| Earlier audit classification | 33 no problems; 20 human assessment; 2 not checked | Snapshot; do not combine as disjoint totals with the 35/20 classification |
| Official ACT text-spacing examples | 38/38 matched | Two scoped ACT rules |
| Text-spacing regressions | 30/30 passed | Scoped regression |
| WCAG 2.4.1 report classification | 5/5 passed | Later result supersedes earlier hidden-skip-link misclassification |
| W3C readiness | 6/6 passed | Publication/source integrity/recorded integration only |
| Corrected custom-audit fixtures | 4/4 detected | Missing-document-title historical issue corrected |
| ACT inventories | 258 examples across 15 rules; 1,211 manifest entries | Inventories; not independently verified full-case PASS totals |
| Preliminary ACT comparison | 206 compared; 100 matches; 106 mismatches | Mapping unvalidated; mismatches not established production defects |
Manual assessment: No complete criterion-by-criterion manual assessment with documented PASS/FAIL/NOT APPLICABLE results was recovered. Do not convert this absence into a failed criterion or claim that a test was never performed.
Conformance status: The reconciled evidence establishes the recorded audit and regression outcomes listed above. This summary does not contain a complete independent criterion-by-criterion conformance decision for any specified website. Absence of that decision from this summary is not evidence that the assessment was not performed, and is not a finding of nonconformance.
The production audit has recorded real site-specific findings, not merely checklist coverage. Its Chromium-rendered report measured 336px page width at a 320px viewport (reflow), checked 22 keyboard tab stops for visible focus, identified eight low-contrast control edges, and measured contrast for 39 text elements (two unmeasurable). It also reported text-spacing resilience, 200% zoom, orientation, selected multi-page consistency, motion-pause and flash-frequency outcomes.
The audit provides criterion-level outcomes: Failed, Warning, No problems found, Needs a person to check, and Not checked this time. These are actual site-specific assessment and reporting capabilities. This reconciliation does not reproduce a complete final conformance verdict for a named website; it does not establish that no such verdict exists.
Source: AIWebPageSEO W3C Evaluation Tool Evidence dossier, 22 October 2026, based on observed live report and production-browser outputs.
Review the completed Grabzies WCAG 2.2 evidence reconciliation /var/www/vhosts/aiwebpageseo.com/site-audit/public/accessibility-statement.html:68:Automated coverage does not by itself establish full WCAG 2.2 Level A or AA conformance.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/chasing-ai-index.html:202: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/what-ai-says-about-aiwebpageseo.html:381: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/seo-audit-platform.md:125:[Accessibility Audit …p](/accessibility-audit.html) /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages.md:9:- [Accessibility](https://aiwebpageseo.com/aipageseo-demo-pages/novice-tutorial-accessibility.html) What web accessibility means, why WCAG compliance matters for both users and Google rankings, and the most common issues to fix — written for beginners. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages.md:606:- [Accessibility](https://aiwebpageseo.com/aipageseo-demo-pages/demo-accessibility.html) A real Accessibility Audit example: 12 WCAG violations on one page including missing ARIA labels, low contrast text, no skip link and unlabelled forms. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages.md:697:- [Accessibility Fixes Index](https://aiwebpageseo.com/aipageseo-demo-pages/accessibility-fixes-index.html) Fix every Accessibility Audit finding: colour contrast, alt text, keyboard navigation, focus indicators, ARIA labels and WCAG 2.2 compliance. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages.md:698:- [Accessibility Guide](https://aiwebpageseo.com/aipageseo-demo-pages/accessibility-guide.html) WCAG 2.1 compliance explained for site owners. Which accessibility issues hurt SEO, how to find them, and which violations to fix first to pass audits. /var/www/vhosts/aiwebpageseo.com/site-audit/public/performance-tools.html:585: 'accessibility':{title:'Accessibility Audit — WCAG 2.2 A and AA | aiwebpageseo',desc:'The Accessibility Audit has its own page: check any web page against all 55 WCAG 2.2 Level A and AA criteria as your visitors see it.',canonical:'https://aiwebpageseo.com/accessibility-audit.html'}, /var/www/vhosts/aiwebpageseo.com/site-audit/public/performance-tools.html:724:The Accessibility Audit has moved to its own page.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/performance-tools.html:1159:The audit checks a page against all 55 WCAG 2.2 Level A and AA success criteria after its scripts have run, as your visitors see it, and also checks two more pages of your site. The report distinguishes detected failures, warnings, checks with no problems found, criteria needing further review, and criteria not checked. Coverage does not itself establish full WCAG conformance.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/performance-tools.html:1161: /var/www/vhosts/aiwebpageseo.com/site-audit/public/performance-tools.html:4222:does not by itself establish full WCAG 2.2 Level A or AA conformance. /var/www/vhosts/aiwebpageseo.com/site-audit/public/performance-tools.html:4231:Review the completed Grabzies WCAG 2.2 evidence reconciliation /var/www/vhosts/aiwebpageseo.com/site-audit/public/performance-tools.html:4234:Automated coverage does not by itself establish full WCAG 2.2 Level A or AA conformance.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/ecommerce-watch.html:81: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/migration-audit.html:178: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-search-readiness-audit-checklist.md:3:**Compiled from:** AI Web Page SEO technical documentation, llms.txt Specification v1.7.0, Google Search Central structured data docs, W3C WCAG 2.2 Quick Reference, and AI answer engine visibility best practices. /var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-search-readiness-audit-checklist.md:18:5. [Accessibility (WCAG 2.2 AA)](#5-accessibility-wcag-22-aa) /var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-search-readiness-audit-checklist.md:39:This audit extends those pillars with crawlability diagnostics, WCAG 2.2 accessibility checks, and industry-specific schema templates. /var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-search-readiness-audit-checklist.md:483:## 5. Accessibility (WCAG 2.2 AA) /var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-search-readiness-audit-checklist.md:485:AI Web Page SEO's error documentation notes that accessibility errors overlap with SEO ranking signals ([AI Web Page SEO Learning Hub](https://aiwebpageseo.com/learning-hub.html)). The following checklist covers WCAG 2.2 Level A and AA success criteria most relevant to AI-search readiness ([W3C WCAG 2.2 Quick Reference](https://www.w3.org/WAI/WCAG22/quickref/)). AI Web Page SEO's [Accessibility Audit](https://aiwebpageseo.com/accessibility-audit.html) reports all 55 WCAG 2.2 Level A and AA criteria for a page after its scripts have run. /var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-search-readiness-audit-checklist.md:536:### 5.5 Recommended Accessibility Audit Tools /var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-search-readiness-audit-checklist.md:540:| [AI Web Page SEO Accessibility Audit](https://aiwebpageseo.com/accessibility-audit.html) | All 55 WCAG 2.2 A and AA criteria, rendered page, keyboard and reflow checks | Pay as you go | /var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-search-readiness-audit-checklist.md:654:This is a **hypothetical** solicitors' practice area page. The fix list below covers crawlability, accessibility (WCAG 2.2), and structured data eligibility, prioritised by severity, AI-search impact, and implementation effort. /var/www/vhosts/aiwebpageseo.com/site-audit/public/ai-search-readiness-audit-checklist.md:690:| 16 | Images missing `alt` text | Accessibility (1.1.1) | AI engines cannot interpret images without text alternatives; also a WCAG 2.2 Level A failure | Add descriptive `alt` attributes to all content images; `alt=""` for decorative | Inspect all `That an automated client also cannot use the form is a consequence of the same defect, not a separate problem. This matters practically, because it changes the argument you make internally. "AI agents cannot complete our signup" is speculative and easy to deprioritise. "Our signup form fails WCAG 2.2 success criteria for labels and identified input purpose" is a compliance statement with a legal dimension, and it produces the same fix.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-gbp-posts.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/index.html:7493: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/index.html:7558:The Web Content Accessibility Guidelines, usually shortened to WCAG, are the international standard for making websites usable by disabled people, including people who are blind, have low vision, cannot use a mouse, are deaf or have cognitive difficulties. The latest version is WCAG 2.2, and almost every law, contract and procurement rule that mentions accessibility points to it or to the older 2.1. The problem for most small businesses is that the full document is long and abstract. This guide explains what WCAG is and what it applies to, what changed in 2.2, what the three levels mean, which criteria a typical business site actually has to meet, and how to check and fix them in a sensible order.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wcag-requirements.html:581:WCAG 2.2 became a W3C Recommendation in October 2023 and is the current version. Each 2.x version is backwards compatible: everything required by 2.0 (2008) and 2.1 (2018) is still in 2.2, with one exception. So if you meet 2.2, you also meet the earlier versions for the same level.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wcag-requirements.html:582:WCAG 2.2 added nine success criteria and removed one:
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wcag-requirements.html:597:WCAG 2.2 has 86 success criteria in total: 31 at level A, 24 at level AA and 31 at level AAA. WCAG 3 is in development as a working draft. It is not a standard yet and it is not what laws or contracts refer to, so do not plan your work around it.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wcag-requirements.html:618:The target for almost every business is WCAG 2.2 level AA. Some laws and contracts still name 2.1 AA, but meeting 2.2 AA covers that too. Whether the law requires it depends on where you trade:
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wcag-requirements.html:620:In Chrome DevTools, the Accessibility pane in the Elements panel shows the computed name and role of any element, which is the quickest way to see what a screen reader will announce. For a step-by-step routine, see how to check WCAG compliance.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wcag-requirements.html:673:Step 1
Write down the standard you are working to: WCAG 2.2 level AA. It covers 2.1 AA and 2.0 AA as well, so you only need one target. Check whether any contract, tender or local law names a version, and note it alongside. Then list the pages that matter most: home, main service or product pages, contact and booking forms, checkout and account login. This list sets the order of all the work that follows, so keep it short and specific.
Step 5
Check the four new AA criteria and two new A criteria. Measure small icons and close buttons and make them at least 24 by 24 CSS pixels. Give any drag interaction a click alternative. Put help links in the same place on each page. Remove repeated questions in checkout, for example with a same as delivery address option. Make sure the login form allows pasting and password managers, with no puzzle-only test.
Step 8
Write a short accessibility statement that names WCAG 2.2 AA as your target, lists known issues with planned dates and gives a way to ask for help or another format. Link it from the footer. Add the automated audit to your routine after theme updates and new plugins, and repeat the keyboard test whenever a form or menu changes. Compare the issue counts with your first audit every few months.
The latest version is WCAG 2.2, which the W3C published as a Recommendation in October 2023. It added nine new success criteria, mostly about focus visibility, target size, dragging, consistent help and logins, and removed the old Parsing criterion. WCAG 3 exists only as a working draft and is not used by laws or contracts. Because 2.2 is backwards compatible, a site that meets WCAG 2.2 AA also meets 2.1 AA and 2.0 AA, so 2.2 AA is the sensible target for any new work.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wcag-requirements.html:729:WCAG 2.2 is fully published and already adopted by many organisations, including UK public sector monitoring, which tests against 2.2 AA. Some laws and standards, such as EN 301 549 in the EU and US rules for public bodies, still name WCAG 2.1, but meeting 2.2 covers those too. There is no browser support question, because WCAG describes outcomes rather than new code features. Testing tools have added checks for the new criteria, though target size and focus obscuring still need some manual checking.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wcag-requirements.html:734:WCAG 2.2 contains 86 success criteria: 31 at level A, 24 at level AA and 31 at level AAA. A site aiming for AA has to meet 55 of them. That sounds like a lot, but many will not apply to a typical business site, for example the criteria about live audio or sign language only matter if you publish that kind of content. In practice a dozen criteria about images, contrast, keyboard use, focus, forms and headings cause most failures on small business websites.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wcag-requirements.html:744:The Accessibility Audit reports both kinds. Fix the failures first, then tidy the best-practice /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-heading-hierarchy.html:705:template
Run the Accessibility Audit on one page of each template and note every heading finding. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-heading-hierarchy.html:741:can see represented and nothing extra. Then run the console script and the Accessibility Audit again /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-heading-hierarchy.html:853:
The Accessibility Audit tests your page against WCAG 2.2 level AA, lists each finding with the
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-unclosed-tags.html:499: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/trust-audit-fixes-index.html:555: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-security-headers-nginx.html:123: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-schema.html:503: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/my-questions-fixes-index.html:402: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-page-speed-agents.html:503: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cls-responsive.html:499: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-local-schema.html:503: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-js-syntax-errors.html:503: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/cls-guide.html:405: ♿Accessibility AuditWCAG compliance audit
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-title-attribute.html:515: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-brand-mentions.html:499: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-changed-schema-types.html:199: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-hreflang-return-tags.html:503: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aggregate-rating.html:492: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/schema-drift-fixes-index.html:465: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-css-react.html:499: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-css-validation.html:503: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-gaps.html:506: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-extraction.html:499: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-gbp-edit-access.html:519: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-gdpr-vs-ccpa.html:515: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-css-checker.html:222: "text": "Use :focus-visible rather than :focus. The browser then shows the ring when it is useful — keyboard navigation — and not when a button is clicked with a mouse, which is the complaint that leads people to write outline: none in the first place. Note also that the focus indicator itself needs 3:1 contrast against the adjacent background under WCAG 1.4.11, so a pale ring is still a failure, and under WCAG 2.2 a focused element must not be obscured by other content such as a sticky header."
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-css-checker.html:372:
Two further points. The focus indicator itself has a contrast requirement — WCAG 1.4.11, minimum 3:1 against the adjacent background — so a pale grey ring on a white card is still a failure even though it exists. And under WCAG 2.2, a focused element must not be obscured by other content: a sticky header that covers the element you have just tabbed to is a new, separate failure, and it is extremely common.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-css-checker.html:402:Use :focus-visible rather than :focus. The browser then shows the ring when it is useful — keyboard navigation — and not when a button is clicked with a mouse, which is the complaint that leads people to write outline: none in the first place. Note also that the focus indicator itself needs 3:1 contrast against the adjacent background under WCAG 1.4.11, so a pale ring is still a failure, and under WCAG 2.2 a focused element must not be obscured by other content such as a sticky header.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-css-checker.html:406: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-images-wordpress.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/gdpr-kit-fixes-index.html:402: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-redirects-cloudflare.html:491: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/internal-links-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-404-errors.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-schema-dates.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-app-keywords.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-gbp-services.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/spam-audit-fixes-index.html:455: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-label-not-working.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-meta-descriptions.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-get-cited-by-ai-search-engines.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ssl-not-trusted.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-debug-schema-wordpress.html:214: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-fcp.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-schema-errors.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-llms-txt-static-sites.html:237: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-grade-level.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-grade-level.html:578:The Web Content Accessibility Guidelines touch on this too. WCAG 2.2 success criterion 3.1.5, Reading
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-track-scores-ecommerce.html:219: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/html-checker-guide.html:396: ♿Accessibility GuideWCAG compliance for SEO benefit
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-opt-out-ai-overviews.html:519: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-hsts-missing-from-https-server.html:510: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/schema-builder-fixes-index.html:465: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-shopify-no-traffic.html:519: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-crawled-currently-not-indexed.html:519: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/image-optimisation-fixes-index.html:465: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-http-errors-wordpress.html:503: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-differentiation-playbook.html:499: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/ai-schema-fixes-index.html:465: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-serp-breadcrumbs.html:199: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-page-speed.html:519: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-blog-internal-linking.html:499: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-js-wordpress.html:503: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/social-preview-fixes-index.html:465: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-lang-attribute.html:492: "WCAG compliance",
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-lang-attribute.html:571:
WCAG 2.2 has a second, related criterion: 3.1.2 Language of Parts, at Level AA. It asks that a passage /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ssl-not-working.html:526: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-google-business-profile-suspended.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-security-headers-iis.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-shopify-migration.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-maps-category.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-processor-contracts.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-js-react.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-maps-reviews.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/ecommerce-crawl-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-product-launches.html:484: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cls-video.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-keywords-wordpress.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-css-size.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-crux-mismatch.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-meta-tags-wordpress.html:214: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-dark-mode.html:230: "text": "Measure text contrast in each scheme with a contrast checker: WCAG 2.2 asks for at least 4.5 to 1 for normal text and 3 to 1 for large text, and 3 to 1 for the visual boundaries of form controls and focus indicators. Pay attention to muted text, placeholders, disabled buttons and links, which often fail in dark mode. Then re-run the CSS Checker and repeat your test list from step one.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-dark-mode.html:296: "text": "The same as in light mode. WCAG 2.2 asks for a contrast ratio of at least 4.5 to 1 for normal body text, 3 to 1 for large text, and 3 to 1 for the visual boundaries of form controls and focus indicators. Dark themes often fail on muted grey text, placeholder text, disabled buttons and thin borders. Measure each colour pairing in both schemes with a contrast checker rather than judging by eye, because screens and eyesight vary a great deal." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-dark-mode.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-dark-mode.html:647:in both modes
Measure text contrast in each scheme with a contrast checker: WCAG 2.2 asks for /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-dark-mode.html:792:
The same as in light mode. WCAG 2.2 asks for a contrast ratio of at least 4.5 to 1 /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/gdpr-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cls-fonts.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-add-canonical-tag.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/geo-grid-fixes-index.html:403: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-canonicals.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-image-cls.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-hreflang-sitemap.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cookie-banner-dark-patterns.html:515: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/aipageseo-demo-pages-llms.md:9:- [Accessibility](https://aiwebpageseo.com/aipageseo-demo-pages/novice-tutorial-accessibility.html) What web accessibility means, why WCAG compliance matters for both users and Google rankings, and the most common issues to fix — written for beginners. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/aipageseo-demo-pages-llms.md:606:- [Accessibility](https://aiwebpageseo.com/aipageseo-demo-pages/demo-accessibility.html) A real Accessibility Audit example: 12 WCAG violations on one page including missing ARIA labels, low contrast text, no skip link and unlabelled forms. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/aipageseo-demo-pages-llms.md:697:- [Accessibility Fixes Index](https://aiwebpageseo.com/aipageseo-demo-pages/accessibility-fixes-index.html) Fix every Accessibility Audit finding: colour contrast, alt text, keyboard navigation, focus indicators, ARIA labels and WCAG 2.2 compliance. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/aipageseo-demo-pages-llms.md:698:- [Accessibility Guide](https://aiwebpageseo.com/aipageseo-demo-pages/accessibility-guide.html) WCAG 2.1 compliance explained for site owners. Which accessibility issues hurt SEO, how to find them, and which violations to fix first to pass audits. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-previews-nextjs.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-recover-ecommerce-algo.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-react.html:13: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-react.html:75: "keywords": "React accessibility, Next.js accessibility, eslint-plugin-jsx-a11y, route change focus, route announcer, single page app accessibility, useId, React focus management, jest-axe, Testing Library getByRole, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-react.html:150: "keywords": "React accessibility, Next.js accessibility, eslint-plugin-jsx-a11y, route change focus, route announcer, single page app accessibility, useId, React focus management, jest-axe, Testing Library getByRole, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-react.html:168: "name": "Accessibility Audit" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-react.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-react.html:583:
The Accessibility Audit reports findings against the rendered HTML, which is what browsers and assistive /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-react.html:881:
The Accessibility Audit tests the rendered page against WCAG 2.2 level AA and lists each finding /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-imessage-preview.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ecommerce-seo-shopify.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-faq-schema-worth-it.html:515: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/gbp-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-readiness-react.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-schema-shopify.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-mixed-content-proxy.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-combined-audit.html:202: "text": "The hero photo appears in Image Optimisation, the CLS Debugger, Core Web Vitals and the Page Speed Analyzer, so it becomes one task. The broken LocalBusiness block explains results in the JSON Checker, Schema Debugger, Rich Snippets Suite and Local SEO Checker, so that becomes another. The missing newsletter label appears in both the HTML and Accessibility Audits. Grouping like this turns several dozen findings into a short list of real jobs.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-combined-audit.html:475: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-combined-audit.html:559:
WCAG 2.2 success criterion 1.4.4, Resize Text, asks that text can be enlarged to 200% without losing /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/aeo-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/pagespeed-fixes-index.html:473: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-502-errors.html:495: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-sitemap-could-not-be-read.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-maps-services.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:13: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:32: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:75: "keywords": "Shopify accessibility, Shopify WCAG, accessible Shopify theme, Shopify alt text, Shopify app embeds, Shopify variant picker accessibility, Shopify cart drawer, Liquid accessibility, Shopify accessibility statement, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:128: "name": "WCAG 2.2" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:150: "keywords": "Shopify accessibility, Shopify WCAG, accessible Shopify theme, Shopify alt text, Shopify app embeds, Shopify variant picker accessibility, Shopify cart drawer, Liquid accessibility, Shopify accessibility statement, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:168: "name": "Accessibility Audit" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:188: "text": "In the admin, go to Online Store, then Themes, open the Actions menu on your live theme and choose Duplicate. Do all work on the copy. Run the Accessibility Audit on the preview of one page of each template type and save the results, so you can see what improved. Note the theme name and version, because an update from the theme developer may already fix some of the problems you find.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:264: "text": "There is no single answer, and it changes as themes are updated. Themes in the Shopify Theme Store must meet Shopify's accessibility requirements before listing, and Shopify's own free themes are a solid starting point. Before buying a paid theme, try its demo store with only a keyboard, run the Accessibility Audit on a demo product page and look for a statement about accessibility from the developer. Your own settings and apps will still matter more than the theme name." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:602:and choose Duplicate. Do all work on the copy. Run the Accessibility Audit on the preview of one page /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:785:the Accessibility Audit on a demo product page and look for a statement about accessibility from the /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-shopify.html:833:
The Accessibility Audit tests your page against WCAG 2.2 level AA and lists each finding with /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-hreflang-shopify.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-maps-service-area.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-build-schema-nextjs.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-hreflang-language-codes.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-app-audit.html:162: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-robots-sitemap-shopify.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-yoast-seo-errors.html:526: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/real-traffic-audit-guide.html:487: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/questions-and-answers-fixes-index.html:402: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-price-hike.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-update-dates.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-sudden-drop.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-page-with-redirect-redirect-error.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-image-alt.html:511: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-broken-internal-links.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-app-category.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-score-traffic-divergence.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:13: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:75: "keywords": "ARIA labels, aria-label, aria-labelledby, aria-describedby, accessible name, button has no accessible name, aria-hidden focusable, label in name WCAG 2.5.3, WCAG 4.1.2, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:150: "keywords": "ARIA labels, aria-label, aria-labelledby, aria-describedby, accessible name, button has no accessible name, aria-hidden focusable, label in name WCAG 2.5.3, WCAG 4.1.2, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:168: "name": "Accessibility Audit" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:188: "text": "Run the Accessibility Audit and open the first flagged element in your browser. In Chrome or Edge, inspect it and open the Accessibility pane in the Elements panel, which shows the computed role and name and which source the name came from. Firefox has a similar Accessibility Inspector. Write down the current name for each flagged element. Seeing the name the browser actually computes is faster and more reliable than reading the markup and guessing.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:230: "text": "Open the page with NVDA and press Tab through every control, or use the VoiceOver rotor on a Mac to list form controls, links and landmarks. Each item should be announced with a clear name, the right role and any state, such as expanded or pressed. Listen for anything announced as just button or link, names that repeat, and hidden content that is still read. Then run the Accessibility Audit again and confirm the findings have cleared.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:627:tools
Run the Accessibility Audit and open the first flagged element in your browser. In Chrome /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:666:or link, names that repeat, and hidden content that is still read. Then run the Accessibility Audit /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-labels.html:759:
The Accessibility Audit tests your page against WCAG 2.2 level AA and lists each finding, such /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-long-sentences.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-html-errors-shopify.html:491: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-preview-cache.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-missing-lang.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-negative-mentions.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-memory-leaks.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-deleted-schema.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-coverage-gaps.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-howto-carousel.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-review-schema.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-navigation.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:13: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:75: "keywords": "colour contrast, color contrast ratio, WCAG 1.4.3, WCAG 1.4.11 non-text contrast, 4.5:1 contrast, low contrast text, contrast checker, brand colours accessibility, text over images, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:150: "keywords": "colour contrast, color contrast ratio, WCAG 1.4.3, WCAG 1.4.11 non-text contrast, 4.5:1 contrast, low contrast text, contrast checker, brand colours accessibility, text over images, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:168: "name": "Accessibility Audit" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:188: "text": "Run the Accessibility Audit on the home page and on one page of each template, and list each contrast finding with its foreground colour, background colour and where it appears. You will usually find the same few pairs repeated many times, such as grey body text, a button style and footer links. Record each unique pair once, with the CSS selector or theme setting that produces it, so you fix causes rather than chasing individual instances around the site.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:230: "text": "Run the Accessibility Audit again on every template you changed. If your site offers a dark theme or follows the visitor's system setting with prefers-color-scheme, switch it on and test again, because colours that pass on white often fail on near-black. Zoom to 200 percent and check that text has not reflowed onto a lower contrast part of a background image. Finally, look at the key pages on a phone outdoors or at low brightness.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:581:WCAG 3. It is not part of WCAG 2.2, which is what checkers and most policies test against. Meet the WCAG /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:644:the Accessibility Audit on the home page and on one page of each template, and list each contrast finding /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:680:views
Run the Accessibility Audit again on every template you changed. If your site offers a /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-colour-contrast.html:821:
The Accessibility Audit tests your page against WCAG 2.2 level AA and lists each finding, including /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-seo-working.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-title-truncation.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-serp-nextjs.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-redirects-wordpress.html:214: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-og-wordpress.html:214: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-sentiment-shifts.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-helpful-content.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-handle-brand-mentions-podcasts.html:491: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-llms-language.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-invisibility.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-app-title.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-search-intent.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-layout-shift-css.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-multiple-schemas.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-maps-pin.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-pdp-seo.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-robots-syntax.html:104: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-build-schema-shopify.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-disable-hsts.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/llms-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-real-traffic-audit.html:482: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-no-rich-results-detected.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-yoast-rank-math-meta-description-not-working.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-security-headers-apache.html:123: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-citations.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cross-links.html:495: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-page-speed-wordpress.html:125: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cls.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-readability-product-pages.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-organization-schema.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-nofollow-ratio.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-search-console-server-error-5xx.html:526: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-schema-references.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-new-backlinks.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-thin-content.html:124: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cls-dynamic.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-jsonld-coverage.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-decorative-images.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-author-bios.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-recipe-schema.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/cls-debugger-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ttfb.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-local-keywords.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/css-checker-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/real-traffic-audit-fixes-index.html:437: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-og-image-size.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-pricing-changes.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-shopify-crawl.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/question-finder-guide.html:161: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/site-crawler-fixes-index.html:438: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-images-speed.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-rich-snippets-wordpress.html:214: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-improve-website-seo.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ymyl-rankings.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-hallucinations.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-cwv.html:420:
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-ai-visibility-chatgpt.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/meta-analyzer-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-content-extractability.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-schema-recommended.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-image-cdn.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-502-bad-gateway-nginx.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-compete-content-sites.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-schema-types.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-anchor-jump-links-not-working.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-question-finder.html:206: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-eprivacy-tracking.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-passive-voice.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-schema-conflicts.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/competitor-analysis-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/readability-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-https-redirects.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-new-content.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-gbp-service-area.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-css-shopify.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-security-headers-wordpress.html:194: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-aeo-gemini.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-llms-full.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-new-keywords.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-http-errors-plesk.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-international-transfers.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/spam-audit-guide.html:490: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-regression.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-browser-prefixes.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-readability-blog-posts.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ux-signals.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-compat-shopify.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-302-vs-301.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:13: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:31: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:75: "keywords": "form labels accessibility, label for id, placeholder is not a label, fieldset legend, aria-describedby, form field accessible name, WCAG 1.3.1, WCAG 3.3.2, label in name, autocomplete attribute, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:124: "name": "WCAG 2.2" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:150: "keywords": "form labels accessibility, label for id, placeholder is not a label, fieldset legend, aria-describedby, form field accessible name, WCAG 1.3.1, WCAG 3.3.2, label in name, autocomplete attribute, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:168: "name": "Accessibility Audit" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:188: "text": "Run the Accessibility Audit on each page with a form, including the header search, footer newsletter, contact, booking, login and checkout pages. For each finding, inspect the field and open the accessibility pane in the browser developer tools, which shows the computed name and where it came from. Note fields with no name, a name from a placeholder or title, or a name that does not match the words on screen.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:230: "text": "Tab through the form with NVDA on Windows or VoiceOver on a Mac and listen: every field should announce its label, its type, whether it is required and any hint. Check each group announces its question. Then read each visible label aloud and confirm it appears in the computed name, which is what voice control users rely on. Finally, run the Accessibility Audit again to confirm the findings have cleared.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:719:nameRun the Accessibility Audit on each page with a form, including the header search, footer /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:758:what voice control users rely on. Finally, run the Accessibility Audit again to confirm the findings /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-form-labels.html:871:
The Accessibility Audit tests your page against WCAG 2.2 level AA, lists each finding with the /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-semantic-html.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-json-ld-format.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-perplexity-invisibility.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-html-errors-ssg.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-anchor-text.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-acquire-backlinks-content-pr.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/site-audit-pro-fixes-index.html:411: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-flesch-score.html:485: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-score-plateau.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-my-questions.html:206: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-schema-required.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-llms-txt.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-site-audit-wordpress.html:214: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-security-headers-cpanel.html:112: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-twitter-cards.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-author-trust-signals.html:511: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-gaps.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-eeat-product-reviews.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-accessibility.html:7:
This is a real report from the AI Web Page SEO Accessibility Audit. We ran it on the home page of aipageseo.com, our sister site, in October 2026, and copied the result here exactly as the tool showed it. The page scored 20 out of 100: 3 errors, 7 warnings and 17 checks passed, with all 55 WCAG 2.2 Level A and AA criteria listed in the coverage table at the end of the report.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-accessibility.html:245:Accessibility Audit Results
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-accessibility.html:283:WCAG 2.2 coverage, Level A and AA: 3 failed, 4 with warnings, 26 with no problems found, 20 need a person to check, 2 not checked this time
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-accessibility.html:284:| Criterion | Level | Name | Result |
|---|---|---|---|
| 1.1.1 | A | Non-text Content | Warning |
| 1.2.1 | A | Audio-only and Video-only (Prerecorded) | Needs a person to check |
| 1.2.2 | A | Captions (Prerecorded) (also check that captions are accurate and complete) | No problems found |
| 1.2.3 | A | Audio Description or Media Alternative (Prerecorded) | Needs a person to check |
| 1.3.1 | A | Info and Relationships | Warning |
| 1.3.2 | A | Meaningful Sequence | Needs a person to check |
| 1.3.3 | A | Sensory Characteristics | Needs a person to check |
| 1.4.1 | A | Use of Color (also check that colour is never the only way information is shown) | No problems found |
| 1.4.2 | A | Audio Control | No problems found |
| 2.1.1 | A | Keyboard (also check that every function works with the keyboard alone) | No problems found |
| 2.1.2 | A | No Keyboard Trap (also check the parts of the page beyond the first 40 tab stops) | No problems found |
| 2.1.4 | A | Character Key Shortcuts | Needs a person to check |
| 2.2.1 | A | Timing Adjustable (also check time limits set by scripts (session timeouts)) | No problems found |
| 2.2.2 | A | Pause, Stop, Hide (also check content further down the page) | No problems found |
| 2.3.1 | A | Three Flashes or Below Threshold (also check videos and animations beyond the first seconds) | No problems found |
| 2.4.1 | A | Bypass Blocks | No problems found |
| 2.4.2 | A | Page Titled (also check that the title describes the page) | No problems found |
| 2.4.3 | A | Focus Order (also check that the tab order follows the page in a sensible order) | No problems found |
| 2.4.4 | A | Link Purpose (In Context) (also check that each link says where it goes) | No problems found |
| 2.5.1 | A | Pointer Gestures | Needs a person to check |
| 2.5.2 | A | Pointer Cancellation | Needs a person to check |
| 2.5.3 | A | Label in Name (also check controls named by pictures of text) | No problems found |
| 2.5.4 | A | Motion Actuation | Needs a person to check |
| 3.1.1 | A | Language of Page | No problems found |
| 3.2.1 | A | On Focus (also check the parts of the page beyond the first 40 tab stops) | No problems found |
| 3.2.2 | A | On Input | Needs a person to check |
| 3.2.6 | A | Consistent Help | Not checked this time |
| 3.3.1 | A | Error Identification | Needs a person to check |
| 3.3.2 | A | Labels or Instructions | Warning |
| 3.3.7 | A | Redundant Entry | Needs a person to check |
| 4.1.2 | A | Name, Role, Value (also check custom controls built with scripts) | No problems found |
| 1.2.4 | AA | Captions (Live) | Needs a person to check |
| 1.2.5 | AA | Audio Description (Prerecorded) | Needs a person to check |
| 1.3.4 | AA | Orientation | No problems found |
| 1.3.5 | AA | Identify Input Purpose | Failed |
| 1.4.3 | AA | Contrast (Minimum) (also check text drawn inside images) | No problems found |
| 1.4.4 | AA | Resize Text (also check text that grows only partly when zoomed) | No problems found |
| 1.4.5 | AA | Images of Text | Needs a person to check |
| 1.4.10 | AA | Reflow (also check content that only appears after an action) | No problems found |
| 1.4.11 | AA | Non-text Contrast | Failed |
| 1.4.12 | AA | Text Spacing (also check text that overlaps rather than being cut off) | No problems found |
| 1.4.13 | AA | Content on Hover or Focus (also check pop-ups beyond the menus and tooltips tried) | No problems found |
| 2.4.5 | AA | Multiple Ways | Warning |
| 2.4.6 | AA | Headings and Labels (also check that headings and labels describe their content) | No problems found |
| 2.4.7 | AA | Focus Visible | Failed |
| 2.4.11 | AA | Focus Not Obscured (Minimum) (also check the parts of the page beyond the first 40 tab stops) | No problems found |
| 2.5.7 | AA | Dragging Movements | Needs a person to check |
| 2.5.8 | AA | Target Size (Minimum) (also check controls drawn without their own box) | No problems found |
| 3.1.2 | AA | Language of Parts (also check passages in another language that are not marked) | No problems found |
| 3.2.3 | AA | Consistent Navigation | Not checked this time |
| 3.2.4 | AA | Consistent Identification | Needs a person to check |
| 3.3.3 | AA | Error Suggestion | Needs a person to check |
| 3.3.4 | AA | Error Prevention (Legal, Financial, Data) | Needs a person to check |
| 3.3.8 | AA | Accessible Authentication (Minimum) | Needs a person to check |
| 4.1.3 | AA | Status Messages | Needs a person to check |
The coverage table at the end of the report is the most honest summary. Of the 55 WCAG 2.2 Level A and AA criteria, 3 failed, 4 had warnings, 26 showed no problems, 20 can only be judged by a person (such as whether alt text describes each image well), and 2 were not checked on this run. Nothing is left out, so "not tested" is never mistaken for "no problems".
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-accessibility.html:351:It is a real report. It is the output of the AI Web Page SEO Accessibility Audit run on the home page of aipageseo.com, our sister site, in October 2026. Nothing in it has been invented or tidied up: the score, the counts, the examples, the colours and the 55-row coverage table are exactly what the tool returned. The explanations below the report are ours, written to show what each finding means for visitors and how it would be fixed.
No. A page conforms at Level AA only when it meets every Level A and AA success criterion, and 20 of the 55 need a person to check, such as whether alt text describes each image well or whether error messages are clear. A score of 100 means the audit found no problems in the criteria it could test on that run. It is the right point to start a manual review of the rest, not proof of compliance.
WCAG 2.2 Level A and AA, all 55 criteria reported, your page checked as visitors see it.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-accessibility.html:372: Run the Accessibility Audit /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/site-audit-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-schema-wordpress.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-stock-out.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-watch-competitors-electronics.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/question-finder-fixes-index.html:402: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-google-play.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-content-gaps.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-encoding-errors.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-broken-links.html:124: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-errors.html:304: "text": "Not automatically. WCAG 2.2 removed the old parsing criterion, so an invalid attribute on its own is no longer a failure. What matters is the effect. If a misspelt attribute leaves a button with no accessible name, or a bad role means a custom checkbox does not report whether it is checked, that fails criteria such as 4.1.2 Name, Role, Value. Fixing validation errors is the quickest way to remove those effects. This is not legal advice about any accessibility obligation." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-errors.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aria-errors.html:849:Not automatically. WCAG 2.2 removed the old parsing criterion, so an invalid attribute /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-lost-backlinks.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-duplicate-products.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-301-redirect-not-working.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-rendering.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-js-console-errors.html:518: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-contact.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-schema-urls.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-doctype-errors.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-serp-wordpress.html:214: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/backlinks-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-gbp-qa.html:487: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-internal-links-migration.html:495: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-recover-content-sites-algo.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-ecommerce-audit.html:83: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/html-checker-fixes-index.html:474: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/html-checker-fixes-index.html:546:
WCAG 2.2, the current version of the Web Content Accessibility Guidelines, removed the old success /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-serp-shopify.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-twitter-card.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-lawful-basis.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-duplicate-content.html:124: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-seasonal-products.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/agent-compat-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-schema-required-fields.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-privacy-policy.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-questions-and-answers.html:206: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-backlinks-not-being-indexed.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-combined-audit.html:475: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-no-lcp-lighthouse-error.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-review-velocity.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-collection-architecture.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-referring-domain-gap.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-ai-visibility-perplexity.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-previews-shopify.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-maps-multi-location.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-trust-audit.html:111: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-blocks.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-title-tags.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-aeo-content-structure.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-security-headers-joomla.html:112: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-facebook-preview.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-sitemap-404s.html:104: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-json-ld-wordpress.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-json-ld-shopify.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/security-audit-fixes-index.html:483: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-duplicate-ids.html:491: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-jargon.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-jargon.html:683:
Accessibility guidance backs this up. WCAG 2.2 success criteria 3.1.3 Unusual Words and 3.1.4 Abbreviations, /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-competitor-balance.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-breadcrumb-structured-data-issues.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-response-time.html:491: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-disavow-file.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-gemini-invisibility.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-og-cache.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-render-blocking-js.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-azure-gateway-errors.html:515: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-category-shifts.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-orphan-pages.html:123: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-homepage-internal-linking.html:237: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-long-tail-keywords.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-og-title-mismatch.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-sitemap-size.html:104: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-authority-building.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-missing-og.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/agent-readiness-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-maps-hours.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-create-xml-sitemap.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-robots-txt-unreachable-errors.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-google-title-rewrite.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-positive-mentions.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-deprecated-html.html:304: "text": "A static announcement bar with the text visible all the time is the simplest and most accessible replacement. Scrolling text is hard to read, easy to miss and a problem for people with vestibular or attention difficulties. If you need to show several messages, list them, or rotate them slowly with a visible pause button and no movement when the visitor's system asks for reduced motion. Under WCAG 2.2, moving content that lasts more than five seconds must be possible to pause, stop or hide." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-deprecated-html.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-deprecated-html.html:618:
Flashing content also carries an accessibility risk of its own: WCAG 2.2 limits content that flashes /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/http-error-audit-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-render-blocking-resources-wordpress.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-sitemap-index-xml-wordpress.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-alt-text-not-showing-hover.html:512: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-403-errors.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-forms.html:280: "text": "Very much so. Agents that drive a browser rely on the same accessibility tree that screen readers use, so linked labels, native controls, grouped questions and clear error messages help both. The fixes in this guide line up closely with WCAG 2.2 success criteria on labels, names, error identification and input purpose. Treat the work as one job that serves disabled users, agents and everyone filling in the form on a small phone." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-forms.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-forms.html:752:
Step 7
If the content lands under a fixed header, set scroll-margin-top on the target to the header height plus a little space, for example 6rem. This keeps the first heading visible after the jump and meets Focus Not Obscured in WCAG 2.2. Test at several widths, because headers often grow taller on small screens when the menu wraps onto two lines or a promotional banner appears.
WCAG 2.2 became a W3C Recommendation in October 2023 and is now the version most organisations work /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-fixes-index.html:598:to. It keeps almost everything in WCAG 2.1 and adds new success criteria. The ones at levels A and AA /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-fixes-index.html:614:
WCAG 2.2 also removed 4.1.1 Parsing, because modern browsers and assistive technology handle the HTML /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-fixes-index.html:641:
WCAG 2.2 is the current version of the Web Content Accessibility Guidelines published /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-fixes-index.html:669:
For public sector bodies, yes: the 2018 accessibility regulations require WCAG 2.2 /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-fixes-index.html:719:
The Accessibility Audit tests your page against WCAG 2.2 level AA, lists each finding with the /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-fixes-index.html:721: Run the Accessibility Audit → /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cls-components.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-watch-competitors-home.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-aeo-perplexity.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-volatility.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-prevent-schema-drift-custom.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-keywords-shopify.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-schema-type-choice.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-schema-duplicates.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:13: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:75: "keywords": "focus indicator, focus visible, outline none accessibility, :focus-visible, WCAG 2.4.7, WCAG 2.4.11 focus not obscured, focus ring CSS, keyboard focus outline, sticky header hides focus, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:150: "keywords": "focus indicator, focus visible, outline none accessibility, :focus-visible, WCAG 2.4.7, WCAG 2.4.11 focus not obscured, focus ring CSS, keyboard focus outline, sticky header hides focus, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:168: "name": "Accessibility Audit" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:188: "text": "Click in the browser address bar, then press Tab repeatedly through the whole page, including the header, menus, forms, footer and any cookie banner. Write down every point where you lose track of where focus is, where the indicator is faint, and where a focused item is covered by something. On a Mac using Safari, first turn on the setting that lets Tab highlight each item on a web page, otherwise Tab skips links. Compare your notes with the Accessibility Audit findings.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:230: "text": "Tab through the whole page again and confirm you can always see where focus is, on every background and with nothing covering it. Repeat at a narrow mobile width and at 200 percent zoom, where sticky headers take up more of the screen. In Chrome or Edge developer tools, open the Rendering panel and emulate forced colours to check the indicator survives. Then run the Accessibility Audit again on each changed template.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:272: "text": "A solid outline around the element, at least two pixels thick, in a colour with at least three to one contrast against the surrounding background, and slightly offset so it does not merge with the element's own border. That meets the WCAG 2.2 AAA Focus Appearance measure, which is a useful target even though level AA only asks for visibility. It should be consistent across the site, so users learn what focus looks like once and can recognise it everywhere." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:280: "text": "It is a WCAG 2.2 success criterion, 2.4.11 at level AA, which says that when an element receives keyboard focus it must not be completely hidden by content the site has added, such as a sticky header, sticky footer, cookie banner or chat widget. The level AA version allows partial overlap; the AAA version, 2.4.12, does not. The usual fixes are scroll padding equal to the height of sticky bars, and banners that do not float over page content." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:555:
Three success criteria in WCAG 2.2 deal directly with focus, and one more affects how visible the indicator must be.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:604:your notes with the Accessibility Audit findings.It is a WCAG 2.2 success criterion, 2.4.11 at level AA, which says that when an element /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-focus-indicators.html:809:
The Accessibility Audit tests your page against WCAG 2.2 level AA and lists each finding with /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-schema-changes.html:488: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/brand-mention-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-build-schema-wordpress.html:214: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-twitter-preview.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/hreflang-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-redirect-domain-301.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-hsts-error.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessible-error-messages.html:13: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessible-error-messages.html:75: "keywords": "WCAG error identification, WCAG error messages, WCAG error suggestion, WCAG error prevention, WCAG error summary, aria error message, aria label for error message, aria-invalid, aria-describedby error, html form validation custom error message, WCAG 2.2 error messages, accessible form errors", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessible-error-messages.html:150: "keywords": "WCAG error identification, WCAG error messages, WCAG error suggestion, WCAG error prevention, WCAG error summary, aria error message, aria label for error message, aria-invalid, aria-describedby error, html form validation custom error message, WCAG 2.2 error messages, accessible form errors", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessible-error-messages.html:227: "text": "Make sure a failed submit, whether checked in the browser or on the server, returns the form with every valid answer still filled in, to meet Redundant Entry in WCAG 2.2. Validate fields when the user leaves them or submits, not on every keystroke, and only announce errors once. If you show a count without moving focus, put it in an element with role set to status that is present on page load.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessible-error-messages.html:312: "name": "What changed for error messages in WCAG 2.2?", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessible-error-messages.html:315: "text": "WCAG 2.2 did not change the error identification, suggestion or prevention criteria, but two new criteria affect how forms handle errors. Redundant Entry, at level A, means people should not have to retype information they already gave in the same process, so a failed submit must keep their answers. Accessible Authentication, at level AA, means login forms must allow pasting and password managers, and must not rely on memory puzzles alone. Both are common failures in checkout and account forms." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessible-error-messages.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessible-error-messages.html:575:
Others support them. 3.3.2 Labels or Instructions (A) requires labels and any format instructions up front. 1.4.1 (A) says colour must not be the only way information is shown, so a red border alone fails. 4.1.3 Status Messages (AA) requires messages such as 3 errors found to be announced without moving focus, if focus does not move. WCAG 2.2 adds 3.3.7 Redundant Entry (A), so a failed submission must not wipe the answers people already gave, and 3.3.8 Accessible Authentication (AA), which matters for login error handling.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessible-error-messages.html:700:Step 6
Make sure a failed submit, whether checked in the browser or on the server, returns the form with every valid answer still filled in, to meet Redundant Entry in WCAG 2.2. Validate fields when the user leaves them or submits, not on every keystroke, and only announce errors once. If you show a count without moving focus, put it in an element with role set to status that is present on page load.
WCAG 2.2 did not change the error identification, suggestion or prevention criteria, but two new criteria affect how forms handle errors. Redundant Entry, at level A, means people should not have to retype information they already gave in the same process, so a failed submit must keep their answers. Accessible Authentication, at level AA, means login forms must allow pasting and password managers, and must not rely on memory puzzles alone. Both are common failures in checkout and account forms.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/js-checker-fixes-index.html:473: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-csp-report-only.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-html-errors-react.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-local-seo-brick-and-mortar.html:237: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-serp-gains.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-accessibility.html:9: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-accessibility.html:17: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-accessibility.html:31: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-accessibility.html:41: "description": "Learn what web accessibility means, why WCAG compliance matters for both users and Google rankings, and the most common issues to fix. Step by step for complete beginners.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-accessibility.html:293:Learn what web accessibility means, why WCAG compliance matters for both users and Google rankings, and the most common issues to fix. Step by step for complete beginners.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-accessibility.html:297: 🔍 Accessibility Audit → /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-accessibility.html:305:When a focused link slides under a fixed header or a cookie banner, WCAG 2.2 criterion 2.4.11 is failed. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-keyboard-nav.html:846:
The Accessibility Audit tests your page against WCAG 2.2 level AA and lists each finding with /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-apply-keywords-editorial.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-local-seo-service-area.html:237: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-www-canonicalisation.html:104: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/rich-snippets-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-x-default.html:485: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-redirect-chains.html:124: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-security-headers-directadmin.html:112: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-debug-schema-shopify.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/ecommerce-audit-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-local-citations.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-json-ld-nextjs.html:237: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/my-questions-guide.html:161: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-site-audit-pro.html:206: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-redirect-loops.html:484: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-missed-opportunities.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-keyword-gaps.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cookie-consent.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-og-article.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-crawler-traps.html:104: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-third-party-tags.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-pagination-seo.html:526: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-expertise-credentials.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/score-history-fixes-index.html:465: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-excluded-by-noindex-tag.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-product-schema.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-price-cut.html:507: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-site-audit-nextjs.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-wrong-attribution.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-recover-service-algo.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-app-localisation.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-page-speed-shopify.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-seasonal.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-velocity.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-noindex-a-page.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-discovered-currently-not-indexed.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-tracking.html:506: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/novice-tutorial-real-traffic-audit.html:483: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-indexation.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-llms-txt-wordpress.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-serp-stars.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-rich-result-errors.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-hreflang-nextjs.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-og-tags.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-duplicate-meta-descriptions.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-hreflang-canonical-conflict.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-use-ai-schema-editorial.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-core-web-vitals-assessment-failed.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-test-rich-results.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-render-blocking.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-app-screenshots.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-acquire-backlinks-tools.html:209: "text": "Put the tool on a permanent address on your main domain, with a real title, heading and explanatory text in the HTML the server sends. Make inputs labelled, keyboard usable and readable on a phone, and test against WCAG 2.2. Keep it fast and free of signup walls. If the calculation runs in JavaScript, make sure the surrounding page, headings and a worked example still appear without it.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-acquire-backlinks-tools.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-acquire-backlinks-tools.html:619:on a phone, and test against WCAG 2.2. Keep it fast and free of signup walls. If the calculation runs /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-pdp-speed.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-review-surge.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-whatsapp-preview.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-track-scores-content-sites.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-alternate-page-proper-canonical.html:526: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-missing-security-headers.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cookie-banner-not-showing.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-act-product-launch.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-technical-gaps.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-serp-thumbnails.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-meta-tags-shopify.html:237: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-og-locale.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cwv-shopify.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-faceted-nav.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-app-conversion.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-spam-audit.html:475: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-schema-gaps.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-image-lazy-load.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-page-speed-nextjs.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-og-nextjs.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ymyl-content.html:491: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-track-scores-b2b-saas.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-page-indexed.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-meta-description-not-showing-google.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:13: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:30: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:75: "keywords": "link text accessibility, vague link text, click here, read more links, WCAG 2.4.4, link purpose, descriptive links, empty links, image links, label in name, screen reader links list, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:120: "name": "WCAG 2.2" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:150: "keywords": "link text accessibility, vague link text, click here, read more links, WCAG 2.4.4, link purpose, descriptive links, empty links, image links, label in name, screen reader links list, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:168: "name": "Accessibility Audit" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:188: "text": "Run the Accessibility Audit on each template, then open a screen reader and bring up its list of links, using Insert+F7 in NVDA or Control+Option+U in VoiceOver on a Mac. Read the list from top to bottom as if you had never seen the page. Mark every entry where you cannot say where it goes, every group of identical entries, and every entry that is just an address, a file name or the word link.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:619:the Accessibility Audit on each template, then open a screen reader and bring up its list of links, /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-link-text.html:834:
The Accessibility Audit tests your page against WCAG 2.2 level AA and lists each finding with /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-timeout-errors.html:495: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:11: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:18: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:29: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:30: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:37: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:86: "headline": "How to check WCAG 2.1 and 2.2 compliance on your website", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:87: "description": "How to check WCAG compliance: run automated scans, then test by keyboard, screen reader, zoom and contrast against WCAG 2.1 and 2.2 AA, and record the results.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:116: "name": "WCAG 2.1" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:120: "name": "WCAG 2.2" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:160: "name": "How to check WCAG 2.1 and 2.2 compliance on your website", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:161: "description": "How to check WCAG compliance: run automated scans, then test by keyboard, screen reader, zoom and contrast against WCAG 2.1 and 2.2 AA, and record the results.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:192: "text": "Decide which standard you are testing against, normally WCAG 2.2 level AA unless a contract names WCAG 2.1. List 10 to 25 pages that cover every template, every step of your key tasks such as contact, sign-up and checkout, pages with media or tables, and a few random pages. Save the list with the date, because your results only apply to the pages you tested.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:279: "name": "How do I check for WCAG 2.1 specifically?", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:282: "text": "Test against WCAG 2.1 level AA by running your automated tool with the 2.0 and 2.1 A and AA rules, then adding the manual checks that 2.1 introduced. Those include reflow at 320 CSS pixels, text spacing, non-text contrast for icons and borders, content on hover or focus, orientation and character key shortcuts. Because WCAG 2.2 builds on 2.1, a site that passes 2.2 AA also passes 2.1 AA, so testing to 2.2 is a safe way to meet a 2.1 requirement." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:287: "name": "What is the difference between WCAG 2.1 and 2.2?", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:290: "text": "WCAG 2.2 keeps every WCAG 2.1 criterion except 4.1.1 Parsing, which was removed as obsolete, and adds nine new ones. The new A and AA criteria cover focus not being hidden by sticky content, pointer targets of at least 24 by 24 pixels, alternatives to dragging, consistent placement of help, not asking for the same information twice, and sign-in that does not depend on memory tests. WCAG 2.2 became a W3C Recommendation in October 2023 and is now the version most new guidance points to." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:314: "text": "Level AA is the target for almost every legal requirement and contract. UK public sector websites must meet WCAG 2.2 AA under the accessibility regulations, the European standard EN 301 549 references WCAG AA, and US guidance for public bodies uses WCAG 2.1 AA. Level AAA is not recommended as a whole-site requirement, because some content cannot meet every AAA criterion, but individual AAA criteria are worth meeting where they are practical for your site." /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:319: "name": "How often should I check WCAG compliance?", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:526: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:554:
Checking a website against the Web Content Accessibility Guidelines is not a matter of running one scanner and reading a score. Automated tools are quick and useful, but they can only test the parts of WCAG a machine can measure, such as missing alt attributes or low contrast. Whether the alt text makes sense, whether a menu works with a keyboard, or whether a screen reader user can complete your checkout needs a person to try it. This guide shows how to check WCAG 2.1 and WCAG 2.2 at level AA on a small site: choosing which pages to test, running automated scanners from the browser and the command line, the manual keyboard, screen reader, zoom and contrast tests that cover what tools miss, and how to record the results so you can fix them and prove progress.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:567:The versions are backwards compatible: a page that meets 2.2 AA also meets 2.1 AA and 2.0 AA. So if you are asked how to check for WCAG 2.1, testing against 2.2 covers it, with a few extra checks on top. Test against 2.2 AA unless a contract names another version.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:608:To test your page list in one go, use a command line tool. With axe, limited to WCAG 2.2 A and AA rules:
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:670:Step 1
Decide which standard you are testing against, normally WCAG 2.2 level AA unless a contract names WCAG 2.1. List 10 to 25 pages that cover every template, every step of your key tasks such as contact, sign-up and checkout, pages with media or tables, and a few random pages. Save the list with the date, because your results only apply to the pages you tested.
Test against WCAG 2.1 level AA by running your automated tool with the 2.0 and 2.1 A and AA rules, then adding the manual checks that 2.1 introduced. Those include reflow at 320 CSS pixels, text spacing, non-text contrast for icons and borders, content on hover or focus, orientation and character key shortcuts. Because WCAG 2.2 builds on 2.1, a site that passes 2.2 AA also passes 2.1 AA, so testing to 2.2 is a safe way to meet a 2.1 requirement.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:718:WCAG 2.2 keeps every WCAG 2.1 criterion except 4.1.1 Parsing, which was removed as obsolete, and adds nine new ones. The new A and AA criteria cover focus not being hidden by sticky content, pointer targets of at least 24 by 24 pixels, alternatives to dragging, consistent placement of help, not asking for the same information twice, and sign-in that does not depend on memory tests. WCAG 2.2 became a W3C Recommendation in October 2023 and is now the version most new guidance points to.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:731:Level AA is the target for almost every legal requirement and contract. UK public sector websites must meet WCAG 2.2 AA under the accessibility regulations, the European standard EN 301 549 references WCAG AA, and US guidance for public bodies uses WCAG 2.1 AA. Level AAA is not recommended as a whole-site requirement, because some content cannot meet every AAA criterion, but individual AAA criteria are worth meeting where they are practical for your site.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-check-wcag-compliance.html:734:The accessibility audit tests your pages against WCAG 2.2 A and AA rules, lists each failure with its criterion and element, and points out the manual checks no scanner can make for you.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-service-areas.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-schema-id-refs.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-inp.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-maps-posts.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-headless-migration.html:219: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-slack-preview.html:492: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-anchor-text-distribution.html:215: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-optimise-ios-app-store.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-multi-location.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-handle-brand-mentions-news.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cwv-nextjs.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-stale-llms.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-js-crawler-rendering.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:13: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:31: /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:75: "keywords": "WordPress accessibility, accessibility-ready theme, WordPress WCAG 2.2, block editor accessibility, Gutenberg alt text, Elementor accessibility, Contact Form 7 labels, WordPress skip link, WordPress focus styles, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:124: "name": "WCAG 2.2" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:150: "keywords": "WordPress accessibility, accessibility-ready theme, WordPress WCAG 2.2, block editor accessibility, Gutenberg alt text, Elementor accessibility, Contact Form 7 labels, WordPress skip link, WordPress focus styles, Accessibility Audit", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:168: "name": "Accessibility Audit" /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:192: "text": "Make a staging copy of the site, which many hosts offer with one click, so you can deactivate plugins and edit templates without affecting visitors. Run the Accessibility Audit on one URL of each template: home, page, post, archive, search, contact and any shop pages. Group the findings by the class names on the failing elements, so you can see which came from the theme, a builder, a form plugin or content.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:234: "text": "Add alt text, heading order and descriptive link text to your editors' publishing checklist, and save accessible layouts as synced patterns. After every theme, builder or major plugin update, run the Accessibility Audit again on the same template URLs and compare with the previous results. Publish an accessibility statement explaining what you have tested, any known gaps and how visitors can contact you for help.", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:535:This guide shows how to trace each Accessibility Audit finding back to the part of WordPress that produced /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:740:plugins and edit templates without affecting visitors. Run the Accessibility Audit on one URL of each /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:774:update, run the Accessibility Audit again on the same template URLs and compare with the previous results. /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-accessibility-wordpress.html:883:The Accessibility Audit tests your page against WCAG 2.2 level AA, lists each finding with the /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-gdpr-compliance-steps.html:526: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-experience-signals.html:491: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-set-up-gbp.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-redirects-apache.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-alt-text-length-icons.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-alt-text-length-icons.html:721:
The Accessibility Audit measures the parts of WCAG 2.1 that can be tested reliably, and Image Optimisation /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/combined-audit-fixes-index.html:626:fixes. WCAG 2.2 is now the current version, and meeting the 2.1 criteria the checker tests is a sound /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-agent-readiness-wordpress.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-schema-rich-results.html:496: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-recipe-carousel.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-eligible-not-shown.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-security-headers-ghost.html:112: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-local-seo-multi-location.html:237: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-guide.html:11:
WCAG stands for Web Content Accessibility Guidelines — the internationally recognised standard for accessibility, published by the W3C (the organisation that maintains core web standards generally). Each individual rule within WCAG has a reference number like "1.1.1" and a level — A, AA, or AAA — indicating how essential it is. Level A covers the most fundamental requirements; almost any genuinely inaccessible site is failing Level A rules. Level AA is the level most organisations target, and the level required by UK law for public sector sites. Level AAA is the most stringent and is rarely required outside specialist contexts. When you see "WCAG 2.1 AA" mentioned, it simply means "the standard, mid-tier, widely-expected level of accessibility compliance."
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-guide.html:254:Text must have sufficient contrast against its background to be readable — this affects not just visually impaired users, but anyone using a phone outdoors in bright sunlight, or anyone with mild age-related vision changes, which is a much larger group than "accessibility" might initially suggest. Light grey text on a white background is a classic failure: it might look stylish on a designer's monitor but becomes genuinely unreadable for a meaningful chunk of real visitors. "Contrast ratio" is a precise mathematical measurement comparing the brightness of text against its background; WCAG AA requires a minimum ratio of 4.5:1 for normal text, or 3:1 for large text. Fix: use the Accessibility Audit to find failing elements — it shows you the exact ratio for each one — then darken the text colour until it passes.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-guide.html:266:Run the Accessibility Audit and get actionable results in minutes. Pay as you go — no subscription needed.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/accessibility-guide.html:302:The Accessibility Audit tests your page against WCAG 2.2 level AA and lists each finding, including /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-cls-images.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-query-match.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ssl-iis-bindings.html:526: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-html-errors-wordpress.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-noindex-disallow.html:104: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-crawl-budget.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-gbp-attributes.html:499: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-headless-ecommerce-seo.html:510: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-high-lcp-mobile.html:519: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-migration-redirects.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-images-shopify.html:503: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-stale-datemodified.html:199: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/how-to-fix-ai-overviews-citation.html:526: "WCAG compliance", /var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/demo-index.html:365:
Authorship and attribution: Every AIWebPageSEO Security Audit, Accessibility Audit and related AIWebPageSEO technical audit or tool described here is my own work. WCAG Repair is the third-party scanner under examination. WAVE and the separate axe-core scan are independent third-party evidence, not audits I authored.
/var/www/vhosts/aiwebpageseo.com/site-audit/public/aipageseo-demo-pages/wcag-repair-full-comparison.html:22:An evidence-led examination of scanner contradictions, unsupported failures, manual-review classifications and missing diagnostic evidence. Independent axe-core and WAVE results are used to test WCAG Repair claims, not to celebrate positive scores.
Assessment scope: WCAG Repair's saved multi-page audit is compared with its own internal scoring, an independent axe-core homepage scan dated 19 October 2026, the WAVE homepage assessment and the supplied My AIWebPageSEO Audit security evidence. The question is whether the scanner actually documents the test and evidence supporting each negative verdict.
Confirmed reporting inconsistency. WCAG Repair's Site Health module reports security headers as 0/6, while its Security module reports 100%. The report does not supply matching raw HTTP responses that would explain the discrepancy. The two verdicts conflict, and the published audit gives no per-header response evidence to explain why.
Independent countercheck. WCAG Repair reports 201 issues across ten pages. The independent a11y-check.eu axe-core scan of the homepage reports zero automated violations, 46 passed checks and one contrast review item. WCAG Repair does not expose sufficient element-level evidence for all 201 issues in the saved report. Its homepage findings cannot be independently checked against the zero-violation axe-core homepage result where affected elements and rule evidence are withheld.
Classification risk. WCAG Repair flags 1,394 colour-contrast occurrences for manual review. These must not be presented as 1,394 confirmed WCAG failures. The independent axe-core scan likewise could not resolve the background colour of 21 gradient-backed elements; its report identifies them as a single manual-review category, not a violation.
Unsupported negative finding in the published report. WCAG Repair reports an HTTP-to-HTTPS redirection problem and missing HSTS in Site Health, while My AIWebPageSEO Audit's security audit records the corresponding checks as passing. WCAG Repair does not show the HTTP status, Location header, HSTS response header or redirect chain used to reach either negative conclusion. The published audit therefore does not substantiate these failures.
Evidence gap. The saved WCAG Repair report does not disclose all 201 element-level issues. A numerical total without a complete URL, selector, rule, evidence and remediation record prevents independent verification of those undisclosed claims. The published audit asks readers to accept findings that it does not disclose or substantiate.
Methodological weakness. WCAG Repair's 86/100 security score and My AIWebPageSEO Audit's 97/100 security score arise from different checks and weights. A numerical grade does not validate a negative finding. WCAG Repair must disclose which checks failed and what observable evidence supports each verdict.
Independent primary evidence: a11y-check.eu generated an axe-core WCAG 2.1 AA report on 19 October 2026 for the assessed website with 0 violations, 46 passed checks and 1 manual-review category affecting 21 elements. WAVE reported 18 alerts and an AIM score of 9.7/10; alerts are not automatically failures.
Security headers are scored 0% in WCAG Repair’s Site Health module, but 100% in its Security module. The published report gives mutually inconsistent conclusions without the header-level evidence necessary to reconcile them. Its HTTP-to-HTTPS and HSTS failure verdicts also lack the actual HTTP responses needed to substantiate those conclusions.
Do not misread the accessibility counts: 1,394 colour-contrast occurrences are flagged for manual review; they are not 1,394 additional confirmed violations. The free HTML does not reveal all 201 element-level findings.
The submitted My AIWebPageSEO Audit security report supplies 64 classified checks (47 pass, 2 warning, 11 N/A, 4 information), including explicit CSP directive semantics and contextual interpretation of optional/deprecated headers. This is independently assessable report granularity. WCAG Repair's saved free HTML provides Site Health security headers 0/6 and Security security headers 100%, without raw per-response header evidence to reconcile the scoring models. This is an evidence-presentation defect in the accessible export; it is not evidence that all WCAG Repair checks are technically unsound.
Separate My AIWebPageSEO Audit products such as Spam Audit and Accessibility Audit are documented capabilities, but their accuracy, coverage and superiority over competing products cannot be quantified from a security scan alone. The relevant published-report question is whether WCAG Repair provides those inputs, selectors, response chains and check definitions for its own failed checks.
Each finding is assessed on whether WCAG Repair demonstrates the conclusion it publishes. A failed check without its supporting diagnostic evidence is classified as an unsubstantiated audit finding.
The 64-check security assessment reports named response-header controls rather than a single unexplained header score. Its documented inventory covers Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, Cross-Origin-Resource-Policy and Cross-Origin-Opener-Policy. The reported security-audit outcome is 97/100, with 47 PASS, two WARN, 11 N/A and four INFO results. The overall score is contextual information, not a substitute for those individual checks.
The 64-check security assessment reports named response-header controls rather than a single unexplained header score. Its documented inventory covers Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, Cross-Origin-Resource-Policy and Cross-Origin-Opener-Policy. The reported security-audit outcome is 97/100, with 47 PASS, two WARN, 11 N/A and four INFO results. The overall score is contextual information, not a substitute for those individual checks.
The saved WCAG Repair results page gives Security Headers 0/6, or 0%, within Site Health, while the Security section gives Security Headers 100%. These values cannot be read as one coherent result for an identical set of six checks. If the modules use different tests, WCAG Repair needs to name them and explain the difference. It does neither in the available results. This contradiction exists inside its own output and does not depend on trusting another scanner.
A security-header audit should identify the tested HTTPS response, header name, actual value, applicable rule and whether the header is expected for that resource. CSP needs particular attention: the mere presence of a policy does not prove that directives are suitably restrictive. Likewise, COOP and CORP can be intentionally configured according to application architecture. My AIWebPageSEO Audit's itemised controls provide a more inspectable basis than WCAG Repair's incompatible module-level percentages.
NEGATIVE — WCAG Repair produces an internally inconsistent header assessment and does not reconcile it. POSITIVE — my AIWebPageSEO Audit names the controls and records their results individually. This is a demonstrable difference in report quality and audit traceability.
My AIWebPageSEO Security Audit explicitly marks HTTP-to-HTTPS redirection PASS. The supplied server configuration also contains a port-80 redirect returning HTTP 301 to the HTTPS scheme, preserving the requested path. The audit result and configured behaviour point in the same direction: the tested site is intended to enforce encrypted transport.
My AIWebPageSEO Security Audit explicitly marks HTTP-to-HTTPS redirection PASS. The supplied server configuration also contains a port-80 redirect returning HTTP 301 to the HTTPS scheme, preserving the requested path. The audit result and configured behaviour point in the same direction: the tested site is intended to enforce encrypted transport.
WCAG Repair marks HTTP-to-HTTPS redirection FAIL and states that the HTTP endpoint returned status 200 without redirecting. This is not a minor grading disagreement: the two reports assert opposite observable HTTP behaviours. The WCAG Repair results supplied here do not include the exact request, hostname variant, response headers or returned body establishing its claimed 200 response.
For a redirecting HTTP endpoint, the client normally receives a 3xx response and a Location header identifying the HTTPS target. A status 200 for that same initial HTTP request means the requested resource was served rather than redirected. A proper report records the initial URL, status and Location, including any intermediate hops. WCAG Repair's unexplained failure can cause a site to be penalised for a transport control that my AIWebPageSEO Audit reports as passed.
POSITIVE — my AIWebPageSEO Audit records a direct redirect PASS supported by the documented server configuration. NEGATIVE — WCAG Repair reports the opposite result without displaying the HTTP exchange on which it relies. The evidence here is a recorded audit and configuration comparison, not a newly captured network transaction.
My AIWebPageSEO Security Audit explicitly records Strict-Transport-Security as PASS. The supplied server configuration specifies a one-year max-age, includeSubDomains and preload in the HSTS value, with configuration intended to add the header to HTTPS responses. This is more specific evidence than a generic security grade.
My AIWebPageSEO Security Audit explicitly records Strict-Transport-Security as PASS. The supplied server configuration specifies a one-year max-age, includeSubDomains and preload in the HSTS value, with configuration intended to add the header to HTTPS responses. This is more specific evidence than a generic security grade.
WCAG Repair reports HSTS missing. It does not identify which HTTPS URL it requested, the status returned or the headers observed. The contradiction is direct: one audit records the presence of HSTS and the other records its absence.
HSTS is defined by RFC 6797 and is conveyed in HTTPS responses. Looking for the header on an unencrypted HTTP response is not an appropriate way to determine whether an HTTPS endpoint implements HSTS. The effective policy also depends on max-age and deployment details; a site-wide assertion should identify the host and response actually examined. An unsupported missing-HSTS verdict wrongly suggests browsers lack a transport protection.
POSITIVE — my AIWebPageSEO Audit records HSTS PASS and has corroborating configuration evidence. NEGATIVE — WCAG Repair's published missing-header finding is contrary to that evidence and lacks a corresponding HTTPS response trace.
My AIWebPageSEO Security Audit records HTTP-to-HTTPS redirection as PASS. Separately, the documented Redirect Chain Checker enumerates redirect hops, HTTP status codes and destination URLs, and detects excessive chains or loops. This matters because the existence of a redirect is normal: moving from HTTP to HTTPS, canonicalising a hostname or forwarding an old page does not itself imply suspicious behaviour.
My AIWebPageSEO Security Audit records HTTP-to-HTTPS redirection as PASS. Separately, the documented Redirect Chain Checker enumerates redirect hops, HTTP status codes and destination URLs, and detects excessive chains or loops. This matters because the existence of a redirect is normal: moving from HTTP to HTTPS, canonicalising a hostname or forwarding an old page does not itself imply suspicious behaviour.
WCAG Repair marks 'No Suspicious Redirects' failed. Its available Security summary gives no originating URL, destination hostname, intermediate hop, reputation classification or reason for suspicion. The adverse finding therefore cannot be traced to an actual destination in the published report. A scanner should not ask the site owner to accept a security accusation without identifying the address it considers dangerous.
Redirect-chain integrity and malicious-destination classification are related but distinct checks. A malicious-redirect determination requires the actual chain plus a stated detection criterion, such as a dangerous external destination, unexpected host transition or malicious reputation signal. My AIWebPageSEO Audit demonstrably documents redirect paths and passes its HTTPS-enforcement test; the available evidence does not identify a separately recorded malicious-destination PASS. That distinction prevents inventing a result while still holding WCAG Repair responsible for its opaque failure.
NEGATIVE — WCAG Repair reports a suspicious-redirect failure without naming a suspicious redirect. POSITIVE — my AIWebPageSEO Audit documents redirect-hop analysis and records secure redirection as passing. The defect in WCAG Repair is substantive: its negative claim cannot be investigated or corrected from the evidence it supplies.
My AIWebPageSEO Security Audit includes a specific check for Cache-Control on private responses. It records that check as N/A when the relevant preconditions — cookies or private data — are absent. This is an intentional distinction between an inapplicable risk and a failed control, not an omission.
My AIWebPageSEO Security Audit includes a specific check for Cache-Control on private responses. It records that check as N/A when the relevant preconditions — cookies or private data — are absent. This is an intentional distinction between an inapplicable risk and a failed control, not an omission.
WCAG Repair marks 'Cache Headers' failed in the Security report. The visible result does not identify a URL, resource classification, observed Cache-Control directive or reason that the response should not be cached. That missing context matters because caching is normal and often desirable for public resources.
A public static page can legitimately use caching directives, whereas authenticated, personalised or sensitive responses require careful storage controls. 'no-cache' permits storage subject to revalidation; 'no-store' is a stronger instruction against storage. A security finding should explain which data is at risk and what directive is required. Scoring every absent or different cache header as a security failure conflates performance policy with confidentiality risk.
POSITIVE — my AIWebPageSEO Audit evaluates the security significance of the response and explains N/A results. NEGATIVE — WCAG Repair's cache failure is not tied to a named resource or concrete exposure in the available report. This difference directly affects the reliability of its security score.
My AIWebPageSEO Audit has broader AI-readiness tooling, including assessment of machine-readable website information and separate structured-data capabilities. Those tools address discoverability and interoperability through multiple formats rather than assuming one legacy integration file is compulsory.
My AIWebPageSEO Audit has broader AI-readiness tooling, including assessment of machine-readable website information and separate structured-data capabilities. Those tools address discoverability and interoperability through multiple formats rather than assuming one legacy integration file is compulsory.
WCAG Repair marks 'AI Plugin Manifest' failed. Its published result does not establish that the audited website offers an application plugin requiring an ai-plugin.json manifest, nor does it identify a general standard making that file mandatory for websites. An absent optional integration file is not, by itself, a website security vulnerability.
The ai-plugin.json convention arose in a particular plugin ecosystem. It is not a WCAG accessibility success criterion, HTTP security header or universal search indexing requirement. A meaningful AI-readiness assessment should distinguish optional ecosystem compatibility from machine-readable content, structured data, crawler accessibility and other capabilities. Treating the optional file as a blanket failure can reduce an AI-readiness score even when the site has no reason to publish it.
NEGATIVE — WCAG Repair applies a failure label to an optional, context-dependent integration artefact without demonstrating applicability. POSITIVE — my AIWebPageSEO Audit documents a wider range of AI-readable content checks. This is a methodological advantage, not a claim that every AI-readiness test on either platform is equivalent.
My AIWebPageSEO Audit documents structured-data analysis and tooling for JSON-LD, schema.org types and Google-oriented validation requirements. This allows a reviewer to examine markup syntax, recognised entity types, required properties, recommended properties and actionable errors. A structured-data assessment is meaningful when it names the precise node and property at issue.
My AIWebPageSEO Audit documents structured-data analysis and tooling for JSON-LD, schema.org types and Google-oriented validation requirements. This allows a reviewer to examine markup syntax, recognised entity types, required properties, recommended properties and actionable errors. A structured-data assessment is meaningful when it names the precise node and property at issue.
WCAG Repair reports 'Structured Data for AI' as failed in its AI-readiness checks. The visible report does not supply the tested page, extracted JSON-LD block, schema type, invalid property, parser error or validation rule. The phrase 'for AI' also does not define a universally required schema standard. A website can publish valid structured data without satisfying an undefined vendor-specific criterion.
Schema.org vocabulary validity, Google's feature-specific eligibility and an individual AI product's data-ingestion preferences are different questions. A validator should not collapse them into a single unqualified failure. For example, a syntactically valid JSON-LD block may be ineligible for a particular rich-result feature without being invalid structured data. A diagnostic report should explain which standard or feature is being applied and why the observed markup fails it.
POSITIVE — my AIWebPageSEO Audit has documented, rule-specific structured-data tools. NEGATIVE — WCAG Repair offers a failed category without the source markup or validation rule required to reproduce or remedy the problem. This is a substantive diagnostic gap, not merely a presentation preference.
My AIWebPageSEO Accessibility Audit is documented as using axe-core alongside supplementary checks, including keyboard behaviour, focus, reflow, text spacing, non-text contrast, flashing and navigation consistency. The separate independent axe-core report for the homepage records zero automated violations, 46 passed checks and one manual-review category affecting 21 gradient-related elements. These are specific method and result statements.
My AIWebPageSEO Accessibility Audit is documented as using axe-core alongside supplementary checks, including keyboard behaviour, focus, reflow, text spacing, non-text contrast, flashing and navigation consistency. The separate independent axe-core report for the homepage records zero automated violations, 46 passed checks and one manual-review category affecting 21 gradient-related elements. These are specific method and result statements.
WCAG Repair reports 201 accessibility issues across ten pages: one critical, 31 major and 169 minor. Its free report shows some issue classes, including labels, contrast, touch targets, accessible names and keyboard-accessible scrollable regions, but does not expose the complete URL-and-element inventory behind all 201 instances. A ten-page total cannot fairly be compared numerically with a one-page scan without first matching the page set.
For each contested issue the scanner should provide the URL, selector or DOM excerpt, rule identifier, tested state, viewport and observed failure. That evidence distinguishes a genuine defect from a false positive, a different page state or a difference in rule coverage. The AIWebPageSEO's documented supplementary tests matter because automated axe-core results alone cannot establish every aspect of WCAG conformance. WCAG Repair's available report does not give enough detail to audit its complete issue total against the independent homepage result.
POSITIVE — my AIWebPageSEO Audit documents axe-core plus additional accessibility checks, and the independent homepage scan records zero automated violations. NEGATIVE — WCAG Repair's published free summary does not make all 201 alleged issues individually traceable. This is a concrete evidence-disclosure weakness; it is not a claim that ten pages were proved issue-free.
The independent axe-core report identifies 21 homepage elements for manual assessment because gradient backgrounds prevent a reliable automated foreground/background contrast calculation. It records those items separately from its zero confirmed automated violations. That distinction is technically important.
The independent axe-core report identifies 21 homepage elements for manual assessment because gradient backgrounds prevent a reliable automated foreground/background contrast calculation. It records those items separately from its zero confirmed automated violations. That distinction is technically important.
WCAG Repair lists eight visible contrast-related issues among its top findings and separately lists a much larger number of contrast occurrences requiring manual review. The free report does not expose computed colour values, contrast ratios and corresponding DOM selectors for every contested instance. Its headline totals therefore do not allow an external reviewer to reproduce each contrast decision.
WCAG text contrast generally requires at least 4.5:1 for ordinary text or 3:1 for qualifying large text, subject to exceptions. A reliable result depends on rendered text colour, background colour at the text's location, font characteristics and state. Gradients, images and overlays can defeat simplistic colour sampling. A tool should mark such cases as inconclusive until a representative rendered contrast value is established; it should not silently convert uncertainty into a confirmed failure.
POSITIVE — the independent axe-core result explicitly separates gradient-related manual review from violations. NEGATIVE — WCAG Repair's available report lacks sufficient per-element measurements to reproduce its displayed contrast failures. The issue is diagnostic substantiation, not an assumption that all contrast warnings are false.
The saved WCAG Repair report distinguishes 201 accessibility issues from 1,394 colour-contrast occurrences flagged for manual review. The 1,394 occurrences are distributed across nine pages and are not 1,394 additional confirmed violations. Any summary that combines these figures into a single failure count would misstate the source.
The saved WCAG Repair report distinguishes 201 accessibility issues from 1,394 colour-contrast occurrences flagged for manual review. The 1,394 occurrences are distributed across nine pages and are not 1,394 additional confirmed violations. Any summary that combines these figures into a single failure count would misstate the source.
The independent axe-core homepage report records one manual-review category involving 21 gradient-backed elements while reporting zero automated violations. That demonstrates why occurrence counts, categories and confirmed violations must remain separate. One rule category can affect multiple elements, and a manual-review item has not yet received a definitive pass/fail determination.
A serious accessibility audit must maintain separate tallies for automated failures, potential issues needing human inspection, passed rules and not-applicable rules. It must also retain page and element identifiers so repeated instances are not confused with distinct accessibility criteria. Large counts are not inherently more thorough: they are useful only when their definitions and evidence are transparent.
The independent axe-core scanner's explicit manual-review classification is a positive. WCAG Repair's 1,394 figure must be described accurately as manual-review occurrences, not proven violations. This section is retained because misinterpretation of the figure would materially distort the comparative assessment.
My AIWebPageSEO Security Audit identifies 64 checks and classifies them as 47 PASS, two WARN, 11 N/A and four INFO. The counts reconcile to the stated total. Crucially, the N/A and INFO categories are visible rather than being disguised as failures. This gives the reader a defined basis for understanding why a control did or did not affect the security assessment.
My AIWebPageSEO Security Audit identifies 64 checks and classifies them as 47 PASS, two WARN, 11 N/A and four INFO. The counts reconcile to the stated total. Crucially, the N/A and INFO categories are visible rather than being disguised as failures. This gives the reader a defined basis for understanding why a control did or did not affect the security assessment.
The available WCAG Repair Security summary says 'and 3 more failing checks' without naming those checks. It reports an overall Security score of 86/100 and 43/51 checks passed, but the displayed summary does not expose the full failure inventory. This means the reader cannot reconstruct the deduction, identify affected URLs or determine whether the remaining failed checks concern applicable security requirements.
A security audit is an engineering diagnostic, not simply a score. Every adverse result should identify its control, evidence, applicability, severity and remediation. Hiding three failures prevents an independent reviewer from distinguishing real vulnerabilities from optional hardening, policy preferences or scanner mistakes. A complete itemised inventory is therefore a functional advantage, not merely a more attractive presentation.
POSITIVE — my AIWebPageSEO Audit accounts for all 64 check outcomes and distinguishes applicability from failure. NEGATIVE — WCAG Repair withholds the identity of three reported failures in its free summary. The consequence is reduced reproducibility and a weaker basis for trusting the overall score.
Finding not substantiated: the scanner does not provide the evidence required to justify its negative conclusion. Internal inconsistency: the scanner publishes conflicting results. Manual review: the scanner itself has not confirmed a failure. Supported: the published evidence supports the finding.
Accessibility obligations depend on the applicable legal context and WCAG conformance target. An optional security or AI-readiness enhancement is not automatically a legal requirement. This page does not claim legal certification or a complete element-level re-audit.
Sources used: saved WCAG Repair results page, uploaded Nginx server configuration, My AIWebPageSEO Audit security audit, and available source files. Standards for independent checks: W3C WCAG 2.2, RFC 6797 (HSTS), RFC 9110 (HTTP), and RFC 9111 (Caching).
This is an evidence review of the findings visible in the saved free report. Unexposed paid findings are not fabricated. No third-party company is accused of intentional misrepresentation.