Skip to content
https://gumgum.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
D
Form Accessibility
Action
13 of 27 controls have issues
FIX
13 of 27 controls have issues
Critical::
12 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="First-Name-2" id="First-Name-2">; <input type="text" name="Last-Name-3" id="Last-Name-3">; <input type="email" name="Email-2" id="Email-2">; <input type="text" name="Title-2" id="Title-2">; <input type="text" name="Company-Name-2" id="Company-Name-2">; <select name="Country-3" id="Country-3">; <select name="Persona-2" id="Persona-2">; <textarea name="Message-2" id="Message-2">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit"> (+2 more)
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="Email" id="Email">
Info::
14 control(s) properly labeled
27 controls
14 labeled
1 placeholder only
12 unlabeled
ControlTypeLabelMethod
#How-Did-You-Hear-About-Us-2textHow did you hear about us?for/id
#smallradionone
#medium-2radionone
#mediumradionone
#largeradionone
#Marketing-Opt-In-2checkboxnone
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextVendor Searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
#Emailemail(Your Email)placeholder only
inputsubmit(none)none
#Persona-2select(none)none
#footer-submitsubmit(none)none
#g-recaptcha-response-1textarea(none)none
#First-Name-2text(none)none
#Last-Name-3text(none)none
#Email-2email(none)none
#Title-2text(none)none
#Company-Name-2text(none)none
#Message-2textarea(none)none
#Country-3select(none)none
#g-recaptcha-responsetextarea(none)none

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

<input type="text" name="First-Name-2" id="First-Name-2">; <input type="text" name="Last-Name-3" id="Last-Name-3">; <input type="email" name="Email-2" id="Email-2">; <input type="text" name="Title-2" id="Title-2">; <input type="text" name="Company-Name-2" id="Company-Name-2">; <select name="Country-3" id="Country-3">; <select name="Persona-2" id="Persona-2">; <textarea name="Message-2" id="Message-2">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit"> (+2 more)

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="email" name="Email" id="Email">

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

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 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
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::
10 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 10 <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
23 landmarks
REVIEW
23 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
10 <nav> landmark(s) found
Warning::
2 of 10 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 MAIN ASIDE "Language selected: English" CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

B
Heading Hierarchy
98 headings
REVIEW
98 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H5 The GumGum Platform™
  • H5 Contextual
  • H5 Attention
  • H5 Creative
  • H5 The Mindset Graph™
  • H5 BY CUSTOMER TYPE
  • H5 Advertisers
  • H5 Publishers
  • H5 Platforms & Partners
  • H5 By Solution Type
  • H5 OLV Advertising
  • H5 Connected TV Advertising / In-Video
  • H5 GumGum's Exchange
  • H5 GUMGUM library
  • H5 GumGum Blog
  • H5 Research & Guides
  • H5 Case Studies
  • H5 Webinars
  • H5 Contextual Pioneers
  • H5 GUMGUM community
  • H5 Tech Blog
  • H5 Culture Blog
  • H5 The VOICE
  • H5 About Us
  • H5 Mission & Values
  • H5 Leadership
  • H5 Careers we're hiring
  • H5 Newsroom
  • H5 Engineering @ GumGum
  • H5 Culture @ GumGum
  • H5 Diversity, Equity, Inclusion and Belonging
  • H5 The GumGum Platform™
  • H5 Contextual
  • H5 Attention
  • H5 Creative
  • H5 The Mindset Graph™
  • H5 BY CUSTOMER TYPE
  • H5 Advertisers
  • H5 Publishers
  • H5 Platforms & Partners
  • H5 By Solution Type
  • H5 OLV Advertising
  • H5 Connected TV Advertising / In-Video
  • H5 GumGum's Exchange
  • H5 GUMGUM library
  • H5 GumGum Blog
  • H5 Research & Guides
  • H5 Case Studies
  • H5 Webinars
  • H5 Contextual Pioneers
  • H5 GUMGUM community
  • H5 Tech Blog
  • H5 Culture Blog
  • H5 The VOICE
  • H5 About Us
  • H5 Mission & Values
  • H5 Leadership
  • H5 Careers we're hiring
  • H5 Newsroom
  • H5 Engineering @ GumGum
  • H5 Culture @ GumGum
  • H5 Diversity, Equity, Inclusion and Belonging
  • H2 Advertising that Resonates, Built for Your Audience
  • H2 Where Reach Meets Relevance.
  • H2 Contextual
  • H2 Creative
  • H2 Attention
  • H2 Innovation, Scale, and Trusted Results
  • H2 LA Tourism Inspires Exploration with High-Impact Creative
  • H2 LA Tourism Inspires Exploration with High-Impact Creative
  • H2 Join Our Global Partners
  • H2 Find Your Place.Join Your Crew.
  • H2 Find Your Place with Us. Join Your Crew.
  • H2 Our Commitment to Sustainability & Inclusivity
  • H2 Lead the Industry with Us
  • H2 Stay in the Know with the Latest Adtech Resources
  • H2 Inside the UK Mindset Upfronts: Why Advertising Strategy Needs to Evolve
  • H2 Own the Break: Introducing Pause Ads Built for Viewer Mindset
  • H2 Five Signals From CES That Will Shape Advertising in 2026
  • H2 Ready to Enter the Mindset Era of Advertising?
  • H3 Solutions
  • H3 Insights
  • H3 About Us
  • H3 Terms & Policies
  • H3 Helpful Links
  • H3 Certifications
  • H2 Privacy Preference Center
  • H3 Your Privacy
  • H3 Strictly Necessary Cookies
  • H3 Performance Cookies
  • H3 Functional Cookies
  • H3 Targeting Cookies
  • H3 Your Privacy
  • H3 Strictly Necessary Cookies
  • H3 Performance Cookies
  • H3 Functional Cookies
  • H3 Targeting Cookies
  • H3 Back Button Back

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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
h2 Advertising that
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 , Built for Your Audience
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Where Reach Meets Relevance.
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contextual
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Creative
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Attention
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 LA Tourism Inspires Exploration with Hig…
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 LA Tourism Inspires Exploration with Hig…
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join Our Global Partners
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Find Your Place.
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join Your Crew.
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Find Your Place with Us. Join Your Crew.
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Lead the Industry with Us
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stay in the Know with the Latest Adtech …
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Inside the UK Mindset Upfronts: Why Adve…
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Own the Break: Introducing Pause Ads Bui…
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Five Signals From CES That Will Shape Ad…
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to Enter the
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 of Advertising?
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy Preference Center
1.39:1
#000000
on
#002A3A
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Advertising that1.39:13.0:1
#000000
#002A3A
Fail
h2 , Built for Your Aud…1.39:13.0:1
#000000
#002A3A
Fail
h2 Where Reach Meets Re…1.39:13.0:1
#000000
#002A3A
Fail
h2 Contextual1.39:13.0:1
#000000
#002A3A
Fail
h2 Creative1.39:13.0:1
#000000
#002A3A
Fail
h2 Attention1.39:13.0:1
#000000
#002A3A
Fail
h2 LA Tourism Inspires …1.39:13.0:1
#000000
#002A3A
Fail
h2 LA Tourism Inspires …1.39:13.0:1
#000000
#002A3A
Fail
h2 Join Our Global Part…1.39:13.0:1
#000000
#002A3A
Fail
h2 Find Your Place.1.39:13.0:1
#000000
#002A3A
Fail
h2 Join Your Crew.1.39:13.0:1
#000000
#002A3A
Fail
h2 Find Your Place with…1.39:13.0:1
#000000
#002A3A
Fail
h2 Lead the Industry wi…1.39:13.0:1
#000000
#002A3A
Fail
h2 Stay in the Know wit…1.39:13.0:1
#000000
#002A3A
Fail
h2 Inside the UK Mindse…1.39:13.0:1
#000000
#002A3A
Fail
h2 Own the Break: Intro…1.39:13.0:1
#000000
#002A3A
Fail
h2 Five Signals From CE…1.39:13.0:1
#000000
#002A3A
Fail
h2 Ready to Enter the1.39:13.0:1
#000000
#002A3A
Fail
h2 of Advertising?1.39:13.0:1
#000000
#002A3A
Fail
h2 Privacy Preference C…1.39:13.0:1
#000000
#002A3A
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 30 passed
REVIEW
86

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
EN div.wg-dropdown-1 > div#w-dropdown-toggle-3 > div.wg-selector-text-wrapper > div.lang-tag
Advertise with Us  div.bkgd-color > div.hero-section-btn-wrapper > div.btn-outline > a.btn
Watch Video  div.bkgd-color > div.hero-section-btn-wrapper > div.btn-outline > a.btn
Advertising that Resonates, Built for Your Audience div.section > div.w-layout-grid > div#w-node-b43d603d-671e-8bd5-412f-c88512bc5b05-7e1afea7 > h2.h2
Resonates div.w-layout-grid > div#w-node-b43d603d-671e-8bd5-412f-c88512bc5b05-7e1afea7 > h2.h2 > span.text-span-3
Learn More  div.w-layout-grid > div#w-node-_6bbc7146-2570-c698-f550-6e274f4d5a44-7e1afea7 > div.margin-bottom > a.btn
Top 15 div.section > div.w-layout-grid > div#w-node-_429f6cfc-d512-cf54-bf9b-5f5944686964-7e1afea7 > div.stat-large
15 div.w-layout-grid > div#w-node-_429f6cfc-d512-cf54-bf9b-5f5944686964-7e1afea7 > div.stat-large > span.counter
500 bn div.section > div.w-layout-grid > div#w-node-_00575f96-94c2-f1ae-4194-9c1ed741c291-7e1afea7 > div.stat-large
500 div.w-layout-grid > div#w-node-_00575f96-94c2-f1ae-4194-9c1ed741c291-7e1afea7 > div.stat-large > span.counter
40,000 div.w-layout-grid > div#w-node-_7791a707-98d3-a2b5-9ff1-d13b428829a7-7e1afea7 > div.stat-large > span.counter
1,000 div.w-layout-grid > div#w-node-ddec0a5e-a2f8-108d-d01a-cd0b622ebd82-7e1afea7 > div.stat-large > span.counter
3,000 div.w-layout-grid > div#w-node-_80f5c8ae-3c3b-985a-0f45-a0ffbdcaf737-7e1afea7 > div.stat-large > span.counter
Jack Lancaster div#w-node-_7cd1bf4f-6370-b1aa-9192-de77b0f30de6-7e1afea7 > div.bento-quote-wrapper > div.margin-bottom > p.paragraph-lg
Read The Case Study  main.page-wrapper > div.section > div#w-node-_7cd1bf4f-6370-b1aa-9192-de77b0f30de6-7e1afea7 > a.btn
View Open Roles  div.section > div.w-layout-grid > div#w-node-_5bafc25f-f592-b34e-072e-b1490a64b124-7e1afea7 > a.btn
Access All Resources main.page-wrapper > section.section > div.margin-top > a.btn
div._1440-wrapper > div.form_element > form#homepage-contact-us-form-v2 > input.btn-submit div._1440-wrapper > div.form_element > form#homepage-contact-us-form-v2 > input.btn-submit
Accept div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#homepage-contact-us-form-v2 > div.horiz-wrap_fields > div.field_wrapper > input#First-Name-2 form#homepage-contact-us-form-v2 > div.horiz-wrap_fields > div.field_wrapper > input#First-Name-2
form#homepage-contact-us-form-v2 > div.horiz-wrap_fields > div.field_wrapper > input#Last-Name-3 form#homepage-contact-us-form-v2 > div.horiz-wrap_fields > div.field_wrapper > input#Last-Name-3
div.form_element > form#homepage-contact-us-form-v2 > div.field_wrapper > input#Email-2 div.form_element > form#homepage-contact-us-form-v2 > div.field_wrapper > input#Email-2
form#homepage-contact-us-form-v2 > div.horiz-wrap_fields > div.field_wrapper > input#Title-2 form#homepage-contact-us-form-v2 > div.horiz-wrap_fields > div.field_wrapper > input#Title-2
form#homepage-contact-us-form-v2 > div.horiz-wrap_fields > div.field_wrapper > input#Company-Name-2 form#homepage-contact-us-form-v2 > div.horiz-wrap_fields > div.field_wrapper > input#Company-Name-2
div.form_element > form#homepage-contact-us-form-v2 > div.field_wrapper > textarea#Message-2 div.form_element > form#homepage-contact-us-form-v2 > div.field_wrapper > textarea#Message-2

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
United States United Kingdom Canada Germany Netherlands Japan Australia Mexico … div.form_element > form#homepage-contact-us-form-v2 > div.field_wrapper > select#Country-3
Brand Agency Publisher DSP or Trading Desk Reporter / Analyst Technology Partne… div.form_element > form#homepage-contact-us-form-v2 > div.field_wrapper > select#Persona-2

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.cms-announcement_wrapper > div.cms-announcement_list > div.cms-announcement_item > a.cms-announcement_close div.cms-announcement_wrapper > div.cms-announcement_list > div.cms-announcement_item > a.cms-announcement_close
div.w-layout-grid > div.footer-column > div.footer-social-block > a.social-link div.w-layout-grid > div.footer-column > div.footer-social-block > a.social-link
div.w-layout-grid > div.footer-column > div.footer-social-block > a.social-link div.w-layout-grid > div.footer-column > div.footer-social-block > a.social-link
div.w-layout-grid > div.footer-column > div.footer-social-block > a.social-link div.w-layout-grid > div.footer-column > div.footer-social-block > a.social-link
div.w-layout-grid > div.footer-column > div.footer-social-block > a.social-link div.w-layout-grid > div.footer-column > div.footer-social-block > a.social-link

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.

○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
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Links are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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 type="image">` elements have `[alt]` text
○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
○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.
○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+
Alt Text Quality
All 176 images OK
PASS
All 176 images OK
Info::
164 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
176 images 12 good alt text 164 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback