https://www.lyfehotels.com
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
71
GRADE
C
FIX
7
REVIEW
8
PASS
9
INFO
0
Checks
249 PASS 8 REVIEW 7 FIX
DMobile Keyboard & AutofillAction1/1 eligible field(s) missing autocomplete or inputmodeFIX
Mobile Keyboard & Autofill
Action1/1 eligible field(s) missing autocomplete or inputmode
1/1 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: current-password.
Got: <input type="password">
DTabindex Anti-PatternsAction0 positive, 115 -1-on-focusableFIX
Tabindex Anti-Patterns
Action0 positive, 115 -1-on-focusable
0 positive, 115 -1-on-focusable
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
tabindex="-1" on naturally-focusable <button id="slick-slide-control01">
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
FFavicon & BrandingAction2 icon(s) detectedFIX
Favicon & Branding
Action2 icon(s) detected
2 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::
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
DWeb ManifestActionNot foundFIX
Web Manifest
ActionNot found
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.
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
No dark mode signals
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 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.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
No print styles
Info::
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 ✗
CLandmark StructureAction3 landmarksREVIEW
Landmark Structure
Action3 landmarks
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Why this matters
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
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
BForm Accessibility3 of 3 controls have issuesREVIEW
Form Accessibility
3 of 3 controls have issues
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="password">; <input type="text" name="txt_searchbox" id="txt_searchbox">
3 controls
0 labeled
3 placeholder only
0 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| input | text | (Email Id) | placeholder only |
| input | password | (Password) | placeholder only |
| #txt_searchbox | text | (Type Something Here) | placeholder only |
Placeholder text disappears on focus and is not a reliable label.
<input type="text">; <input type="password">; <input type="text" name="txt_searchbox" id="txt_searchbox">
Why this matters
Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.
Learn more ▾ ▴
Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).
Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman
CLink & Button QualityAction57 issue(s) across 187 links and 6 buttonsREVIEW
Link & Button Quality
Action57 issue(s) across 187 links and 6 buttons
57 issue(s) across 187 links and 6 buttons
Critical::
57 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: https://www.lyfehotels.com/media/mnahmcce/lyfe-factsheet.pdf; /wellness/fitness-centre/; /wellness/salon/; /wellness/spa/; javascript:void(0);; javascript:void(0);; javascript:void(0);; javascript:void(0);; javascript:void(0);; javascript:void(0); (+47 more)
Warning::
8 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: https://www.swiftbook.io/inst/#home?propertyId=883MjY7ZbdO4gCgjiXEG4Wcg7PnLd0…; https://maps.app.goo.gl/ETrmGYVnL6aefLHD8; mailto:reservations.bbsr@lyfehotels.com; /sitemap; https://www.linkedin.com/company/lyfe-hotels; https://www.facebook.com/Lyfehotelsandresorts; https://twitter.com/LyfeHotels; https://www.instagram.com/lyfehotelsandresorts/
Info::
122 link(s) with descriptive text
187 links
57 empty
0 generic text
8 new tab
0 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.swiftbook.io/inst/#home?prop… | BOOK NOW | new tab | Add '(opens in new tab)' to text |
| https://www.lyfehotels.com/media/mnahmcc… | (empty) | empty | Add link text or aria-label |
| /wellness/fitness-centre/ | (empty) | empty | Add link text or aria-label |
| /wellness/salon/ | (empty) | empty | Add link text or aria-label |
| /wellness/spa/ | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| javascript:void(0); | (empty) | empty | Add link text or aria-label |
| https://maps.app.goo.gl/ETrmGYVnL6aefLHD… | VIEW DIRECTIONS | new tab | Add '(opens in new tab)' to text |
| mailto:reservations.bbsr@lyfehotels.com | reservations.bbsr@lyfehotels.c… | new tab | Add '(opens in new tab)' to text |
| /sitemap | Sitemap | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/company/lyfe-ho… | new tab | Add '(opens in new tab)' to text | |
| https://www.facebook.com/Lyfehotelsandre… | new tab | Add '(opens in new tab)' to text | |
| https://twitter.com/LyfeHotels | new tab | Add '(opens in new tab)' to text | |
| https://www.instagram.com/lyfehotelsandr… | new tab | Add '(opens in new tab)' to text |
128 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
https://www.lyfehotels.com/media/mnahmcce/lyfe-factsheet.pdf; /wellness/fitness-centre/; /wellness/salon/; /wellness/spa/; javascript:void(0);; javascript:void(0);; javascript:void(0);; javascript:void(0);; javascript:void(0);; javascript:void(0); (+47 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
Add '(opens in new tab)' to link text or aria-label.
https://www.swiftbook.io/inst/#home?propertyId=883MjY7ZbdO4gCgjiXEG4Wcg7PnLd0…; https://maps.app.goo.gl/ETrmGYVnL6aefLHD8; mailto:reservations.bbsr@lyfehotels.com; /sitemap; https://www.linkedin.com/company/lyfe-hotels; https://www.facebook.com/Lyfehotelsandresorts; https://twitter.com/LyfeHotels; https://www.instagram.com/lyfehotelsandresorts/
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
BForm Input Quality2 input-semantic issue(s) across 3 form control(s)REVIEW
Form Input Quality
2 input-semantic issue(s) across 3 form control(s)
2 input-semantic issue(s) across 3 form control(s)
Info::
1 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password">.
Info::
1 login form field(s) missing `autocomplete=username` (or `email`)
On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="text">.
BMobile-Readable Font Sizes93% of visible text renders at >= 12 CSS px (9 below threshold)REVIEW
Mobile-Readable Font Sizes
93% of visible text renders at >= 12 CSS px (9 below threshold)
93% of visible text renders at >= 12 CSS px (9 below threshold)
Info::
9 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <button> 0.0px ("Previous"); <button> 0.0px ("Next"); <button> 0.0px ("Previous"); <p> 10.0px ("February 19, 2025"); <p> 10.0px ("1.6k").
B404 Error PageHTTP 404, custom pageREVIEW
404 Error Page
HTTP 404, custom page
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Color Contrast (Screenshot)
Action20 text elements analyzed, 20 fail WCAG AA
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
0 pass 20 fail WCAG AA
h1 Arrive at a Luxury Stay for Business & L…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)32px · bottom of viewport
h2 About Lyfe Hotels
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Royal Rooms & Suits in a Luxury Hotel of…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Experience Luxury Dining at 5-star Resta…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Wellness Luxury Hotel & Spa in Bhubanesw…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Our Services
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Nearby Attractions
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Read Also
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 FAQs
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 What makes Lyfe Hotels one of the best 5…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Does Lyfe Hotels offer luxury rooms and …
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 What wellness and spa facilities are ava…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Are there fine dining restaurants at Lyf…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Can I host corporate meetings or wedding…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 How far is Lyfe Hotels from Bhubaneswar …
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Is parking available at Lyfe Hotels, Bhu…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 What safety and hygiene measures are fol…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 What is the cancellation policy at Lyfe …
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
h2 Are there nearby attractions close to Ly…
1.83:1#000000
on#1B3F3F
needs 3.0:1 (large text)24px · bottom of viewport
title Luxury & Business Hotel in Bhubaneswar |…
1.83:1#000000
on#1B3F3F
needs 4.5:1 (normal text)16px · top of page (header area)
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Arrive at a Luxury S… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 About Lyfe Hotels | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Royal Rooms & Suits … | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Experience Luxury Di… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Wellness Luxury Hote… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Our Services | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Nearby Attractions | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Read Also | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 FAQs | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 What makes Lyfe Hote… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Does Lyfe Hotels off… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 What wellness and sp… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Are there fine dinin… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Can I host corporate… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 How far is Lyfe Hote… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Is parking available… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 What safety and hygi… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 What is the cancella… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| h2 Are there nearby att… | 1.83:1 | 3.0:1 | #000000 | #1B3F3F | Fail |
| title Luxury & Business Ho… | 1.83:1 | 4.5:1 | #000000 | #1B3F3F | Fail |
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.
BLighthouse Accessibility AuditsScore 81/100 — 7 failing, 21 passedREVIEW
Lighthouse Accessibility Audits
Score 81/100 — 7 failing, 21 passed
81
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
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.
Why this matters
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
02
Udayagiri and Khandagiri Caves ul.nearbyAttractionSiderWrap > div.slick-list > div.slick-track > li.nearbyAttractionSide |
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.
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 |
|---|
BOOK NOW body > section.spotlightHome > div.mobFormBtn > a.primaryBtn |
CALL NOW body > section.spotlightHome > div.mobFormBtn > a.primaryBtn |
DISCOVER MORE div.row > div.col-12 > div > a.primaryBtn |
Fitness Centre div#slick-slide30 > div.wellnessContentWrap > div.wellnessCopy > p.greenText |
Planet Fitness div#slick-slide30 > div.wellnessContentWrap > div.wellnessCopy > div.subHeading |
01 div.slick-list > div.slick-track > li.nearbyAttractionSide > p.goldenText |
December 30, 2025 div.blogBootomSlide > div.blogSliderInfo > div.blogleft-info-date > p |
1.6k div.blogSliderInfo > div.blogleft-info-views > div.viewwrap > p#blogCount-2137 |
1/25 div.col-12 > div.blogBottomSlidertitile > div.blogBootomSliderWrap > div.slider__counter |
What makes Lyfe Hotels one of the best 5-star hotels in Bhubaneswar? ul > div.at-item > div.at-title > h2 |
Does Lyfe Hotels offer luxury rooms and suites in Bhubaneswar? ul > div.at-item > div.at-title > h2 |
What wellness and spa facilities are available at Lyfe Hotels? ul > div.at-item > div.at-title > h2 |
Are there fine dining restaurants at Lyfe Hotels, Bhubaneswar? ul > div.at-item > div.at-title > h2 |
Can I host corporate meetings or weddings at Lyfe Hotels Bhubaneswar? ul > div.at-item > div.at-title > h2 |
How far is Lyfe Hotels from Bhubaneswar Airport and Railway Station? ul > div.at-item > div.at-title > h2 |
Is parking available at Lyfe Hotels, Bhubaneswar? ul > div.at-item > div.at-title > h2 |
What safety and hygiene measures are followed at Lyfe Hotels? ul > div.at-item > div.at-title > h2 |
What is the cancellation policy at Lyfe Hotels Bhubaneswar? ul > div.at-item > div.at-title > h2 |
Are there nearby attractions close to Lyfe Hotels Bhubaneswar? ul > div.at-item > div.at-title > h2 |
BOOK NOW ul.footerContactList > li > div.footerContactInfo > a.primaryBtn |
These are opportunities to improve the legibility of your content.
Names and labels
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 |
|---|
ul.aboutList > li > div.QR-code-img > a ul.aboutList > li > div.QR-code-img > a |
div.slick-track > div#slick-slide30 > div.wellnessContentWrap > a.circleArrowNext div.slick-track > div#slick-slide30 > div.wellnessContentWrap > a.circleArrowNext |
div.blogleft-info-views > div.shareWrap > span > a div.blogleft-info-views > div.shareWrap > span > 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.
Tables and lists
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Located strategically at the heart of the temple city.
Bringing the best of ho… div.row > div.col-12 > div.homeBusinessSliderMob > ul.slick-initialized |
Standard Rooms
VIEW DETAILS
Deluxe Rooms
VIEW DETAILS
Studio Suites
VIEW DETAIL… div.row > div.col-12 > div > ul.twoColWrap |
Hotel Deluxe Room div.row > div.col-12 > div > ul.twoColWrapNav |
01
Lingaraj Temple
02
Udayagiri and Khandagiri Caves
03
Regional Museum of… div.container > div.row > div.col-12 > ul.nearbyAttractionSiderWrap |
What makes Lyfe Hotels one of the best 5-star hotels in Bhubaneswar?
Lyfe Hotel… div.faqSectionWrapper > div.faqright_section > div.accordion > ul |
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Technologically advanced meeting and conference rooms. ul.slick-initialized > div.slick-list > div.slick-track > li.slick-slide |
Standard Rooms
VIEW DETAILS ul.twoColWrap > div.slick-list > div.slick-track > li.slick-slide |
Hotel Standard Rooms ul.twoColWrapNav > div.slick-list > div.slick-track > li.slick-slide |
Hotel Deluxe Room ul.twoColWrapNav > div.slick-list > div.slick-track > li.slick-slide |
Hotel Studio Suites ul.twoColWrapNav > div.slick-list > div.slick-track > li.slick-slide |
01
Lingaraj Temple ul.nearbyAttractionSiderWrap > div.slick-list > div.slick-track > li.nearbyAttractionSide |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
VIEW ROOMS div.slick-track > div#slick-slide00 > div.bannerContentWrap > a.primaryBtn |
CALL NOW body > section.spotlightHome > div.mobFormBtn > a.primaryBtn |
EXPLORE MORE div.dinningSlide > div.dinningImgCopyWrap > div.dinningCopyWrap > a.primaryBtn |
VIEW DIRECTIONS div.footerLogo > div.footerLogoText > div.footerDirectionWrap > a.footerTitle |
○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 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 use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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.
○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+Heading Hierarchy19 headingsPASS
Heading Hierarchy
19 headings
19 headings
Info::
Single H1 present
- H1 Arrive at a Luxury Stay for Business & Leisure
- H2 About Lyfe Hotels
- H2 Royal Rooms & Suits in a Luxury Hotel of Odisha
- H2 Experience Luxury Dining at 5-star Restaurants in Bhubaneswar
- H2 Wellness Luxury Hotel & Spa in Bhubaneswar
- H2 Our Services
- H2 Nearby Attractions
- H2 Read Also
- H2 FAQs
- H2 What makes Lyfe Hotels one of the best 5-star hotels in Bhubaneswar?
- H2 Does Lyfe Hotels offer luxury rooms and suites in Bhubaneswar?
- H2 What wellness and spa facilities are available at Lyfe Hotels?
- H2 Are there fine dining restaurants at Lyfe Hotels, Bhubaneswar?
- H2 Can I host corporate meetings or weddings at Lyfe Hotels Bhubaneswar?
- H2 How far is Lyfe Hotels from Bhubaneswar Airport and Railway Station?
- H2 Is parking available at Lyfe Hotels, Bhubaneswar?
- H2 What safety and hygiene measures are followed at Lyfe Hotels?
- H2 What is the cancellation policy at Lyfe Hotels Bhubaneswar?
- H2 Are there nearby attractions close to Lyfe Hotels Bhubaneswar?
A+Heading Text QualityAll 19 heading(s) have substantive, well-formed textPASS
Heading Text Quality
All 19 heading(s) have substantive, well-formed text
All 19 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
AAlt Text Quality2 of 213 images have issuesPASS
Alt Text Quality
2 of 213 images have issues
2 of 213 images have issues
Warning::
2 image(s) with generic alt text
Info::
161 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
213 images 50 good alt text 161 decorative 2 generic
| Issue | Count |
|---|---|
| generic | 2 image(s) |
A+Form Input Types1 input(s) using type=text where a specific type would helpPASS
Form Input Types
1 input(s) using type=text where a specific type would help
1 input(s) using type=text where a specific type would help
Info::
Input "Email Id" should use type="email" (currently type="text")
Field name "Email Id" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+Document LanguageLang attribute set to "en"PASS
Document Language
Lang attribute set to "en"
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+Iframe AccessibilityNo iframes on this pagePASS
Iframe Accessibility
No iframes on this page
No iframes on this page
Info::
No iframes on this page
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+PWA DepthNo PWA depth issues detectedPASS
PWA Depth
No PWA depth issues detected
No PWA depth issues detected
Info::
No PWA depth issues detected
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
Mobile UX Depth
1 mobile-depth signal(s) detected
1 mobile-depth signal(s) detected
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.