Skip to content
https://ffmpeg.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 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 404 Not Found ✓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::
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
Landmark Structure
Action
2 landmarks
REVIEW
2 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 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 header 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

B
Heading Hierarchy
78 headings, 1 skip(s)
REVIEW
78 headings, 1 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: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 FFmpeg
  • H2 A complete, cross-platform solution to record, convert and stream audio and video.
  • H3 Converting video and audio has never been so easy.
  • H1 News duplicate H1
  • H3 March 16th, 2026, FFmpeg 8.1 "Hoare" skipped
  • H3 August 22nd, 2025, FFmpeg 8.0 "Huffman"
  • H3 September 30th, 2024, FFmpeg 7.1 "Péter"
  • H3 September 11th, 2024, Coverity
  • H3 June 2nd, 2024, native xHE-AAC decoder
  • H3 May 13th, 2024, Sovereign Tech Fund
  • H3 April 5th, 2024, FFmpeg 7.0 "Dijkstra"
  • H3 January 3rd, 2024, native VVC decoder
  • H3 December 18th, 2023, IAMF support
  • H3 December 12th, 2023, multi-threaded ffmpeg CLI tool
  • H3 November 10th, 2023, FFmpeg 6.1 "Heaviside"
  • H3 May 31st, 2023, Vulkan decoding
  • H3 February 28th, 2023, FFmpeg 6.0 "Von Neumann"
  • H3 July 22nd, 2022, FFmpeg 5.1 "Riemann"
  • H3 January 17th, 2022, FFmpeg 5.0 "Lorentz"
  • H3 June 19th, 2021, IRC
  • H3 April 8th, 2021, FFmpeg 4.4 "Rao"
  • H3 June 15th, 2020, FFmpeg 4.3 "4:3"
  • H3 October 5th, 2019, Bright Lights
  • H3 August 5th, 2019, FFmpeg 4.2 "Ada"
  • H3 November 6th, 2018, FFmpeg 4.1 "al-Khwarizmi"
  • H3 April 20th, 2018, FFmpeg 4.0 "Wu"
  • H3 October 15th, 2017, FFmpeg 3.4 "Cantor"
  • H3 April 13th, 2017, FFmpeg 3.3 "Hilbert"
  • H3 October 30th, 2016, Results: Summer Of Code 2016.
  • H4 FFv1 (Mentor: Michael Niedermayer)
  • H4 Self test coverage (Mentor: Michael Niedermayer)
  • H4 MPEG-4 ALS encoder implementation (Mentor: Thilo Borgmann)
  • H4 Tee muxer improvements (Mentor: Marton Balint)
  • H4 TrueHD encoder (Mentor: Rostislav Pehlivanov)
  • H4 Motion interpolation filter (Mentor: Paul B Mahol)
  • H3 September 24th, 2016, SDL1 support dropped.
  • H3 August 9th, 2016, FFmpeg 3.1.2 "Laplace"
  • H3 July 10th, 2016, ffserver program being dropped
  • H3 July 1st, 2016, FFmpeg 3.1.1 "Laplace"
  • H3 June 27th, 2016, FFmpeg 3.1 "Laplace"
  • H3 March 16th, 2016, Google Summer of Code
  • H3 February 15th, 2016, FFmpeg 3.0 "Einstein"
  • H3 January 30, 2016, Removing support for two external AAC encoders
  • H3 January 16, 2016, FFmpeg 2.8.5, 2.7.5, 2.6.7, 2.5.10
  • H3 December 5th, 2015, The native FFmpeg AAC encoder is now stable!
  • H3 October 13th, 2015, Telepoint & MediaHub are now supporting our project
  • H3 September 29th, 2015, GSoC 2015 results
  • H4 Basic servers for network protocols, mentee: Stephan Holljes, mentor: Nicolas George
  • H4 Browsing content on the server, mentee: Mariusz Szczepańczyk, mentor: Lukasz Marek
  • H4 Directshow digital video capture, mentee: Mate Sebok, mentor: Roger Pack
  • H4 Implementing full support for 3GPP Timed Text Subtitles, mentee: Niklesh Lalwani, mentor: Philip Langdale
  • H4 libswscale refactoring, mentee: Pedro Arthur, mentors: Michael Niedermayer, Ramiro Polla
  • H4 AAC Encoder Improvements, mentee: Rostislav Pehlivanov, mentor: Claudio Freire
  • H4 Animated Portable Network Graphics (APNG), mentee: Donny Yang, mentor: Paul B Mahol
  • H3 September 9th, 2015, FFmpeg 2.8
  • H3 August 1st, 2015, A message from the FFmpeg project
  • H3 July 4th, 2015, FFmpeg needs a new host
  • H3 March 16, 2015, FFmpeg 2.6.1
  • H3 March 4, 2015, Google Summer of Code
  • H3 March 1, 2015, Chemnitzer Linux-Tage
  • H3 December 5, 2014, FFmpeg 2.5
  • H3 October 10, 2014, FFmpeg is in Debian unstable again
  • H3 October 8, 2014, FFmpeg secured a place in OPW!
  • H3 September 15, 2014, FFmpeg 2.4
  • H3 August 20, 2014, FFmpeg 2.3.3, 2.2.7, 1.2.8
  • H3 July 29, 2014, Help us out securing our spot in OPW
  • H3 July 20, 2014, New website
  • H3 July 17, 2014, FFmpeg 2.3
  • H3 July 3, 2014, FFmpeg and the Outreach Program For Women
  • H3 June 29, 2014, FFmpeg 2.2.4, 2.1.5, 2.0.5, 1.2.7, 1.1.12, 0.10.14
  • H3 May 1, 2014, LinuxTag
  • H3 April 18, 2014, OpenSSL Heartbeat bug
  • H3 April 11, 2014, FFmpeg 2.2.1
  • H3 March 24, 2014, FFmpeg 2.2
  • H3 February 3, 2014, Chemnitzer Linux-Tage
  • H3 February 9, 2014, trac.ffmpeg.org / trac.mplayerhq.hu Security Breach
  • H3 November 12, 2013, FFmpeg RFP in Debian
  • H3 October 28, 2013, FFmpeg 2.1

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

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 FFmpeg
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
32px · bottom of viewport
h1 News
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
32px · bottom of viewport
h2 A complete, cross-platform solution to r…
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Converting
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 and
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 has never been so easy.
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 March 16th, 2026, FFmpeg 8.1
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 August 22nd, 2025, FFmpeg 8.0
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 September 30th, 2024, FFmpeg 7.1
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 September 11th, 2024, Coverity
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 June 2nd, 2024, native xHE-AAC decoder
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 May 13th, 2024, Sovereign Tech Fund
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 April 5th, 2024, FFmpeg 7.0 "Dijkstra"
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 January 3rd, 2024, native VVC decoder
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 December 18th, 2023, IAMF support
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 December 12th, 2023, multi-threaded
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CLI tool
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 November 10th, 2023, FFmpeg 6.1 "Heavisi…
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 May 31st, 2023, Vulkan decoding
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
h3 February 28th, 2023, FFmpeg 6.0 "Von Neu…
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 FFmpeg1.61:13.0:1
#000000
#313131
Fail
h1 News1.61:13.0:1
#000000
#313131
Fail
h2 A complete, cross-pl…1.61:13.0:1
#000000
#313131
Fail
h3 Converting1.61:13.0:1
#000000
#313131
Fail
h3 and1.61:13.0:1
#000000
#313131
Fail
h3 has never been so ea…1.61:13.0:1
#000000
#313131
Fail
h3 March 16th, 2026, FF…1.61:13.0:1
#000000
#313131
Fail
h3 August 22nd, 2025, F…1.61:13.0:1
#000000
#313131
Fail
h3 September 30th, 2024…1.61:13.0:1
#000000
#313131
Fail
h3 September 11th, 2024…1.61:13.0:1
#000000
#313131
Fail
h3 June 2nd, 2024, nati…1.61:13.0:1
#000000
#313131
Fail
h3 May 13th, 2024, Sove…1.61:13.0:1
#000000
#313131
Fail
h3 April 5th, 2024, FFm…1.61:13.0:1
#000000
#313131
Fail
h3 January 3rd, 2024, n…1.61:13.0:1
#000000
#313131
Fail
h3 December 18th, 2023,…1.61:13.0:1
#000000
#313131
Fail
h3 December 12th, 2023,…1.61:13.0:1
#000000
#313131
Fail
h3 CLI tool1.61:13.0:1
#000000
#313131
Fail
h3 November 10th, 2023,…1.61:13.0:1
#000000
#313131
Fail
h3 May 31st, 2023, Vulk…1.61:13.0:1
#000000
#313131
Fail
h3 February 28th, 2023,…1.61:13.0:1
#000000
#313131
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 73/100 — 5 failing, 11 passed
REVIEW
73

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
Download div.row > div.col-md-6 > div.btn-download-wrapper > a.btn
Discover more div#index > div.well > div.text-right > a.btn
Past news div.page-content > div#index > div.text-right > a.btn

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
FFmpeg 8.1 "Hoare" div.page-content > div#index > p > a
Khronos blog div.page-content > div#index > p > a
FFmpeg 8.0 "Huffman" div.page-content > div#index > p > a
Vulkan decoding div.page-content > div#index > p > a
code.ffmpeg.org div.page-content > div#index > p > a
FFmpeg 7.1 "Péter" div.page-content > div#index > p > a
changelog div.page-content > div#index > p > a
Coverity (a static analyzer) div.page-content > div#index > p > a
Sovereign Tech Fund div.page-content > div#index > p > a
Sovereign Tech Fund div.page-content > div#index > p > a
FFmpeg 7.0 "Dijkstra" div.page-content > div#index > p > a
native VVC decoder div.page-content > div#index > p > a
IAMF support div.page-content > div#index > p > a
multi-threaded ffmpeg CLI tool div.page-content > div#index > p > a
Changelog div.page-content > div#index > p > a
APIchanges div.page-content > div#index > p > a
IAMF div.page-content > div#index > p > a
FFmpeg 6.1 "Heaviside" div.page-content > div#index > p > a
documentation page div.page-content > div#index > p > a
repository div.page-content > div#index > p > a
FFmpeg 6.0 "Von Neumann" div.page-content > div#index > p > a
FFmpeg 5.1 "Riemann" div.page-content > div#index > p > a
FFmpeg 5.0 "Lorentz" div.page-content > div#index > p > a
contact#IRCChannels div.page-content > div#index > p > a
FFmpeg 4.4 "Rao" div.page-content > div#index > p > a
FFmpeg 4.3 "4:3" div.page-content > div#index > p > a
Incredibles 2 Screen Slaver div.page-content > div#index > p > a
trac div.page-content > div#index > p > a
See for yourself div.page-content > div#index > p > a
please let me know div.page-content > div#index > p > a
since 2013 div.page-content > div#index > p > a
FFmpeg 4.2 "Ada" div.page-content > div#index > p > a
FFmpeg 4.1 "al-Khwarizmi" div.page-content > div#index > p > a
FFmpeg 4.0 "Wu" div.page-content > div#index > p > a
FFmpeg 3.4 "Cantor" div.page-content > div#index > p > a
FFmpeg 3.3 "Hilbert" div.page-content > div#index > p > a
FFmpeg 3.1.2 div.page-content > div#index > p > a
FFmpeg 3.1.1 div.page-content > div#index > p > a
FFmpeg 3.1 "Laplace" div.page-content > div#index > p > a
Google Summer of Code div.page-content > div#index > p > a
project ideas page div.page-content > div#index > p > a
FFmpeg 3.0 "Einstein" div.page-content > div#index > p > a
Changelog div#index > ul > li > a
stable div.page-content > div#index > p > a
Kamedo2 div.page-content > div#index > p > a
bug tracker div.page-content > div#index > p > a
Telepoint ul > li > p > a
Google Summer of Code div.page-content > div#index > p > a
Google div.page-content > div#index > p > a
VideoLAN Developer Days div.page-content > div#index > p > a
FFmpeg div.page-content > div#index > p > a
MPlayer div.page-content > div#index > p > a
rtmpdump div.page-content > div#index > p > a
ffmpeg-devel div.page-content > div#index > p > a
trac div.page-content > div#index > p > a
samples repo div.page-content > div#index > p > a
Google Summer of Code div.page-content > div#index > p > a
project ideas page div.page-content > div#index > p > a
here div.page-content > div#index > p > a
here div.page-content > div#index > p > a
FFmpeg packages in Debian unstable div.page-content > div#index > p > a
Read the argumentation over at Debian. div.page-content > div#index > p > a
OPW wiki page div.page-content > div#index > p > a
Click&Pledge div.page-content > div#index > p > a
e-mail div.page-content > div#index > p > a
db0 div.page-content > div#index > p > a
OPW div.page-content > div#index > p > a
email address div.page-content > div#index > p > a
security issue in the LZO implementation div.page-content > div#index > p > a
here div.page-content > div#index > p > a
archive div.page-content > div#index > p > a
"OpenSSL heartbleed" div.page-content > div#index > p > a
here div.page-content > div#index > p > a
Rogério Brito div.page-content > div#index > p > a
ticket #729203 div.page-content > div#index > p > a

These are opportunities to improve the legibility of your content.

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
March 16th, 2026, FFmpeg 8.1 "Hoare" div#page-content-wrapper > div.page-content > div#index > h3#pr8.1

These are opportunities to improve keyboard navigation in your application.

Names and labels

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#page-content-wrapper > header.content-header > h1 > a#menu-toggle div#page-content-wrapper > header.content-header > h1 > a#menu-toggle
div#index > h1#news > span.pull-right > a div#index > h1#news > span.pull-right > a
div#index > h1#news > span.pull-right > a div#index > h1#news > span.pull-right > a
div#index > h1#news > span.pull-right > a div#index > h1#news > span.pull-right > 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.

Best practices

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-hidden="true"]` is not present on the document `<body>`
●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.
●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
●Touch targets have sufficient size and spacing.
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○Select elements have associated label elements.
○Skip links are focusable.
○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
○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 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback