Skip to content
https://breaktheice.games

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
83
GRADE
B
FIX
5
REVIEW
1
PASS
18
INFO
0
Checks
24
18 PASS 1 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title Break The Ice ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+
Landmark Structure
17 landmarks
PASS
17 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN ASIDE "Analytics preference" CONTENTINFO footer
A+
Heading Hierarchy
10 headings
PASS
10 headings
Info::
Single H1 present
  • H1 Fun Icebreaker Questions
  • H2 Find the question that fits the room
  • H2 90 fun icebreaker questions for work, parties, and team meetings
  • H2 Fun Icebreaker Questions for Work
  • H3 How to choose a work icebreaker
  • H2 Fun Icebreaker Questions for Parties
  • H3 How to make party questions feel natural
  • H2 Fun Icebreaker Questions for Team Meetings
  • H3 How to run a team meeting icebreaker
  • H2 Turn a good conversation into a game of People Bingo
A+
Heading Text Quality
All 10 heading(s) have substantive, well-formed text
PASS
All 10 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
1 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
2 images 1 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#question-categoryselectForfor/id
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
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
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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+
Mobile-Readable Font Sizes
All 119 visible text node(s) render at >= 12 CSS pixels
PASS
All 119 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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
h1 Fun Icebreaker19.15:13.0:1
#000000
#F8F4ED
Pass
h2 Find the question th…19.66:13.0:1
#000000
#FBF7F0
Pass
h2 fun icebreaker quest…19.66:13.0:1
#000000
#FBF7F0
Pass
h2 Fun Icebreaker Quest…19.66:13.0:1
#000000
#FBF7F0
Pass
h2 Fun Icebreaker Quest…19.66:13.0:1
#000000
#FBF7F0
Pass
h2 Fun Icebreaker Quest…19.66:13.0:1
#000000
#FBF7F0
Pass
h2 Turn a good conversa…19.66:13.0:1
#000000
#FBF7F0
Pass
h3 How to choose a work…19.66:13.0:1
#000000
#FBF7F0
Pass
h3 How to make party qu…19.66:13.0:1
#000000
#FBF7F0
Pass
h3 How to run a team me…19.66:13.0:1
#000000
#FBF7F0
Pass
title Fun Icebreaker Quest…19.68:14.5:1
#000000
#FBF7F1
Pass
a Skip to content19.68:14.5:1
#000000
#FBF7F1
Pass
span Break The Ice19.66:14.5:1
#000000
#FBF7F0
Pass
button Questions19.66:14.5:1
#000000
#FBF7F0
Pass
a Browse questions19.66:14.5:1
#000000
#FBF7F0
Pass
a AI Questions Generat…19.66:14.5:1
#000000
#FBF7F0
Pass
a Games19.66:14.5:1
#000000
#FBF7F0
Pass
button Bingo19.66:14.5:1
#000000
#FBF7F0
Pass
a Bingo Card Generator19.66:14.5:1
#000000
#FBF7F0
Pass
a AI Bingo Generator19.66:14.5:1
#000000
#FBF7F0
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+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 25 passed
PASS
96

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
Generate Questions main#main > section.hero > div.hero__copy > a.primary-button
Copy question section#question-generator > div.picker > div.picker__question > button
QUESTIONS BY SETTING main#main > article.question-guide > header.guide-header > p.section-label
FOR WORK article.question-guide > section#work > header.question-section__header > span
01 div.question-list-wrap > ol#work-question-list > li > span
02 div.question-list-wrap > ol#work-question-list > li > span
03 div.question-list-wrap > ol#work-question-list > li > span
04 div.question-list-wrap > ol#work-question-list > li > span
05 div.question-list-wrap > ol#work-question-list > li > span
06 div.question-list-wrap > ol#work-question-list > li > span
How to run it article.question-guide > section#work > aside.host-tip > strong
FOR PARTIES article.question-guide > section#party > header.question-section__header > span
01 div.question-list-wrap > ol#party-question-list > li > span
02 div.question-list-wrap > ol#party-question-list > li > span
03 div.question-list-wrap > ol#party-question-list > li > span
04 div.question-list-wrap > ol#party-question-list > li > span
05 div.question-list-wrap > ol#party-question-list > li > span
06 div.question-list-wrap > ol#party-question-list > li > span
How to run it article.question-guide > section#party > aside.host-tip > strong
FOR TEAM MEETINGS article.question-guide > section#team > header.question-section__header > span
01 div.question-list-wrap > ol#team-question-list > li > span
02 div.question-list-wrap > ol#team-question-list > li > span
03 div.question-list-wrap > ol#team-question-list > li > span
04 div.question-list-wrap > ol#team-question-list > li > span
05 div.question-list-wrap > ol#team-question-list > li > span
06 div.question-list-wrap > ol#team-question-list > li > span
How to run it article.question-guide > section#team > aside.host-tip > strong
Make 30 cards free main#main > section.pro-cta > div.shell > a.primary-button

These are opportunities to improve the legibility of your content.

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
AI Questions Generator section.hero > div.hero__copy > nav.tool-strip > a
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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 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
○Form elements have associated labels
○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.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback