Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 5 REVIEW 4 FIX

Mobile-Readable Font Sizes

Action

69% of visible text renders at >= 12 CSS px (149 below threshold)

FIX

69% of visible text renders at >= 12 CSS px (149 below threshold)

149 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.5px ("Scaplet Search"); <span> 9.5px ("Ask Scaplet anything"); <span> 10.0px ("yourbrand.com"); <span> 10.0px ("+3"); <div> 11.5px ("Organic clicks").

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #7735fd

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 ModePartial Dark Mode

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.

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found · Scaplet ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Scaplet

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name Scaplet ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode browser ✗

Name Scaplet Display Mode browser Theme Color #7735fd Background Color #fbfbfb Icons 2 icon(s)

PWA Depth

2 PWA signal(s) surfaced

REVIEW

2 PWA signal(s) surfaced

Manifest declares display="browser" -- no PWA UX

When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

h2 What does AI say about you?

1.00:1

#FFFFFF

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

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 Get found when	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 Built on	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 impressions.	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 An agency's worth of…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 SEO isn't a project …	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 Results in 30 days.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Connect in few minut…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 Already working on h…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 Your SEO team,	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 from	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 Start with a free au…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 A few good questions…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h2 What does AI say abo…	1.00:1	3.0:1	#FFFFFF	#FFFFFF	Fail
h3 A payments API earne…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h3 An accounting app gr…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h3 An invoicing app rep…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h3 A data platform ship…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h3 A fintech ranked #1 …	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h3 A payments API earne…	15.23:1	3.0:1	#0E2A27	#FFFFFF	Pass
h3 An accounting app gr…	15.23:1	3.0:1	#0E2A27	#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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

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

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

Heading Hierarchy

22 headings, 1 skip(s)

PASS

22 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 Get found whenbuyers ask ChatGPT.Perplexity.Google.Gemini.AI Overviews.
H3 A payments API earned 7 ChatGPT citations skipped
H3 An accounting app grew clicks by 212%
H3 An invoicing app replaced a $6,000 retainer
H3 A data platform shipped 46 fixes
H3 A fintech ranked #1 for payouts
H3 A payments API earned 7 ChatGPT citations
H3 An accounting app grew clicks by 212%
H3 An invoicing app replaced a $6,000 retainer
H3 A data platform shipped 46 fixes
H3 A fintech ranked #1 for payouts
H2 Tools tell you.Agencies advise you.Scaplet does it.
H2 Built on 2.4 billion impressions.
H2 An agency's worth of work. Minus the monthly call.
H2 SEO isn't a project you finish. It's more like the dishes.
H2 Results in 30 days. Effort: about 12 minutes.
H2 Connect in few minutes.
H2 Already working on hundreds of sites.
H2 Your SEO team,from $1 a day.
H2 Start with a free audit. Stay for the fixes.
H2 A few good questions.
H2 What does AI say about you?

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

A+

Heading Text Quality

All 22 heading(s) have substantive, well-formed text

PASS

All 22 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

Alt Text Quality

All 33 images OK

PASS

All 33 images OK

3 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

29 image(s) with good alt text

33 images 29 good alt text 1 decorative

Issue	Count
too long	3 image(s)

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#base-ui-_r16R_5m6_	input	Your website	aria-label
#base-ui-_r27R_bl_	input	Your website	aria-label
#base-ui-_r29R_2s_	input	Your website	aria-label

Link & Button Quality

94 links, 55 buttons — all OK

PASS

94 links, 55 buttons — all OK

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://startupfa.me/s/scaplet?utm_source=scaplet.com; https://aiboom.tools; https://gets.tools

91 link(s) with descriptive text

94 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://startupfa.me/s/scaplet?utm_sourc…	Scaplet - Featured on Startup …	new tab	Add '(opens in new tab)' to text
https://aiboom.tools	Featured on AIBoom.Tools	new tab	Add '(opens in new tab)' to text
https://gets.tools	Featured on Gets.Tools	new tab	Add '(opens in new tab)' to text

146 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://startupfa.me/s/scaplet?utm_source=scaplet.com; https://aiboom.tools; https://gets.tools

Why this matters

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

Form Input Types

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

PASS

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

Input "website" should use type="url" (currently type="text")

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

Input "website" should use type="url" (currently type="text")

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

Input "website" should use type="url" (currently type="text")

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

A+

Form Input Quality

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

PASS

3 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

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

tabindex="-1" on naturally-focusable <button id="base-ui-_r22R_ba_">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="base-ui-_r22R_ja_">

tabindex="-1" on naturally-focusable <button id="base-ui-_r22R_ra_">

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 UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 21 passed

PASS

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.

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
Free audit `div > div > div > span`
No account needed `div > div > div > span`
ASK SCAPLET ANYTHING `div > div > div > span`

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
A payments API earned 7 ChatGPT citations `div.story-rail > div.a-cards > article.a-card > h3`

These are opportunities to improve keyboard navigation in your application.

○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>`

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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 have a discernible name

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○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

○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

○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.

○Input buttons have discernible text.

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

○Links are distinguishable without relying on color.

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○`<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.

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

○`<td>` elements in a large `<table>` have one or more table headers.

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