Skip to content
https://viewsnow.co.in

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
12
REVIEW
6
PASS
6
INFO
0
Checks
24
6 PASS 6 REVIEW 12 FIX
F
Alt Text Quality
Action
3 of 31 images have issues
FIX
3 of 31 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
14 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
13 image(s) with good alt text
31 images 13 good alt text 1 decorative 3 missing
IssueCount
missing3 image(s)
too long14 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Form Accessibility
Action
16 of 18 controls have issues
FIX
16 of 18 controls have issues
Critical::
12 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="dark">; <input type="submit">; <input type="text" id="Wikipedia1_wikipedia-search-input">; <input type="submit">; <select id="BlogArchive1_ArchiveMenu">; <input type="submit">; <input type="button" id="ContactForm1_contact-form-submit">; <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText"> (+2 more)
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="text" name="name" id="ContactForm1_contact-form-name">; <input type="text" name="email" id="ContactForm1_contact-form-email">; <textarea name="email-message" id="ContactForm1_contact-form-email-message">
Info::
2 control(s) properly labeled
18 controls
2 labeled
4 placeholder only
12 unlabeled
ControlTypeLabelMethod
selectselectWidget de idiomas del Traductoraria-label
qinputSearch this blogaria-label
qtext(Search Here...)placeholder only
#ContactForm1_contact-form-nametext(Name)placeholder only
#ContactForm1_contact-form-emailtext(Email*)placeholder only
#ContactForm1_contact-form-email-messagetextarea(Message*)placeholder only
#darkcheckbox(none)none
inputsubmit(none)none
inputsubmit(none)none
#Wikipedia1_wikipedia-search-inputtext(none)none
inputsubmit(none)none
#BlogArchive1_ArchiveMenuselect(none)none
#ContactForm1_contact-form-submitbutton(none)none
#goog-gt-votingInputSrcLangtext(none)none
#goog-gt-votingInputTrgLangtext(none)none
#goog-gt-votingInputSrcTexttext(none)none
#goog-gt-votingInputTrgTexttext(none)none
#goog-gt-votingInputVotetext(none)none

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

<input type="checkbox" id="dark">; <input type="submit">; <input type="text" id="Wikipedia1_wikipedia-search-input">; <input type="submit">; <select id="BlogArchive1_ArchiveMenu">; <input type="submit">; <input type="button" id="ContactForm1_contact-form-submit">; <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText"> (+2 more)

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

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

<input type="text" name="q">; <input type="text" name="name" id="ContactForm1_contact-form-name">; <input type="text" name="email" id="ContactForm1_contact-form-email">; <textarea name="email-message" id="ContactForm1_contact-form-email-message">

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

