Skip to content
https://ces.tech

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
3
REVIEW
5
PASS
5
INFO
0
Checks
13
5 PASS 5 REVIEW 3 FIX
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::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Alt Text Quality
2 of 29 images have issues
REVIEW
2 of 29 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
23 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
29 images 4 good alt text 23 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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 Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: CES
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name CES ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name CES Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 1 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
h2 Secondary Navigation
1.41:1
#000000
on
#1E2254
needs 3.0:1 (large text)
24px · top of page (header area)
h2 Primary Navigation
1.35:1
#000000
on
#131F53
needs 3.0:1 (large text)
24px · above the fold
h3 Why Attend
1.37:1
#000000
on
#1B2050
needs 3.0:1 (large text)
19px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Mobile Navigation18.59:13.0:1
#000000
#F1F1F1
Pass
h1 The Global Stage for…18.59:13.0:1
#000000
#F1F1F1
Pass
h1 Contact Sales18.59:13.0:1
#000000
#F1F1F1
Pass
h2 Secondary Navigation1.41:13.0:1
#000000
#1E2254
Fail
h2 Primary Navigation1.35:13.0:1
#000000
#131F53
Fail
h2 Primary Mobile Navig…18.59:13.0:1
#000000
#F1F1F1
Pass
h2 CES 2026 Highlights18.59:13.0:1
#000000
#F1F1F1
Pass
h2 Who Was There?18.59:13.0:1
#000000
#F1F1F1
Pass
h2 Exhibit at CES 202718.59:13.0:1
#000000
#F1F1F1
Pass
h2 CES Innovation Award…18.59:13.0:1
#000000
#F1F1F1
Pass
h2 Featured Content18.59:13.0:1
#000000
#F1F1F1
Pass
h2 CTA is Pushing Techn…18.59:13.0:1
#000000
#F1F1F1
Pass
h2 Latest Releases18.59:13.0:1
#000000
#F1F1F1
Pass
h2 Footer18.59:13.0:1
#000000
#F1F1F1
Pass
h3 Why Attend1.37:13.0:1
#000000
#1B2050
Fail
h3 Attendee Types18.59:13.0:1
#000000
#F1F1F1
Pass
h3 Featured Guides18.59:13.0:1
#000000
#F1F1F1
Pass
h3 Your Guide to CES St…18.59:13.0:1
#000000
#F1F1F1
Pass
h3 A Sample Itinerary f…18.59:13.0:1
#000000
#F1F1F1
Pass
h3 CES 2026 Attendance …18.59:13.0:1
#000000
#F1F1F1
Pass

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

A
Landmark Structure
22 landmarks
PASS
22 landmarks
Info::
<main> landmark present
Info::
6 <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 "Secondary" MAIN CONTENTINFO footer

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

A
Heading Hierarchy
98 headings
PASS
98 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Secondary Navigation
  • H2 Primary Navigation
  • H3 Why Attend
  • H3 Attendee Types
  • H3 Featured Guides
  • H3 Your Guide to CES Stages
  • H3 A Sample Itinerary for Media and Creators
  • H3 CES 2026 Attendance Audit
  • H3 Why Exhibit
  • H3 Plan
  • H3 Featured Guides
  • H3 Exhibitor Dashboard: Quick 3-Step Guide
  • H3 Exhibitor Tool Kit
  • H3 Planning Resources
  • H3 Travel & Hotels
  • H3 Featured Guides
  • H3 Sample Itineraries for CES 2026
  • H3 Your Essential First-Time CES Experience Guide
  • H3 Navigate
  • H3 Show Experiences
  • H3 Additional Resources
  • H3 Featured Topics
  • H3 Artificial Intelligence
  • H3 Content and Entertainment
  • H3 Vehicle Tech and Advanced Mobility
  • H3 Content Type
  • H3 Featured Content
  • H3 Keynote: Lenovo Tech World @ CES
  • H3 C Space Keynote: Havas
  • H3 AMD Keynote
  • H1 Mobile Navigation
  • H2 Primary Mobile Navigation
  • H3 Attend
  • H4 Why Attend
  • H4 Attendee Types
  • H4 Featured Guides
  • H3 Your Guide to CES Stages
  • H3 A Sample Itinerary for Media and Creators
  • H3 CES 2026 Attendance Audit
  • H3 Exhibit
  • H4 Why Exhibit
  • H4 Plan
  • H4 Featured Guides
  • H3 Exhibitor Dashboard: Quick 3-Step Guide
  • H3 Exhibitor Tool Kit
  • H3 Plan Your Visit
  • H4 Planning Resources
  • H4 Travel & Hotels
  • H4 Featured Guides
  • H3 Sample Itineraries for CES 2026
  • H3 Your Essential First-Time CES Experience Guide
  • H3 Explore CES
  • H4 Navigate
  • H4 Show Experiences
  • H4 Additional Resources
  • H4 Featured Topics
  • H3 Artificial Intelligence
  • H3 Content and Entertainment
  • H3 Vehicle Tech and Advanced Mobility
  • H3 Discover
  • H4 Content Type
  • H4 Featured Content
  • H3 Keynote: Lenovo Tech World @ CES
  • H3 C Space Keynote: Havas
  • H3 AMD Keynote
  • H1 The Global Stage for Innovation duplicate H1
  • H2 CES 2026 Highlights
  • H3 Robotics in a New Era: Powered by Physical AI
  • H3 Digital Health Breakthroughs at CES 2026
  • H3 The Future of Advanced Mobility Starts at CES 2026
  • H3 Eureka Park 2026: Where Bold Ideas Come to Life
  • H2 Who Was There?
  • H3 2026 Best of CES Winners, Awarded by CNET Group
  • H2 Exhibit at CES 2027
  • H3 Don't be left in the past as we shape the future.
  • H1 Contact Sales duplicate H1
  • H2 CES Innovation Awards®
  • H3 ASUS
  • H3 HP Inc.
  • H3 LG Electronics
  • H3 Anker Innovations
  • H2 Featured Content
  • H3 Building Trust, Measurement and Brand Safety at Scale
  • H3 Why CTV Discovery is the Next Big Battleground for Performance Marketing
  • H3 Making the Smart Home Simpler, Safer and More Intelligent with AI
  • H3 Innovation for Longevity — How Trust and Relevance will Define the Next Decade
  • H2 CTA is Pushing Technology Forward
  • H2 Latest Releases
  • H3 A Runway for Innovation: CES Unveiled Milan
  • H3 CTA Unveils Speaker Lineup for HealthFuture Summit 2026, Spotlighting AI’s Role in Everyday Health
  • H3 CTA Praises FCC Selection of New Lead Administrator for U.S. Cyber Trust Mark
  • H3 CES on the Hill Brings the Future of Technology Directly to Policymakers During Washington’s Biggest Tech Policy Week
  • H2 Footer
  • H3 CES
  • H3 Media
  • H3 CTA
  • H3 Social Media
  • H3 Footer Legal Navigation

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

A
Form Accessibility
1 of 13 controls have issues
PASS
1 of 13 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q" id="q">
Info::
12 control(s) properly labeled
13 controls
12 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#field171413420-firsttextFirst Namefor/id
#field171413420-lasttextLast Namefor/id
#field171413422textTitle*none
#field171413424textCompany*none
#field171413428emailEmail*none
#field171413430textPhone Number*none
#field171413437selectCountry, Region or Territory*none
#field171413443textWebsite*none
#field171413445_1radionone
#field171413445_2radionone
#field171413503_1checkboxnone
#field179739388textTOPICnone
#qsearch(Search sessions, articles, speakers and more)placeholder only

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

<input type="search" name="q" id="q">

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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page Not Found - CES.tech ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 29 passed
PASS
97

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.

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
Read more div#cookiescript_toppart > div#cookiescript_leftpart > div#cookiescript_description > a#cookiescript_readmore

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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 are distinguishable without relying on color.
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback