Skip to content
https://videolan.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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 (missing!)

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

F
Alt Text Quality
Action
7 of 32 images have issues
FIX
7 of 32 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
25 image(s) with good alt text
32 images 25 good alt text 7 missing
IssueCount
missing7 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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::
1 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 1 <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
Form Accessibility
Action
5 of 5 controls have issues
REVIEW
5 of 5 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="amount">; <input type="text" name="amount">; <input type="text" name="amount">; <input type="text" name="amount">; <select>
5 controls
0 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
amounttext(none)none
amounttext(none)none
amounttext(none)none
amounttext(none)none
selectselect(none)none

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

<input type="text" name="amount">; <input type="text" name="amount">; <input type="text" name="amount">; <input type="text" name="amount">; <select>

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 not found - VideoLAN ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 80/100 — 7 failing, 24 passed
REVIEW
80

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.

ARIA

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
VLC for Windows Store div.v-align > div#header-carousel > div.slick-list > div.slick-track

These are opportunities to improve the usage of ARIA in your application which 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
VideoLAN, a project and a non-profit organization. body.new-design > div#bodyInner > div.header > div#nonprofitOrganizationDiv2
Version 3.7.0  •  Android div.row > div.v-align > div.inner > div#downloadDetails
FOR EVERYONE div.container > div.row > div.col-md-5 > div.audienceCallout
FOR PROFESSIONALS div.container > div.row > div.col-sm-6 > div.audienceCallout
FOR DEVELOPERS div.container > div.row > div.col-sm-6 > div.audienceCallout
DONATE div.container > div.row > div.col-md-4 > div.audienceCallout
CONTRIBUTE div.container > div.row > div.col-md-4 > div.audienceCallout
SPREAD THE WORD div.container > div.row > div.col-md-4 > div.audienceCallout
2026-02-25 div.col-md-6 > div > div.item > div.date
2026-01-31 div.col-md-6 > div > div.item > div.date
2026-01-08 div.col-md-6 > div > div.item > div.date
2026-01-08 div.col-md-6 > div > div.item > div.date
2025-12-01 div.col-md-6 > div > div.item > div.date
Legal div.row > div.col-md-12 > p > a
Report Trademark Abuse div.col-md-12 > p > span > a
VideoLAN non-profit organization. div.col-md-12 > p > span > a
Made By Argon div.col-md-12 > p > span > a
CC BY-SA 3.0+ div.col-md-12 > p > span > a
Roman Khramov div.col-md-12 > p > span > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
non-profit organization. div#bodyInner > div.header > div#nonprofitOrganizationDiv2 > a.noUnderline
[...] div.col-md-6 > div > p > a
[...] div.col-md-6 > div > p > a
[...] div.col-md-6 > div > p > a

These are opportunities to improve the legibility of your content.

Names and labels

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
Afrikaans | Afrikaans Amharic | አማርኛ Aragonese | Aragonese Arabic | العربية Ass… div.row > div#translation > div.footerHeading > select

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.v-align > div.inner > div.btn-group > a.btn div.v-align > div.inner > div.btn-group > a.btn
div.v-align > div.inner > div.platform-icons > a.icon div.v-align > div.inner > div.platform-icons > a.icon
div.v-align > div.inner > div.platform-icons > a.icon div.v-align > div.inner > div.platform-icons > a.icon
div.v-align > div.inner > div.platform-icons > a.icon div.v-align > div.inner > div.platform-icons > a.icon
div.v-align > div.inner > div.platform-icons > a.icon div.v-align > div.inner > div.platform-icons > a.icon
div.v-align > div.inner > div.platform-icons > a.icon div.v-align > div.inner > div.platform-icons > a.icon
div.overflow-hidden > h1 > span.ltrFloatRight > a.social div.overflow-hidden > h1 > span.ltrFloatRight > a.social
div.overflow-hidden > h1 > span.ltrFloatRight > a.social div.overflow-hidden > h1 > span.ltrFloatRight > a.social
div.overflow-hidden > h1 > span.ltrFloatRight > a.social div.overflow-hidden > h1 > span.ltrFloatRight > a.social
div.row > div.col-sm-12 > div.social-box > a.social div.row > div.col-sm-12 > div.social-box > a.social
div.row > div.col-sm-12 > div.social-box > a.social div.row > div.col-sm-12 > div.social-box > a.social
div.row > div.col-sm-12 > div.social-box > a.social div.row > div.col-sm-12 > div.social-box > a.social

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.

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
VLC for Windows div.col-xs-6 > ul > li > a
VLC for Mac OS X div.col-xs-6 > ul > li > a
VLC for Ubuntu div.col-xs-6 > ul > li > a
VLC for Android div.col-xs-6 > ul > li > a
VLC for iOS div.col-xs-6 > ul > li > a
Skins div.col-xs-6 > ul > li > a
Extensions div.col-xs-6 > ul > li > a
Features div.col-xs-6 > ul > li > a
Screenshots div.col-xs-6 > ul > li > a
VLC Skin Editor div.col-xs-6 > ul > li > a
DVBlast div.col-xs-6 > ul > li > a
x264 div.col-xs-6 > ul > li > a
x262 div.col-xs-6 > ul > li > a
x265 div.col-xs-6 > ul > li > a
multicat div.col-xs-6 > ul > li > a
dav1d div.col-xs-6 > ul > li > a
VLMa div.col-xs-6 > ul > li > a
libVLC div.col-xs-6 > ul > li > a
libdvdcss div.col-xs-6 > ul > li > a
libdvdnav div.col-xs-6 > ul > li > a
libdvdread div.col-xs-6 > ul > li > a
libbluray div.col-xs-6 > ul > li > a
libdvbpsi div.col-xs-6 > ul > li > a
libaacs div.col-xs-6 > ul > li > a
libdvbcsa div.col-xs-6 > ul > li > a
biTStream div.col-xs-6 > ul > li > a
vlc-unity div.col-xs-6 > ul > li > a
Wiki div.col-xs-6 > ul > li > a
Forums div.col-xs-6 > ul > li > a
Mailing-Lists div.col-xs-6 > ul > li > a
Donate money div.col-xs-6 > ul > li > a
Donate time div.col-xs-6 > ul > li > a
Get Goodies div.col-xs-6 > ul > li > a
Team div.col-xs-6 > ul > li > a
Legal div.col-xs-6 > ul > li > a
Contact us div.col-xs-6 > ul > li > a
Partners div.col-xs-6 > ul > li > a
Mirrors div.col-xs-6 > ul > li > a
Press center div.col-xs-6 > ul > li > a
Events div.col-xs-6 > ul > li > a
Security center div.col-xs-6 > ul > li > a
Get Involved div.col-xs-6 > ul > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●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 `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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
○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.
○`<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.
○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
Heading Hierarchy
7 headings
PASS
7 headings
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H6 Partners
  • H1 VLC media player
  • H1 Other projects from VideoLAN duplicate H1
  • H1 Help us out! duplicate H1
  • H1 News & Updates duplicate H1
  • H1 Development Blogs duplicate H1
  • H1 Social media duplicate H1

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+
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 VLC media player21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Other projects from …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Help us out!21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Social media21.00:13.0:1
#000000
#FFFFFF
Pass
title VLC: Official site -…20.29:14.5:1
#000000
#FBFBFB
Pass
span Toggle navigation20.65:14.5:1
#000000
#FDFDFD
Pass
a VideoLAN21.00:14.5:1
#000000
#FFFFFF
Pass
a Team & Organization21.00:14.5:1
#000000
#FFFFFF
Pass
a Consulting Services …21.00:14.5:1
#000000
#FFFFFF
Pass
a Events21.00:14.5:1
#000000
#FFFFFF
Pass
a Legal21.00:14.5:1
#000000
#FFFFFF
Pass
a Press center21.00:14.5:1
#000000
#FFFFFF
Pass
a Contact us21.00:14.5:1
#000000
#FFFFFF
Pass
a VLC21.00:14.5:1
#000000
#FFFFFF
Pass
a Download21.00:14.5:1
#000000
#FFFFFF
Pass
a Features21.00:14.5:1
#000000
#FFFFFF
Pass
a Customize21.00:14.5:1
#000000
#FFFFFF
Pass
a Get Goodies21.00:14.5:1
#000000
#FFFFFF
Pass
a Projects21.00:14.5:1
#000000
#FFFFFF
Pass
a DVBlast21.00:14.5:1
#000000
#FFFFFF
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