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 4 REVIEW 5 FIX

Mobile Keyboard & Autofill

Action

6/6 eligible field(s) missing autocomplete or inputmode

FIX

6/6 eligible field(s) missing autocomplete or inputmode

3 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name, email.

Got: <input type="text" name="name" id="name">, <input type="email" name="email" id="email">, <input type="email" name="email">

3 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.

Got: <input type="search">, <input type="email" name="email" id="email">, <input type="email" name="email">

Mobile-Readable Font Sizes

Action

52% of visible text renders at >= 12 CSS px (184 below threshold)

FIX

52% of visible text renders at >= 12 CSS px (184 below threshold)

184 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: <a> 11.2px ("Services"); <a> 11.2px ("Use Cases"); <a> 11.2px ("Pricing"); <a> 11.2px ("Integrations"); <a> 11.2px ("About").

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.

Tap Target Adequacy

1 tap target(s) too small or too close together

REVIEW

1 tap target(s) too small or too close together

1 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: SetebosStudio — AI automation for service businesses

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name SetebosStudio — AI automation for service businesses ✓192×192 icon ✗512×512 icon ✗Start URL / ✓Display Mode standalone ✓

Name SetebosStudio — AI automation for service businesses Display Mode standalone Theme Color #10b981 Background Color #050608 Icons 1 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Turn every enquiry into a

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

32px · bottom of viewport

h2 How leads

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Fixed in

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 is the pipeline

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What we

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What we

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 If it has an API,

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Questions

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What happens

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Let's

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Starter Website

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Visibility Foundation

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Website + Visibility

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI Visibility Growth

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Custom Process Automation

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 SETEBOS AIOS

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Second Brain

1.04:1

#000000

#07070A

needs 3.0:1 (large text)

19px · bottom of viewport

title SetebosStudio — AI automation for serv…

1.11:1

#000000

#101115

needs 4.5:1 (normal text)

16px · top of page (header area)

span SETEBOSSTUDIO

1.10:1

#000000

#0E0F13

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Turn every enquiry i…	1.04:1	3.0:1	#000000	#07070A	Fail
h2 How leads	1.04:1	3.0:1	#000000	#07070A	Fail
h2 Fixed in	1.04:1	3.0:1	#000000	#07070A	Fail
h2 The	1.04:1	3.0:1	#000000	#07070A	Fail
h2 is the pipeline	1.04:1	3.0:1	#000000	#07070A	Fail
h2 What we	1.04:1	3.0:1	#000000	#07070A	Fail
h2 What we	1.04:1	3.0:1	#000000	#07070A	Fail
h2 If it has an API,	1.04:1	3.0:1	#000000	#07070A	Fail
h2 Questions	1.04:1	3.0:1	#000000	#07070A	Fail
h2 What happens	1.04:1	3.0:1	#000000	#07070A	Fail
h2 Let's	1.04:1	3.0:1	#000000	#07070A	Fail
h3 Starter Website	1.04:1	3.0:1	#000000	#07070A	Fail
h3 Visibility Foundatio…	1.04:1	3.0:1	#000000	#07070A	Fail
h3 Website + Visibility	1.04:1	3.0:1	#000000	#07070A	Fail
h3 AI Visibility Growth	1.04:1	3.0:1	#000000	#07070A	Fail
h3 Custom Process Autom…	1.04:1	3.0:1	#000000	#07070A	Fail
h3 SETEBOS AIOS	1.04:1	3.0:1	#000000	#07070A	Fail
h3 Second Brain	1.04:1	3.0:1	#000000	#07070A	Fail
title SetebosStudio — AI…	1.11:1	4.5:1	#000000	#101115	Fail
span SETEBOSSTUDIO	1.10:1	4.5:1	#000000	#0E0F13	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.

Landmark Structure

4 landmarks

PASS

4 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

A+

Heading Hierarchy

17 headings

PASS

17 headings

Single H1 present

H1 Turn every enquiry into aqualified lead
H2 How leads slip away
H2 Fixed in three steps
H2 The difference is the pipeline
H2 What we automate
H2 What we offer
H3 Starter Website
H3 Visibility Foundation
H3 Website + Visibility
H3 AI Visibility Growth
H3 Custom Process Automation
H3 SETEBOS AIOS
H3 Second Brain
H2 If it has an API, wire it up
H2 Questions before you start?
H2 What happens after you book?
H2 Let's talk

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

