Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction26 landmarksFIX
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
F404 Error PageActionSoft 404 detectedFIX
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
FFavicon & BrandingAction2 icon(s) detectedFIX
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy14 headings, 1 skip(s)REVIEW
- H2 for Growing Businesses
- H1 Reliable Web & IT Solutions
- H1 Business-Focused Technical Support You Can Depend On duplicate H1
- H2 Our Services Include:
- H2 Why Businesses Choose Us
- H3 Senior-Level Experience
- H3 Reliable Communication
- H3 Practical Solutions
- H3 Long-Term Support
- H1 Need Help With Your Website or Technology Systems? duplicate H1
- H3 Interesting Links skipped
- H3 Where to find us
- H3 More Stuff
- H3 Our Office Hours
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
BTap Target Adequacy2 tap target(s) too small or too close togetherREVIEW
BMobile-Readable Font Sizes94% of visible text renders at >= 12 CSS px (3 below threshold)REVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 4 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
1 contrast failures on background images/gradients
These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Reliable Web & | 1.00:1 | 3.0:1 | #FFFFFF | #FFFFFF | Fail |
| h1 IT Solutions | 1.00:1 | 3.0:1 | #FFFFFF | #FFFFFF | Fail |
| h1 Business-Focused Tec… | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h1 Need Help With Your … | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h2 for Growing Business… | 3.99:1 | 3.0:1 | #FFFFFF | #897D78 | Pass |
| h2 Our Services Include… | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h2 Why Businesses Choos… | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h3 Senior-Level Experie… | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h3 Reliable Communicati… | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h3 Practical Solutions | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h3 Long-Term Support | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h3 Interesting Links | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h3 Where to find us | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h3 More Stuff | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h3 Our Office Hours | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| title Hopson Technology | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Home | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Services | 11.28:1 | 4.5:1 | #000000 | #BDBEBF | Pass |
| span Pricing Plans | 3.24:1 | 4.5:1 | #000000 | #5D5E60 | Fail |
| span Free Website Review | 2.64:1 | 4.5:1 | #000000 | #4D5345 | Fail |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
A+Heading Text QualityAll 14 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityAll 4 images OKPASS
A+Form AccessibilityNo form controlsPASS
ALink & Button Quality24 links, 0 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://twitter.com/hopsontechnology | Link to X | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/company/hopson-… | Link to LinkedIn | new tab | Add '(opens in new tab)' to text |
Add '(opens in new tab)' to link text or aria-label.
https://twitter.com/hopsontechnology; https://www.linkedin.com/company/hopson-technology-inc/
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
A+Form Input TypesNo form controls on this pagePASS
A+Form Input QualityNo form controls on this pagePASS
A+Mobile Keyboard & AutofillNo form controls -- mobile keyboard check is N/APASS
A+Document LanguageLang attribute set to "en"PASS
A+Tabindex Anti-Patterns0 positive, 1 -1-on-focusablePASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
ALighthouse Accessibility AuditsScore 93/100 — 4 failing, 23 passedPASS
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
INTERESTING LINKS div.container > div.flex_column > section#text-2 > h3.widgettitle |
These are opportunities to improve keyboard navigation in your application.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Pricing Plans section#text-5 > div.textwidget > p > a |
Website Review section#text-5 > div.textwidget > p > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html#ls-global html#ls-global |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Request A Free Website Review div.entry-content-wrapper > div.flex_column > div.avia-button-wrap > a.avia-color-dark |
Contact Us div.entry-content-wrapper > div.flex_column > div.avia-button-wrap > a.avia-color-dark |
Request a Free Website Review div.flex_cell_inner > div.flex_column > div.avia-button-wrap > a.avia-button |