https://compaq-mtv-progressive-surgeons.trycloudflare.com

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 6 REVIEW 4 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.

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 ✗

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

No <nav> landmark found

No contentinfo (footer) 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

Mobile-Readable Font Sizes

Action

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

REVIEW

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

12 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> 9.0px ("Elevating Standards"); <label> 11.0px ("Category"); <label> 11.0px ("Location"); <label> 11.0px ("Budget"); <label> 11.0px ("Posted").

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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 #0d9488 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

h1 Discover Jobs Near You

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Filters

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · above the fold

h2 Wooden Bed Frame Assembly

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Water Tank Cleaning

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Office Network Cable Wiring

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kitchen Cabinet Door Repair

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Garden Fence Painting

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Front Door Lock Replacement

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AC Service and Gas Refill

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Office Desk Replacement (Broken)

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Rooftop Garden Setup

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kitchen Sink Repair

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Quick stats

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Login Required

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

title KajiBhai | Find Local Jobs Near You

1.07:1

#000000

#090D0C

needs 4.5:1 (normal text)

16px · top of page (header area)

span KajiBhai

1.07:1

#000000

#090C0C

needs 4.5:1 (normal text)

16px · top of page (header area)

span Elevating Standards

1.07:1

#000000

#090C0C

needs 4.5:1 (normal text)

16px · top of page (header area)

span Find clients

1.12:1

#000000

#0E1312

needs 4.5:1 (normal text)

16px · top of page (header area)

span Find Workers

1.09:1

#000000

#0A0F0F

needs 4.5:1 (normal text)

16px · above the fold

a Log in

1.07:1

#000000

#0A0C0C

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Discover Jobs Near Y…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Filters	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Wooden Bed Frame Ass…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Water Tank Cleaning	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Office Network Cable…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Kitchen Cabinet Door…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Garden Fence Paintin…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Front Door Lock Repl…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 AC Service and Gas R…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Office Desk Replacem…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Rooftop Garden Setup	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Kitchen Sink Repair	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Quick stats	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 Login Required	1.06:1	3.0:1	#000000	#0A0A0A	Fail
title KajiBhai \| Find Loca…	1.07:1	4.5:1	#000000	#090D0C	Fail
span KajiBhai	1.07:1	4.5:1	#000000	#090C0C	Fail
span Elevating Standards	1.07:1	4.5:1	#000000	#090C0C	Fail
span Find clients	1.12:1	4.5:1	#000000	#0E1312	Fail
span Find Workers	1.09:1	4.5:1	#000000	#0A0F0F	Fail
a Log in	1.07:1	4.5:1	#000000	#0A0C0C	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.

Lighthouse Accessibility Audits

Score 89/100 — 2 failing, 18 passed

REVIEW

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mx-auto > div.order-last > div.flex > button.relative `div.mx-auto > div.order-last > div.flex > button.relative`
div.mx-auto > div.order-last > div.flex > button.relative `div.mx-auto > div.order-last > div.flex > button.relative`

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.

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
Sign Up `header.sticky > div.mx-auto > div.flex > a.relative`
Apply Now `div.[:where(&)]:bg-white > div.flex > button.relative > span`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Identical links have the same purpose.

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

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

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

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H2 Filters
H1 Discover Jobs Near You
H2 Wooden Bed Frame Assembly
H2 Water Tank Cleaning
H2 Office Network Cable Wiring
H2 Kitchen Cabinet Door Repair
H2 Garden Fence Painting
H2 Front Door Lock Replacement
H2 AC Service and Gas Refill
H2 Office Desk Replacement (Broken)
H2 Rooftop Garden Setup
H2 Kitchen Sink Repair
H2 Quick stats
H2 Login Required

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 9 images OK

PASS

All 9 images OK

9 decorative image(s) correctly marked

9 images 9 decorative

All images have appropriate alt text.

Form Accessibility

1 of 41 controls have issues

PASS

1 of 41 controls have issues

1 control(s) rely on placeholder only

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

Got: <textarea>

40 control(s) properly labeled

41 controls

40 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
search	text	Search jobs by title or location	aria-label
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
input	radio		none
#filter-category	select	Category	for/id
#filter-location	select	Location	for/id
#filter-budget	select	Budget	for/id
#filter-posted	select	Posted	for/id
textarea	textarea	(Type your message…)	placeholder only

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

A+

Link & Button Quality

19 links, 34 buttons — all OK

PASS

19 links, 34 buttons — all OK

19 link(s) with descriptive text

19 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

53 links and buttons have descriptive text

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 "search" should use type="search" (currently type="text")

Field name "search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

41 form control(s) checked, no input-semantic issues

PASS

41 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

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

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

PASS

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

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.