Skip to content
https://thewire.in

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-ttyj0s
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.

F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 1 pass AA only
a తెలుగు
3.89:1
#000000
on
#CD2529
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title The Wire: The Wire N…21.00:14.5:1
#000000
#FFFFFF
Pass
span header21.00:14.5:1
#000000
#FFFFFF
Pass
a English19.25:14.5:1
#000000
#F7F5EE
Pass
a हिंदी15.78:14.5:1
#000000
#E4DFD2
Pass
a తెలుగు3.89:14.5:1
#000000
#CD2529
Fail
a اردو6.02:14.5:1
#000000
#D16B6A
Pass
span 10 Years of The Wire18.11:14.5:1
#000000
#F2EEE3
Pass
a Become A Supporter18.11:14.5:1
#000000
#F2EEE3
Pass
a Hindi18.11:14.5:1
#000000
#F2EEE3
Pass
a Urdu18.11:14.5:1
#000000
#F2EEE3
Pass
span Home18.11:14.5:1
#000000
#F2EEE3
Pass
span category18.11:14.5:1
#000000
#F2EEE3
Pass
span opinion18.11:14.5:1
#000000
#F2EEE3
Pass
span Video18.11:14.5:1
#000000
#F2EEE3
Pass
a Terms18.11:14.5:1
#000000
#F2EEE3
Pass
a Privacy18.11:14.5:1
#000000
#F2EEE3
Pass
a About Us18.11:14.5:1
#000000
#F2EEE3
Pass
span The Wire | 201818.11:14.5:1
#000000
#F2EEE3
Pass
a Home18.11:14.5:1
#000000
#F2EEE3
Pass
a Politics18.11:14.5:1
#000000
#F2EEE3
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.

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 6 failing, 15 passed
REVIEW
77

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
The commission also issued directions to identify and arrest the persons on the… a.facc_list > div.tfcc_list > div.wrapper_list > div.excerpt_980515
22 Apr div > div.fpt_crsl > div.p_crsl > span.t_crsl
21 Apr div > div.fpt_crsl > div.p_crsl > span.t_crsl
His graduation is evidenced by his increasingly unhinged Truth Social posts. a.facc_list > div.tfcc_list > div.wrapper_list > div.excerpt_980262
GOVERNMENT div > div.fpt_crsl > h3.post_catdet > span.cat_name
GOVERNMENT div > div.fpt_crsl > h3.post_catdet > span.cat_name
GOVERNMENT div > div.fpt_crsl > h3.post_catdet > span.cat_name
WOMEN div > div.fpt_crsl > h3.post_catdet > span.cat_name
PODCASTS body.home-body > div.podcast > div.podcast_header > span.podcast_tag
THE INTERVIEW WITH KARAN THAPAR a.podcast_link > div.podcast_container > div.podcast_content > span.podcast_show
00:00 div.podcast_item > div.podcast_controls > div.podcast_wave > span.time
THE WIRE WRAP a.podcast_link > div.podcast_container > div.podcast_content > span.podcast_show
THE WIRE TALKS a.podcast_link > div.podcast_container > div.podcast_content > span.podcast_show
SEEMA SAYS a.podcast_link > div.podcast_container > div.podcast_content > span.podcast_show
BOOK SHOOK a.podcast_link > div.podcast_container > div.podcast_content > span.podcast_show
TOPICS div.footer-container > div.footer-section > div.footr-link > h3
VOICES div.footer-container > div.footer-section > div.footr-link > h3
NAVIGATE div.footer-container > div.footer-section > div.footr-link > h3

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
Why Aadhaar’s Missing Middle is Causing an Identity Crisis in India’s Adivasi A… div.row > div.col-md-8 > a > h6.origin
Calcutta HC Stays ECI's List of 'Troublemakers', Says 'Cannot Issue Such Blanke… div.row > div.col-md-8 > a > h6.origin
When Gandhi Visited Ceylon and Did Some Plain Speaking to Its Citizens, Sometim… div.row > div.col-md-8 > a > h6.origin
A Farm Labourer in Jangalmahal, Rabindranath Sardar Is a Candidate on a Mission div.row > div.col-md-8 > a > h6.origin
Congress, TMC File Complaint Against BJP Over Special Trains to Bengal During E… div.row > div.col-md-8 > a > h6.origin
Interview | Delimitation, Divisive Politics Were BJP Strategies in Tamil Nadu P… div.row > div.col-md-8 > a > h6.origin
Nepal's Home Minister Resigns Under Cloud of Allegations About His Business Dea… div.row > div.col-md-8 > a > h6.origin
Midnight FIRs, Undercover Police Counselling Employees: Questions Surround the … div.row > div.col-md-8 > a > h6.origin
CASTE a.mlrt_facc_list > div.mlrt_tfcc_list > div.mlrt_fct_list > h3.post_catdet

These are opportunities to improve keyboard navigation in your application.

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.pref_src_main_container > div.pref_src_sub_container > a > img div.pref_src_main_container > div.pref_src_sub_container > a > img

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
body.home-body > div.pref_src_main_container > div.pref_src_sub_container > a body.home-body > div.pref_src_main_container > div.pref_src_sub_container > a

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

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
Politics div.footer-container > div.footer-section > div.footr-link > a
Economy div.footer-container > div.footer-section > div.footr-link > a
World div.footer-container > div.footer-section > div.footr-link > a
Security div.footer-container > div.footer-section > div.footr-link > a
Law div.footer-container > div.footer-section > div.footr-link > a
Science div.footer-container > div.footer-section > div.footr-link > a
Society div.footer-container > div.footer-section > div.footr-link > a
Culture div.footer-container > div.footer-section > div.footr-link > a
Opinion div.footer-container > div.footer-section > div.footr-link > a
Editor's Pick div.footer-container > div.footer-section > div.footr-link > a
Analysis div.footer-container > div.footer-section > div.footr-link > a
About Us div.footer-container > div.footer-section > div.footr-link > a
Support Us div.footer-container > div.footer-section > div.footr-link > a
Contact Us div.footer-container > div.footer-section > div.footr-link > a

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearch(Search news)placeholder only

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

<input type="search">

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

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

Send Feedback