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

Favicon & Branding

Action

2 icon(s) detected

FIX

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

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

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

Link & Button Quality

2 issue(s) across 27 links and 0 buttons

REVIEW

2 issue(s) across 27 links and 0 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: ./project/en/hirecentral; ./project/en/quidsi

25 link(s) with descriptive text

27 links

2 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
./project/en/hirecentral	(empty)	empty	Add link text or aria-label
./project/en/quidsi	(empty)	empty	Add link text or aria-label

25 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

./project/en/hirecentral; ./project/en/quidsi

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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 Page Not Found | TOC Studio ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Heading Hierarchy

33 headings, 1 skip(s)

PASS

33 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Custom website development agency for businesses that need results
H3 Websites designed for B2B service companies that want to be taken seriously online. skipped
H2 Framer experts who work the way you actually want
H3 Professional by design
H3 Fully handled
H3 No surprises
H3 Always in control
H2 Web design services for small businesses, done right
H3 Website Design & Development
H3 SEO Optimization
H3 Maintenance & Monthly SEO
H2 We build from briefs. Every time, for every client
H3 Where talent meets its perfect match
H3 Built for those who lead at the highest level
H2 The work speaks. So do our clients
H3 "Logró captar la esencia de lo que buscaba desde el primer momento y lo plasmó en un diseño moderno, limpio y con mucha personalidad. Tiene una creatividad que realmente marca la diferencia."
H3 “Jet transformed our entire workflow. We cut load times by 80% and our development team couldn’t be happier.”
H3 "Logró captar la esencia de lo que buscaba desde el primer momento y lo plasmó en un diseño moderno, limpio y con mucha personalidad. Tiene una creatividad que realmente marca la diferencia."
H3 “Click, done. Pagespeed jumped, bounce rates dropped. Killer ROI.”
H3 Our client websites went from sluggish to lightning-fast overnight. Jet’s optimization is pure magic for SEO rankings.”
H3 “Click, done. Pagespeed jumped, bounce rates dropped. Killer ROI.”
H3 “No tech skills, no plugins. Jet just made my portfolio fast on any device.”
H3 “I used to spend hours optimizing each site. With Jet, it’s automatic. My clients get amazing performance without the extra work.”
H3 “No tech skills, no plugins. Jet just made my portfolio fast on any device.”
H2 Frequently asked questions.
H3 How much does a project cost?
H3 How long does it take?
H3 Do I need to have everything ready before we start?
H3 Do you write the copy for the website?
H3 What happens after the site launches?
H3 Will I be able to manage the site on my own after launch?
H3 How do we communicate during the project?
H2 Your next website starts here.

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 191 chars - H3: 191 chars - H3: 130 chars

Got: 3 >120-char heading(s)

Alt Text Quality

2 of 13 images have issues

PASS

2 of 13 images have issues

2 image(s) with generic alt text

2 decorative image(s) correctly marked

9 image(s) with good alt text

13 images 9 good alt text 2 decorative 2 generic

Issue	Count
generic	2 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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

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

PASS

22 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+

Mobile-Readable Font Sizes

All 107 visible text node(s) render at >= 12 CSS pixels

PASS

All 107 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 Custom website devel…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h2 Framer experts who w…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h2 Web design services …	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h2 We build from briefs…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h2 Frequently asked que…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h2 Your next website st…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 Websites designed fo…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 Professional by desi…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 Fully handled	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 No surprises	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 Always in control	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 Website Design & Dev…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 SEO Optimization	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 Maintenance & Monthl…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 Where talent meets i…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 "Logró captar la es…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 “Jet transformed o…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 "Logró captar la es…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 “Click, done. Page…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h3 Our client websites …	18.30:1	3.0:1	#000000	#F2EFE9	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 94/100 — 2 failing, 22 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Websites designed for B2B service companies that want to be taken seriously onl… `div.framer-utgkb0 > div.framer-xbqly6 > div#lightning-fast-sites-in-a-single-click-1654kat > h3.framer-text`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.framer-13233yh > div.ssr-variant > div.framer-ly05gp-container > a.framer-yy7Ux `div.framer-13233yh > div.ssr-variant > div.framer-ly05gp-container > a.framer-yy7Ux`
div.framer-evmzau > div.ssr-variant > div.framer-sxmsc9-container > a.framer-yy7Ux `div.framer-evmzau > div.ssr-variant > div.framer-sxmsc9-container > a.framer-yy7Ux`

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

○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

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

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

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