Lighthouse Report

Performance

First Contentful Paint

2.6 s

First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Speed Index

4.7 s

Speed Index shows how quickly the contents of a page are visibly populated. Learn more.

Largest Contentful Paint

4.2 s

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More

Time to Interactive

8.3 s

Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Total Blocking Time

10 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.

Cumulative Layout Shift

0.338

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.

Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.

Eliminate render-blocking resources

1.32 s

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL	Transfer Size	Potential Savings
/assets/light-0eace2597ca3.css (github.githubassets.com)	4.5 KiB	780 ms
/assets/dark-a167e256da9c.css (github.githubassets.com)	4.5 KiB	150 ms
/assets/primer-08e422afeb43.css (github.githubassets.com)	49.9 KiB	150 ms
/assets/global-fcad22128422.css (github.githubassets.com)	43.9 KiB	300 ms
/assets/github-2f3974e4587d.css (github.githubassets.com)	24.3 KiB	150 ms

Remove unused JavaScript

0.75 s

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

URL	Transfer Size	Potential Savings
/assets/app_asset….js (github.githubassets.com)	103.8 KiB	76 KiB
/assets/behaviors-1e4a69ad752e.js (github.githubassets.com)	64.7 KiB	50.2 KiB
/assets/react-lib-1fbfc5be2c18.js (github.githubassets.com)	59.4 KiB	29.2 KiB

Remove unused CSS

0.6 s

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL	Transfer Size	Potential Savings
/assets/primer-08e422afeb43.css (github.githubassets.com)	49.9 KiB	45.8 KiB
/assets/global-fcad22128422.css (github.githubassets.com)	43.9 KiB	41.8 KiB
/assets/github-2f3974e4587d.css (github.githubassets.com)	24.3 KiB	24.3 KiB

Avoid an excessive DOM size 1,259 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

Statistic	Element	Value
Total DOM Elements		NaN
Maximum DOM Depth	<path d="m.427 1.927 1.215 1.215a8.002 8.002 0 1 1-1.6 5.685.75.75 0 1 1 1.493-.154…">	36
Maximum Child Elements	<div data-view-component="true" class="Layout-main">	26

Serve static assets with an efficient cache policy 15 resources found

A long cache lifetime can speed up repeat visits to your page. Learn more.

URL	Cache TTL	Transfer Size
/u/1310872?s=64&v=4 (avatars.githubusercontent.com)	5 m	10 KiB
/u/1143280?s=64&v=4 (avatars.githubusercontent.com)	5 m	8 KiB
/u/506932?s=64&v=4 (avatars.githubusercontent.com)	5 m	5 KiB
/u/1310872?v=4&size=40 (avatars.githubusercontent.com)	5 m	4 KiB
/u/802788?s=64&v=4 (avatars.githubusercontent.com)	5 m	3 KiB
/u/2997061?s=64&v=4 (avatars.githubusercontent.com)	5 m	2 KiB
/u/1146924?s=64&v=4 (avatars.githubusercontent.com)	5 m	2 KiB
/u/6368493?s=64&v=4 (avatars.githubusercontent.com)	5 m	2 KiB
/u/2410382?s=64&v=4 (avatars.githubusercontent.com)	5 m	2 KiB
/u/11391441?s=64&v=4 (avatars.githubusercontent.com)	5 m	2 KiB
/u/500068?s=64&v=4 (avatars.githubusercontent.com)	5 m	2 KiB
/u/7537109?s=64&v=4 (avatars.githubusercontent.com)	5 m	2 KiB
/u/115765?s=64&v=4 (avatars.githubusercontent.com)	5 m	2 KiB
/u/23580910?s=64&v=4 (avatars.githubusercontent.com)	5 m	0 KiB
/u/7629614?s=64&v=4 (avatars.githubusercontent.com)	5 m	0 KiB

Avoid chaining critical requests 8 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Maximum critical path latency: 370 ms

Initial Navigation

/ddevault/scdoc

(github.com)

/assets/light-0eace2597ca3.css

(github.githubassets.com)

- 50 ms, 4.54 KiB

/assets/dark-a167e256da9c.css

(github.githubassets.com)

- 60 ms, 4.54 KiB

/assets/primer-primitives-971c6be3ec9f.css

(github.githubassets.com)

- 50 ms, 1.84 KiB

/assets/primer-08e422afeb43.css

(github.githubassets.com)

- 70 ms, 49.85 KiB

/assets/global-fcad22128422.css

(github.githubassets.com)

- 70 ms, 43.91 KiB

/assets/github-2f3974e4587d.css

(github.githubassets.com)

- 70 ms, 24.27 KiB

/assets/repository-b6b0e69bbb90.css

(github.githubassets.com)

- 60 ms, 5.77 KiB

/assets/code-aed6ab8a6a15.css

(github.githubassets.com)

- 60 ms, 6.42 KiB

User Timing marks and measures 1 user timing

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Name	Type	Start Time	Duration
HPC	Measure	0 ms	986.2 ms

Keep request counts low and transfer sizes small 131 requests • 1,174 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type	Requests	Transfer Size
Total	131	1,173.7 KiB
Script	83	879.7 KiB
Stylesheet	8	141.1 KiB
Other	24	70.1 KiB
Image	15	44.2 KiB
Document	1	38.7 KiB
Media	0	0 KiB
Font	0	0 KiB
Third-party	109	1,081.7 KiB

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport. Learn More

Element
Mirror of git.sr.ht/~sircmpwn/scdoc for GitHub performance testing <p class="f4 mb-3 ">

Avoid large layout shifts 2 elements found

These DOM elements contribute most to the CLS of the page.

Element	CLS Contribution
Contributors 21 + 7 contributors Languages C 66.4% Shell 15.6% SuperCol… <div data-view-component="true" class="Layout-sidebar">	0.337
History <div class="Box-sc-g0xbh4-0 jGfYmh">	0.001

Avoid long main-thread tasks 2 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

URL	Start Time	Duration
/assets/react-lib-1fbfc5be2c18.js (github.githubassets.com)	8,149 ms	69 ms
/assets/vendors-node_modules_primer_octicons-react_dist_inde….js (github.githubassets.com)	8,904 ms	55 ms

Avoid non-composited animations 25 animated elements found

Animations which are not composited can be janky and increase CLS. Learn more

Element	Name
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
div <div class="Skeleton avatar avatar-user mr-2" style="width:32px;height:32px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text" data-testid="loading" style="width: 120px;">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading
<div class="Skeleton Skeleton--text">
Unsupported CSS Properties: -webkit-mask-position-y, -webkit-mask-position-x	skeleton-loading

Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn more.

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn more.

Serve images in next-gen formats

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Preconnect to required origins

Warnings: A preconnect <link> was found for "https://github.githubassets.com" but was not used by the browser. Check that you are using the `crossorigin` attribute properly.

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Initial server response time was short Root document took 270 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more.

URL	Time Spent
/ddevault/scdoc (github.com)	270 ms

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn more.

Preload key requests

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.

Use HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Learn more.

Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more

Remove duplicate modules in JavaScript bundles

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More

URL		Potential Savings
/assets/vendors-node_modules_virtualized-list_es_index_js-no….js (github.githubassets.com)		0.1 KiB
/assets/vendors-node_modules_virtualized-list_es_index_js-no….js:1:362 (github.githubassets.com)	@babel/plugin-transform-classes

Avoids enormous network payloads Total size was 1,174 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL	Transfer Size
/assets/vendors-node_modules_primer_octicons-react_dist_inde….js (github.githubassets.com)	141.2 KiB
/assets/app_asset….js (github.githubassets.com)	103.8 KiB
/assets/behaviors-1e4a69ad752e.js (github.githubassets.com)	64.7 KiB
/assets/react-lib-1fbfc5be2c18.js (github.githubassets.com)	59.4 KiB
/assets/primer-08e422afeb43.css (github.githubassets.com)	49.9 KiB
/assets/global-fcad22128422.css (github.githubassets.com)	43.9 KiB
/ddevault/scdoc (github.com)	38.7 KiB
/assets/vendors-node_modules_github_file-attachment-element_….js (github.githubassets.com)	25.4 KiB
/assets/github-2f3974e4587d.css (github.githubassets.com)	24.3 KiB
/assets/vendors-node_modules_github_turbo_dist_turbo_es2017-….js (github.githubassets.com)	20.9 KiB

JavaScript execution time 0.3 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL	Total CPU Time	Script Evaluation	Script Parse
/assets/react-lib-1fbfc5be2c18.js (github.githubassets.com)	281 ms	236 ms	2 ms
/ddevault/scdoc (github.com)	183 ms	14 ms	2 ms
Unattributable	181 ms	2 ms	0 ms

Minimizes main-thread work 1.0 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

Category	Time Spent
Script Evaluation	526 ms
Other	272 ms
Style & Layout	124 ms
Parse HTML & CSS	46 ms
Script Parsing & Compilation	30 ms
Rendering	19 ms
Garbage Collection	17 ms

All text remains visible during webfont loads

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Minimize third-party usage

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Uses passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.

Avoids document.write()

For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.

Avoids large JavaScript libraries with smaller alternatives 0 large libraries found

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size. Learn more.

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.

Links do not have a discernible name

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 more.

Failing Elements
a <a class="types__StyledButton-sc-ws60qy-0 hsBZZU react-last-commit-history-icon" href="/ddevault/scdoc/commits/master/">

The page has a logical tab order

Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.

Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.

The user's focus is directed to new content added to the page

If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.

User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.

Custom controls have associated labels

Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn more.

Visual order on the page follows DOM order

DOM order matches the visual order, improving navigation for assistive technology. Learn more.

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn more.

HTML5 landmark elements are used to improve navigation

Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.

[aria-*] attributes match their roles

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.

[aria-hidden="true"] is not present on the document <body>

Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.

[aria-hidden="true"] elements do not contain focusable descendents

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.

[role]s have all required [aria-*] attributes

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.

Elements with an ARIA [role] that require children to contain a specific [role] have all required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.

[role]s are contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.

[role] values are valid

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.

[aria-*] attributes have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.

[aria-*] attributes are valid and not misspelled

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.

Buttons have an accessible name

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 more.

The page contains a heading, skip link, or landmark region

Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.

Background and foreground colors have a sufficient contrast ratio

Low-contrast text is difficult or impossible for many users to read. Learn more.

Document has a <title> element

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.

[id] attributes on active, focusable elements are unique

All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.

ARIA IDs are unique

The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.

Heading elements appear in a sequentially-descending order

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.

<html> element has a [lang] attribute

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.

<html> element has a valid value for its [lang] attribute

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.

Image elements have [alt] attributes

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

Lists contain only <li> elements and script supporting elements (<script> and <template>).

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.

List items (<li>) are contained within <ul> or <ol> parent elements

Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.

[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.

No element has a [tabindex] value greater than 0

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.

Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.

Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.

<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.

Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.

[accesskey] values are unique

Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.

ARIA input fields have accessible names

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.

ARIA toggle fields have accessible names

When a toggle 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.

<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.

Definition list items are wrapped in <dl> elements

Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.

No form fields have multiple labels

Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.

<frame> or <iframe> elements have a title

Screen reader users rely on frame titles to describe the contents of frames. Learn more.

<input type="image"> elements have [alt] text

When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.

Form elements have associated labels

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

Presentational <table> elements avoid using <th>, <caption> or the [summary] attribute.

A table being used for layout purposes should not include data elements, such as the th or caption elements or the summary attribute, because this can create a confusing experience for screen reader users. Learn more.

The document does not use <meta http-equiv="refresh">

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.

<object> elements have [alt] text

Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.

[lang] attributes have a valid value

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.

<video> elements contain a <track> element with [kind="captions"]

When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.

<video> elements contain a <track> element with [kind="description"]

Audio descriptions provide relevant information for videos that dialogue cannot, such as facial expressions and scenes. Learn more.