Issues found
No character encoding declared
minor1 occurrence
Without a declared charset, browsers may guess and mis-render text, including assistive output.
How to fix: Declare UTF-8 as the first element in <head>.
No help or contact link found
minor1 occurrence
WCAG 3.2.6 requires that help mechanisms (contact, chat, support) appear in the same location on every page so users can always find assistance.
How to fix: Add a consistent help/contact link in the header or footer on every page.
Unlock the full accessibility auditThis is the free summary. The full Pro report groups every check by WCAG principle, samples the exact failing elements, prioritises fixes with code examples, lists what needs manual review, and exports to PDF or HTML.
Get the full report — free, straight to your inboxEvery issue, the exact fixes, and your PDF download link.
Upgrade to Pro for the full report