Skip to content
https://band.us

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-5ndc42
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://band.us/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://band.us/manifest.json

Manifest contains invalid JSON.

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
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light
Info::
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 light Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

2 pass 18 fail WCAG AA 1 pass AA only
h2 Build the Team
2.94:1
#000000
on
#55585C
needs 3.0:1 (large text)
24px · mid-page · over background image/gradient
h2 With One App
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · mid-page
h2 THE NO. 1 APP FOR TEAM
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 COMMUNICATION
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most Private &
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Safe Communication App
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted by Industry Leaders Nationwide
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Organize Everything,
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Notify Everyone
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Features
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How Groups Use BAND
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Operating Policies and Terms
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Posts & Announcements
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Shared Calendars
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Instant Messages
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Files, Photos, Videos
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Admin Control
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Collect Responses
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
19px · bottom of viewport

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Build the Team2.94:13.0:1
#000000
#55585C
Fail
h2 You Envision4.39:13.0:1
#000000
#79716B
Pass
h2 With One App1.44:13.0:1
#000000
#292929
Fail
h2 THE NO. 1 APP FOR TE…1.48:13.0:1
#000000
#2B2B2B
Fail
h2 COMMUNICATION1.48:13.0:1
#000000
#2B2B2B
Fail
h2 Most Private &1.48:13.0:1
#000000
#2B2B2B
Fail
h2 Safe Communication A…1.48:13.0:1
#000000
#2B2B2B
Fail
h2 Trusted by Industry …1.48:13.0:1
#000000
#2B2B2B
Fail
h2 Organize Everything,1.48:13.0:1
#000000
#2B2B2B
Fail
h2 Notify Everyone1.48:13.0:1
#000000
#2B2B2B
Fail
h2 Features1.48:13.0:1
#000000
#2B2B2B
Fail
h2 How Groups Use BAND1.48:13.0:1
#000000
#2B2B2B
Fail
h2 Operating Policies a…1.48:13.0:1
#000000
#2B2B2B
Fail
h3 Posts & Announcement…1.48:13.0:1
#000000
#2B2B2B
Fail
h3 Shared Calendars1.48:13.0:1
#000000
#2B2B2B
Fail
h3 Instant Messages1.48:13.0:1
#000000
#2B2B2B
Fail
h3 Files, Photos, Video…1.48:13.0:1
#000000
#2B2B2B
Fail
h3 Admin Control1.48:13.0:1
#000000
#2B2B2B
Fail
h3 Collect Responses1.48:13.0:1
#000000
#2B2B2B
Fail
title BAND – The App For…19.73:14.5:1
#000000
#F6F8FA
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 3 failing, 18 passed
REVIEW
83

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
THE NO. 1 APP FOR TEAM COMMUNICATION div > div.introSnapArea > div.teamCommArea > h2.title
13 div.useBandArea > div.navi > div.paging > span._totalPage
Free div.appDownloadArea > div.explanationSection > strong.subTitle > em.pointColor
BAND © 2026 div._footer > div.footer_inner > div.floor2nd > span.copyright
English 한국어 日本語 Español 繁體中文 Bahasa Indonesia div.footer_inner > div.floor2nd > div.uSelect > select.lang_list

These are opportunities to improve the legibility of your content.

Best practices

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 about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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
English 한국어 日本語 Español 繁體中文 Bahasa Indonesia div.footer_inner > div.floor2nd > div.uSelect > select.lang_list

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>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
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.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
`[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
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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
`<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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 CONTENTINFO footer

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

A+
Heading Hierarchy
15 headings
PASS
15 headings
Info::
Single H1 present
  • H1 BAND
  • H2 Build the Team You Envision With One App
  • H2 THE NO. 1 APP FOR TEAMCOMMUNICATION
  • H2 Most Private &Safe Communication App
  • H2 Trusted by Industry Leaders Nationwide
  • H2 Organize Everything,Notify Everyone
  • H2 Features
  • H3 Posts & Announcements
  • H3 Shared Calendars
  • H3 Instant Messages
  • H3 Files, Photos, Videos
  • H3 Admin Control
  • H3 Collect Responses
  • H2 How Groups Use BAND
  • H2 Operating Policies and Terms
A+
Alt Text Quality
All 42 images OK
PASS
All 42 images OK
Info::
31 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
42 images 11 good alt text 31 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback