Accessibility

F

Heading Hierarchy

Action

128 headings, 24 skip(s)

FIX

128 headings, 24 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H4 Choose a Time Out City
H4 Choose a Time Out Market
H1 Discover the world’s coolest cities
H1 Welcome to Time Out duplicate H1
H2 Your ultimate guide to the world’s best cities
H3 The world’s most walkable cities in 2026, according to locals
H3 The 51 most beautiful places in the world
H3 The world’s best cities for green spaces and nature in 2026
H3 The best family holidays in the world to try this year
H3 The world’s most walkable cities in 2026, according to locals
H3 The 51 most beautiful places in the world
H3 The world’s best cities for green spaces and nature in 2026
H3 The best family holidays in the world to try this year
H2 Trending around the world
H3 This is the world’s most walkable city in 2026, according to Time Out’s survey
H3 It’s official: This is the best restaurant in Paris right now
H3 Sony World Photography Awards: Here are the winning photos for 2026
H3 Is it safe to travel to Japan? Here’s the latest advice after tsunami warnings issued
H3 Another European capital is rewarding tourists for ‘sustainable behaviour’
H2 Top travel inspiration
H5 Travel skipped
H3 The 50 best cities in the world in 2026
H5 Travel skipped
H3 The 31 coolest streets in the world in 2025
H5 Travel skipped
H3 The 39 coolest neighbourhoods in the world in 2025
H5 Things to do skipped
H3 The world’s best cities for Gen Z to live in – according to Gen Z
H5 Travel skipped
H3 The world’s 20 best cities for nightlife right now
H5 Travel skipped
H3 The world’s 20 best cities for food right now
H5 Travel skipped
H3 The world’s 20 best cities for culture right now
H2 Discover Time Out Market in North America
H3 Time Out Market Boston
H3 Time Out Market New York
H3 Time Out Market Montréal
H3 Time Out Market Union Square
H2 Discover Time Out Market around the world
H3 Time Out Market Bahrain
H3 Time Out Market Barcelona
H3 Time Out Market Budapest
H3 Time Out Market Cape Town
H3 Time Out Market Dubai
H3 Time Out Market Lisboa
H3 Time Out Market Osaka
H3 Time Out Market Porto
H2 Movies we love
H5 Film skipped
H3 'Lee Cronin’s The Mummy' review: distinctly Raimi-esque in its goo and gore
H5 Film skipped
H3 'You, Me & Tuscany' review: a knowing call back to a golden age of romantic comedy
H3 'You, Me & Tuscany' review: a knowing call back to a golden age of romantic comedy
H5 Film skipped
H3 'The Super Mario Galaxy Movie' review: it’s not deep but it’s made with love
H3 'The Super Mario Galaxy Movie' review: it’s not deep but it’s made with love
H5 Film skipped
H3 'The Drama' review: our verdict on the film everyone's talking about
H3 'The Drama' review: our verdict on the film everyone's talking about
H5 Film skipped
H3 'Project Hail Mary' review: the science-fiction blockbuster we need in these fractious times
H3 'Project Hail Mary' review: the science-fiction blockbuster we need in these fractious times
H5 Film skipped
H3 Here’s what’s new on Netflix in April 2026
H3 Here’s what’s new on Netflix in April 2026
H5 Film skipped
H3 The 100 best movies of all time
H3 The 100 best movies of all time
H2 Music we love
H5 Music skipped
H3 The 50 best karaoke songs ever made
H5 Music skipped
H3 The 40 best party songs ever made
H5 Music skipped
H3 The 37 best inspirational songs of all time
H5 Music skipped
H3 The 35 best cover songs of all time
H5 Music skipped
H3 The 30 best love songs of all time
H5 Music skipped
H3 The 50 greatest breakup songs of all time
H5 Music skipped
H3 The 40 best songs of 2025
H5 Music skipped
H3 The 25 best albums of 2025
H5 Music skipped
H3 The 50 best sad songs ever written
H5 Music skipped
H3 The 64 best ’80s hits
H2 Our favourite hotels
H3 The best hotels in New York City
H3 The best hotels in London
H3 The best hotels in London
H3 The coolest and most unique hotels in Tokyo
H3 The coolest and most unique hotels in Tokyo
H3 The best hotels in Los Angeles
H3 The best hotels in Los Angeles
H3 The best hotels to stay in Paris
H3 The best hotels to stay in Paris
H3 The best hotels in Singapore
H3 The best hotels in Singapore
H3 The best hotels in Chicago
H3 The best hotels in Chicago
H2 Explore Europe
H3 London
H3 Paris
H3 Barcelona
H2 Explore North America
H3 New York
H3 Los Angeles
H3 Chicago
H2 Explore Asia
H3 Singapore
H3 Tokyo
H3 Hong Kong
H2 Explore the South Pacific
H3 Sydney
H3 Melbourne
H3 Brisbane
H2 Explore Africa
H3 Cape Town
H3 Marrakech
H3 Johannesburg
H2 Explore South America
H3 Buenos Aires
H3 Rio de Janeiro
H3 Bogotá

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

F

Alt Text Quality

Action

12 of 78 images have issues

FIX

12 of 78 images have issues

12 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

12 image-in-link without alt text

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

66 image(s) with good alt text

78 images 66 good alt text 12 missing

Issue	Count
missing	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

F

Link & Button Quality

Action

31 issue(s) across 289 links and 17 buttons

FIX

31 issue(s) across 289 links and 17 buttons

17 link(s) with no accessible text

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

Got: https://www.timeout.com; a._cta_1thw9_56 (#174 on page); https://www.timeout.com; a._cta_1thw9_56 (#348 on page); /movies/you-me-tuscany-review-2026; /movies/the-super-mario-galaxy-movie-review-2026; /movies/the-drama-review-2026; /movies/project-hail-mary-review-2026; /news/best-new-movies-shows-on-netflix-april-2026-040126; /film/best-movies-of-all-time (+7 more)

4 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /travel/most-walkable-cities-2026 ("Read more"); /travel/worlds-most-beautiful-places ("Read more"); /travel/best-cities-for-green-space-2026 ("Read more"); /travel/worlds-best-family-breaks ("Read more")

33 link(s) open in new tab without warning

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

Got: https://www.timeout.com/terms-of-use; https://www.timeout.com/privacy-notice; https://www.timeout.com/terms-of-use; https://www.timeout.com/privacy-notice; https://www.instagram.com/timeouttravel/; https://www.tiktok.com/@timeouttravel; https://www.facebook.com/TimeOutTravel/; https://twitter.com/TimeOutTravel; https://www.youtube.com/user/timeoutlondonvideo; https://www.timeout.com/terms-of-use (+23 more)

10 button(s) with no accessible text

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

