Skip to content
https://www.loom.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Loom | Free Screen & Video Recording Software | Loom ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 25 passed
REVIEW
88

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.bg-thd-color-blue-70 > div.thd-container-max > div.absolute > button.css-1vfng2u div.bg-thd-color-blue-70 > div.thd-container-max > div.absolute > button.css-1vfng2u

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.

Tables and lists

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sales Personalize your pitch with video outreach to close more deals. Enginee… main#skip-to-content > section.mb-fluid-md > section.thd-container-max > ul.mx-auto

These are opportunities to improve the experience of reading tabular or list data using 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
Pause recording in animation div.RecordScreenAnimation_controls__QF857 > div.RecordScreenAnimation_controlsButtonWrapper__xVVXl > div.css-nez7wg > button.RecordScreenAnimation_controlsButton__tRpOw
Cancel recording in animation div.RecordScreenAnimation_controls__QF857 > div.RecordScreenAnimation_controlsButtonWrapper__xVVXl > div.css-nez7wg > button.RecordScreenAnimation_controlsButton__tRpOw

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●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
○Elements with `role="dialog"` or `role="alertdialog"` 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
○`<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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Landmark Structure
24 landmarks
PASS
24 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "primary" MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
27 headings
PASS
27 headings
Info::
Single H1 present
  • H1 One video is worth a thousand words
  • H2 Millions of people across 400,000 companies choose Loom
  • H2 Ship faster with AI bug reports
  • H2 The easiest screen recorder you’ll ever use
  • H2 Lightning fast screen recording
  • H2 So much more than a screen recorder
  • H3 Edit your videos like a pro
  • H3 Share or embed video anywhere you work
  • H3 Engage and connect with video
  • H2 Keep your content safe
  • H2 Video messaging for all use cases
  • H3 Sales
  • H3 Engineering
  • H3 Customer support
  • H3 Design
  • H2 Powerful features for easy, custom recordings
  • H2 How to use async video messaging to improve communication
  • H3 When to Choose Synchronous Vs. Asynchronous Communication
  • H3 Let Loom AI Do the Work: Say Goodbye to Manual Documentation
  • H2 Loom for Enterprise
  • H3 Loom Footer Menu
  • H4 App
  • H4 Solutions
  • H4 For Business
  • H4 Downloads
  • H4 Resources
  • H4 Company
A+
Alt Text Quality
All 82 images OK
PASS
All 82 images OK
Info::
7 decorative image(s) correctly marked
Info::
75 image(s) with good alt text
82 images 75 good alt text 7 decorative
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.
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 One video is worth a…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Millions of people a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ship faster with AI …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The easiest screen r…17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Lightning fast scree…17.62:13.0:1
#000000
#EBEBEB
Pass
h2 So much more than a …17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Keep your content sa…17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Video messaging for …17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Powerful features fo…17.62:13.0:1
#000000
#EBEBEB
Pass
h2 How to use async vid…17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Loom for Enterprise17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Edit your videos lik…17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Share or embed video…17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Engage and connect w…17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Sales17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Engineering17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Customer support17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Design17.62:13.0:1
#000000
#EBEBEB
Pass
h3 When to Choose Synch…17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Let Loom AI Do the W…17.62:13.0:1
#000000
#EBEBEB
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