Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ 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

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

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

Action

2 landmarks

REVIEW

2 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

No banner (header) 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

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

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 404: Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Heading Hierarchy

28 headings

PASS

28 headings

Multiple H1 headings (2 found)

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

H1 Lunnie Studio
H1 Get to Know Us! duplicate H1
H2 The Perfect Answer For...
H3 Elevating Professional Presence
H4 A Face for Your Brand
H4 Full Control & Insight
H2 Build Options
H3 Landing Site
H3 E-Commerce
H3 Custom
H2 Every Build Includes
H3 Free domain for a year
H3 Search Engine Ready
H3 Modern UI/UX
H3 Security & Analytics
H3 Lightning Fast
H2 Your Journey With Us
H2 Your Journey With Us
H3 Say Hello !
H3 Talk It Through
H3 Make ItOfficial
H3 Shape theVision
H3 Bring Itto Life
H3 Handover &Walkthrough
H2 Ready to reach your horizon?
H3 Lunnie Studio
H4 Navigation
H4 Location

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

13 links, 0 buttons — all OK

PASS

13 links, 0 buttons — all OK

13 link(s) with descriptive text

13 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

13 links and buttons have descriptive text

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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

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.

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 93 visible text node(s) render at >= 12 CSS pixels

PASS

All 93 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.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Lunnie Studio	14.79:1	3.0:1	#000000	#CBDCDA	Pass
h1 Get to	13.60:1	3.0:1	#000000	#FDC93C	Pass
h1 Know Us!	13.27:1	3.0:1	#000000	#FCC637	Pass
h2 The Perfect	12.63:1	3.0:1	#000000	#B9CDC8	Pass
h2 For...	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h2 Build Options	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h2 Every Build Includes	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h2 Ready to reach	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h2 your	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Elevating Profession…	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Landing Site	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 E-Commerce	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Custom	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Free domain for a ye…	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Search Engine Ready	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Modern UI/UX	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Security & Analytics	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Lightning Fast	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Say Hello !	12.65:1	3.0:1	#000000	#B9CDCA	Pass
h3 Talk It Through	12.65:1	3.0:1	#000000	#B9CDCA	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 93/100 — 2 failing, 17 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
Lunnie Studio `div.max-w-4xl > div.max-w-2xl > p.font-sans > span.font-black`
Contact us `div.max-w-4xl > div.max-w-2xl > div.flex > a.bg-transparent`
We create digital spaces that don't just look pretty - they perform, scale, and… `div.container-lock > div.grid > div.lg:col-span-5 > p.font-sans`
Establish credibility and legitimacy, positioning your business as trustworthy … `div.grid > div.lg:col-span-7 > div.bg-white > p.font-sans`
Reflect your identity and connect with your community deeply. `div.grid > div.lg:col-span-7 > div.bg-brand-light > p.font-sans`
Explore assistance based on your needs. Every build is optimized for growth. `section#pricing > div.container-lock > div.mb-16 > p.font-sans`
LAUNCH 5-7 BUSINESS DAYS `div.container-lock > div.grid > div.bg-brand-light > p.font-sans`
Perfect for portfolios & startups `div.grid > div.bg-brand-light > ul.space-y-4 > li.flex`
High-performance & responsive `div.grid > div.bg-brand-light > ul.space-y-4 > li.flex`
30 days post-launch support `div.grid > div.bg-brand-light > ul.space-y-4 > li.flex`
STARTING FROM `div.grid > div.bg-brand-light > div.mt-auto > span.font-sans`
LAUNCH 14-21 BUSINESS DAYS `div.container-lock > div.grid > div.bg-brand-main > p.font-sans`
STARTING FROM `div.grid > div.bg-brand-main > div.mt-auto > span.font-sans`
TIMELINE BASED ON COMPLEXITY `div.container-lock > div.grid > div.bg-brand-lightest > p.font-sans`
Unique & complex workflows `div.grid > div.bg-brand-lightest > ul.space-y-4 > li.flex`
Fully tailored architecture `div.grid > div.bg-brand-lightest > ul.space-y-4 > li.flex`
Dedicated support `div.grid > div.bg-brand-lightest > ul.space-y-4 > li.flex`
VARIABLE `div.grid > div.bg-brand-lightest > div.mt-auto > span.font-sans`
We don't just build websites, we build complete digital foundations ready for g… `section.py-20 > div.container-lock > div.mb-16 > p.mt-4`
Optimized semantic structure and metadata so you show up on Google from day one. `div.grid > article.bg-white > div > p.text-[#4a6b74]/75`
Clean, intuitive, and fully responsive interfaces that adapt perfectly to any s… `div.grid > article.bg-white > div > p.text-[#4a6b74]/75`
Highly optimized code and assets make your site fly, boosting conversions and r… `div.grid > article.bg-[#4a6b74] > div.relative > p.text-white/80`
Say Hello ! `div.relative > div.absolute > div.bg-[#b4c8c4] > h3.text-2xl`
Start the Conversation `div.relative > div.absolute > div.bg-[#b4c8c4] > p.text-sm`
Talk It Through `div.relative > div.absolute > div.bg-[#b4c8c4] > h3.text-2xl`
Map your needs with us `div.relative > div.absolute > div.bg-[#b4c8c4] > p.text-sm`
Make It Official `div.relative > div.absolute > div.bg-[#b4c8c4] > h3.text-2xl`
Lock the deal `div.relative > div.absolute > div.bg-[#b4c8c4] > p.text-sm`
Shape the Vision `div.relative > div.absolute > div.bg-[#b4c8c4] > h3.text-2xl`
Design direction `div.relative > div.absolute > div.bg-[#b4c8c4] > p.text-sm`
Bring It to Life `div.relative > div.absolute > div.bg-[#b4c8c4] > h3.text-2xl`
In the works `div.relative > div.absolute > div.bg-[#b4c8c4] > p.text-sm`
Handover & Walkthrough `div.relative > div.absolute > div.bg-[#b4c8c4] > h3.text-xl`
Launch and learn `div.relative > div.absolute > div.bg-[#b4c8c4] > p.text-sm`
Let’s build a digital presence that actually works for your business. `div.container-lock > div.bg-brand-main > div.relative > p.font-sans`
Empowering scaling small businesses through growth-driven digital experiences. … `div.container-lock > div.grid > div.md:col-span-5 > p.font-sans`
Build Options `div.md:col-span-3 > ul.space-y-2 > li > a.hover:text-brand-main`
Our Journey `div.md:col-span-3 > ul.space-y-2 > li > a.hover:text-brand-main`
Contact `div.md:col-span-3 > ul.space-y-2 > li > a.hover:text-brand-main`
Based Globally Working in Indonesia and Poland contact@lunniestudio.com `div.container-lock > div.grid > div.md:col-span-4 > p.font-sans`
© 2026 Lunnie Studio. All rights reserved. `footer#contact > div.container-lock > div.mt-12 > p`

These are opportunities to improve the legibility of your content.

Best practices

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.

○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

●Image elements have `[alt]` attributes

●`[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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

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

○Buttons have an accessible name

○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

○Form elements have associated labels

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

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