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

Form Accessibility

Action

7 of 7 controls have issues

FIX

7 of 7 controls have issues

2 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <select name="projectType">; <select name="budget">

5 control(s) rely on placeholder only

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

Got: <input type="text" name="name">; <input type="email" name="email">; <input type="text" name="business">; <input type="text" name="website">; <textarea name="details">

7 controls

0 labeled

5 placeholder only

2 unlabeled

Control	Type	Label	Method
name	text	(Name)	placeholder only
email	email	(Email)	placeholder only
business	text	(Business)	placeholder only
website	text	(Current Website)	placeholder only
details	textarea	(Tell me about your project...)	placeholder only
budget	select	(none)	none
projectType	select	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

Mobile Keyboard & Autofill

Action

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

FIX

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

2 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">, <input type="email" name="email">

1 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: email.

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

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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

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.

Mobile-Readable Font Sizes

Action

83% of visible text renders at >= 12 CSS px (39 below threshold)

REVIEW

83% of visible text renders at >= 12 CSS px (39 below threshold)

39 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.0px ("Appsero__"); <span> 11.0px ("/ Web Design & Development"); <span> 10.0px ("Scroll"); <p> 11.0px ("Paris, FR"); <span> 9.0px ("Web Design").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

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

h2 Your website is your

2.27:1

#000000

#6C3932

needs 3.0:1 (large text)

24px · mid-page

h2 Selected Work

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Behind Appsero__

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What I do

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Pretty isn't enough.

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How we work

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kind words

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Good design gets attention.

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Let's make something

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Let's make it unforgettable.

2.38:1

#000000

#6E3D34

needs 3.0:1 (large text)

19px · mid-page

h3 Maison Lumière

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Studio Noir

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Sel & Safran

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Aurelia Clinic

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Atelier Rouge

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Vance & Hale

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Maison Vœux

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Iris Moreau

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cedar Capital

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Maison Voyage

1.53:1

#000000

#3D2825

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Your website is your	2.27:1	3.0:1	#000000	#6C3932	Fail
h2 Selected Work	1.53:1	3.0:1	#000000	#3D2825	Fail
h2 Behind Appsero__	1.53:1	3.0:1	#000000	#3D2825	Fail
h2 What I do	1.53:1	3.0:1	#000000	#3D2825	Fail
h2 Pretty isn't enough.	1.53:1	3.0:1	#000000	#3D2825	Fail
h2 How we work	1.53:1	3.0:1	#000000	#3D2825	Fail
h2 Kind words	1.53:1	3.0:1	#000000	#3D2825	Fail
h2 Good design gets att…	1.53:1	3.0:1	#000000	#3D2825	Fail
h2 Let's make something	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Let's make it unforg…	2.38:1	3.0:1	#000000	#6E3D34	Fail
h3 Maison Lumière	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Studio Noir	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Sel & Safran	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Aurelia Clinic	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Atelier Rouge	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Vance & Hale	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Maison Vœux	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Iris Moreau	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Cedar Capital	1.53:1	3.0:1	#000000	#3D2825	Fail
h3 Maison Voyage	1.53:1	3.0:1	#000000	#3D2825	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

32 headings

PASS

32 headings

Single H1 present

H1 Websites witha point of view.
H2 Your website is yourfirst impression.
H3 Let's make it unforgettable.
H2 Selected Work
H3 Maison Lumière
H3 Studio Noir
H3 Sel & Safran
H3 Aurelia Clinic
H3 Atelier Rouge
H3 Vance & Hale
H3 Maison Vœux
H3 Iris Moreau
H3 Cedar Capital
H3 Maison Voyage
H2 Behind Appsero__
H3 Hi, I'm the designer behind Appsero__.
H2 What I do
H3 Website Design
H3 Website Development
H3 Website Redesign
H3 E-Commerce
H2 Pretty isn't enough.
H3 It needs to work.
H2 How we work
H3 DISCOVER
H3 DESIGN
H3 DEVELOP
H3 LAUNCH
H2 Kind words
H2 Good design gets attention.
H3 Great design gets remembered.
H2 Let's make somethingunforgettable.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

4 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: 4 all-caps heading(s)

A+

Alt Text Quality

All 34 images OK

PASS

All 34 images OK

5 decorative image(s) correctly marked

29 image(s) with good alt text

34 images 29 good alt text 5 decorative

All images have appropriate alt text.

Link & Button Quality

18 links, 2 buttons — all OK

PASS

18 links, 2 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://www.instagram.com/appsero__/; https://www.instagram.com/appsero__/; https://linkedin.com; https://x.com; mailto:appsero7997@gmail.com

13 link(s) with descriptive text

18 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/appsero__/	Instagram ↗	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/appsero__/	Instagram	new tab	Add '(opens in new tab)' to text
https://linkedin.com	LinkedIn	new tab	Add '(opens in new tab)' to text
https://x.com	X	new tab	Add '(opens in new tab)' to text
mailto:appsero7997@gmail.com	Email	new tab	Add '(opens in new tab)' to text

15 links and buttons have descriptive text

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

https://www.instagram.com/appsero__/; https://www.instagram.com/appsero__/; https://linkedin.com; https://x.com; mailto:appsero7997@gmail.com

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

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+

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+

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

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 — 1 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.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select... Website Design Website Development Website Redesign E-Commerce Other `div.mt-20 > form.space-y-6 > div > select.w-full`
Select... < $2k $2k – $5k $5k – $10k $10k – $25k $25k+ `div.mt-20 > form.space-y-6 > div > select.w-full`

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.

○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

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

○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

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

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