D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
2 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: name, email.
Got: <input type="text" name="name" id="ContactForm1_contact-form-name">, <input type="text" name="email" id="ContactForm1_contact-form-email">
D
Iframe Accessibility
Action
12/19 iframe(s) missing title; 0 placeholder(s)
FIX
12/19 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="#")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://docs.google.com/forms/d/e/1FAIpQLSec3hFntAjji5prPCT_j8-uAfrMWZBoyuo_Ge-…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.blogger.com/navbar/2045041305744675074?origin=https://www.viewsnow.…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.blogger.com/followers/frame/2045041305744675074?colors=Cgt0cmFuc3Bh…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://views-123.os.tc/webPushIframe")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://pagead2.googlesyndication.com/pagead/html/r20260805/r20190131/zrt_looku…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
D
Mobile-Readable Font Sizes
Action
63% of visible text renders at >= 12 CSS px (41 below threshold)
FIX
63% of visible text renders at >= 12 CSS px (41 below threshold)
Warning::
41 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: <h3> 11.0px ("Breaking Ticker"); <span> 10.0px ("Assembly Election 2026"); <span> 10.0px ("News"); <time> 11.0px ("04 May"); <span> 10.0px ("Blood donation camp").
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ 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: #5401d8
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
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.
D
Lighthouse Accessibility Audits
Action
Score 69/100 — 9 failing, 25 passed
FIX
69

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
দুর্গাপুর পূর্ব: সিপিআই(এম)-এর ভোটের শতাংশ ও ফলাফল বিশ্লেষণ div.megawrap > div.featured-meta > h2.entry-title > a
04 May div.featured-meta > div.post-snip > span.post-date > time.published
দুর্গাপুরে বিয়ের আসরেই রক্তদান শিবির! সামাজিক দায়বদ্ধতার অনন্য নজির লিটন খানের পরিবারে div.megawrap > div.featured-meta > h2.entry-title > a
02 May div.featured-meta > div.post-snip > span.post-date > time.published
দুর্গাপুরে স্বেচ্ছায় রক্তদান আন্দোলনের রজতজয়ন্তী উদযাপন, রক্তদাতাদের সম্মাননা div.megawrap > div.featured-meta > h2.entry-title > a
22 June div.featured-meta > div.post-snip > span.post-date > time.published
তৃণমূল থেকে বহিষ্কৃত এন্টালির বিধায়ক সন্দীপন সাহা, দলের বিরুদ্ধে বিস্ফোরক মন্তব্য div.megawrap > div.featured-meta > h2.entry-title > a
01 June div.featured-meta > div.post-snip > span.post-date > time.published
তামিলনাড়ুর তিরুথুরাইপুন্ডি কেন্দ্রে সিপিআই প্রার্থী কমরেড কে. মারিমুথুর বিপুল জয় div.megawrap > div.featured-meta > h2.entry-title > a
04 May div.featured-meta > div.post-snip > span.post-date > time.published
twitter div.widget-content > ul.socialFilter > li > a.twitter
youtube div.widget-content > ul.socialFilter > li > a.youtube
Your Responsive Ads code (Google Ads) div#main-ads2 > div#HTML15 > div.widget-content > a.piki-ads

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Live Web Directory body#mainContent > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#HTML16 > div.widget-content > a > img div#HTML16 > div.widget-content > a > img
div.wikipedia-searchtable > span > a.wikipedia-search-wiki-link > img.wikipedia-icon div.wikipedia-searchtable > span > a.wikipedia-search-wiki-link > img.wikipedia-icon
div#sidebar1 > div#FeaturedPost1 > div.post-summary > img.image div#sidebar1 > div#FeaturedPost1 > div.post-summary > img.image

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.wikipedia-searchtable > span.wikipedia-search-bar > span.wikipedia-input-box > input#Wikipedia1_wikipedia-search-input div.wikipedia-searchtable > span.wikipedia-search-bar > span.wikipedia-input-box > input#Wikipedia1_wikipedia-search-input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Archive August (49) July (237) June (251) May (201) April (158) March (214) Feb… div.widget-content > div#ArchiveList > div#BlogArchive1_ArchiveList > select#BlogArchive1_ArchiveMenu

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div > div#followers-iframe-container > iframe#I0_1786355230722 div > div > div#followers-iframe-container > iframe#I0_1786355230722

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.headerHero-wrap > div.headerHero > div.container > a.show-MenuNews-pro-container div.headerHero-wrap > div.headerHero > div.container > a.show-MenuNews-pro-container
div.headerHero-wrap > div.headerHero > div.container > a.search-button div.headerHero-wrap > div.headerHero > div.container > a.search-button
div#HTML6 > div.breaking-content > div.mydivs-bt > a.prev div#HTML6 > div.breaking-content > div.mydivs-bt > a.prev
div#HTML6 > div.breaking-content > div.mydivs-bt > a.next div#HTML6 > div.breaking-content > div.mydivs-bt > a.next
div#sidebar1 > div#HTML16 > div.widget-content > a div#sidebar1 > div#HTML16 > div.widget-content > a
form#Wikipedia1_wikipedia-search-form > div.wikipedia-searchtable > span > a.wikipedia-search-wiki-link
div.widget-content > ul.social-footer > li.facebook-f > a.facebook-f div.widget-content > ul.social-footer > li.facebook-f > a.facebook-f
div.widget-content > ul.social-footer > li.twitter > a.twitter div.widget-content > ul.social-footer > li.twitter > a.twitter
div.widget-content > ul.social-footer > li.youtube > a.youtube div.widget-content > ul.social-footer > li.youtube > a.youtube
div.widget-content > ul.social-footer > li.instagram > a.instagram div.widget-content > ul.social-footer > li.instagram > a.instagram
div.widget-content > ul.social-footer > li.reddit > a.reddit div.widget-content > ul.social-footer > li.reddit > a.reddit

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
body#mainContent > meta body#mainContent > meta

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
শাহরুখ খানের জওয়ান টিজার আলোড়ন ফেললো দেশ জুড়ে ul > li > span.item-title > a
১০ বছর পর আবার ফিরে এলো গ্যাংনাম স্টাইল এর স্মৃতি ul > li > span.item-title > a

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
●Buttons have an accessible name
●Input buttons have discernible text.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●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.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○`<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.
○`<td>` elements in a large `<table>` have one or more table headers.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN CONTENTINFO (missing!)

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
Heading Text Quality
Action
3 heading-text-quality issue(s) detected
REVIEW
3 heading-text-quality issue(s) detected
Warning::
1 heading(s) contain placeholder / generic text
Some headings contain placeholder or generic text patterns that often leak through from CMS templates / WYSIWYG defaults / unfinished drafts. Affected (first 1): - H3: "Read more" Replace with descriptive text that summarizes the section's content. Search engines use heading text to understand page structure; placeholder text contributes nothing to relevance signals.
Got: 1 placeholder heading(s)
Info::
2 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "Ad" - H3: "Ad"
Got: 2 ≤2-char heading(s)
Info::
27 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 27 all-caps heading(s)
B
Form Input Types
5 input(s) using type=text where a specific type would help
REVIEW
5 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "Wikipedia1_wikipedia-search-input" should use type="search" (currently type="text")
Field name "Wikipedia1_wikipedia-search-input" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "query" should use type="search" (currently type="text")
Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 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.
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 Views now ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h1 Views now
1.14:1
#000000
on
#07064B
needs 3.0:1 (large text)
32px · above the fold
h3 # Top Heads
1.16:1
#000000
on
#09084E
needs 3.0:1 (large text)
19px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Views now1.14:13.0:1
#000000
#07064B
Fail
h2 news on move21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Archive21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Followers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 # Top Heads1.16:13.0:1
#000000
#09084E
Fail
h3 Breaking Ticker21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hotest News21.00:13.0:1
#000000
#FFFFFF
Pass
h3 World Fresh Updates21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Subscribe via Mobile21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Views now21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hollywood Movies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Views now21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Wikipedia21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Total Pageviews21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Social Plugin21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Translate21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Social Plugin21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Popular Posts21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Most Viewed21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Search This Blog21.00:13.0: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
Heading Hierarchy
69 headings, 1 skip(s)
PASS
69 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Views now
  • H3 # Top Heads skipped
  • H3 Breaking Ticker
  • H2 কিস্তি না দিলেই স্তব্ধ হবে স্মার্টফোন: ফাইন্যান্সিয়াল অ্যাপের রিমোট লকিং ঘ
  • H2 Yemen’s Houthis unleash missile barrage on Saudi-backed troops (VIDEOS)
  • H2 Top US streamer banned over ‘just shoot kids’ comment (VIDEO)
  • H2 Netanyahu nixes Trump’s Gaza peace plan (VIDEO)
  • H2 Can ‘Islamic NATO’ reign in both Israel and Iran?
  • H2 বৃষ্টিভেজা ভারী মাঠে কৌশলগত স্ট্র্যাটেজির বাজিমাত: ২-০ ব্যবধানে চ্যাম্পিয�
  • H3 Hotest News
  • H2 ব্রাজিলে রাষ্ট্রপতি নির্বাচনে বাজিমাত বামেদের
  • H2 তৃণমূলে যোগদানের খবর ভিত্তিহীন জানালেন জয়ী বাম প্রার্থী
  • H2 গণনাতেও হিংসা! দুপুর পর্যন্ত রাজ্যে আহত ৬১ জন পঞ্চায়েত নির্বাচনের গণনার দ��
  • H2 RG KAR: উত্তাল নৈহাটি আক্রান্ত আন্দোলনকারীরা
  • H2 সোদপুর থেকে শ্যামবাজার পর্যন্ত হাতে হাত
  • H2 হাসপাতালের বেনিয়ম: আগেই সতর্ক করেছিল ক্যাগ
  • H2 তিলোত্তমা বিচারের দাবির আন্দোলন দমানোর চেষ্টা কুনাল ঘোষের অডিও বের করার পর
  • H2 বাংলার উপনির্বাচনে সবুজ ঝড়: বামেদের ভোটবৃদ্ধিতে নতুন সমীকরণ
  • H2 সিআইটিইউ-এর ১১তম পশ্চিম বর্ধমান জেলা সম্মেলন উদ্বোধন
  • H2 ভয়াবহ দুর্ঘটনা দুর্গাপুর ইস্পাত কারখানায় মৃত্যু শ্রমিকের
  • H2 দুর্গাপুর পূর্ব: সিপিআই(এম)-এর ভোটের শতাংশ ও ফলাফল বিশ্লেষণ
  • H2 দুর্গাপুরে বিয়ের আসরেই রক্তদান শিবির! সামাজিক দায়বদ্ধতার অনন্য নজির লিটন খ
  • H2 দুর্গাপুরে স্বেচ্ছায় রক্তদান আন্দোলনের রজতজয়ন্তী উদযাপন, রক্তদাতাদের স
  • H2 তৃণমূল থেকে বহিষ্কৃত এন্টালির বিধায়ক সন্দীপন সাহা, দলের বিরুদ্ধে বিস্ফোর�
  • H2 তামিলনাড়ুর তিরুথুরাইপুন্ডি কেন্দ্রে সিপিআই প্রার্থী কমরেড কে. মারিমুথুর
  • H3 World Fresh Updates
  • H2 কিস্তি না দিলেই স্তব্ধ হবে স্মার্টফোন: ফাইন্যান্সিয়াল অ্যাপের রিমোট লকিং ঘ
  • H2 Yemen’s Houthis unleash missile barrage on Saudi-backed troops (VIDEOS)
  • H2 Top US streamer banned over ‘just shoot kids’ comment (VIDEO)
  • H2 Netanyahu nixes Trump’s Gaza peace plan (VIDEO)
  • H3 Subscribe via Mobile
  • H3 Views now
  • H3 Read more
  • H2 কিস্তি না দিলেই স্তব্ধ হবে স্মার্টফোন: ফাইন্যান্সিয়াল অ্যাপের রিমোট লকিং ঘ
  • H2 Yemen’s Houthis unleash missile barrage on Saudi-backed troops (VIDEOS)
  • H2 Top US streamer banned over ‘just shoot kids’ comment (VIDEO)
  • H2 Netanyahu nixes Trump’s Gaza peace plan (VIDEO)
  • H2 Can ‘Islamic NATO’ reign in both Israel and Iran?
  • H2 বৃষ্টিভেজা ভারী মাঠে কৌশলগত স্ট্র্যাটেজির বাজিমাত: ২-০ ব্যবধানে চ্যাম্পিয�
  • H3 Hollywood Movies
  • H3 Ad
  • H3 Ad
  • H3 Views now
  • H3 Wikipedia
  • H3 Report Abuse
  • H2 news on move
  • H3 কিস্তি না দিলেই স্তব্ধ হবে স্মার্টফোন: ফাইন্যান্সিয়াল অ্যাপের রিমোট লকিং ঘ
  • H3 Total Pageviews
  • H2 Archive
  • H3 Social Plugin
  • H2 Followers
  • H3 Translate
  • H3 Social Plugin
  • H3 Popular Posts
  • H2 দুর্গাপুর পূর্ব: সিপিআই(এম)-এর ভোটের শতাংশ ও ফলাফল বিশ্লেষণ
  • H2 দুর্গাপুরে বিয়ের আসরেই রক্তদান শিবির! সামাজিক দায়বদ্ধতার অনন্য নজির লিটন খ
  • H2 দুর্গাপুরে স্বেচ্ছায় রক্তদান আন্দোলনের রজতজয়ন্তী উদযাপন, রক্তদাতাদের স
  • H2 তৃণমূল থেকে বহিষ্কৃত এন্টালির বিধায়ক সন্দীপন সাহা, দলের বিরুদ্ধে বিস্ফোর�
  • H2 তামিলনাড়ুর তিরুথুরাইপুন্ডি কেন্দ্রে সিপিআই প্রার্থী কমরেড কে. মারিমুথুর
  • H3 Most Viewed
  • H2 কিস্তি না দিলেই স্তব্ধ হবে স্মার্টফোন: ফাইন্যান্সিয়াল অ্যাপের রিমোট লকিং ঘ
  • H2 Yemen’s Houthis unleash missile barrage on Saudi-backed troops (VIDEOS)
  • H2 Top US streamer banned over ‘just shoot kids’ comment (VIDEO)
  • H2 Netanyahu nixes Trump’s Gaza peace plan (VIDEO)
  • H3 Search This Blog
  • H3 About Us
  • H3 Follow Us
  • H3 Footer Copyright
  • H3 Contact form

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+
Form Input Quality
18 form control(s) checked, no input-semantic issues
PASS
18 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
32 explicit tabindex attribute(s) checked, no anti-patterns
PASS
32 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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::
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.

Send Feedback