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 6 REVIEW 3 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" id="newsletter-email">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" id="newsletter-email">

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.

Mobile-Readable Font Sizes

Action

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

REVIEW

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

84 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> 10.0px ("Advisor + AI"); <p> 11.0px ("Start with 10 free credits"); <p> 11.0px ("From idea to actionable plan"); <p> 11.0px ("Monthly billing via Paddle"); <p> 11.0px ("All unlocked on every plan").

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 MushirAI — AI Co-Founder That Builds Your Business ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✗ Multiple Sizes Missing

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: MushirAI — AI Co-Founder

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name MushirAI — AI Co-Founder ✓192×192 icon ✗512×512 icon ✗Start URL /dashboard ✓Display Mode standalone ✓

Name MushirAI — AI Co-Founder Display Mode standalone Theme Color #004f34 Background Color #f9f6ec Icons 2 icon(s)

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

Detection limited to meta tags and inline styles.

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 26 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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
We use cookies and similar tools to keep MushirAI secure, process payments, and… `body > div.fixed`

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.

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
Financial model `div.space-y-2.5 > div.rounded-lg > div.flex > span.text-[10px]`
Brand identity `div.space-y-2.5 > div.rounded-lg > div.flex > span.text-[10px]`
Valued at $1,200 `div.overflow-hidden > div.flex > div.flex > span.rounded-full`
Traditional Route (Human / Agency / Guru) `div.relative > div.mt-14 > div.grid > div.border-border`
Real deliverables `section.border-y > div.mx-auto > div.text-center > span.inline-flex`
$1,000 `div.mt-8 > div.mt-3 > span > span.font-semibold`

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mx-auto > div.mt-10 > div.mb-8 > input.mt-4 `div.mx-auto > div.mt-10 > div.mb-8 > input.mt-4`

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

●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 are distinguishable without relying on color.

●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

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

●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

●Identical links have the same purpose.

●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

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

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

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

45 headings

PASS

45 headings

Single H1 present

H1 Turn Any Idea into a Real, Revenue-Generating Business with Your AI Co-Founder
H2 Inspect the Real Documents Your Co-Founder Builds for You
H3 5-Year Cash Flow & Unit Economics Model
H4 Ready to Download & Share
H2 Why Give Away 50% of Your Business When You Can Hire 24 Specialists for $19?
H2 From idea to actionable plan in minutes
H3 Tell your idea
H3 It thinks with you
H3 It does the work
H2 See what your co-founder builds
H3 Market Research Report
H3 Financial Model
H3 Brand Kit
H3 Landing Page Copy
H2 Everything a co-founder would do — done with you
H3 Journey Stages & Tasks
H3 Market Research
H3 Financial Model
H3 Leads & Sales
H3 Marketing & Content
H3 Local by default
H3 Any language
H2 12 Sequential Phases From Napkin Idea to First Revenue
H3 Ideation & Clarity
H4 Core Business Thesis & Elevator Pitch
H2 Trusted by first-time founders
H2 See the math yourself
H2 Start free. Upgrade when ready.
H3 Free
H3 MushirAI
H2 Frequently asked questions
H3 Is this only for brand-new ideas?
H3 Will it actually do the work, or just advise?
H3 Do I need to be technical?
H3 What are credits?
H3 Does it understand my country's market?
H3 Which languages can I use?
H3 Who can see my business plan?
H3 Can I cancel anytime?
H2 Enter your idea. Leave with a business.
H3 Founder tips
H3 Follow Us
H3 Product
H3 Resources
H3 Account

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 decorative image(s) correctly marked

2 images 2 decorative

All images have appropriate alt text.

Form Accessibility

1 of 3 controls have issues

PASS

1 of 3 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="range">

2 control(s) properly labeled

3 controls

2 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#idea	textarea	Your business idea	for/id
#newsletter-email	email	Email address	for/id
input	range	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Link & Button Quality

40 links, 35 buttons — all OK

PASS

40 links, 35 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://x.com/MushirAicom; https://www.facebook.com/mushiraipk; https://www.linkedin.com/company/mushirai/; https://tiktok.com/@mushirai; https://www.youtube.com/@MushirAicom

35 link(s) with descriptive text

40 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	MushirAIAdvisor + AI	img no alt	Add alt attribute to the image
https://x.com/MushirAicom	X / Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/mushiraipk	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/mushira…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://tiktok.com/@mushirai	TikTok	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@MushirAicom	YouTube	new tab	Add '(opens in new tab)' to text

70 links and buttons have descriptive text

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

https://x.com/MushirAicom; https://www.facebook.com/mushiraipk; https://www.linkedin.com/company/mushirai/; https://tiktok.com/@mushirai; https://www.youtube.com/@MushirAicom

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

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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

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

PASS

10 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

2 mobile-depth signal(s) detected

PASS

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

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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 Turn Any Idea into a…	16.13:1	3.0:1	#000000	#E7E2CA	Pass
h1 Business with Your A…	16.63:1	3.0:1	#000000	#EBE5CE	Pass
h2 Inspect the Real Doc…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Why Give Away 50% of…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 From idea to actiona…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 See what your co-fou…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Everything a co-foun…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 12 Sequential Phases	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Trusted by first-tim…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 See the math yoursel…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Start free. Upgrade …	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Frequently asked que…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Enter your idea. Lea…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 5-Year Cash Flow & U…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 Tell your idea	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 It thinks with you	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 It does the work	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 Market Research Repo…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 Financial Model	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 Brand Kit	20.67:1	3.0:1	#000000	#FFFDF9	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.

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