All 15 images OK

PASS

All 15 images OK

15 image(s) with good alt text

15 images 15 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 6 controls have issues

PASS

1 of 6 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="email" name="email">

5 control(s) properly labeled

6 controls

5 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	search	Search	aria-label
#name	text	Name	for/id
#email	email	Email	for/id
#company	text	Company / Website	for/id
#message	textarea	Your message	for/id
email	email	(you@company.com)	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

A+

Link & Button Quality

60 links, 11 buttons — all OK

PASS

60 links, 11 buttons — all OK

60 link(s) with descriptive text

60 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

71 links and buttons have descriptive text

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 "company" should use type="url" (currently type="text")

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

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

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 <input>

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Not found · SetebosStudio ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

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

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.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 23 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
01 `div.problem-inner > div.problem-cards > div.problem-card > div.problem-card-number`
It's 9 PM. A potential customer just messaged your Facebook page. You'll see it… `div.problem-inner > div.problem-cards > div.problem-card > div.problem-card-scene`
02 `div.problem-inner > div.problem-cards > div.problem-card > div.problem-card-number`
Email, WhatsApp, Facebook messages, phone calls, a spreadsheet someone forgot t… `div.problem-inner > div.problem-cards > div.problem-card > div.problem-card-scene`
03 `div.problem-inner > div.problem-cards > div.problem-card > div.problem-card-number`
A customer asks for a quote at 10 AM. You promise to "get back to them." By the… `div.problem-inner > div.problem-cards > div.problem-card > div.problem-card-scene`
04 `div.problem-inner > div.problem-cards > div.problem-card > div.problem-card-number`
Most deals die from silence, not rejection. You know you should follow up with … `div.problem-inner > div.problem-cards > div.problem-card > div.problem-card-scene`
DISCOVER `div.hiw-steps > div.hiw-step > div.hiw-step-body > div.hiw-step-label`
BUILD `div.hiw-steps > div.hiw-step > div.hiw-step-body > div.hiw-step-label`
RUN `div.hiw-steps > div.hiw-step > div.hiw-step-body > div.hiw-step-label`
BEFORE `div.before-after-inner > div.ba-pipeline > div.ba-pipe-row > div.ba-pipe-label`
Enquiry arrives `div.ba-pipe-row > div.ba-pipe-flow > div.ba-pipe-step > span.ba-pipe-text`
Nobody notices `div.ba-pipe-row > div.ba-pipe-flow > div.ba-pipe-step > span.ba-pipe-text`
Manual reply `div.ba-pipe-row > div.ba-pipe-flow > div.ba-pipe-step > span.ba-pipe-text`
Quote hours later `div.ba-pipe-row > div.ba-pipe-flow > div.ba-pipe-step > span.ba-pipe-text`
Forgotten `div.ba-pipe-row > div.ba-pipe-flow > div.ba-pipe-step > span.ba-pipe-text`
Lost lead `div.ba-pipe-row > div.ba-pipe-flow > div.ba-pipe-step > span.ba-pipe-text`
Book a free audit `div.packages-inner > div.packages-grid > div.pkg-card > a.pkg-card-cta`
01 `div.after-book-inner > div.after-book-steps > div.after-book-step > div.after-book-num`
02 `div.after-book-inner > div.after-book-steps > div.after-book-step > div.after-book-num`
03 `div.after-book-inner > div.after-book-steps > div.after-book-step > div.after-book-num`
No spam. Just a reply. `main > section#start > form.contact-form > p.form-note`
No spam. Unsubscribe anytime. `footer.footer > div.footer-bottom > div.footer-newsletter > div.footer-newsletter-desc`
© 2026 SETEBOSSTUDIO `footer.footer > div.footer-bottom > div.footer-legal-row > span.footer-copy`

These are opportunities to improve the legibility of your content.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Toggle menu `div.content-layer > header.navbar > div.nav-left > button.nav-toggle`

These items highlight common accessibility best practices.

○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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○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

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

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