Skip to content
https://brightcove.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
39
GRADE
F
FIX
9
REVIEW
4
PASS
0
INFO
0
Checks
13
4 REVIEW 9 FIX
D
Landmark Structure
Action
9 landmarks
FIX
9 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::
2 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
Heading Hierarchy
Action
52 headings, 3 skip(s)
FIX
52 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H3 → H5 (missing H4)
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.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Product
  • H3 Solutions
  • H3 Resources
  • H3 Company
  • H5 Hosting and Library skipped
  • H5 Features
  • H5 Platform
  • H5 Packs
  • H5 Brightcove for
  • H5 Industries
  • H5 General
  • H5 Learning
  • H5 Company
  • H5 Updates
  • H5 Get Started
  • H1 Drive engagement through video
  • H2 End-to-end video delivery & monetization platform
  • H3 Host and stream
  • H3 Manage your video library
  • H3 Leverage analytics
  • H1 Monetize your content duplicate H1
  • H2 We think you'll love it, but don't just take our word for it.
  • H3 Power up your business with video tools
  • H4 Interactivity
  • H4 Gallery
  • H4 OTT
  • H4 Live Streaming
  • H4 AI SuiteNew
  • H4 Analytics
  • H4 Player
  • H4 Developer APIs
  • H2 Our solutions
  • H4 Media StudioTM skipped
  • H4 Communications StudioTM
  • H4 Marketing StudioTM
  • H4 Beacon StudioTM
  • H4 Zencoder StudioTM
  • H2 Let AI handle the heavy lifting
  • H2 Scale without switching tools
  • H2 Stream confidently with enterprise-grade protection.
  • H2 Ready, set, engage
  • H5 Core skipped
  • H5 Features
  • H5 Platform
  • H5 Solutions
  • H5 Brightcove for
  • H5 Industries
  • H5 Resources
  • H5 Learning
  • H5 Get Started
  • H5 Updates
  • H5 Company

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

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

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 Brightcove | Leading video hosting & streaming platform ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
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
Alt Text Quality
Action
4 of 67 images have issues
REVIEW
4 of 67 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
58 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
67 images 5 good alt text 58 decorative 4 missing
IssueCount
missing4 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

C
Form Accessibility
Action
18 of 54 controls have issues
REVIEW
18 of 54 controls have issues
Critical::
18 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="vjs_select_8937">; <select id="vjs_select_8956">; <select id="vjs_select_8971">; <select id="vjs_select_7224">; <select id="vjs_select_7243">; <select id="vjs_select_7258">; <select id="vjs_select_5548">; <select id="vjs_select_5567">; <select id="vjs_select_5582">; <select id="vjs_select_3902"> (+8 more)
Info::
36 control(s) properly labeled
54 controls
36 labeled
0 placeholder only
18 unlabeled
ControlTypeLabelMethod
#vjs_select_8887selectColorfor/id
#vjs_select_8892selectOpacityfor/id
#vjs_select_8902selectColorfor/id
#vjs_select_8907selectOpacityfor/id
#vjs_select_8917selectColorfor/id
#vjs_select_8922selectOpacityfor/id
#vjs_select_7174selectColorfor/id
#vjs_select_7179selectOpacityfor/id
#vjs_select_7189selectColorfor/id
#vjs_select_7194selectOpacityfor/id
#vjs_select_7204selectColorfor/id
#vjs_select_7209selectOpacityfor/id
#vjs_select_5498selectColorfor/id
#vjs_select_5503selectOpacityfor/id
#vjs_select_5513selectColorfor/id
#vjs_select_5518selectOpacityfor/id
#vjs_select_5528selectColorfor/id
#vjs_select_5533selectOpacityfor/id
#vjs_select_3852selectColorfor/id
#vjs_select_3857selectOpacityfor/id
#vjs_select_3867selectColorfor/id
#vjs_select_3872selectOpacityfor/id
#vjs_select_3882selectColorfor/id
#vjs_select_3887selectOpacityfor/id
#vjs_select_1596selectColorfor/id
#vjs_select_1601selectOpacityfor/id
#vjs_select_1611selectColorfor/id
#vjs_select_1616selectOpacityfor/id
#vjs_select_1626selectColorfor/id
#vjs_select_1631selectOpacityfor/id
#vjs_select_588selectColorfor/id
#vjs_select_593selectOpacityfor/id
#vjs_select_603selectColorfor/id
#vjs_select_608selectOpacityfor/id
#vjs_select_618selectColorfor/id
#vjs_select_623selectOpacityfor/id
#vjs_select_5548select(none)none
#vjs_select_5567select(none)none
#vjs_select_5582select(none)none
#vjs_select_8937select(none)none
#vjs_select_8956select(none)none
#vjs_select_8971select(none)none
#vjs_select_1646select(none)none
#vjs_select_1665select(none)none
#vjs_select_1680select(none)none
#vjs_select_7224select(none)none
#vjs_select_7243select(none)none
#vjs_select_7258select(none)none
#vjs_select_3902select(none)none
#vjs_select_3921select(none)none
#vjs_select_3936select(none)none
#vjs_select_638select(none)none
#vjs_select_657select(none)none
#vjs_select_672select(none)none

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

