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 7 REVIEW 1 FIX

Tap Target Adequacy

Action

6 tap target(s) too small or too close together

REVIEW

6 tap target(s) too small or too close together

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

Mobile-Readable Font Sizes

Action

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

REVIEW

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

48 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 ("PRO"); <span> 11.0px ("Day"); <span> 11.0px ("Translate to:"); <span> 11.0px ("Instant full breakdown"); <span> 10.0px ("Urdu").

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 Global Shayari AI | Understand Every Verse ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✓ Manifest Icons Present

✗ Multiple Sizes Missing

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

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

14 pass 6 fail WCAG AA 1 pass AA only

h1 Understand

1.17:1

#000000

#16171C

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Translation Modes

1.17:1

#000000

#16171C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Simple Meaning & Deep Explanation

1.17:1

#000000

#16171C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Difficult Words & Word-by-Word Meaning

1.17:1

#000000

#16171C

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Core Theme:

1.17:1

#000000

#16171C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Mirza Asadullah Khan Ghalib

1.17:1

#000000

#16171C

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Understand	1.17:1	3.0:1	#000000	#16171C	Fail
h2 Translation Modes	1.17:1	3.0:1	#000000	#16171C	Fail
h2 Simple Meaning & Dee…	1.17:1	3.0:1	#000000	#16171C	Fail
h2 Difficult Words & Wo…	1.17:1	3.0:1	#000000	#16171C	Fail
h3 Core Theme:	1.17:1	3.0:1	#000000	#16171C	Fail
h3 Mirza Asadullah Khan…	1.17:1	3.0:1	#000000	#16171C	Fail
title Global Shayari AI \| …	9.40:1	4.5:1	#000000	#A9AEB4	Pass
a Skip to main content	5.25:1	4.5:1	#000000	#7C7F88	Pass
span SHAYARI	17.80:1	4.5:1	#000000	#EEECE8	Pass
span PRO	19.96:1	4.5:1	#000000	#FBF9F4	Pass
span Analyze	19.96:1	4.5:1	#000000	#FBF9F4	Pass
span Dictionary	19.96:1	4.5:1	#000000	#FBF9F4	Pass
span Video Studio	19.96:1	4.5:1	#000000	#FBF9F4	Pass
span Poetry Academy	19.96:1	4.5:1	#000000	#FBF9F4	Pass
span Cloud Synced	19.61:1	4.5:1	#000000	#F9F7F2	Pass
span Day	19.44:1	4.5:1	#000000	#F8F6F1	Pass
span Auto (Light)	19.44:1	4.5:1	#000000	#F8F6F1	Pass
span Translate to:	19.44:1	4.5:1	#000000	#F8F6F1	Pass
option English (English)	19.44:1	4.5:1	#000000	#F8F6F1	Pass
option বাংলা (Ben…	19.44:1	4.5:1	#000000	#F8F6F1	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 87/100 — 4 failing, 24 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#shayari-result-section > div.flex > div.flex > button.flex `div#shayari-result-section > div.flex > div.flex > button.flex`
div#shayari-result-section > div.flex > div.flex > button.flex `div#shayari-result-section > div.flex > div.flex > button.flex`
div#shayari-result-section > div.flex > div.flex > button.flex `div#shayari-result-section > div.flex > div.flex > button.flex`

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
SHAYARI AI `div.flex > div > div.flex > span.font-display`
AI `div > div.flex > span.font-display > span.text-amber-400`
Multilingual Poetry Intelligence & Cultural Decoder `div.relative > div.text-center > div.inline-flex > span`
Understand Every Shayari. `div.space-y-4 > div.relative > div.text-center > h1.font-display`
Upload a voice, video, image or text and discover its meaning in seconds. `div.space-y-4 > div.relative > div.text-center > p.mx-auto`
SECONDARY POETRY TOOLS: `div.mt-6 > div.flex > span.text-xs > span`
Tools → Shayari Card Studio `div.mt-6 > div.flex > button.text-xs > span`
OR EXPLORE ICONIC MASTERPIECES WITH 1-CLICK: `div.mt-6 > div.flex > p.text-xs > span`
Instant full breakdown `div.relative > div.mt-6 > div.flex > span.text-[11px]`
Mirza Asadullah Khan Ghalib `div.grid > button.flex > div.flex > span.text-xs`
Faiz Ahmad Faiz `div.grid > button.flex > div.flex > span.text-xs`
Dr. Rahat Indori `div.grid > button.flex > div.flex > span.text-xs`
Kazi Nazrul Islam `div.grid > button.flex > div.flex > span.text-xs`
Jaun Elia `div.grid > button.flex > div.flex > span.text-xs`
Lang: Urdu (Nastaliq) `div.flex > div > div.flex > span`
Citation: Diwan-e-Ghalib, Ghazal #112 (Rekhta Archive verified) `div#shayari-result-section > div.rounded-xl > div.flex > 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
Share This Poetry Analysis `div.rounded-2xl > div.space-y-1 > div.flex > h4.text-sm`

These are opportunities to improve keyboard navigation in your application.

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
Privacy Policy `footer.border-t > div.mx-auto > div.flex > a.hover:text-amber-300`
Terms of Service `footer.border-t > div.mx-auto > div.flex > a.hover:text-amber-300`
Refund Policy `footer.border-t > div.mx-auto > div.flex > a.hover:text-amber-300`
FAQ & DMCA `footer.border-t > div.mx-auto > div.flex > a.hover:text-slate-300`
Suggest Feature `footer.border-t > div.mx-auto > div.flex > button.hover:text-slate-300`
Quality Dashboard `footer.border-t > div.mx-auto > div.flex > a.hover:text-slate-300`

These items highlight common accessibility best practices.

○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

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

●Select elements have associated label elements.

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

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

○Image elements have `[alt]` attributes

○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

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

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

7 headings, 1 skip(s)

PASS

7 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Understand Every Shayari.
H2 Translation Modes
H2 Simple Meaning & Deep Explanation
H3 Core Theme:
H3 Mirza Asadullah Khan Ghalib
H2 Difficult Words & Word-by-Word Meaning
H4 Share This Poetry Analysis skipped

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) rely on placeholder only

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

