Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 6 REVIEW 10 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

Search landmark present

Page Structure — as a screen reader sees it

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

Form Accessibility

Action

11 of 13 controls have issues

FIX

11 of 13 controls have issues

8 control(s) without accessible label

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

Got: <input type="submit">; <input type="text" id="Wikipedia1_wikipedia-search-input">; <input type="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">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

3 control(s) rely on placeholder only

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

Got: <input type="search" name="q">; <input type="search" name="q">; <input type="search" name="q">

2 control(s) properly labeled

13 controls

2 labeled

3 placeholder only

8 unlabeled

Control	Type	Label	Method
q	input	Search this blog	aria-label
select	select	ابزاره ترجمه زبان	aria-label
q	search	(Search this blog)	placeholder only
q	search	(Search this blog)	placeholder only
q	search	(Search)	placeholder only
input	submit	(none)	none
input	submit	(none)	none
#Wikipedia1_wikipedia-search-input	text	(none)	none
#goog-gt-votingInputSrcLang	text	(none)	none
#goog-gt-votingInputTrgLang	text	(none)	none
#goog-gt-votingInputSrcText	text	(none)	none
#goog-gt-votingInputTrgText	text	(none)	none
#goog-gt-votingInputVote	text	(none)	none

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

Why this matters

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

Source: WCAG 2.1 SC 3.3.2

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

Action

7 issue(s) across 138 links and 5 buttons

FIX

7 issue(s) across 138 links and 5 buttons

5 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; #; https://www.blogger.com/profile/13758337234136888352; https://wikipedia.org/wiki/; javascript:;

28 link(s) open in new tab without warning

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

Got: https://www.facebook.com/templatesyard/; https://twitter.com/LiveBlogger1; https://www.instagram.com/livebloggerofficial/; #; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352 (+18 more)

2 button(s) with no accessible text

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

Got: input[type="submit"].wikipedia-search-button (#378 on page); button.search-action (#1018 on page)

105 link(s) with descriptive text

138 links

5 empty

0 generic text

28 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/templatesyard/	facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/LiveBlogger1	x-twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/livebloggeroff…	instagram	new tab	Add '(opens in new tab)' to text
#	pinterest	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
https://www.blogger.com/profile/13758337…	Cinebuzz Tamil	new tab	Add '(opens in new tab)' to text
https://www.blogger.com/profile/13758337…	Cinebuzz Tamil	new tab	Add '(opens in new tab)' to text
https://www.blogger.com/profile/13758337…	Cinebuzz Tamil	new tab	Add '(opens in new tab)' to text
https://www.blogger.com/profile/13758337…	Cinebuzz Tamil	new tab	Add '(opens in new tab)' to text
https://www.blogger.com/profile/13758337…	Cinebuzz Tamil	new tab	Add '(opens in new tab)' to text
https://www.blogger.com/profile/13758337…	Cinebuzz Tamil	new tab	Add '(opens in new tab)' to text
https://www.blogger.com/profile/13758337…	Cinebuzz Tamil	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://www.blogger.com/go/report-abuse	Report Abuse	new tab	Add '(opens in new tab)' to text
https://www.blogger.com/profile/13758337…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/templatesyard/	facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/LiveBlogger1	x-twitter	new tab	Add '(opens in new tab)' to text
#	rss	new tab	Add '(opens in new tab)' to text
#	pinterest	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/livebloggeroff…	instagram	new tab	Add '(opens in new tab)' to text
#	vk	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/liveblogger	youtube	new tab	Add '(opens in new tab)' to text
#	linkedin	new tab	Add '(opens in new tab)' to text
#	snapchat	new tab	Add '(opens in new tab)' to text
#	dribbble	new tab	Add '(opens in new tab)' to text
https://wikipedia.org/wiki/	(empty)	empty	Add link text or aria-label
https://translate.google.com	ترجمه	new tab	Add '(opens in new tab)' to text
https://gooyaabitemplates.com/	Gooyaabi	new tab	Add '(opens in new tab)' to text
javascript:;	(empty)	empty	Add link text or aria-label
https://www.facebook.com/templatesyard/	facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/LiveBlogger1	x-twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/livebloggeroff…	instagram	new tab	Add '(opens in new tab)' to text
#	pinterest	new tab	Add '(opens in new tab)' to text
<input>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

108 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; #; https://www.blogger.com/profile/13758337234136888352; https://wikipedia.org/wiki/; javascript:;

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.facebook.com/templatesyard/; https://twitter.com/LiveBlogger1; https://www.instagram.com/livebloggerofficial/; #; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352; https://www.blogger.com/profile/13758337234136888352 (+18 more)

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.

input[type="submit"].wikipedia-search-button (#378 on page); button.search-action (#1018 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

Document Language

Action

Missing <html lang> attribute (WCAG 3.1.1)

FIX

Missing <html lang> attribute (WCAG 3.1.1)

Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

Favicon & Branding

Action

2 icon(s) detected

FIX

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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: #e6e8e9

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 ✗

Lighthouse Accessibility Audits

Action

Score 67/100 — 10 failing, 22 passed

FIX

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
SHOW MORE `div#main > div#Blog1 > div.home-posts-headline > a.view-all`
SIMRAN `div.blog-posts > div.blog-post > div.post-image-wrap > span.post-tag`
Cinebuzz Tamil `div.post-info > div.post-meta > span.post-author > a`
August 14, 2026 `div.blog-post > div.post-info > div.post-meta > span.post-date`
SIVAKARTHIKEYAN `div.blog-posts > div.blog-post > div.post-image-wrap > span.post-tag`
Cinebuzz Tamil `div.post-info > div.post-meta > span.post-author > a`
August 14, 2026 `div.blog-post > div.post-info > div.post-meta > span.post-date`
LOKESH KANAGARAJ `div.blog-posts > div.blog-post > div.post-image-wrap > span.post-tag`
Cinebuzz Tamil `div.post-info > div.post-meta > span.post-author > a`
August 12, 2026 `div.blog-post > div.post-info > div.post-meta > span.post-date`
SILAMBARASAN TR `div.blog-posts > div.blog-post > div.post-image-wrap > span.post-tag`
Cinebuzz Tamil `div.post-info > div.post-meta > span.post-author > a`
August 11, 2026 `div.blog-post > div.post-info > div.post-meta > span.post-date`
VIJAY SETHUPATHI `div.blog-posts > div.blog-post > div.post-image-wrap > span.post-tag`
Cinebuzz Tamil `div.post-info > div.post-meta > span.post-author > a`
August 11, 2026 `div.blog-post > div.post-info > div.post-meta > span.post-date`
DEEPIKA PADUKONE `div.blog-posts > div.blog-post > div.post-image-wrap > span.post-tag`
Cinebuzz Tamil `div.post-info > div.post-meta > span.post-author > a`
August 11, 2026 `div.blog-post > div.post-info > div.post-meta > span.post-date`
SURYA `div.blog-posts > div.blog-post > div.post-image-wrap > span.post-tag`
Cinebuzz Tamil `div.post-info > div.post-meta > span.post-author > a`
August 07, 2026 `div.blog-post > div.post-info > div.post-meta > span.post-date`
div#BlogSearch1 > div.widget-content > form.search-form > input.search-action `div#BlogSearch1 > div.widget-content > form.search-form > input.search-action`
Powered by Blogger `div#Attribution1 > div.widget-content > div.blogger > a`
21 `ul.flat > li.archivedate > a > span.post-count`
SIMRAN `div.post > div.post-content > a.post-image-link > span.post-tag`
Cinebuzz Tamil `div.post-content > div.post-info > div.post-meta > span.post-author`
August 14, 2026 `div.post-content > div.post-info > div.post-meta > span.post-date`
August 11, 2026 `div.post-content > div.post-info > div.post-meta > span.post-date`
August 11, 2026 `div.post-content > div.post-info > div.post-meta > span.post-date`
August 11, 2026 `div.post-content > div.post-info > div.post-meta > span.post-date`
ராமாயணம் (2026) `div.post-content > div.post-info > h2.post-title > a`
The Odyssey திரைப்பட விமர்சனம் `div.post-content > div.post-info > h2.post-title > a`
டிமான்டி காலனி 3 `div.post-content > div.post-info > h2.post-title > a`
ராமாயணம் (2026) `div.post-content > div.post-info > h2.post-title > a`
The Odyssey திரைப்பட விமர்சனம் `div.post-content > div.post-info > h2.post-title > a`
டிமான்டி காலனி 3 `div.post-content > div.post-info > h2.post-title > a`
3,012 `div#Stats1 > div.widget-content > div#Stats1_content > span#Stats1_totalCount`
SlumDog: 33 Temple Road – விஜய் சேதுபதியின் மிரட்டலான புதிய அவதாரம்! `div.post-content > div.post-info > h2.post-title > a`
Raaka – அல்லு அர்ஜுனின் அடுத்த பிரம்மாண்டம் எப்படி இருக்கும்? `div.post-content > div.post-info > h2.post-title > a`
Arasan: சிம்புவின் அடுத்த பிரம்மாண்ட திரைப்படம் – முழு தகவல்கள் `div.post-content > div.post-info > h2.post-title > a`
Home `div.widget-content > ul > li > a`
About `div.widget-content > ul > li > a`
Contact Us `div.widget-content > ul > li > a`
Crafted with by TemplatesYard \| Distributed by Gooyaabi `div#footer-wrapper > div#sub-footer-wrapper > div.container > div.copyright-area`

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
Gooyaabi `div#sub-footer-wrapper > div.container > div.copyright-area > a`

These are opportunities to improve the legibility of your content.

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
Cinebuzz Tamil `div#Profile1 > div.widget-content > div.profile-info > dl.profile-datablock`

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

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.wikipedia-searchtable > span > a.wikipedia-search-wiki-link > img.wikipedia-icon `div.wikipedia-searchtable > span > a.wikipedia-search-wiki-link > img.wikipedia-icon`

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`

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_1786727874752 `div > div > div#followers-iframe-container > iframe#I0_1786727874752`
div#HTML14 > div.widget-content > div.videoWrapper > iframe `div#HTML14 > div.widget-content > div.videoWrapper > iframe`

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#main > div#Blog1 > div#blog-pager > a.page-num `div#main > div#Blog1 > div#blog-pager > a.page-num`
div#sidebar1 > div#Profile1 > div.widget-content > a `div#sidebar1 > div#Profile1 > div.widget-content > a`
`form#Wikipedia1_wikipedia-search-form > div.wikipedia-searchtable > span > a.wikipedia-search-wiki-link`

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.ltr `html.ltr`

These are opportunities to improve the interpretation of your content by users in different locales.

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
head > meta `head > meta`

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.ltr `html.ltr`

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

●Input buttons have discernible text.

●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

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●Touch targets have sufficient size and spacing.

●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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has a valid value for its `[lang]` attribute

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

○Elements with visible text labels have matching accessible names.

○`<td>` elements in a large `<table>` have one or more table headers.

Heading Hierarchy

40 headings

REVIEW

40 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 Header Ads Widget
H3 Read more
H2 ரஜினிகாந்தின் 173வது திரைப்படமான தர்மன் படத்தின் லேட்டஸ்ட் அப்டேட், நடிகர்
H2 சிவகார்த்திகேயனின் புதிய கிராமத்து ஆக்‌ஷன் படம் 2026
H2 DC திரைப்பட விமர்சனம்
H2 Arasan: சிம்புவின் அடுத்த பிரம்மாண்ட திரைப்படம் – முழு தகவல்கள்
H2 SlumDog: 33 Temple Road – விஜய் சேதுபதியின் மிரட்டலான புதிய அவதாரம்!
H2 Raaka – அல்லு அர்ஜுனின் அடுத்த பிரம்மாண்டம் எப்படி இருக்கும்?
H2 விஷ்வநாத் & சன்ஸ்
H3 Native Banner
H2 Followers
H3 Search This Blog
H3 Report Abuse
H3 About Me
H2 ரஜினிகாந்தின் 173வது திரைப்படமான தர்மன் படத்தின் லேட்டஸ்ட் அப்டேட், நடிகர்
H3 Social Plugin
H3 Wikipedia
H3 Translate
H3 Subscribe Us
H3 Most Popular
H2 SlumDog: 33 Temple Road – விஜய் சேதுபதியின் மிரட்டலான புதிய அவதாரம்!
H2 Raaka – அல்லு அர்ஜுனின் அடுத்த பிரம்மாண்டம் எப்படி இருக்கும்?
H2 Arasan: சிம்புவின் அடுத்த பிரம்மாண்ட திரைப்படம் – முழு தகவல்கள்
H3 Labels
H3 ADS3
H3 Random Posts
H2 ராமாயணம் (2026)
H2 The Odyssey திரைப்பட விமர்சனம்
H2 டிமான்டி காலனி 3
H3 Recent in Sports
H2 ராமாயணம் (2026)
H2 The Odyssey திரைப்பட விமர்சனம்
H2 டிமான்டி காலனி 3
H3 Total Pageviews
H3 ADS 2
H3 Popular Posts
H2 SlumDog: 33 Temple Road – விஜய் சேதுபதியின் மிரட்டலான புதிய அவதாரம்!
H2 Raaka – அல்லு அர்ஜுனின் அடுத்த பிரம்மாண்டம் எப்படி இருக்கும்?
H2 Arasan: சிம்புவின் அடுத்த பிரம்மாண்ட திரைப்படம் – முழு தகவல்கள்
H3 Menu Footer Widget

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Heading Text Quality

2 heading-text-quality issue(s) detected

REVIEW

2 heading-text-quality issue(s) detected

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)

11 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: 11 all-caps heading(s)

Alt Text Quality

Action

1 of 25 images have issues

REVIEW

1 of 25 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

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

12 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

11 image(s) with good alt text

25 images 11 good alt text 1 decorative 1 missing

Issue	Count
missing	1 image(s)
too long	12 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

Iframe Accessibility

Action

4/6 iframe(s) missing title; 0 placeholder(s)

REVIEW

4/6 iframe(s) missing title; 0 placeholder(s)

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.

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.

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.

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.

Mobile-Readable Font Sizes

Action

82% of visible text renders at >= 12 CSS px (16 below threshold)

REVIEW

82% of visible text renders at >= 12 CSS px (16 below threshold)

16 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: <a> 11.0px ("Show more"); <span> 10.0px ("Simran"); <span> 10.0px ("Sivakarthikeyan"); <span> 10.0px ("lokesh kanagaraj"); <span> 10.0px ("Silambarasan TR").

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Cinebuzz Tamil ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Form Input Types

3 input(s) using type=text where a specific type would help

PASS

3 input(s) using type=text where a specific type would help

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

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

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

A+

Form Input Quality

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

PASS

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

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+

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.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Followers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Header Ads Widget	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Read more	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Native Banner	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Search This Blog	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About Me	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Social Plugin	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Wikipedia	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Translate	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Subscribe Us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Most Popular	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Labels	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ADS3	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Random Posts	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Recent in Sports	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Total Pageviews	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ADS 2	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Popular Posts	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Menu Footer Widget	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Cinebuzz Tamil	20.43:1	4.5:1	#000000	#FAFCFF	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.