Skip to content
https://thetimes.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
3
REVIEW
7
PASS
3
INFO
0
Checks
13
3 PASS 7 REVIEW 3 FIX
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::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Form Accessibility
Action
3 of 9 controls have issues
REVIEW
3 of 9 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="vjs_select_652">; <select id="vjs_select_671">; <select id="vjs_select_686">
Info::
6 control(s) properly labeled
9 controls
6 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#vjs_select_602selectColorfor/id
#vjs_select_607selectOpacityfor/id
#vjs_select_617selectColorfor/id
#vjs_select_622selectOpacityfor/id
#vjs_select_632selectColorfor/id
#vjs_select_637selectOpacityfor/id
#vjs_select_652select(none)none
#vjs_select_671select(none)none
#vjs_select_686select(none)none

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

<select id="vjs_select_652">; <select id="vjs_select_671">; <select id="vjs_select_686">

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

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 Page not found | The Times & The Sunday Times Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
8 icon(s) detected
REVIEW
8 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: The Times & The Sunday Times
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name The Times & The Sunday Times 192×192 icon 512×512 icon Start URL Display Mode standalone
Name The Times & The Sunday Times Display Mode standalone Icons 6 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: dark light
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta dark light Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

C
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 The Times & The Sunday Times Homepage
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Accessibility Links
1.04:1
#000000
on
#060607
needs 3.0:1 (large text)
24px · top of page (header area)
h3 Editor's picks
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 World
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Comment
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Money
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Life & Style
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Business
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sport
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Culture
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Travel
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Obituaries
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Luxury
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Today's puzzles
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Crosswords
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sudokus
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Word puzzles
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Numbers & Logic
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Get in touch
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
h3 More from The Times and The Sunday Times
1.03:1
#000000
on
#020506
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Times & The Sund…1.03:13.0:1
#000000
#020506
Fail
h2 Accessibility Links1.04:13.0:1
#000000
#060607
Fail
h3 Editor's picks1.03:13.0:1
#000000
#020506
Fail
h3 World1.03:13.0:1
#000000
#020506
Fail
h3 Comment1.03:13.0:1
#000000
#020506
Fail
h3 Money1.03:13.0:1
#000000
#020506
Fail
h3 Life & Style1.03:13.0:1
#000000
#020506
Fail
h3 Business1.03:13.0:1
#000000
#020506
Fail
h3 Sport1.03:13.0:1
#000000
#020506
Fail
h3 Culture1.03:13.0:1
#000000
#020506
Fail
h3 Travel1.03:13.0:1
#000000
#020506
Fail
h3 Obituaries1.03:13.0:1
#000000
#020506
Fail
h3 Luxury1.03:13.0:1
#000000
#020506
Fail
h3 Today's puzzles1.03:13.0:1
#000000
#020506
Fail
h3 Crosswords1.03:13.0:1
#000000
#020506
Fail
h3 Sudokus1.03:13.0:1
#000000
#020506
Fail
h3 Word puzzles1.03:13.0:1
#000000
#020506
Fail
h3 Numbers & Logic1.03:13.0:1
#000000
#020506
Fail
h3 Get in touch1.03:13.0:1
#000000
#020506
Fail
h3 More from The Times …1.03:13.0:1
#000000
#020506
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.

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 7 failing, 25 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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Open Search div.css-rgzt88 > div#top-nav-container > a > button.css-9my8jc

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-128tvvg > a.css-denvhe > div.css-2w79da > button.css-rl0dul div.css-128tvvg > a.css-denvhe > div.css-2w79da > button.css-rl0dul
div.css-1s0afzm > a.css-denvhe > div.css-2w79da > button.css-tv6sze div.css-1s0afzm > a.css-denvhe > div.css-2w79da > button.css-tv6sze
div.css-scfek8 > a.css-denvhe > div.css-2w79da > button.css-1xgjhpe div.css-scfek8 > a.css-denvhe > div.css-2w79da > button.css-1xgjhpe
div.css-1wfh0t8 > a.css-denvhe > div.css-2w79da > button.css-kzmtyy div.css-1wfh0t8 > a.css-denvhe > div.css-2w79da > button.css-kzmtyy
div.css-11rt2wr > a.css-denvhe > div.css-2w79da > button.css-1y1oh5k div.css-11rt2wr > a.css-denvhe > div.css-2w79da > button.css-1y1oh5k
div.css-fzacen > a.css-denvhe > div.css-2w79da > button.css-1uthnd2 div.css-fzacen > a.css-denvhe > div.css-2w79da > button.css-1uthnd2
div.css-rmdsy4 > a.css-denvhe > div.css-2w79da > button.css-1qg9yak div.css-rmdsy4 > a.css-denvhe > div.css-2w79da > button.css-1qg9yak
div.css-13dwo3c > a.css-denvhe > div.css-2w79da > button.css-1miqkf6 div.css-13dwo3c > a.css-denvhe > div.css-2w79da > button.css-1miqkf6
div.css-16emzsh > a.css-denvhe > div.css-2w79da > button.css-1wi27n5 div.css-16emzsh > a.css-denvhe > div.css-2w79da > button.css-1wi27n5
div.css-1wfh0t8 > a.css-denvhe > div.css-2w79da > button.css-kzmtyy div.css-1wfh0t8 > a.css-denvhe > div.css-2w79da > button.css-kzmtyy
div.css-1kxkjzb > a.css-denvhe > div.css-2w79da > button.css-1q95566 div.css-1kxkjzb > a.css-denvhe > div.css-2w79da > button.css-1q95566
div.css-pu54k6 > div.css-1ty81u7 > div.css-xxv4fm > button.css-1fo30ap div.css-pu54k6 > div.css-1ty81u7 > div.css-xxv4fm > button.css-1fo30ap
div.css-pu54k6 > div.css-1ty81u7 > div.css-xxv4fm > button.css-1fo30ap div.css-pu54k6 > div.css-1ty81u7 > div.css-xxv4fm > button.css-1fo30ap
div.css-pu54k6 > div.css-1ty81u7 > div.css-xxv4fm > button.css-1fo30ap div.css-pu54k6 > div.css-1ty81u7 > div.css-xxv4fm > button.css-1fo30ap
div.css-pu54k6 > div.css-1ty81u7 > div.css-xxv4fm > button.css-1fo30ap div.css-pu54k6 > div.css-1ty81u7 > div.css-xxv4fm > button.css-1fo30ap

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
Open Search div.css-rgzt88 > div#top-nav-container > div.css-1smju7m > a
section.css-1x7s6xy > div.css-c3rutd > div.css-ch1f3c > a.css-1xfpats section.css-1x7s6xy > div.css-c3rutd > div.css-ch1f3c > a.css-1xfpats

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
13 minutes ago div.css-1fbarol > div.grouped-article > div.css-2k5lbk > span.css-n2r6lw
TOM PECK | POLITICAL SKETCH div > div.grouped-article > div.article-info > span.css-1ljkbxa
11 minutes ago div.css-e0ep94 > div.lead-media-article-content > div.css-2k5lbk > span.css-n2r6lw
ADVERTISEMENT div.css-y837vj > div.css-1ieito0 > div.ad-container > span.ad-label
INTERVIEW div.css-1lbbuqf > div.grid-area--content > div.article-info > span.css-1ljkbxa
REVIEW div > div.css-578et1 > div.article-info > span.css-1ljkbxa
ADVERTISEMENT div.css-xwghjd > div.css-1ieito0 > div.ad-container > span.ad-label
57 minutes ago div.css-1lbbuqf > div.grid-area--content > div.css-2k5lbk > span.css-n2r6lw
THE TIMES DIARY div.css-h3sd9w > div > div.article-info > span.css-1ljkbxa
ADVERTISEMENT div.css-xwghjd > div.css-1ieito0 > div.ad-container > span.ad-label
Q&A div.css-52c2gb > div.css-syejc > div.article-info > span.css-1ljkbxa
RENTAL HEALTH div.css-52c2gb > div.css-syejc > div.article-info > span.css-1ljkbxa
ADVERTISEMENT div.css-xwghjd > div.css-1ieito0 > div.ad-container > span.ad-label
Bec Wilson div.css-eyspfo > div.css-1yz5ayv > a.css-12jspul > span
Holly Thomas div.css-eyspfo > div.css-1yz5ayv > a.css-12jspul > span
ADVERTISEMENT div.css-xwghjd > div.css-1ieito0 > div.ad-container > span.ad-label
6 minutes ago div.css-15403k6 > div.css-52c2gb > div.css-2k5lbk > span.css-n2r6lw
ADVERTISEMENT div.css-xwghjd > div.css-1ieito0 > div.ad-container > span.ad-label
ADVERTISEMENT div.css-xwghjd > div.css-1ieito0 > div.ad-container > span.ad-label

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content body#top > div.AccessibilityLinks > a.u-hide

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
Enjoy unlimited digital access. div.css-1x6275u > div.css-qv552d > div > h4

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-home-mobile
UK div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-uk-mobile
World div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-world-mobile
Comment div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-comment-mobile
Money div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-money-mobile
Life & Style div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-life & style-mobile
Business div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-business-mobile
Sport div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-sport-mobile
Culture div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-culture-mobile
Travel div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-travel-mobile
Obituaries div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-obituaries-mobile
Puzzles div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-puzzles-mobile
Magazines div.css-1d7xt34 > div#top-nav-mobile-scroll > nav.css-15nlsyl > li#menu-item-magazines-mobile

These are opportunities to improve the experience of reading tabular or list data using 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>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
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
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Main menu" MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A
Heading Hierarchy
34 headings, 1 skip(s)
PASS
34 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Accessibility Links
  • H1 The Times & The Sunday Times Homepage
  • H4 Enjoy unlimited digital access. skipped
  • H3 Editor's picks
  • H3 World
  • H3 Comment
  • H3 Money
  • H3 Life & Style
  • H3 Business
  • H3 Sport
  • H3 Culture
  • H3 Travel
  • H3 Obituaries
  • H3 Luxury
  • H3 Today's puzzles
  • H3 Crosswords
  • H3 Crossword Club
  • H3 Concise10136
  • H3 Quick Cryptic3281
  • H3 Sudokus
  • H3 Mild16728
  • H3 Difficult16729
  • H3 Super Fiendish16730
  • H3 Word puzzles
  • H3 Polygon3
  • H3 Codeword5820
  • H3 Lexica8824
  • H3 Numbers & Logic
  • H3 Sakuro4721
  • H3 Futoshiki5360
  • H3 Kenken6812
  • H3 Get in touch
  • H3 More from The Times and The Sunday Times
  • H3 More from News Corp

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
Alt Text Quality
All 362 images OK
PASS
All 362 images OK
Info::
46 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
315 image(s) with good alt text
362 images 315 good alt text 1 decorative
IssueCount
too long46 image(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback