Skip to content
https://mytypingai.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
D
Mobile-Readable Font Sizes
Action
58% of visible text renders at >= 12 CSS px (117 below threshold)
FIX
58% of visible text renders at >= 12 CSS px (117 below threshold)
Warning::
117 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: <p> 11.0px ("Rewards depend on the tasks you complete..."); <a> 11.0px ("Earnings Disclaimer"); <p> 9.0px ("Task types"); <p> 9.0px ("Works on"); <p> 11.0px ("Phone").
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
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 Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ 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
Theme color only
FIX
Theme color only
Info::
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: #0f172a
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 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.

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
7 landmarks
REVIEW
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 "Legal and support" MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

C
Tap Target Adequacy
Action
7 tap target(s) too small or too close together
REVIEW
7 tap target(s) too small or too close together
Warning::
7 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title MyTypingAI — Typing Tasks Platform in India ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 23 passed
REVIEW
88

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
5 out of 5 stars div.flex > div.min-w-0 > div.mt-1 > div.flex
4 out of 5 stars div.flex > div.min-w-0 > div.mt-1 > div.flex
5 out of 5 stars div.flex > div.min-w-0 > div.mt-1 > div.flex

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.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Earnings ₹0.05 / task Payout target ₹300 Accuracy 100% Min tasks 6,000 to payout div.min-w-0 > div.tilt-3d > div.group > dl.mt-3
Earnings ₹0.3 / task Payout target ₹600 Accuracy 100% Min tasks 2,000 to payout div.min-w-0 > div.tilt-3d > div.group > dl.mt-3
Earnings ₹1 / task Payout target ₹1200 Accuracy 100% Min tasks 1,200 to payout div.min-w-0 > div.tilt-3d > div.group > dl.mt-3
Earnings ₹1.5 / task Payout target ₹1500 Accuracy 100% Min tasks 1,000 to payout div.min-w-0 > div.tilt-3d > div.group > dl.mt-3
Earnings ₹2.5 / task Payout target ₹2000 Accuracy 98% Min tasks 800 to payout div.min-w-0 > div.tilt-3d > div.group > dl.mt-3

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to video 1 div.relative > div.relative > div.mt-4 > button.h-1.5
Go to video 2 div.relative > div.relative > div.mt-4 > button.h-1.5
Go to video 3 div.relative > div.relative > div.mt-4 > button.h-1.5
Go to video 4 div.relative > div.relative > div.mt-4 > button.h-1.5
Go to video 5 div.relative > div.relative > div.mt-4 > button.h-1.5
Go to video 6 div.relative > div.relative > div.mt-4 > button.h-1.5
support@mytypingai.com div.flex > div.space-y-1 > p > a.transition

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

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
EN div.mx-auto > div.flex > span.inline-flex > button.inline-flex
Akash Rs 300 paid Verified · #33 all-time section.px-4 > div.mx-auto > div.-mx-4 > button.w-[68%]
Sruthi Rs 300 paid Verified · #1 all-time section.px-4 > div.mx-auto > div.-mx-4 > button.w-[68%]
○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
●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
●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
●Heading elements appear in a sequentially-descending order
●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
○The page contains a heading, skip link, or landmark region
○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
○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.
A+
Heading Hierarchy
23 headings
PASS
23 headings
Info::
Single H1 present
  • H1 Typing tasks, done right.From your couch.
  • H2 Real reviews. Real members.
  • H2 5 skill-based typing task categories
  • H3 Captcha
  • H3 Basic Typing
  • H3 Data Entry
  • H3 Form Filling
  • H3 Page Typing
  • H2 See how the work is done and how payout reaches you
  • H3 How to pick a task
  • H3 Type & Submit
  • H3 UPI Payout
  • H2 Complete tasks or refer users — rewards for both
  • H3 Complete tasks & receive accuracy rewards
  • H3 Refer users & get referral rewards
  • H2 How it works · Why us · Who it's for
  • H3 Sign up free
  • H3 Type & submit
  • H3 Request UPI payout
  • H3 Automatic checks
  • H3 No platform deductions
  • H3 UPI-first payouts
  • H2 Common questions
A+
Heading Text Quality
All 23 heading(s) have substantive, well-formed text
PASS
All 23 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
9 image(s) with good alt text
9 images 9 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
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
3 mobile-depth signal(s) detected
PASS
3 mobile-depth signal(s) detected
Info::
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.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
Info::
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)
ElementRatioRequiredFGBGResult
h1 Typing tasks,19.00:13.0:1
#000000
#F9F3E7
Pass
h1 From your19.00:13.0:1
#000000
#F9F3E7
Pass
h2 Real reviews. Real m…19.00:13.0:1
#000000
#F9F3E7
Pass
h2 5 skill-based typing…19.00:13.0:1
#000000
#F9F3E7
Pass
h2 See how the work is …19.00:13.0:1
#000000
#F9F3E7
Pass
h2 Complete tasks19.00:13.0:1
#000000
#F9F3E7
Pass
h2 refer users — rewa…19.00:13.0:1
#000000
#F9F3E7
Pass
h2 How it works · Why …19.00:13.0:1
#000000
#F9F3E7
Pass
h2 Common questions19.00:13.0:1
#000000
#F9F3E7
Pass
h3 Captcha19.00:13.0:1
#000000
#F9F3E7
Pass
h3 Basic Typing19.00:13.0:1
#000000
#F9F3E7
Pass
h3 Data Entry19.00:13.0:1
#000000
#F9F3E7
Pass
h3 Form Filling19.00:13.0:1
#000000
#F9F3E7
Pass
h3 Page Typing19.00:13.0:1
#000000
#F9F3E7
Pass
h3 How to pick a task19.00:13.0:1
#000000
#F9F3E7
Pass
h3 Type & Submit19.00:13.0:1
#000000
#F9F3E7
Pass
h3 UPI Payout19.00:13.0:1
#000000
#F9F3E7
Pass
h3 Complete tasks & rec…19.00:13.0:1
#000000
#F9F3E7
Pass
h3 Refer users & get re…19.00:13.0:1
#000000
#F9F3E7
Pass
h3 Sign up free19.00:13.0:1
#000000
#F9F3E7
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.

Send Feedback