Got: button._navButton_1igce_61 (#201 on page); button._navButton_1igce_61 (#205 on page); button._carouselButton_y3uc9_33 (#608 on page); button._carouselButton_y3uc9_33 (#611 on page); button._carouselButton_y3uc9_33 (#711 on page); button._carouselButton_y3uc9_33 (#714 on page); button._carouselButton_y3uc9_33 (#763 on page); button._carouselButton_y3uc9_33 (#766 on page); button._carouselButton_y3uc9_33 (#988 on page); button._carouselButton_y3uc9_33 (#991 on page)

235 link(s) with descriptive text

289 links

17 empty

4 generic text

33 new tab

10 empty buttons

Element	Text	Issue	Suggested Fix
https://www.timeout.com/terms-of-use	Terms of Use	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/privacy-notice	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/terms-of-use	Terms of Use	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/privacy-notice	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.timeout.com	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.timeout.com	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.instagram.com/timeouttravel/	instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@timeouttravel	tiktok	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/TimeOutTravel/	facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/TimeOutTravel	twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/timeoutlond…	youtube	new tab	Add '(opens in new tab)' to text
/travel/most-walkable-cities-2026	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Most Walkable Cities 2026
/travel/worlds-most-beautiful-places	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Worlds Most Beautiful Places
/travel/best-cities-for-green-space-2026	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Best Cities For Green Space 2026
/travel/worlds-best-family-breaks	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Worlds Best Family Breaks
https://www.timeout.com/terms-of-use	Terms	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/privacy-notice	Privacy Policy	new tab	Add '(opens in new tab)' to text
/movies/you-me-tuscany-review-2026	(empty)	empty	Add link text or aria-label
/movies/the-super-mario-galaxy-movie-rev…	(empty)	empty	Add link text or aria-label
/movies/the-drama-review-2026	(empty)	empty	Add link text or aria-label
/movies/project-hail-mary-review-2026	(empty)	empty	Add link text or aria-label
/news/best-new-movies-shows-on-netflix-a…	(empty)	empty	Add link text or aria-label
/film/best-movies-of-all-time	(empty)	empty	Add link text or aria-label
/london/hotels/the-100-best-hotels-in-lo…	(empty)	empty	Add link text or aria-label
/tokyo/hotels/cool-and-unique-places-to-…	(empty)	empty	Add link text or aria-label
/los-angeles/hotels/best-hotels-in-los-a…	(empty)	empty	Add link text or aria-label
/paris/en/hotels/best-hotels-in-paris	(empty)	empty	Add link text or aria-label
/singapore/hotels/best-hotels-in-singapo…	(empty)	empty	Add link text or aria-label
/chicago/hotels/the-best-hotels-in-chica…	(empty)	empty	Add link text or aria-label
https://www.timeout.com	(empty)	empty	Add link text or aria-label
https://www.timeout.com/terms-of-use	Terms of Use	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/privacy-notice	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/timeouttravel/	instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@timeouttravel	tiktok	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/TimeOutTravel/	facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/TimeOutTravel	twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/timeoutlond…	youtube	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/about	About us	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/about/latest-new…	Press office	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/about/investors	Investor relations	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/about/awards	Our awards	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/about/work-for-t…	Work for Time Out	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/about/editorial-…	Editorial guidelines	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/privacy-notice	Privacy notice	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/privacy-notice#C…	Do not sell my information	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/cookie-policy	Cookie policy	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/accessibility-st…	Accessibility statement	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/terms-of-use	Terms of use	new tab	Add '(opens in new tab)' to text
https://assets.timeout.com/application/p…	Modern slavery statement	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/about/contact-us	Contact us	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/about/commercial…	Advertising	new tab	Add '(opens in new tab)' to text
https://www.timeout.com/time-out-market	Time Out Market	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

242 links and buttons have descriptive text

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

https://www.timeout.com; a._cta_1thw9_56 (#174 on page); https://www.timeout.com; a._cta_1thw9_56 (#348 on page); /movies/you-me-tuscany-review-2026; /movies/the-super-mario-galaxy-movie-review-2026; /movies/the-drama-review-2026; /movies/project-hail-mary-review-2026; /news/best-new-movies-shows-on-netflix-april-2026-040126; /film/best-movies-of-all-time (+7 more)

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

Generic link text like 'click here' doesn't describe the destination.

/travel/most-walkable-cities-2026 ("Read more"); /travel/worlds-most-beautiful-places ("Read more"); /travel/best-cities-for-green-space-2026 ("Read more"); /travel/worlds-best-family-breaks ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.timeout.com/terms-of-use; https://www.timeout.com/privacy-notice; https://www.timeout.com/terms-of-use; https://www.timeout.com/privacy-notice; https://www.instagram.com/timeouttravel/; https://www.tiktok.com/@timeouttravel; https://www.facebook.com/TimeOutTravel/; https://twitter.com/TimeOutTravel; https://www.youtube.com/user/timeoutlondonvideo; https://www.timeout.com/terms-of-use (+23 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.

button._navButton_1igce_61 (#201 on page); button._navButton_1igce_61 (#205 on page); button._carouselButton_y3uc9_33 (#608 on page); button._carouselButton_y3uc9_33 (#611 on page); button._carouselButton_y3uc9_33 (#711 on page); button._carouselButton_y3uc9_33 (#714 on page); button._carouselButton_y3uc9_33 (#763 on page); button._carouselButton_y3uc9_33 (#766 on page); button._carouselButton_y3uc9_33 (#988 on page); button._carouselButton_y3uc9_33 (#991 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

D

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.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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)

Back-to-top link detected

1 navigation landmark(s) detected

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)

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

B

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C

Form Accessibility

Action

5 of 10 controls have issues

REVIEW

5 of 10 controls have issues

5 control(s) without accessible label

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

Got: <input type="submit">; <input type="submit">; <input type="checkbox" id="checkbox-navigation-toggle">; <input type="submit">; <input type="submit">

5 control(s) properly labeled

10 controls

5 labeled

0 placeholder only

5 unlabeled

Control	Type	Label	Method
#header-newsletter-email	email	Enter email address	for/id
#popup-newsletter-email	email	Enter email address	for/id
#checkbox-city-selector	checkbox	Worldwide	for/id
#zone-newsletter-email	email	Enter email address	for/id
#footer-newsletter-email	email	Email address	for/id
#checkbox-navigation-toggle	checkbox	(none)	none
input	submit	(none)	none
input	submit	(none)	none
input	submit	(none)	none
input	submit	(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

B

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 We're sorry, we can't find the page that you're looking for ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

B

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 25 passed

REVIEW

87

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
ADVERTISING `div.zone > div._inlineAd_4tav2_76 > div._inlineAdContainer_dk7vc_60 > span.caps`
ADVERTISING `div._zoneContainer_17ld3_1 > div._inlineAdWrapper_dk7vc_65 > div._inlineAdContainer_dk7vc_60 > span.caps`
ADVERTISING `div.zone-content > div._inlineAdWrapper_dk7vc_65 > div._inlineAdContainer_dk7vc_60 > span.caps`

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
Film `article.tile > div._imageLinkContainer_170ji_1 > div._tileInfo_170ji_5 > h5._primaryCategory_170ji_28`
Film `article.tile > div.articleContent > div._primaryCategoryContainer_eq5hz_4 > h5._primaryCategory_eq5hz_4`
Film `article.tile > div.articleContent > div._primaryCategoryContainer_eq5hz_4 > h5._primaryCategory_eq5hz_4`
Film `article.tile > div.articleContent > div._primaryCategoryContainer_eq5hz_4 > h5._primaryCategory_eq5hz_4`
Film `article.tile > div.articleContent > div._primaryCategoryContainer_eq5hz_4 > h5._primaryCategory_eq5hz_4`
Film `article.tile > div.articleContent > div._primaryCategoryContainer_eq5hz_4 > h5._primaryCategory_eq5hz_4`
Film `article.tile > div.articleContent > div._primaryCategoryContainer_eq5hz_4 > h5._primaryCategory_eq5hz_4`

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._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`
div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38 `div._imageContainer_eq5hz_38 > a > picture > img._image_eq5hz_38`

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._headerContainer_2j2op_74 > div._content_2j2op_103 > div._left_2j2op_163 > a._logo_2j2op_112 `div._headerContainer_2j2op_74 > div._content_2j2op_103 > div._left_2j2op_163 > a._logo_2j2op_112`
div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems_20kfm_5 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems__firstColumn_7wg3a_106 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems__firstColumn_7wg3a_106 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems__firstColumn_7wg3a_106 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems__firstColumn_7wg3a_106 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems__firstColumn_7wg3a_106 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems__firstColumn_7wg3a_106 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems__secondColumn_7wg3a_107 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems__secondColumn_7wg3a_107 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems__secondColumn_7wg3a_107 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems__secondColumn_7wg3a_107 > article.tile > div._imageContainer_eq5hz_38 > a`
div._zoneItems__secondColumn_7wg3a_107 > article.tile > div._imageContainer_eq5hz_38 > a `div._zoneItems__secondColumn_7wg3a_107 > article.tile > div._imageContainer_eq5hz_38 > 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.

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

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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

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
h1 Welcome to Time Out	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your ultimate guide …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The world’s most w…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The 51 most beautifu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The world’s best c…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The best family holi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The world’s most w…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The 51 most beautifu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The world’s best c…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The best family holi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 This is the world’…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 It’s official: Thi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sony World Photograp…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Is it safe to travel…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Another European cap…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The 50 best cities i…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The 31 coolest stree…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The 39 coolest neigh…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The world’s best c…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The world’s 20 bes…	21.00:1	3.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.