Skip to content
https://kashipixel.in

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
6
REVIEW
2
PASS
16
INFO
0
Checks
24
16 PASS 2 REVIEW 6 FIX
D
Mobile-Readable Font Sizes
Action
42% of visible text renders at >= 12 CSS px (113 below threshold)
FIX
42% of visible text renders at >= 12 CSS px (113 below threshold)
Warning::
113 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 ("DEV STUDIO"); <span> 11.0px ("Services"); <button> 11.0px ("Templates"); <button> 11.0px ("Workspace"); <button> 11.0px ("About").
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
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.
C
Heading Hierarchy
Action
26 headings, 3 skip(s)
REVIEW
26 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Websites thatDemandAttention. ⚡
  • H4 SaaS Template skipped
  • H2 Built for YourIndustry
  • H4 E-Commerce Boutique skipped
  • H4 SaaS Startup Hub
  • H4 Digital Portfolio
  • H4 Artisan Café
  • H4 Wellness Clinic
  • H4 Vanguard Consulting
  • H2 From Idea to Livein 4 Simple Steps
  • H3 Choose a Template
  • H3 AI Generates Your Copy
  • H3 Customize Visually
  • H3 Publish & Go Live
  • H2 Every Tool You Need.Nothing You Don't.
  • H3 Gemini AI Copywriter
  • H3 Real-time SEO Audit
  • H3 Instant Cloud Publishing
  • H3 Block Style Customizer
  • H3 Viewport Simulator
  • H3 Curated Stock Library
  • H2 Creators Love It
  • H2 Ready to LaunchYour Site Today?
  • H4 Quick Links skipped
  • H4 Templates
  • H4 Company & Legal

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

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

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title KashiPixel | AI Website Builder & Premium Dev Studio ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

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 Text Quality
All 26 heading(s) have substantive, well-formed text
PASS
All 26 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 14 images OK
PASS
All 14 images OK
Info::
14 image(s) with good alt text
14 images 14 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
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
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
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
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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)
ElementRatioRequiredFGBGResult
h1 Websites that19.95:13.0:1
#000000
#FAF9F6
Pass
h1 Attention. ⚡19.95:13.0:1
#000000
#FAF9F6
Pass
h2 Built for Your19.95:13.0:1
#000000
#FAF9F6
Pass
h2 From Idea to Live19.95:13.0:1
#000000
#FAF9F6
Pass
h2 Every Tool You Need.19.95:13.0:1
#000000
#FAF9F6
Pass
h2 Creators Love It19.95:13.0:1
#000000
#FAF9F6
Pass
h2 Ready to Launch19.95:13.0:1
#000000
#FAF9F6
Pass
h2 Your Site Today?19.95:13.0:1
#000000
#FAF9F6
Pass
h3 Choose a Template19.95:13.0:1
#000000
#FAF9F6
Pass
h3 AI Generates Your Co…19.95:13.0:1
#000000
#FAF9F6
Pass
h3 Customize Visually19.95:13.0:1
#000000
#FAF9F6
Pass
h3 Publish & Go Live19.95:13.0:1
#000000
#FAF9F6
Pass
h3 Gemini AI Copywriter19.95:13.0:1
#000000
#FAF9F6
Pass
h3 Real-time SEO Audit19.95:13.0:1
#000000
#FAF9F6
Pass
h3 Instant Cloud Publis…19.95:13.0:1
#000000
#FAF9F6
Pass
h3 Block Style Customiz…19.95:13.0:1
#000000
#FAF9F6
Pass
h3 Viewport Simulator19.95:13.0:1
#000000
#FAF9F6
Pass
h3 Curated Stock Librar…19.95:13.0:1
#000000
#FAF9F6
Pass
title KashiPixel | AI Webs…21.00:14.5:1
#000000
#FFFFFF
Pass
span KashiPixel21.00:14.5:1
#000000
#FFFFFF
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.

A
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 18 passed
PASS
93

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
BUILDER 🚀 header.h-16 > div.flex > button.px-3 > span
START BUILDING FREE div.grid > div.lg:col-span-6 > div.flex > button.px-6
ACCENT COLOR div.flex > div.w-40 > div > p.text-[7px]
SEO SCORE div.flex > div.w-40 > div > p.text-[7px]
98% div > div.bg-emerald-50 > div.flex > span.text-[8px]
ACTIVE BLOCK div.flex > div.w-40 > div > p.text-[7px]
HERO div.w-40 > div > div.space-y-1 > div.px-2
FEATURES div.w-40 > div > div.space-y-1 > div.px-2
TESTIMONIALS div.w-40 > div > div.space-y-1 > div.px-2
CTA div.w-40 > div > div.space-y-1 > div.px-2
$4.50 div > div.space-y-1 > div.flex > span.font-mono
$3.75 div > div.space-y-1 > div.flex > span.font-mono
LIVE EDIT SYNC div.flex > div.flex-1 > div.bg-white > span.inline-flex
01 div.max-w-7xl > div.grid > div.bg-white > div.absolute
02 div.max-w-7xl > div.grid > div.bg-white > div.absolute
03 div.max-w-7xl > div.grid > div.bg-white > div.absolute
04 div.max-w-7xl > div.grid > div.bg-white > div.absolute
PROMPT INPUT div.grid > div.bg-white > div.bg-slate-50 > div.text-[7px]
• Gemini AI div.bg-white > div.bg-slate-50 > div.flex > span.text-[7px]
96/100 div.bg-white > div.bg-emerald-50 > div.flex > span.text-[11px]
LIVE div.bg-white > div.bg-sky-50 > div.flex > span.text-[8px]
Uptime 99.9% • Response 0.4s div.bg-white > div.bg-sky-50 > div.flex > span.text-[8px]
MOBILE div.bg-white > div.flex > div.flex > span.text-[8px]
USER STORIES section.bg-[#FAF9F6] > div.max-w-7xl > div.text-center > div.inline-flex
© 2026 KashiPixel Dev Studio. Founded by Gurudeep Verma. footer.bg-black > div.border-t > div.max-w-7xl > span
Privacy div.border-t > div.max-w-7xl > div.flex > button.hover:text-slate-300
Terms div.border-t > div.max-w-7xl > div.flex > button.hover:text-slate-300
Cookie Policy div.border-t > div.max-w-7xl > div.flex > button.hover:text-slate-300
Refund Policy div.border-t > div.max-w-7xl > div.flex > button.hover:text-slate-300
Powered by Neobrutalist Design Systems. footer.bg-black > div.border-t > div.max-w-7xl > span

These are opportunities to improve the legibility of your content.

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
BOUTIQUE CAFÉ div > div.h-16 > div.space-y-1 > h4.text-[8px]
E-COMMERCE BOUTIQUE div.bg-white > div.p-5 > div.space-y-1 > h4.font-black
QUICK LINKS footer.bg-black > div.max-w-7xl > div.space-y-5 > h4.font-black

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 body > div#root > div.fixed > button.relative
○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
●`[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.
●Document has a main landmark.
○`[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
○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.
○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.

Send Feedback