Got: <textarea>

1 control(s) properly labeled

2 controls

1 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	Select translation language	aria-label
textarea	textarea	(Paste or write Shayari in Urdu, Hindi, Bengali, Persian, Arabic, or Roman transliteration... (e.g. 'دل ہی تو ہے نہ سنگ و خشت' or 'Dil hi to hai na sang-o-khisht'))	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

8 links, 67 buttons — all OK

PASS

8 links, 67 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://en.wikipedia.org/wiki/Ghalib

7 link(s) with descriptive text

8 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://en.wikipedia.org/wiki/Ghalib	View Historical Archive	new tab	Add '(opens in new tab)' to text

74 links and buttons have descriptive text

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

https://en.wikipedia.org/wiki/Ghalib

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

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Global Shayari AI

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Global Shayari AI ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Global Shayari AI Display Mode standalone Theme Color #0b0d13 Background Color #0b0d13 Icons 1 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: https://fonts.googleapis.com/css2?family=Amiri:ital,wght@0,400;0,700;1,400&family=Cinzel:wght@500;700;900&family=Gulzar&family=Hind+Siliguri:wght@400;500;600;700&family=Noto+Nastaliq+Urdu:wght@400;600;700&family=Noto+Serif+Bengali:wght@400;600;700&family=Noto+Serif+Devanagari:wght@400;600;700&family=Playfair+Display:ital,wght@0,400;0,600;0,700;1,400;1,600&family=Plus+Jakarta+Sans:wght@300;400;500;600;700;800&display=swap

Print Stylesheet ✓ Print Optimized

Print stylesheet https://fonts.googleapis.com/css2?family=Amiri:ital,wght@0,400;0,700;1,400&family=Cinzel:wght@500;700;900&family=Gulzar&family=Hind+Siliguri:wght@400;500;600;700&family=Noto+Nastaliq+Urdu:wght@400;600;700&family=Noto+Serif+Bengali:wght@400;600;700&family=Noto+Serif+Devanagari:wght@400;600;700&family=Playfair+Display:ital,wght@0,400;0,600;0,700;1,400;1,600&family=Plus+Jakarta+Sans:wght@300;400;500;600;700;800&display=swap ✓Inline @media print Not 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.