https://ais-pre-psgakquiwaol5aevbdjv6g-759203062707.asia-east1.run.app

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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-1yl05v

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://ais-pre-psgakquiwaol5aevbdjv6g-759203062707.asia-east1.run.app/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://ais-pre-psgakquiwaol5aevbdjv6g-759203062707.asia-east1.run.app/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #0b0d13

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Mobile-Readable Font Sizes

Action

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

REVIEW

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

40 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 ("Translate to:"); <span> 11.0px ("Instant full breakdown"); <span> 10.0px ("Urdu"); <p> 11.0px ("After all, it is a tender human heart, n...").

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 Understand

1.06:1

#000000

#090A0F

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Translation Modes

1.06:1

#000000

#090A0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Simple Meaning & Deep Explanation

1.06:1

#000000

#090A0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Difficult Words & Word-by-Word Meaning

1.06:1

#000000

#090A0F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Core Theme:

1.06:1

#000000

#090A0F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Mirza Asadullah Khan Ghalib

1.06:1

#000000

#090A0F

needs 3.0:1 (large text)

19px · bottom of viewport

title Global Shayari AI | Understand Every Ver…

1.25:1

#000000

#161E2A

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span SHAYARI

1.12:1

#000000

#0D121F

needs 4.5:1 (normal text)

16px · top of page (header area)

span PRO

1.14:1

#000000

#17130E

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Analyze

1.05:1

#000000

#07090E

needs 4.5:1 (normal text)

16px · top of page (header area)

span Dictionary

1.05:1

#000000

#07090E

needs 4.5:1 (normal text)

16px · above the fold

span Video Studio

1.05:1

#000000

#07090E

needs 4.5:1 (normal text)

16px · above the fold

span Poetry Academy

1.05:1

#000000

#07090E

needs 4.5:1 (normal text)

16px · above the fold

span Translate to:

1.05:1

#000000

#07090E

needs 4.5:1 (normal text)

16px · above the fold

option English (English)

1.05:1

#000000

#07090E

needs 4.5:1 (normal text)

16px · above the fold

option বাংলা (Bengali)

1.05:1

#000000

#06080D

needs 4.5:1 (normal text)

16px · above the fold

option हिन्दी (Hindi)

1.05:1

#000000

#06080D

needs 4.5:1 (normal text)

16px · above the fold

option اردو (Urdu)

1.05:1

#000000

#06080D

needs 4.5:1 (normal text)

16px · above the fold

option العربية (Arabic)

1.05:1

#000000

#06080D

needs 4.5:1 (normal text)

16px · above the fold

option فارسی (Persian)

1.05:1

#000000

#06080D

needs 4.5:1 (normal text)

16px · mid-page

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Understand	1.06:1	3.0:1	#000000	#090A0F	Fail
h2 Translation Modes	1.06:1	3.0:1	#000000	#090A0F	Fail
h2 Simple Meaning & Dee…	1.06:1	3.0:1	#000000	#090A0F	Fail
h2 Difficult Words & Wo…	1.06:1	3.0:1	#000000	#090A0F	Fail
h3 Core Theme:	1.06:1	3.0:1	#000000	#090A0F	Fail
h3 Mirza Asadullah Khan…	1.06:1	3.0:1	#000000	#090A0F	Fail
title Global Shayari AI \| …	1.25:1	4.5:1	#000000	#161E2A	Fail
span SHAYARI	1.12:1	4.5:1	#000000	#0D121F	Fail
span PRO	1.14:1	4.5:1	#000000	#17130E	Fail
span Analyze	1.05:1	4.5:1	#000000	#07090E	Fail
span Dictionary	1.05:1	4.5:1	#000000	#07090E	Fail
span Video Studio	1.05:1	4.5:1	#000000	#07090E	Fail
span Poetry Academy	1.05:1	4.5:1	#000000	#07090E	Fail
span Translate to:	1.05:1	4.5:1	#000000	#07090E	Fail
option English (English)	1.05:1	4.5:1	#000000	#07090E	Fail
option বাংলা (Ben…	1.05:1	4.5:1	#000000	#06080D	Fail
option हिन्दी (…	1.05:1	4.5:1	#000000	#06080D	Fail
option اردو (Urdu)	1.05:1	4.5:1	#000000	#06080D	Fail
option العربية (Arab…	1.05:1	4.5:1	#000000	#06080D	Fail
option فارسی (Persian)	1.05:1	4.5:1	#000000	#06080D	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.

Landmark Structure

4 landmarks

PASS

4 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

6 headings

PASS

6 headings

Single H1 present

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

A+

Heading Text Quality

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

PASS

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

Link & Button Quality

1 issue(s) across 1 links and 50 buttons

PASS

1 issue(s) across 1 links and 50 buttons

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

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.text-slate-400 (#370 on page)

1 links

0 empty

0 generic text

1 new tab

1 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
<button>	(empty)	empty	Add button text or aria-label

49 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

Icon-only buttons need an aria-label so screen readers can announce them.

button.text-slate-400 (#370 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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.

Lighthouse Accessibility Audits

Score 94/100 — 1 failing, 20 passed

PASS

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
header.sticky > div.mx-auto > div.flex > button.flex `header.sticky > div.mx-auto > 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 `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.

○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

●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

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

●Heading elements appear in a sequentially-descending order

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

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

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