Reutersreuters.com
Accessibility Score
Issues Found
Issues Found
ModerateDocument should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Failing Elements
<html lang="en">
Fix all of the following:
- Document does not have a main landmark
ModeratePage should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Failing Elements
<html lang="en">
Fix all of the following:
- Page must have a level-one heading
Passed Audits
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en">
All page content should be contained by landmarks1 element
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<iframe src="https://geo.captcha-..." sandbox="allow-scripts allow-..." allow="accelerometer; gyros..." title="DataDome Device Chec..." width="100%" height="100%" style="height:100vh;" frameborder="0" border="0" scrolling="yes">
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body style="margin:0">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en">
Frames must have a unique title attribute1 element
Screen reader users navigate frames using a list of frame titles. Duplicate or missing titles make it impossible to distinguish between frames, forcing users to explore each frame's content manually. Unique, descriptive titles enable quick navigation to the correct frame.
Audit Elements
<iframe src="https://geo.captcha-..." sandbox="allow-scripts allow-..." allow="accelerometer; gyros..." title="DataDome Device Chec..." width="100%" height="100%" style="height:100vh;" frameborder="0" border="0" scrolling="yes">
Frames must have an accessible name1 element
Screen reader users rely on frame titles to understand frame content without exploring each one. Without descriptive, unique titles, users receive unhelpful information like "frame," "JavaScript," or URLs, making navigation through frames difficult and confusing.
Audit Elements
<iframe src="https://geo.captcha-..." sandbox="allow-scripts allow-..." allow="accelerometer; gyros..." title="DataDome Device Chec..." width="100%" height="100%" style="height:100vh;" frameborder="0" border="0" scrolling="yes">
Inline text spacing must be adjustable with custom stylesheets2 elements
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<body style="margin:0">
<iframe src="https://geo.captcha-..." sandbox="allow-scripts allow-..." allow="accelerometer; gyros..." title="DataDome Device Chec..." width="100%" height="100%" style="height:100vh;" frameborder="0" border="0" scrolling="yes">
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">