Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 3 REVIEW 7 FIX

Heading Hierarchy

Action

39 headings, 4 skip(s)

FIX

39 headings, 4 skip(s)

Multiple H1 headings (4 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Boost Your Website's SEO with High-Quality Backlinks
H2 Our SEO Services
H3 Ahrefs DR Boost
H3 Moz DA Increase
H3 Majestic TF Power
H3 PBN Backlinks
H3 Guest Post Services
H3 Dofollow Backlinks
H2 Plans: DR, DA & TF
H1 Ahrefs Domain Rating (DR) Boost Service duplicate H1
H3 Why Clients Prefer Our DR Service: skipped
H4 Metric Impact Levels
H1 Moz Domain Authority (DA) Increase Service duplicate H1
H3 Why Clients Prefer Our DA Service: skipped
H4 Metric Impact Levels
H1 Majestic Trust Flow (TF) Power Service duplicate H1
H3 Why Clients Prefer Our TF Service: skipped
H4 Metric Impact Levels
H2 PBN Backlinks Packages
H2 Guest Post Websites
H2 Secure Payment Methods
H4 Bank Transfer skipped
H4 Wise Transfer
H4 Payoneer
H4 Bitcoin (BTC)
H4 USDT
H4 Visa / Mastercard
H4 PayPal
H2 Why Choose Us?
H3 Fast Delivery
H3 Dofollow Focus
H3 Reporting
H3 Support
H3 Order Notes
H3 Privacy Display
H3 About Us
H3 Quick Links
H3 Services
H3 Contact Us

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

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.

Why this matters

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-9lpzna

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://toprankalliance.shop/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://toprankalliance.shop/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

18 pass 2 fail WCAG AA 1 pass AA only

h2 Our SEO Services

2.63:1

#000000

#1F46B9

needs 3.0:1 (large text)

24px · mid-page

h3 Ahrefs DR Boost

2.52:1

#000000

#1E43B4

needs 3.0:1 (large text)

19px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Boost Your Website's…	3.02:1	3.0:1	#000000	#214FC8	Pass
h1 Ahrefs Domain Rating…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Moz Domain Authority…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Majestic Trust Flow …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our SEO Services	2.63:1	3.0:1	#000000	#1F46B9	Fail
h2 Plans: DR, DA & TF	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 PBN Backlinks Packag…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Guest Post Websites	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Secure Payment Metho…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Why Choose Us?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Ahrefs DR Boost	2.52:1	3.0:1	#000000	#1E43B4	Fail
h3 Moz DA Increase	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Majestic TF Power	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 PBN Backlinks	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Guest Post Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Dofollow Backlinks	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Why Clients Prefer O…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Why Clients Prefer O…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Why Clients Prefer O…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Fast Delivery	21.00:1	3.0:1	#000000	#FFFFFF	Pass

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.

Lighthouse Accessibility Audits

Score 80/100 — 6 failing, 18 passed

REVIEW

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#guest-posts > div.container > div.search-bar > button `section#guest-posts > div.container > div.search-bar > button`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
View Plans `body > section.hero > div.container > button.cta-button`
DR `div.container > div.metric-detail > div.metric-header > div.metric-logo`
POPULAR `div.pricing-block > div.pricing-grid > div.price-card > span.popular-badge`
DR 30 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
DR 40 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
DR 50 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
DR 60 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
DR 70 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
DR 75 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
PREMIUM `div.pricing-block > div.pricing-grid > div.price-card > span.popular-badge`
DR 80 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
DR 85 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
DA `div.container > div.metric-detail > div.metric-header > div.metric-logo`
DA 10 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
POPULAR `div.pricing-block > div.pricing-grid > div.price-card > span.popular-badge`
DA 20 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
DA 30 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
DA 40 `div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
POPULAR `div.pricing-block > div.pricing-grid > div.price-card > span.popular-badge`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
Place Order `div.pricing-grid > div.price-card > div.order-row > button.cta-button`
$15 `tbody > tr > td > span.pbn-price`
Order `tbody > tr > td > button.cta-button`
$30 `tbody > tr > td > span.pbn-price`
Order `tbody > tr > td > button.cta-button`
$45 `tbody > tr > td > span.pbn-price`
Order `tbody > tr > td > button.cta-button`
$75 `tbody > tr > td > span.pbn-price`
Order `tbody > tr > td > button.cta-button`
$150 `tbody > tr > td > span.pbn-price`
Order `tbody > tr > td > button.cta-button`
$300 `tbody > tr > td > span.pbn-price`
Order `tbody > tr > td > button.cta-button`
$450 `tbody > tr > td > span.pbn-price`
Order `tbody > tr > td > button.cta-button`
$750 `tbody > tr > td > span.pbn-price`
Order `tbody > tr > td > button.cta-button`
$1,500 `tbody > tr > td > span.pbn-price`
Order `tbody > tr > td > button.cta-button`
Place Order (Selected) `div.gp-wrap > div.gp-head > div.right > button.cta-button`
WhatsApp Order `div.gp-wrap > div.bulk-bar > div.actions > button.cta-button`

These are opportunities to improve the legibility of your content.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Why Clients Prefer Our DR Service: `div.metric-content > div.metric-description > div.metric-advantages > h3`
Why Clients Prefer Our DA Service: `div.metric-content > div.metric-description > div.metric-advantages > h3`
Why Clients Prefer Our TF Service: `div.metric-content > div.metric-description > div.metric-advantages > h3`
Bank Transfer `div.container > div.payment-grid > div.payment-card > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Website Niche Metrics Traffic Price te***ch.com ID: GP-001 Technology DR 9… `div.container > div.gp-wrap > div > table.gp-table`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Form elements have associated labels

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

Form Accessibility

1 of 32 controls have issues

PASS

1 of 32 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" id="searchInput">

31 control(s) properly labeled

32 controls

31 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
input	checkbox	Select guest post site	aria-label
#orderType	text	Order Type	for/id
#orderPlan	text	Selected Plan / Items	for/id
#orderPrice	text	Estimated Price	for/id
#paymentVia	select	Payment Via (click to choose)	for/id
#websiteUrl	url	Website URL	for/id
#targetKeywords	text	Targeted Keywords	for/id
#articleText	textarea	Article Notes (optional)	for/id
#searchInput	text	(Search by niche, traffic, DR, DA, TF (example: tech, 80, 200k)...)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

1 issue(s) across 23 links and 40 buttons

PASS

1 issue(s) across 23 links and 40 buttons

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button (#888 on page)

23 link(s) with descriptive text

23 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label

62 links and buttons have descriptive text

Icon-only buttons need an aria-label so screen readers can announce them.

button (#888 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "searchInput" should use type="search" (currently type="text")

Field name "searchInput" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

32 form control(s) checked, no input-semantic issues

PASS

32 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 370 visible text node(s) render at >= 12 CSS pixels

PASS

All 370 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.