Skip to content
https://coca-colacompany.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
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
Landmark Structure
Action
4 landmarks
REVIEW
4 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
Info::
All <nav> elements are properly labeled
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV "Choose a slide to display" 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

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

C
Heading Hierarchy
Action
32 headings, 2 skip(s)
REVIEW
32 headings, 2 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 139+
  • H3 years of refreshing the world
  • H4 200+
  • H3 Brands worldwide
  • H4 CAREERS
  • H4 GET THE LATEST
  • H2 Search
  • H2 Refreshingly Local
  • H3 Coca‑Cola X A250
  • H3 ACHIEVEMENT UNLOCKED: Wanta Fanta Upgrade
  • H3 Sprite is NBA’s Official Global Soft Drink
  • H1 Football, Music and Culture Collide in the all-new FIFA World Cup 2026™ Anthem
  • H1 FIFA World Cup™ Trophy Tour by Coca‑Cola is Here duplicate H1
  • H2 Refreshingly Local
  • H3 Coca‑Cola X A250
  • H1 Our Purpose & Company Vision duplicate H1
  • H3 Who We Are skipped
  • H3 Letter to Employees from Chairman and CEO James Quincey
  • H2 The Freshest News
  • H3 Coca‑Cola Reports Fourth Quarter and Full Year 2025 Results
  • H3 The Coca‑Cola Company Delivers Big at Cannes with 13 Wins Across Global Campaigns
  • H3 Coca‑Cola unveils new cherry-flavored beverages
  • H3 Time Magazine Ranks The Coca‑Cola Company 3rd Among America's Most Iconic Brands
  • H3 Coca‑Cola Reports Fourth Quarter and Full Year 2025 Results
  • H3 The Coca‑Cola Company Delivers Big at Cannes with 13 Wins Across Global Campaigns
  • H3 Coca‑Cola unveils new cherry-flavored beverages
  • H3 Time Magazine Ranks The Coca‑Cola Company 3rd Among America's Most Iconic Brands
  • H3 Refresh Your Career
  • H3 Start the Next Chapter
  • H2 Say "Hi" to the Team
  • H4 ABOUT US skipped
  • H4 NEED HELP?

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

B
404 Error Page
HTTP 404, custom page
REVIEW
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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 87/100 — 5 failing, 25 passed
REVIEW
87

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
div.container > div#mobile-company-nav > div.button > button#company-mobile-menu div.container > div#mobile-company-nav > div.button > button#company-mobile-menu
div#tabs-b7754b42dc > ol.cmp-tabs__tablist > li#tabs-b7754b42dc-item-87fb4902ba-tab > button#search-button div#tabs-b7754b42dc > ol.cmp-tabs__tablist > li#tabs-b7754b42dc-item-87fb4902ba-tab > button#search-button

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#tabs-b7754b42dc > ol.cmp-tabs__tablist > li#tabs-b7754b42dc-item-2dbda12673-tab > a#language-button div#tabs-b7754b42dc > ol.cmp-tabs__tablist > li#tabs-b7754b42dc-item-2dbda12673-tab > a#language-button
div#tabs-b7754b42dc > ol.cmp-tabs__tablist > li#tabs-b7754b42dc-item-a350c394d4-tab > a#reciteme-button div#tabs-b7754b42dc > ol.cmp-tabs__tablist > li#tabs-b7754b42dc-item-a350c394d4-tab > a#reciteme-button

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
Media Center a.cmp-teaser__link > div.cmp-teaser__content > div.cmp-teaser__heading > p.mediacenter

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Who We Are div#teaser-ec24d938e8 > a.cmp-teaser__link > div.cmp-teaser__content > h3.cmp-teaser__title
ABOUT US div#container-2f591bedd9 > div.text > div#text-158235dd54 > h4
Necessary Cookies section.ot-sdk-row > div.ot-accordion-layout > div.ot-acc-hdr > h4#ot-header-id-1

These are opportunities to improve keyboard navigation in your application.

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
Cookie Policy div > div#ot-pc-content > div#ot-pc-desc > a.privacy-notice-link
○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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<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.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○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+
Alt Text Quality
All 55 images OK
PASS
All 55 images OK
Info::
23 decorative image(s) correctly marked
Info::
32 image(s) with good alt text
55 images 32 good alt text 23 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input>
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputinput(Start typing here...)placeholder only

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

<input>

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

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
h1 Football, Music and …6.95:13.0:1
#000000
#A48F96
Pass
h1 FIFA World Cup™ Tr…6.95:13.0:1
#000000
#A48F96
Pass
h1 Our Purpose & Compan…6.95:13.0:1
#000000
#A48F96
Pass
h2 Search6.95:13.0:1
#000000
#A48F96
Pass
h2 Refreshingly Local6.95:13.0:1
#000000
#A48F96
Pass
h2 Refreshingly Local6.95:13.0:1
#000000
#A48F96
Pass
h2 The Freshest News6.95:13.0:1
#000000
#A48F96
Pass
h2 Say "Hi" to the Team6.95:13.0:1
#000000
#A48F96
Pass
h3 years of refreshing …5.23:13.0:1
#000000
#B9676F
Pass
h3 Brands worldwide6.95:13.0:1
#000000
#A48F96
Pass
h3 Coca‑Cola X A2506.95:13.0:1
#000000
#A48F96
Pass
h3 ACHIEVEMENT UNLOCKED…6.95:13.0:1
#000000
#A48F96
Pass
h3 Sprite is NBA’s Of…6.95:13.0:1
#000000
#A48F96
Pass
h3 Coca‑Cola X A2506.95:13.0:1
#000000
#A48F96
Pass
h3 Who We Are6.95:13.0:1
#000000
#A48F96
Pass
h3 Letter to Employees …6.95:13.0:1
#000000
#A48F96
Pass
h3 Coca‑Cola Reports …6.95:13.0:1
#000000
#A48F96
Pass
h3 The Coca‑Cola Comp…6.95:13.0:1
#000000
#A48F96
Pass
h3 Coca‑Cola unveils …6.95:13.0:1
#000000
#A48F96
Pass
h3 Time Magazine Ranks …6.95:13.0:1
#000000
#A48F96
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