Accessibility

D

Tabindex Anti-Patterns

Action

2 positive, 30 -1-on-focusable

FIX

2 positive, 30 -1-on-focusable

tabindex="-1" on naturally-focusable <select id="booking-mask-hotel">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

Positive tabindex on <input id="bm-checkin-input">: tabindex=1

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <input id="bm-checkout-input">: tabindex=1

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

tabindex="-1" on naturally-focusable <select id="bm-rooms">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <select>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <select>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <select>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <select>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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)

Skip navigation link detected

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 4 <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.

B

Landmark Structure

10 landmarks

REVIEW

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

3 of 4 <nav> elements are unlabeled

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

Skip navigation link present

Skip link target(s) don't exist on page: #header-content, #site-content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

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

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

B

Heading Hierarchy

47 headings, 2 skip(s)

REVIEW

47 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

H1 Rosen Inns in Orlando
H2 Come for the Convenience, Stay for the Service
H2 OFFERS & PACKAGES
H4 Girls' Getaway skipped
H4 Rosen Inn Lake Buena Vista
H4 Florida Fun Grab-n'-Go
H4 Available in multiple properties
H4 Buy 3 Nights, Get the 4th Night Free
H4 Available in multiple properties
H4 Orlando Summer Bed & Breakfast
H4 Available in multiple properties
H4 Pirates & Princess
H4 Rosen Inn Lake Buena Vista
H4 Halloween Happenings
H4 Available in multiple properties
H4 Girls' Getaway
H4 Rosen Inn Lake Buena Vista
H4 Florida Fun Grab-n'-Go
H4 Available in multiple properties
H4 Buy 3 Nights, Get the 4th Night Free
H4 Available in multiple properties
H4 Orlando Summer Bed & Breakfast
H4 Available in multiple properties
H4 Pirates & Princess
H4 Rosen Inn Lake Buena Vista
H4 Halloween Happenings
H4 Available in multiple properties
H4 Girls' Getaway
H4 Rosen Inn Lake Buena Vista
H2 FEATURED AMENITIES
H2 ORLANDO THEME PARKS NEARBY
H3 Walt Disney World®
H3 SeaWorld® Orlando
H3 Universal Orlando Resort™
H2 DELICIOUS DINING
H2 FIND YOUR ROSEN INN
H4 Rosen Inn International skipped
H4 Rosen Inn Closest to Universal
H4 Rosen Inn at Pointe Orlando
H4 Rosen Inn Lake Buena Vista
H2 FAQ About Rosen Inns Hotels
H3 What are Rosen Inns and where are they located?
H3 Do Rosen Inns hotels offer dining options on-site?
H3 Are there vacation packages available at Rosen Inns?
H3 Do Rosen Inns have shuttle services to the theme parks?
H3 Do Rosen Inns charge resort fees?
H2 Orlando Summer Bed & Breakfast

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

C

Alt Text Quality

Action

8 of 37 images have issues

REVIEW

8 of 37 images have issues

8 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

15 decorative image(s) correctly marked

14 image(s) with good alt text

37 images 14 good alt text 15 decorative 8 missing

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

C

Mobile Keyboard & Autofill

Action

1/2 eligible field(s) missing autocomplete or inputmode

REVIEW

1/2 eligible field(s) missing autocomplete or inputmode

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email">

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | Rosen Inn Hotels and Resorts Group Site ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 16 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

4 pass 16 fail WCAG AA 4 pass AA only

h1 Rosen Inns in Orlando

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Come for the Convenience, Stay for the S…

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 OFFERS & PACKAGES

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FEATURED AMENITIES

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ORLANDO THEME PARKS NEARBY

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 DELICIOUS DINING

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FIND YOUR ROSEN INN

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FAQ About Rosen Inns Hotels

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Orlando Summer

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Bed & Breakfast

1.43:1

#000000

on

#122D2A

needs 3.0:1 (large text)

24px · bottom of viewport

a Skip to footer

2.75:1

#000000

on

#525454

needs 4.5:1 (normal text)

16px · top of page (header area)

