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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

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

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 Missing

✓ 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

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: #f3f0e9

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.

Tap Target Adequacy

Action

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

REVIEW

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

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

Mobile-Readable Font Sizes

Action

85% of visible text renders at >= 12 CSS px (9 below threshold)

REVIEW

85% of visible text renders at >= 12 CSS px (9 below threshold)

9 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> 8.0px ("EXPLORE"); <span> 8.0px ("WHAT WE DO"); <span> 11.5px ("01 / UNCONVENTIONAL MARKETING"); <span> 11.5px ("02 / HANDS-ON PRODUCTION"); <span> 11.5px ("03 / PARTNER NETWORK").

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only

h2 We turn bold

1.14:1

#000000

#191212

needs 3.0:1 (large text)

24px · mid-page

h2 ideas into

2.51:1

#000000

#7A3D16

needs 3.0:1 (large text)

24px · mid-page

h2 Where creativity

1.07:1

#000000

#100A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 meets

1.07:1

#000000

#100A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One idea.

1.07:1

#000000

#100A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 to bring it to life.

1.07:1

#000000

#100A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A creative partner

1.07:1

#000000

#100A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 close to

1.07:1

#000000

#100A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Let's make

1.07:1

#000000

#100A0A

needs 3.0:1 (large text)

24px · bottom of viewport

title Creative Marketing & Advertising Agency …

1.16:1

#000000

#12161B

needs 4.5:1 (normal text)

16px · top of page (header area)

b MENU

1.11:1

#000000

#0D1114

needs 3.0:1 (large text)

16px · top of page (header area)

span EXPLORE LUNAHUB

1.19:1

#000000

#16191F

needs 4.5:1 (normal text)

16px · top of page (header area)

button CLOSE ✕

1.26:1

#000000

#1D1E23

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

2.79:1

#000000

#4B5565

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a About us

1.35:1

#000000

#222429

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Services

1.18:1

#000000

#17181B

needs 4.5:1 (normal text)

16px · above the fold

a Contact us

1.33:1

#000000

#1B242B

needs 4.5:1 (normal text)

16px · above the fold

span CREATIVE MARKETING · CONTENT · MEDIA

1.98:1

#000000

#274156

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span TORONTO · WORKING EVERYWHERE

1.23:1

#000000

#1E1B1C

needs 4.5:1 (normal text)

16px · above the fold

3 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
h2 We turn bold	1.14:1	3.0:1	#000000	#191212	Fail
h2 ideas into	2.51:1	3.0:1	#000000	#7A3D16	Fail
h2 world impact.	3.46:1	3.0:1	#000000	#726128	Pass
h2 Where creativity	1.07:1	3.0:1	#000000	#100A0A	Fail
h2 meets	1.07:1	3.0:1	#000000	#100A0A	Fail
h2 One idea.	1.07:1	3.0:1	#000000	#100A0A	Fail
h2 to bring it to life.	1.07:1	3.0:1	#000000	#100A0A	Fail
h2 A creative partner	1.07:1	3.0:1	#000000	#100A0A	Fail
h2 close to	1.07:1	3.0:1	#000000	#100A0A	Fail
h2 Let's make	1.07:1	3.0:1	#000000	#100A0A	Fail
title Creative Marketing &…	1.16:1	4.5:1	#000000	#12161B	Fail
b MENU	1.11:1	3.0:1	#000000	#0D1114	Fail
span EXPLORE LUNAHUB	1.19:1	4.5:1	#000000	#16191F	Fail
button CLOSE ✕	1.26:1	4.5:1	#000000	#1D1E23	Fail
a Home	2.79:1	4.5:1	#000000	#4B5565	Fail
a About us	1.35:1	4.5:1	#000000	#222429	Fail
a Services	1.18:1	4.5:1	#000000	#17181B	Fail
a Contact us	1.33:1	4.5:1	#000000	#1B242B	Fail
span CREATIVE MARKETING �…	1.98:1	4.5:1	#000000	#274156	Fail
span TORONTO · WORKING E…	1.23:1	4.5:1	#000000	#1E1B1C	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

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

A+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 Make yourmark.
H2 We turn boldideas into realworld impact.
H2 Where creativitymeets strategy.
H2 One idea.Many ways to bring it to life.
H2 A creative partnerclose to home.
H2 Let's makesomething happen.

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

4 image(s) with good alt text

4 images 4 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

18 links, 2 buttons — all OK

PASS

18 links, 2 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://www.google.com/maps/dir/?api=1&destination=20+Newbridge+Rd%2C+Etobico…

17 link(s) with descriptive text

18 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.google.com/maps/dir/?api=1&d…	20 NEWBRIDGE RD, ETOBICOKE, ON…	new tab	Add '(opens in new tab)' to text

19 links and buttons have descriptive text

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

https://www.google.com/maps/dir/?api=1&destination=20+Newbridge+Rd%2C+Etobico…

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

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

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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 90/100 — 2 failing, 18 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
EXPLORE LUNAHUBCLOSE ✕ 01 Home02 About us03 Services04 Contact us CREATIVE MARK… `body.home > nav.menu-overlay`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
MENU `body.home > header.site-header > button.menu-toggle`
ALL SERVICES ↗ `main > section.home-services > div.section-head > a.text-link`
03Design & production↗ `main > section.home-services > div.mini-services > a`
04Experiences↗ `main > section.home-services > div.mini-services > a`
TEAM@LUNAHUB.CA ↗ `body.home > footer.site-footer > div.footer-contact > a`

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

●Buttons have an accessible name

●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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Elements with visible text labels have matching accessible names.

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

○Form elements have associated labels

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

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

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