Skip to content
https://Makenaevents.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
8
REVIEW
4
PASS
12
INFO
0
Checks
24
12 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
3 landmarks
FIX
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO footer

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

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

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

D
Form Accessibility
Action
4 of 12 controls have issues
FIX
4 of 12 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="countryCode" id="countryCode">; <select name="countryCode" id="countryCode2">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="customCountryCode" id="customCountryCode">; <input type="text" name="customCountryCode" id="customCountryCode2">
Info::
8 control(s) properly labeled
12 controls
8 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#firstNametextFirst Name *for/id
#lastNametextLast Name *for/id
#emailemailEmail *for/id
#phonetelPhone Number *for/id
#firstName2textFirst Name *for/id
#lastName2textLast Name *for/id
#email2emailEmail *for/id
#phone2telPhone Number *for/id
#customCountryCode2text(+XXX)placeholder only
#customCountryCodetext(+XXX)placeholder only
#countryCodeselect(none)none
#countryCode2select(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="countryCode" id="countryCode">; <select name="countryCode" id="countryCode2">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="customCountryCode" id="customCountryCode">; <input type="text" name="customCountryCode" id="customCountryCode2">

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

D
Mobile Keyboard & Autofill
Action
6/6 eligible field(s) missing autocomplete or inputmode
FIX
6/6 eligible field(s) missing autocomplete or inputmode
Warning::
2 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: email.
Got: <input type="email" name="email" id="email">, <input type="email" name="email" id="email2">
Warning::
4 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, tel.
Got: <input type="email" name="email" id="email">, <input type="tel" name="phone" id="phone">, <input type="email" name="email" id="email2">, <input type="tel" name="phone" id="phone2">
D
Favicon & Branding
Action
2 icon(s) detected
FIX
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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
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.

D
Print Stylesheet
Action
No print styles
FIX
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Mobile-Readable Font Sizes
Action
80% of visible text renders at >= 12 CSS px (34 below threshold)
REVIEW
80% of visible text renders at >= 12 CSS px (34 below threshold)
Warning::
34 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: <div> 9.3px ("FEB 4–7"); <div> 11.5px ("Pennsylvania 🇺🇸"); <div> 11.5px ("Afriskii x Makena · Camelback Resort, PA"); <div> 9.3px ("APR 14–19"); <div> 11.5px ("Jamaica 🇯🇲").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 81/100 — 4 failing, 21 passed
REVIEW
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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav#navbar > div.container > div.nav-content > button#mobileMenuToggle nav#navbar > div.container > div.nav-content > button#mobileMenuToggle

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
🇫🇷 +33 🇵🇹 +351 🇺🇸 +1 🇬🇧 +44 🇩🇪 +49 🇪🇸 +34 🇮🇹 +39 🇧🇪 +32 🇨🇭 +41 🇳🇱 +31 🌍 Other form#discountForm2 > div.form-group > div.phone-input-group > select#countryCode2

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.instagram-posts-grid > div.instagram-embed-wrapper > iframe#instagram-embed-0 div.container > div.instagram-posts-grid > div.instagram-embed-wrapper > iframe#instagram-embed-0

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.

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
2027 div > div.section-header > div > span
CALENDAR div > div.section-header > div > span
Pennsylvania 🇺🇸 div > a > div > div
Afriskii Ski Trip div > a > div > div
Afriskii x Makena · Camelback Resort, PA div > a > div > div
Book Now → div > div > a > div
APR 14–19 div > div > div > div
Jamaica 🇯🇲 div > div > div > div
Group Trip div > div > div > div
Makena Group Travel div > div > div > div
MAY 14–17 div > div > div > div
Berlin 🇩🇪 div > div > div > div
KDK div > div > div > div
Makena x KDK · Berlin div > div > div > div
JUN 5–13 div > div > div > div
Portugal 🇵🇹 div > div > div > div
Afronation div > div > div > div
Makena x Afronation Portugal div > div > div > div
JUN 18–22 div > div > div > div
Paris 🇫🇷 div > div > div > div
Fête de la Musique div > div > div > div
Makena Paris · Annual Music Festival Weekend div > div > div > div
JUL 29–AUG 2 div > div > div > div
Albania 🇦🇱 div > div > div > div
Makena Summer Celebration div > div > div > div
Makena x Albania · Mediterranean Summer div > div > div > div
AUG 26–30 div > div > div > div
London 🇬🇧 div > div > div > div
Notting Hill Carnival div > div > div > div
Makena x Notting Hill Carnival · London div > div > div > div
SEP 2–6 div > div > div > div
Washington D.C. 🇺🇸 div > div > div > div
AfroFest div > div > div > div
Makena x AfroFest · Washington D.C. div > div > div > div
AfroPlusFest DC div > a > div > div
Sep 3–7, 2026 · Washington D.C. div > a > div > div
Afronation Portimao div > a > div > div
Portugal · Archive div > a > div > div
Fête de la Musique div > a > div > div
Paris · Archive div > a > div > div

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○No element has a `[tabindex]` value greater than 0
○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.
○Elements with visible text labels have matching accessible names.
○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 Hierarchy
22 headings
PASS
22 headings
Info::
Single H1 present
  • H2 Stay in the Loop!
  • H3 🎉 You're on the list!
  • H1 MAKENA
  • H2 Upcoming Events
  • H3 Makena Group Trip — Punta Cana
  • H2 Past Events
  • H2 Stay in the Loop!
  • H3 🎉 You're on the list!
  • H2 Latest News
  • H3 Grand Launch
  • H3 Events Coming Soon
  • H3 Join the Community
  • H2 Latest From Instagram
  • H2 Connect With Makena
  • H3 Instagram
  • H3 Eventbrite
  • H3 Email Us
  • H3 WhatsApp
  • H2 About Makena
  • H2 Frequently Asked Questions
  • H3 Quick Links
  • H3 Follow Us
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 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: 1 all-caps heading(s)
A+
Alt Text Quality
All 3 images OK
PASS
All 3 images OK
Info::
3 image(s) with good alt text
3 images 3 good alt text
All images have appropriate alt text.
A+
Form Input Types
12 form control(s) checked, no type mismatches
PASS
12 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
12 form control(s) checked, no input-semantic issues
PASS
12 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.instagram.com/p/DQwv3_WDUqY/embed/captioned/?cr=1&v=14&wp=538&rd=ht…")
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
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.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Stay in the Loop!18.76:13.0:1
#000000
#F3F2EF
Pass
h2 Upcoming Events8.74:13.0:1
#000000
#AEA5A7
Pass
h2 Past Events8.74:13.0:1
#000000
#AEA5A7
Pass
h2 Stay in the Loop!8.74:13.0:1
#000000
#AEA5A7
Pass
h2 Latest News8.74:13.0:1
#000000
#AEA5A7
Pass
h2 Latest From Instagra…8.74:13.0:1
#000000
#AEA5A7
Pass
h2 Connect With Makena8.74:13.0:1
#000000
#AEA5A7
Pass
h2 About Makena8.74:13.0:1
#000000
#AEA5A7
Pass
h2 Frequently Asked Que…8.74:13.0:1
#000000
#AEA5A7
Pass
h3 🎉 You're on the l…7.19:13.0:1
#000000
#9E949F
Pass
h3 Makena Group Trip …8.74:13.0:1
#000000
#AEA5A7
Pass
h3 🎉 You're on the l…8.74:13.0:1
#000000
#AEA5A7
Pass
h3 Grand Launch8.74:13.0:1
#000000
#AEA5A7
Pass
h3 Events Coming Soon8.74:13.0:1
#000000
#AEA5A7
Pass
h3 Join the Community8.74:13.0:1
#000000
#AEA5A7
Pass
h3 Instagram8.74:13.0:1
#000000
#AEA5A7
Pass
h3 Eventbrite8.74:13.0:1
#000000
#AEA5A7
Pass
h3 Email Us8.74:13.0:1
#000000
#AEA5A7
Pass
h3 WhatsApp8.74:13.0:1
#000000
#AEA5A7
Pass
h3 Quick Links8.74:13.0:1
#000000
#AEA5A7
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

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

Send Feedback