Skip to content
https://vrbo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #000000
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 header MAIN CONTENTINFO (missing!)

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

B
Heading Hierarchy
1 headings
REVIEW
1 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Show us your human side...

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 23 passed
REVIEW
82

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
À beira-mar div.tabs-icon-and-text-bar-container > ul.tabs-icon-and-text > li.tab-icon-and-text > a.tab-icon-and-text-anchor

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.

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
Destinos perto de você div.uitk-layout-flex > div.uitk-layout-flex > div.uitk-layout-flex > h4.uitk-heading
STUDIO PERFEITO ITAIM / FARIA LIMA VAGA DE GARAGEM div.uitk-carousel-item > div.uitk-layout-flex > div.uitk-layout-flex > h6.uitk-heading

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 > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media
div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media
div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media
div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media
div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media
div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media
div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media
div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media div > figure.uitk-image > div.uitk-image-placeholder > img.uitk-image-media

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.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link
div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link
div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link
div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link
div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link
div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link
div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link
div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link div.uitk-layout-position > div.uitk-layout-position > div.uitk-card > a.uitk-card-link

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
O preço era R$ 450, veja mais informações sobre a tarifa padrão. R$ 450 div.uitk-layout-flex > div > div.uitk-layout-flex > button.neutral-color-link

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
●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
●`[role]` values are valid
●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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 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
○`<frame>` or `<iframe>` elements have a title
○`<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.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /cgp/simple/challenge.dynamic.styles
Print Stylesheet ✓ Print Optimized
Print stylesheet /cgp/simple/challenge.dynamic.styles ✓Inline @media print Not detected ✗
A+
Color Contrast (Screenshot)
4 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.

4 pass
Show all checked elements (4)
ElementRatioRequiredFGBGResult
h2 Show us your human s…20.82:13.0:1
#000000
#FEFEFE
Pass
title Bot or Not?21.00:14.5:1
#000000
#FFFFFF
Pass
p We can't tell if you…21.00:14.5:1
#000000
#FFFFFF
Pass
div ba354b03-0a3c-b11b-1…21.00:14.5: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.

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

Send Feedback