Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 Airtime | Essential Tools for Video at Work ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Web Manifest

Action

Not found

FIX

Not found

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

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

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

Link & Button Quality

9 issue(s) across 60 links and 9 buttons

REVIEW

9 issue(s) across 60 links and 9 buttons

9 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /home; /en/camera; /en/screen-recorder; /en/creator; /en/stacks; /en/camera; /en/screen-recorder; /en/creator; /en/stacks

51 link(s) with descriptive text

60 links

9 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/home	(empty)	empty	Add link text or aria-label
/en/camera	(empty)	empty	Add link text or aria-label
/en/screen-recorder	(empty)	empty	Add link text or aria-label
/en/creator	(empty)	empty	Add link text or aria-label
/en/stacks	(empty)	empty	Add link text or aria-label
/en/camera	(empty)	empty	Add link text or aria-label
/en/screen-recorder	(empty)	empty	Add link text or aria-label
/en/creator	(empty)	empty	Add link text or aria-label
/en/stacks	(empty)	empty	Add link text or aria-label

60 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/home; /en/camera; /en/screen-recorder; /en/creator; /en/stacks; /en/camera; /en/screen-recorder; /en/creator; /en/stacks

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 The essential tools for video at work
H2 Meet Airtime: one app, four great tools
H3 Webcam superpowers for every video meeting
H3 Easy recordings your audience will love
H3 Put yourself in your presentations
H3 The interactive alternative to traditional screensharing
H2 Meet Airtime: one app, four great tools
H3 Webcam superpowers for every video meeting
H3 Easy recordings your audience will love
H3 Put yourself in your presentations
H3 The interactive alternative to traditional screensharing
H2 Why Airtime?
H2 Why Airtime?
H2 Airtime for everyone
H2 Real videos by real people
H3 Announcing a public API
H3 Power of personality
H3 Podcast masterclass
H3 Virtual Charisma Course Sneak Peek
H2 Raise the bar every time you’re on video.

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

17 image(s) with good alt text

17 images 17 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#react-select-footer_locale_switcher-input	text	Select your locale	aria-label
#react-select-footer_locale_switcher-input	text	Select your locale	aria-label

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)

Element	Ratio	Required	FG	BG	Result
h1 The essential tool…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Meet Airtime: one ap…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Meet Airtime: one ap…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Why Airtime?	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Why Airtime?	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Airtime for everyone	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Real videos by real …	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Raise the bar every …	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Webcam superpowers f…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Easy recordings your…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Put yourself in your…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 The interactive alte…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Webcam superpowers f…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Easy recordings your…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Put yourself in your…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 The interactive alte…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Announcing a public …	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Power of personality	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Podcast masterclass	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h3 Virtual Charisma Cou…	19.77:1	3.0:1	#000000	#F8F8F8	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.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 27 passed

PASS

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

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.block > div.mx-auto > div.flex > a `nav.block > div.mx-auto > 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.

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[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

●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

●Touch targets have sufficient size and spacing.

●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

○Links are distinguishable without relying on color.

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.