<select id="vjs_select_8937">; <select id="vjs_select_8956">; <select id="vjs_select_8971">; <select id="vjs_select_7224">; <select id="vjs_select_7243">; <select id="vjs_select_7258">; <select id="vjs_select_5548">; <select id="vjs_select_5567">; <select id="vjs_select_5582">; <select id="vjs_select_3902"> (+8 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

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
h1 Drive engagement through video
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Monetize your content
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
32px · bottom of viewport
h2 End-to-end video delivery & monetization…
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We think you'll love it, but don't just …
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our solutions
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Let AI handle the heavy lifting
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Scale without switching tools
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stream confidently with enterprise-grade…
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready, set, engage
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Product
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
19px · above the fold
h3 Solutions
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Resources
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Company
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Host and stream
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Manage your video library
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Leverage analytics
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Power up your business with video tools
1.11:1
#000000
on
#11110F
needs 3.0:1 (large text)
19px · bottom of viewport
title Brightcove | Leading Video Hosting & Str…
1.11:1
#000000
on
#11110F
needs 4.5:1 (normal text)
16px · top of page (header area)
p © Brightcove
1.11:1
#000000
on
#11110F
needs 4.5:1 (normal text)
16px · top of page (header area)
a +1 888 882 1880
1.11:1
#000000
on
#11110F
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Drive engagement thr…1.11:13.0:1
#000000
#11110F
Fail
h1 Monetize your conten…1.11:13.0:1
#000000
#11110F
Fail
h2 End-to-end video del…1.11:13.0:1
#000000
#11110F
Fail
h2 We think you'll love…1.11:13.0:1
#000000
#11110F
Fail
h2 Our solutions1.11:13.0:1
#000000
#11110F
Fail
h2 Let AI handle the he…1.11:13.0:1
#000000
#11110F
Fail
h2 Scale without switch…1.11:13.0:1
#000000
#11110F
Fail
h2 Stream confidently w…1.11:13.0:1
#000000
#11110F
Fail
h2 Ready, set, engage1.11:13.0:1
#000000
#11110F
Fail
h3 Product1.11:13.0:1
#000000
#11110F
Fail
h3 Solutions1.11:13.0:1
#000000
#11110F
Fail
h3 Resources1.11:13.0:1
#000000
#11110F
Fail
h3 Company1.11:13.0:1
#000000
#11110F
Fail
h3 Host and stream1.11:13.0:1
#000000
#11110F
Fail
h3 Manage your video l…1.11:13.0:1
#000000
#11110F
Fail
h3 Leverage analytics1.11:13.0:1
#000000
#11110F
Fail
h3 Power up your busine…1.11:13.0:1
#000000
#11110F
Fail
title Brightcove | Leading…1.11:14.5:1
#000000
#11110F
Fail
p © Brightcove1.11:14.5:1
#000000
#11110F
Fail
a +1 888 882 18801.11:14.5:1
#000000
#11110F
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.

C
Lighthouse Accessibility Audits
Action
Score 76/100 — 7 failing, 20 passed
REVIEW
76

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.relative > div.background-color-transition > div > button.flex div.relative > div.background-color-transition > div > button.flex

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.__variable_f1ce36 > section.container--medium > div.basis-1/4 > img.mb-6 body.__variable_f1ce36 > section.container--medium > div.basis-1/4 > img.mb-6
body.__variable_f1ce36 > section.container--medium > div.basis-1/4 > img.mb-6 body.__variable_f1ce36 > section.container--medium > div.basis-1/4 > img.mb-6
body.__variable_f1ce36 > section.container--medium > div.basis-1/4 > img.mb-6 body.__variable_f1ce36 > section.container--medium > div.basis-1/4 > img.mb-6
body.__variable_f1ce36 > section.container--medium > div.basis-1/4 > img.mb-6 body.__variable_f1ce36 > section.container--medium > div.basis-1/4 > img.mb-6

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
nav.fixed > div.relative > div.background-color-transition > a.z-10 nav.fixed > div.relative > div.background-color-transition > a.z-10
div.container > div.mb-4 > div.flex > a div.container > div.mb-4 > div.flex > a
div.container > div.mb-4 > div.flex > a div.container > div.mb-4 > div.flex > a
div.container > div.mb-4 > div.flex > a div.container > div.mb-4 > div.flex > a
div.container > div.mb-4 > div.flex > a div.container > div.mb-4 > div.flex > a

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.

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
Power up your business with video tools body.__variable_f1ce36 > section > section.container--medium > h3.font-size-5xl
Media StudioTM a.group > div.rounded-24 > div.rounded-24 > h4.font-size-5xl
Core div.container > div.flex > div.border-neutrals-grey-200 > h5.font-size-lg

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.max-w-full > div.mt-14 > div.pl-8 > button.cursor-pointer
Go to slide 2 div.max-w-full > div.mt-14 > div.pl-8 > button.cursor-pointer
Go to slide 3 div.max-w-full > div.mt-14 > div.pl-8 > button.cursor-pointer

These items highlight common accessibility best practices.

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
Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`[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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●`[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 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 a valid value for its `[lang]` attribute
○`<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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback