Kayakkayak.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" dir="ltr">
Fix all of the following:
- Document does not have a main landmark
ModerateAll 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.
Failing Elements
<h1 id="title">Please confirm that you are a real user.</h1>
Fix any of the following:
- Some page content is not contained by landmarks
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" dir="ltr">
<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" dir="ltr">
All page content should be contained by landmarks6 elements
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
<div id="outer">
<div class="logo"> </div>
<div id="captcha">
<div style="width: 304px; height: 78px;">
<div>
<iframe title="reCAPTCHA" width="304" height="78" role="presentation" name="a-wrlsm3z7wmg0" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.google.c...">
ARIA role should be appropriate for the element1 element
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<iframe title="reCAPTCHA" width="304" height="78" role="presentation" name="a-wrlsm3z7wmg0" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.google.c...">
ARIA roles used must conform to valid values1 element
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<iframe title="reCAPTCHA" width="304" height="78" role="presentation" name="a-wrlsm3z7wmg0" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.google.c...">
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 id="kayak" style="display: block;">
Deprecated ARIA roles must not be used1 element
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<iframe title="reCAPTCHA" width="304" height="78" role="presentation" name="a-wrlsm3z7wmg0" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.google.c...">
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" dir="ltr">
Elements marked as presentational should be consistently ignored1 element
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<iframe title="reCAPTCHA" width="304" height="78" role="presentation" name="a-wrlsm3z7wmg0" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.google.c...">
Elements must meet minimum color contrast ratio thresholds1 element
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<textarea id="g-recaptcha-response" name="g-recaptcha-response" class="g-recaptcha-response" style="width: 250px; height: 40px; border: 1px solid rgb(193, 193, 193); margin: 10px 25px; padding: 0px; resize: none; display: none;"></textarea>
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 title="reCAPTCHA" width="304" height="78" role="presentation" name="a-wrlsm3z7wmg0" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.google.c...">
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 title="reCAPTCHA" width="304" height="78" role="presentation" name="a-wrlsm3z7wmg0" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.google.c...">
Heading levels should only increase by one1 element
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 id="title">Please confirm that you are a real user.</h1>
Headings should not be empty1 element
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 id="title">Please confirm that you are a real user.</h1>
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 id="kayak" style="display: block;">
<div style="width: 304px; height: 78px;">
Page 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.
Audit Elements
<html lang="en" dir="ltr">
Required ARIA attributes must be provided1 element
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<iframe title="reCAPTCHA" width="304" height="78" role="presentation" name="a-wrlsm3z7wmg0" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.google.c...">
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">
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">