Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 4 REVIEW 4 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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: #1b1b1d

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

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)

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

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

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

Mobile-Readable Font Sizes

Action

87% of visible text renders at >= 12 CSS px (4 below threshold)

REVIEW

87% of visible text renders at >= 12 CSS px (4 below threshold)

4 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: <p> 11.5px ("By continuing you agree to the"); <a> 11.5px ("Terms"); <p> 11.5px ("and the"); <a> 11.5px ("Privacy Policy").

Favicon & Branding

7 icon(s) detected

REVIEW

7 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

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 Vision AI

1.06:1

#000000

#09090A

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Before you continue

1.03:1

#000000

#050505

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Create your account

1.06:1

#000000

#09090A

needs 3.0:1 (large text)

24px · bottom of viewport

title Vision AI — Your Personal AI Assistant…

1.03:1

#000000

#050505

needs 4.5:1 (normal text)

16px · top of page (header area)

p Vision AI is an

1.03:1

#000000

#050505

needs 4.5:1 (normal text)

16px · top of page (header area)

strong artificial intelligence

1.03:1

#000000

#050505

needs 3.0:1 (large text)

16px · top of page (header area)

p assistant — not a human.

1.03:1

#000000

#050505

needs 4.5:1 (normal text)

16px · above the fold

p You must be

1.03:1

#000000

#050505

needs 4.5:1 (normal text)

16px · above the fold

strong 13 years or older

1.03:1

#000000

#050505

needs 3.0:1 (large text)

16px · above the fold

p to use this service.

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

p By continuing, you agree to our

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

a Terms

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

p and

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

a Privacy Policy

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

button I'm under 13

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

button I'm 13 or older

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

span Vision AI is an artificial intelligence …

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

button Got it

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

div Vision AI

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

button ✕

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Vision AI	1.06:1	3.0:1	#000000	#09090A	Fail
h2 Before you continue	1.03:1	3.0:1	#000000	#050505	Fail
h2 Create your account	1.06:1	3.0:1	#000000	#09090A	Fail
title Vision AI — Your P…	1.03:1	4.5:1	#000000	#050505	Fail
p Vision AI is an	1.03:1	4.5:1	#000000	#050505	Fail
strong artificial intellige…	1.03:1	3.0:1	#000000	#050505	Fail
p assistant — not a …	1.03:1	4.5:1	#000000	#050505	Fail
p You must be	1.03:1	4.5:1	#000000	#050505	Fail
strong 13 years or older	1.03:1	3.0:1	#000000	#050505	Fail
p to use this service.	1.02:1	4.5:1	#000000	#040404	Fail
p By continuing, you a…	1.02:1	4.5:1	#000000	#040404	Fail
a Terms	1.02:1	4.5:1	#000000	#040404	Fail
p and	1.02:1	4.5:1	#000000	#040404	Fail
a Privacy Policy	1.02:1	4.5:1	#000000	#040404	Fail
button I'm under 13	1.02:1	4.5:1	#000000	#040404	Fail
button I'm 13 or older	1.02:1	4.5:1	#000000	#040404	Fail
span Vision AI is an arti…	1.02:1	4.5:1	#000000	#040404	Fail
button Got it	1.02:1	4.5:1	#000000	#040404	Fail
div Vision AI	1.02:1	4.5:1	#000000	#040404	Fail
button ✕	1.02:1	4.5:1	#000000	#040404	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 Hierarchy

3 headings

PASS

3 headings

Single H1 present

H2 Before you continue
H1 Vision AI
H2 Create your account

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 decorative image(s) correctly marked

3 images 3 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 7 controls labeled

PASS

All 7 controls labeled

7 control(s) properly labeled

7 controls

7 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#searchInput	text	Search chats	aria-label
#userInput	textarea	Message input	aria-label
#fileInput	file	File input	aria-label
#authName	text	Your name (optional)	for/id
#authEmail	email	Email	for/id
#authPw	password	Password	for/id
#authRemember	checkbox		none

Link & Button Quality

6 links, 59 buttons — all OK

PASS

6 links, 59 buttons — all OK

2 link(s) open in new tab without warning

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

Got: /terms; /privacy

4 link(s) with descriptive text

6 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/terms	Terms	new tab	Add '(opens in new tab)' to text
/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text

63 links and buttons have descriptive text

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

/terms; /privacy

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

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

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

All 4 eligible field(s) carry autocomplete/inputmode

PASS

All 4 eligible field(s) carry autocomplete/inputmode

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

2 explicit tabindex attribute(s) checked, no anti-patterns

PASS

2 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Vision AI

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Vision AI ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Vision AI Display Mode standalone Theme Color #4f87f5 Background Color #0a0f1c Icons 2 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

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

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 29 passed

PASS

100

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.

○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

●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

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

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

●Buttons have an accessible name

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

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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

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

●Touch targets have sufficient size and spacing.

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

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