span Reservations: Toll Free 1-866-33ROSEN (7…

3.48:1

#000000

on

#606367

needs 4.5:1 (normal text)

16px · above the fold

a Local 407-996-7233

3.74:1

#000000

on

#64686C

needs 4.5:1 (normal text)

16px · above the fold

span Stay

4.29:1

#000000

on

#6E7176

needs 4.5:1 (normal text)

16px · above the fold

span Rosen Inn International

4.47:1

#000000

on

#717478

needs 4.5:1 (normal text)

16px · above the fold

span Rosen Inn, closest to Universal

4.11:1

#000000

on

#6C6E72

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Rosen Inns in Orland…	1.43:1	3.0:1	#000000	#122D2A	Fail
h2 Come for the Conveni…	1.43:1	3.0:1	#000000	#122D2A	Fail
h2 OFFERS & PACKAGES	1.43:1	3.0:1	#000000	#122D2A	Fail
h2 FEATURED AMENITIES	1.43:1	3.0:1	#000000	#122D2A	Fail
h2 ORLANDO THEME PARKS …	1.43:1	3.0:1	#000000	#122D2A	Fail
h2 DELICIOUS DINING	1.43:1	3.0:1	#000000	#122D2A	Fail
h2 FIND YOUR ROSEN INN	1.43:1	3.0:1	#000000	#122D2A	Fail
h2 FAQ About Rosen Inns…	1.43:1	3.0:1	#000000	#122D2A	Fail
h2 Orlando Summer	1.43:1	3.0:1	#000000	#122D2A	Fail
h2 Bed & Breakfast	1.43:1	3.0:1	#000000	#122D2A	Fail
title Rosen Inns Orlando \|…	5.85:1	4.5:1	#000000	#878787	Pass
a Skip to navigation	5.69:1	4.5:1	#000000	#858585	Pass
a Skip to main content	5.85:1	4.5:1	#000000	#878787	Pass
a Skip to footer	2.75:1	4.5:1	#000000	#525454	Fail
span Reservations: Toll F…	3.48:1	4.5:1	#000000	#606367	Fail
a Local 407-996-7233	3.74:1	4.5:1	#000000	#64686C	Fail
span Stay	4.29:1	4.5:1	#000000	#6E7176	Fail
span Rosen Inn Internatio…	4.47:1	4.5:1	#000000	#717478	Fail
span Rosen Inn, closest t…	4.11:1	4.5:1	#000000	#6C6E72	Fail
span Rosen Inn Pointe Orl…	4.51:1	4.5:1	#000000	#747478	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.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

5 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 5 all-caps heading(s)

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#bm-checkin-input	text	Date picker. Use arrow keys to navigate dates. Press enter to select a date.	aria-label
#bm-checkout-input	text	Date picker. Use arrow keys to navigate dates. Press enter to select a date.	aria-label
#booking-mask-promocode	text	Promo Code	for/id
email	email	Add your email to subscribe	aria-label

A

Link & Button Quality

70 links, 97 buttons — all OK

PASS

70 links, 97 buttons — all OK

18 link(s) open in new tab without warning

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

Got: https://www.roseninn7600.com/; https://www.roseninn6327.com/; https://www.roseninn9000.com/; https://www.rosenlbv.com/; https://reservations.travelclick.com/2023?ProdID=650211&LanguageID=1&_gl=1*1e…; https://reservations.travelclick.com/2023?ProdID=752962&LanguageID=1&_gl=1*1e…; https://reservations.travelclick.com/2023?ProdID=650211&LanguageID=1&_gl=1*1e…; https://reservations.travelclick.com/2023?ProdID=752962&LanguageID=1&_gl=1*1e…; https://reservations.travelclick.com/2023?ProdID=650211&LanguageID=1&_gl=1*1e…; https://www.roseninn7600.com/ (+8 more)

52 link(s) with descriptive text

70 links

0 empty

0 generic text

18 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.roseninn7600.com/	Rosen Inn International	new tab	Add '(opens in new tab)' to text
https://www.roseninn6327.com/	Rosen Inn, closest to Universa…	new tab	Add '(opens in new tab)' to text
https://www.roseninn9000.com/	Rosen Inn Pointe Orlando	new tab	Add '(opens in new tab)' to text
https://www.rosenlbv.com/	Rosen Inn Lake Buena Vista	new tab	Add '(opens in new tab)' to text
https://reservations.travelclick.com/202…	Book now for Girls' Getaway …	new tab	Add '(opens in new tab)' to text
https://reservations.travelclick.com/202…	Book now for Pirates & Princes…	new tab	Add '(opens in new tab)' to text
https://reservations.travelclick.com/202…	Book now for Girls' Getaway …	new tab	Add '(opens in new tab)' to text
https://reservations.travelclick.com/202…	Book now for Pirates & Princes…	new tab	Add '(opens in new tab)' to text
https://reservations.travelclick.com/202…	Book now for Girls' Getaway …	new tab	Add '(opens in new tab)' to text
/amenities	Read more about	img no alt	Add alt attribute to the image
/amenities	Read more about	img no alt	Add alt attribute to the image
https://www.roseninn7600.com/	Explore Rosen Inn Internationa…	new tab	Add '(opens in new tab)' to text
https://www.roseninn6327.com/	Explore Rosen Inn opens in a n…	new tab	Add '(opens in new tab)' to text
https://www.roseninn9000.com/	Explore Rosen Inn at Pointe Or…	new tab	Add '(opens in new tab)' to text
https://www.rosenlbv.com/	Explore Rosen Inn Lake Buena V…	new tab	Add '(opens in new tab)' to text
https://facebook.com/rosenhotels	Facebook opens in a new tab	new tab	Add '(opens in new tab)' to text
http://twitter.com/rosenhotels	Twitter opens in a new tab	new tab	Add '(opens in new tab)' to text
https://instagram.com/rosenhotels	Instagram opens in a new tab	new tab	Add '(opens in new tab)' to text
https://tiktok.com/@rosenhotels	TikTok opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.amadeus-hospitality.com/	Amadeus Hospitality	new tab	Add '(opens in new tab)' to text

149 links and buttons have descriptive text

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

https://www.roseninn7600.com/; https://www.roseninn6327.com/; https://www.roseninn9000.com/; https://www.rosenlbv.com/; https://reservations.travelclick.com/2023?ProdID=650211&LanguageID=1&_gl=1*1e…; https://reservations.travelclick.com/2023?ProdID=752962&LanguageID=1&_gl=1*1e…; https://reservations.travelclick.com/2023?ProdID=650211&LanguageID=1&_gl=1*1e…; https://reservations.travelclick.com/2023?ProdID=752962&LanguageID=1&_gl=1*1e…; https://reservations.travelclick.com/2023?ProdID=650211&LanguageID=1&_gl=1*1e…; https://www.roseninn7600.com/ (+8 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

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

4 form control(s) checked, no input-semantic issues

PASS

4 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A

Iframe Accessibility

1/2 iframe(s) missing title; 0 placeholder(s)

PASS

1/2 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 29 visible text node(s) render at >= 12 CSS pixels

PASS

All 29 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 25 passed

PASS

96

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
Universal Orlando Resort™ `div.content-container > div.item-content > h3 > font`

These are opportunities to improve the legibility of your content.

○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

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

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

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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