Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 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'>.

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ 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: #0066ff

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

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

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title PTL DIGITAL AGENCY ✓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

h3 Listen First

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Frame the Problem

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Design the Solution

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Build & Test

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ship & Evolve

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Strategy

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Build

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Grow

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Technology

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Sustain

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Haweli — Restaurant Website & Local SE…

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 NGO Donor Automation System

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Nightlife SaaS — Launching Soon

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 SOS Food — 24/7 Grocery, Pizzas & Burg…

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Starter

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Growth

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Business

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Studio

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Fixed prices, always visible

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

h3 You own 100% of what we build

1.10:1

#000000

#101010

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 Listen First	1.10:1	3.0:1	#000000	#101010	Fail
h3 Frame the Problem	1.10:1	3.0:1	#000000	#101010	Fail
h3 Design the Solution	1.10:1	3.0:1	#000000	#101010	Fail
h3 Build & Test	1.10:1	3.0:1	#000000	#101010	Fail
h3 Ship & Evolve	1.10:1	3.0:1	#000000	#101010	Fail
h3 Strategy	1.10:1	3.0:1	#000000	#101010	Fail
h3 Build	1.10:1	3.0:1	#000000	#101010	Fail
h3 Grow	1.10:1	3.0:1	#000000	#101010	Fail
h3 Technology	1.10:1	3.0:1	#000000	#101010	Fail
h3 Sustain	1.10:1	3.0:1	#000000	#101010	Fail
h3 Haweli — Restauran…	1.10:1	3.0:1	#000000	#101010	Fail
h3 NGO Donor Automation…	1.10:1	3.0:1	#000000	#101010	Fail
h3 Nightlife SaaS — L…	1.10:1	3.0:1	#000000	#101010	Fail
h3 SOS Food — 24/7 Gr…	1.10:1	3.0:1	#000000	#101010	Fail
h3 Starter	1.10:1	3.0:1	#000000	#101010	Fail
h3 Growth	1.10:1	3.0:1	#000000	#101010	Fail
h3 Business	1.10:1	3.0:1	#000000	#101010	Fail
h3 Studio	1.10:1	3.0:1	#000000	#101010	Fail
h3 Fixed prices, always…	1.10:1	3.0:1	#000000	#101010	Fail
h3 You own 100% of what…	1.10:1	3.0:1	#000000	#101010	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

31 headings

PASS

31 headings

Single H1 present

H1 Strategy. [ Build.Grow. Automate. ]→ Sustain.
H2 Every project follows the same5-phase discipline
H3 Listen First
H3 Frame the Problem
H3 Design the Solution
H3 Build & Test
H3 Ship & Evolve
H2 Five practices.One studio.
H3 Strategy
H3 Build
H3 Grow
H3 Technology
H3 Sustain
H2 Use cases &real projects
H3 Haweli — Restaurant Website & Local SEO
H3 NGO Donor Automation System
H3 Nightlife SaaS — Launching Soon
H3 SOS Food — 24/7 Grocery, Pizzas & Burgers
H2 Four ways toengage us
H3 Starter
H3 Growth
H3 Business
H3 Studio
H2 Any business whoseclients Google them first
H2 Who we are.
H3 Fixed prices, always visible
H3 You own 100% of what we build
H3 Fast, honest delivery
H2 Things peoplealways ask us
H2 Ready to fix your digital presence?// Start with a free audit.
H2 Start witha free audit

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

1 decorative image(s) correctly marked

2 image(s) with good alt text

3 images 2 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 8 controls labeled

PASS

All 8 controls labeled

8 control(s) properly labeled

8 controls

8 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
firstName	input	First name *	none
lastName	input	Last name *	none
email	email	Email *	none
phone	tel	Phone / WhatsApp	none
company	text	Company / website	none
service	select	Service of interest	none
timeline	select	Project timeline	none
message	textarea	How can we help? *	none

Link & Button Quality

22 links, 10 buttons — all OK

PASS

22 links, 10 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://hawelige.ch; https://sosfood.ch/

20 link(s) with descriptive text

22 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://hawelige.ch	Visit site: Haweli — Restaur…	new tab	Add '(opens in new tab)' to text
https://sosfood.ch/	Visit site: SOS Food — 24/7 …	new tab	Add '(opens in new tab)' to text

30 links and buttons have descriptive text

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

https://hawelige.ch; https://sosfood.ch/

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+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 26 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
EN `nav.relative > div.flex > div.flex > button.flex`
Free Audit → `header.fixed > nav.relative > div.flex > a.hard-shadow-hover`
Explore services → `div.mx-auto > div.fade-up > div.flex > a.hard-shadow-hover`
TECHNOLOGY `div.ticker-track > div.flex > span.flex > span.px-5`
SUSTAIN `div.ticker-track > div.flex > span.flex > span.px-5`
GENEVA · CH `div.ticker-track > div.flex > span.flex > span.px-5`

These are opportunities to improve the legibility of your content.

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

●Select elements have associated label elements.

●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

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

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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