Accessibility check for bearscan.app
bearscan.app
Accessibility checked by BearScan
BearScan scanned 145 pages on Nov 3, 2026. 49 checks found no issues and 12 did not apply to this site. Rescanned every 7 days.
61 checks
Audio and video alternatives
5 not applicable
Prerecorded audio-only and video-only content has an alternativeNot applicable
How it was checkedRead from the page's code, on 145 of 145 pages.
Nothing on the scanned pages for this check to apply to. No <audio>, <video>, or embedded media player in the page markup.
Prerecorded video has captionsNot applicable
How it was checkedRead from the page's code, on 145 of 145 pages.
Nothing on the scanned pages for this check to apply to. No <video> elements on this page.
Prerecorded video has audio description or a full text alternativeNot applicable
How it was checkedRead from the page's code, on 145 of 145 pages.
Nothing on the scanned pages for this check to apply to. No <video> element or embedded video player in the page markup.
Live audio in synchronised media is captionedNot applicable
How it was checkedMeasured in a real browser, on 145 of 145 pages.
Nothing on the scanned pages for this check to apply to. No live stream was found: the page fetched no live playlist or manifest and embeds no live player.
Prerecorded video has audio descriptionNot applicable
How it was checkedRead from the page's code, on 145 of 145 pages.
Nothing on the scanned pages for this check to apply to. No <video> element or embedded video player in the page markup.
Structure, labels and orientation
9 no issues found
Form controls are programmatically labelledNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
named "Enter your website" by its label-element
<input> Enter your website
<input id="_R_8iausnlb_-url" type="url" inputmode="url" autocomplete="url" spellcheck="false" placeholder="yourcompany.com" …></input>Page /

named "Questions?" by its text-content
<button> Questions?
<button type="button" class="help-launcher" popovertarget="_R_1cnlb_-panel"><svg width="16" height="16" viewbox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.4" …><path d="M3 3.5h10v7H8.5L5.5 13v-2.5H3z"…Page /privacy

named "Questions?" by its text-content
<button> Questions?
<button type="button" class="help-launcher" popovertarget="_R_1cnlb_-panel"><svg width="16" height="16" viewbox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.4" …><path d="M3 3.5h10v7H8.5L5.5 13v-2.5H3z"…Page /terms

Data tables expose their headersNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
13 header cells, 13 with a scope attribute, captioned "Website accessibility tools compared by price, coverage and whet…
#main > article > div > div:nth-of-type(1) > table
Page /guides/best-ada-website-scanners

11 header cells, 11 with a scope attribute, captioned "BearScan and Pa11y compared across seven questions"
#main > article > div > div:nth-of-type(1) > table
Page /compare/pa11y

4 header cells, 4 with a scope attribute, captioned "State law on disability discrimination by businesses, as it applie…
#main > div > section:nth-of-type(1) > div:nth-of-type(1) > table
Page /laws

Lists, tables and ARIA structures are marked up correctlyNo issues found
How it was checkedMeasured in a real browser, on 145 of 145 pages.
What the scan examined
passed axe-core's "list" check
.mk-nav__links
<ul class="mk-nav__links"><li><a href="/#how">How it works</a></li><li><a href="/#pricing">Pricing</a></li><li><a href="/lawsuits">Lawsuit tracker</a></li><li><a href="/laws">Laws by state</a></li></ul>Page /

passed axe-core's "list" check
.mk-nav__links
<ul class="mk-nav__links"><li><a href="/#how">How it works</a></li><li><a href="/#pricing">Pricing</a></li><li><a href="/lawsuits">Lawsuit tracker</a></li><li><a href="/laws">Laws by state</a></li></ul>Page /privacy

passed axe-core's "list" check
.mk-nav__links
<ul class="mk-nav__links"><li><a href="/#how">How it works</a></li><li><a href="/#pricing">Pricing</a></li><li><a href="/lawsuits">Lawsuit tracker</a></li><li><a href="/laws">Laws by state</a></li></ul>Page /terms

ARIA ID references resolveNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
its aria-describedby points at an element that exists
<input> input[name="url"]
<input id="_R_8iausnlb_-url" type="url" inputmode="url" autocomplete="url" spellcheck="false" placeholder="yourcompany.com" …></input>Page /

No aria-labelledby or aria-describedby on the page points at a missing id
Page /privacy

No aria-labelledby or aria-describedby on the page points at a missing id
Page /terms

Reading order follows the visual orderNo issues found
How it was checkedMeasured in a real browser, on 12 of 145 pages.
What the scan examined
115 blocks of the page: what is painted in each reads in the same order as its markup
Page /

27 blocks of the page: what is painted in each reads in the same order as its markup
Page /rules/2-5-2-pointer-cancellation

35 blocks of the page: what is painted in each reads in the same order as its markup
Page /laws/nevada

Instructions do not rely on shape, position, colour or sound aloneNo issues found
How it was checkedRead by a model, on 145 of 145 pages.
What the scan examined
The page's sentences were read for pointing at something by its shape, size, position, colour or sound alone, and none …
Page /

The page's sentences were read for pointing at something by its shape, size, position, colour or sound alone, and none …
Page /privacy

The page's sentences were read for pointing at something by its shape, size, position, colour or sound alone, and none …
Page /terms

Content works in both portrait and landscapeNo issues found
How it was checkedRead by a model, on 145 of 145 pages.
What the scan examined
Shown portrait (390 by 844, 8123 characters of text) and landscape (844 by 390, 8185 characters); the text was read and…
Page /

Shown portrait (390 by 844, 7825 characters of text) and landscape (844 by 390, 7876 characters); the text was read and…
Page /privacy

Shown portrait (390 by 844, 5276 characters of text) and landscape (844 by 390, 5327 characters); the text was read and…
Page /terms

Styles do not lock the page to one orientationNo issues found
How it was checkedMeasured in a real browser, on 145 of 145 pages.
What the scan examined
passed axe-core's "css-orientation-lock" check
html
<html lang="en" class="instrument_sans_5a16b3ba-module__n4CW5a__variable ibm_plex_mono_9430b135-module__jXPCDG__variable">Page /

passed axe-core's "css-orientation-lock" check
html
<html lang="en" class="instrument_sans_5a16b3ba-module__n4CW5a__variable ibm_plex_mono_9430b135-module__jXPCDG__variable">Page /privacy

passed axe-core's "css-orientation-lock" check
html
<html lang="en" class="instrument_sans_5a16b3ba-module__n4CW5a__variable ibm_plex_mono_9430b135-module__jXPCDG__variable">Page /terms

Fields that collect personal data identify their purposeNo issues found
How it was checkedRead by a model, on 145 of 145 pages.
What the scan examined
autocomplete="url" is a recognised input purpose
<input> input[name="url"]
<input id="_R_8iausnlb_-url" type="url" inputmode="url" autocomplete="url" spellcheck="false" placeholder="yourcompany.com" …></input>Page /

autocomplete="url" is a recognised input purpose
<input> input[name="url"]
<input id="_R_plfiusnlb_-url" type="url" inputmode="url" autocomplete="url" spellcheck="false" placeholder="yourcompany.com" …></input>Page /ada-compliance-checker

autocomplete="url" is a recognised input purpose
<input> input[name="url"]
<input id="_R_plfiusnlb_-url" type="url" inputmode="url" autocomplete="url" spellcheck="false" placeholder="yourcompany.com" …></input>Page /wcag-checker

Contrast, text size and reflow
6 no issues found1 not applicable
Links in running text are distinguishable without colourNo issues found
How it was checkedMeasured in a real browser, on 145 of 145 pages.
What the scan examined
passed axe-core's "link-in-text-block" check
.mk-hero__filing > a[rel="noreferrer noopener"][target="_blank"]
<a href="https://www.courtlistener.com/docket/75000866/otto-v-still-house-llc/" rel="noreferrer noopener" target="_blank">See the docket</a>Page /

passed axe-core's "link-in-text-block" check
p:nth-child(18) > a[href$="cookies"]
<a href="/cookies">cookie policy</a>Page /privacy

passed axe-core's "link-in-text-block" check
a[href$="billing"]
<a href="/billing">cancel or manage billing</a>Page /terms

Audio that plays automatically can be paused or mutedNot applicable
How it was checkedRead from the page's code, on 145 of 145 pages.
Nothing on the scanned pages for this check to apply to. No <audio>, <video>, or autoplaying embedded player in the page markup.
Text has sufficient contrast against its backgroundNo issues found
How it was checkedMeasured in a real browser, on 145 of 145 pages.
What the scan examined
contrast 15.01:1, passed axe-core's "color-contrast" check
.wordmark
<a class="wordmark" href="/">Page /

contrast 15.01:1, passed axe-core's "color-contrast" check
.wordmark
<a class="wordmark" href="/">Page /privacy

contrast 15.01:1, passed axe-core's "color-contrast" check
.wordmark
<a class="wordmark" href="/">Page /terms

Text resizes without loss of contentNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
viewport "width=device-width, initial-scale=1" does not block zooming
head > meta[name=viewport]
Page /

viewport "width=device-width, initial-scale=1" does not block zooming
head > meta[name=viewport]
Page /privacy

viewport "width=device-width, initial-scale=1" does not block zooming
head > meta[name=viewport]
Page /terms

Content reflows at 320 CSS pixels without horizontal scrollingNo issues found
How it was checkedMeasured in a real browser, on 145 of 145 pages.
What the scan examined
At 320 CSS pixels wide the page content is 320px wide: no horizontal scrolling
Page /

At 320 CSS pixels wide the page content is 320px wide: no horizontal scrolling
Page /privacy

At 320 CSS pixels wide the page content is 320px wide: no horizontal scrolling
Page /terms

Content survives increased text spacingNo issues found
How it was checkedMeasured in a real browser, on 12 of 145 pages.
What the scan examined
285 text elements laid out with 1.4.12's spacing applied: none clipped, overlapping or pushed outside its box
Page /

68 text elements laid out with 1.4.12's spacing applied: none clipped, overlapping or pushed outside its box
Page /rules/2-5-2-pointer-cancellation

82 text elements laid out with 1.4.12's spacing applied: none clipped, overlapping or pushed outside its box
Page /laws/nevada

Content shown on hover or focus is dismissible, hoverable and persistentNo issues found
How it was checkedOperated in a real browser, on 12 of 145 pages.
What the scan examined
11 controls were hovered and focused in a browser; nothing appeared that needed a way to dismiss it
Page /

12 controls were hovered and focused in a browser; nothing appeared that needed a way to dismiss it
Page /rules/2-5-2-pointer-cancellation

10 controls were hovered and focused in a browser; nothing appeared that needed a way to dismiss it
Page /laws/nevada

Keyboard
4 no issues found
All functionality is available from a keyboardNo issues found
How it was checkedOperated in a real browser, on 145 of 145 pages.
What the scan examined
Tab reached 54 controls; none that looks operable was unreachable
Page /

Tab reached 42 controls; none that looks operable was unreachable
Page /privacy

Tab reached 41 controls; none that looks operable was unreachable
Page /terms

Scrollable regions and frames can be reached from the keyboardNo issues found
How it was checkedMeasured in a real browser, on 145 of 145 pages.
What the scan examined
axe-core ran on this page and none of its checks for WCAG 2.1.1 raised anything
Page /

axe-core ran on this page and none of its checks for WCAG 2.1.1 raised anything
Page /privacy

axe-core ran on this page and none of its checks for WCAG 2.1.1 raised anything
Page /terms

No keyboard trapNo issues found
How it was checkedOperated in a real browser, on 145 of 145 pages.
What the scan examined
Tab visited 54 controls and focus came back round to the first; it never stuck
Page /

Tab visited 42 controls and focus came back round to the first; it never stuck
Page /privacy

Tab visited 41 controls and focus came back round to the first; it never stuck
Page /terms

Single-character shortcuts can be turned off or remappedNo issues found
How it was checkedOperated in a real browser, on 12 of 145 pages.
What the scan examined
76 single keys were pressed with nothing focused; the page reacted to none of them
Page /

76 single keys were pressed with nothing focused; the page reacted to none of them
Page /rules/2-5-2-pointer-cancellation

76 single keys were pressed with nothing focused; the page reacted to none of them
Page /laws/nevada

Time limits and motion
2 no issues found
Time limits can be extendedNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
The page's head has no meta refresh, the one time limit a document can state
Page /

The page's head has no meta refresh, the one time limit a document can state
Page /privacy

The page's head has no meta refresh, the one time limit a document can state
Page /terms

Moving, blinking and auto-updating content can be pausedNo issues found
How it was checkedOperated in a real browser, on 12 of 145 pages.
What the scan examined
The page was left alone for 10 seconds: nothing moved, scrolled or updated by itself
Page /

The page was left alone for 10 seconds: nothing moved, scrolled or updated by itself
Page /rules/2-5-2-pointer-cancellation

The page was left alone for 10 seconds: nothing moved, scrolled or updated by itself
Page /laws/nevada

Flashing content
1 no issues found
No content flashes more than three times per secondNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
No video, embedded player, animated GIF or media stream on the page (4 images looked at); no flashing mechanism was fou…
Page /

No video, embedded player, animated GIF or media stream on the page (4 images looked at); no flashing mechanism was fou…
Page /privacy

No video, embedded player, animated GIF or media stream on the page (4 images looked at); no flashing mechanism was fou…
Page /terms

Navigation and focus
8 no issues found
A mechanism exists to bypass repeated blocksNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
skip link to /#main
Skip to main content
Page /

skip link to /privacy#main
Skip to main content
Page /privacy

skip link to /terms#main
Skip to main content
Page /terms

The page has a descriptive titleNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
title "BearScan: free ADA and WCAG website scanner" read as describing the page
<title> BearScan: free ADA and WCAG website scanner
Page /

title "Privacy policy · BearScan" read as describing the page
<title> Privacy policy · BearScan
Page /privacy

title "Terms of service · BearScan" read as describing the page
<title> Terms of service · BearScan
Page /terms

Focus order preserves meaning and operabilityNo issues found
How it was checkedOperated in a real browser, on 145 of 145 pages.
What the scan examined
Tab visited 54 controls in order, first "Scan my site" > "See the docket" > "Seyfarth Shaw, ADA Title III blog" > "Usab…
Page /

Tab visited 42 controls in order, first "Skip to main content" > "BearScan" > "How it works" > "Pricing"
Page /privacy

Tab visited 41 controls in order, first "Skip to main content" > "BearScan" > "How it works" > "Pricing"
Page /terms

No positive tabindex valuesNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
No element on the page sets a positive tabindex
Page /

No element on the page sets a positive tabindex
Page /privacy

No element on the page sets a positive tabindex
Page /terms

Link text describes where the link goesNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
"Skip to main content" read as saying where it goes
<a> Skip to main content
<a class="skip-link" href="#main">Skip to main content</a>Page /

"Skip to main content" read as saying where it goes
<a> Skip to main content
<a class="skip-link" href="#main">Skip to main content</a>Page /privacy

"Skip to main content" read as saying where it goes
<a> Skip to main content
<a class="skip-link" href="#main">Skip to main content</a>Page /terms

Pages can be found in more than one wayNo issues found
How it was checkedRead by a model, on 1 of 1 page.
What the scan examined
The homepage offers navigation, and the site's pages also offer a second way ("BearScan", "Scan your site"): pages can …
Page /
Keyboard focus is visibleNo issues found
How it was checkedOperated in a real browser, on 145 of 145 pages.
What the scan examined
focused with Tab: a visible focus indicator (stop 1 of 54)
<button> Scan my site
Page /

focused with Tab: a visible focus indicator (stop 1 of 42)
<a> Skip to main content
Page /privacy

focused with Tab: a visible focus indicator (stop 1 of 41)
<a> Skip to main content
Page /terms

Focused elements are not hidden by sticky contentNo issues found
How it was checkedOperated in a real browser, on 145 of 145 pages.
What the scan examined
took focus and was not covered by other content
<button> Scan my site
Page /

took focus and was not covered by other content
<a> Skip to main content
Page /privacy

took focus and was not covered by other content
<a> Skip to main content
Page /terms

Touch and pointer
3 no issues found3 not applicable
Multipoint and path gestures have a single-pointer alternativeNot applicable
How it was checkedOperated in a real browser, on 12 of 145 pages.
Nothing on the scanned pages for this check to apply to. Nothing on this page handles touch or pointer movement, so nothing needs a gesture.
Actions fire on release, not on pressNo issues found
How it was checkedOperated in a real browser, on 12 of 145 pages.
What the scan examined
8 buttons and links were pressed and slid away from; none acted on the press alone
Page /

11 buttons and links were pressed and slid away from; none acted on the press alone
Page /rules/2-5-2-pointer-cancellation

9 buttons and links were pressed and slid away from; none acted on the press alone
Page /laws/nevada

Accessible name contains the visible labelNo issues found
How it was checkedMeasured in a real browser, on 12 of 145 pages.
What the scan examined
drawn "Monitoring is from $ 19 a month per site", named "Monitoring is from $19 a month per site →"
Monitoring is from $19 a month per site →
Page /

drawn "W3C Recommendation, WCAG 2.2", named "W3C Recommendation, WCAG 2.2 (opens in a new tab)"
W3C Recommendation, WCAG 2.2 (opens in a new tab)
Page /rules/2-5-2-pointer-cancellation

drawn "NRS 651.050-651.120 (equal enjoyment of places of public accommodation); NRS 651.070, civil action NRS 651.090",…
NRS 651.050-651.120 (equal enjoyment of places of public accommodation); NRS 651.070, civil action …
Page /laws/nevada

Motion-triggered functions have a control and can be disabledNot applicable
How it was checkedOperated in a real browser, on 12 of 145 pages.
Nothing on the scanned pages for this check to apply to. The page listens for no device motion or orientation, so shaking or tilting does nothing.
Dragging has a single-pointer alternativeNot applicable
How it was checkedOperated in a real browser, on 12 of 145 pages.
Nothing on the scanned pages for this check to apply to. Nothing on this page is dragged or dropped on.
Pointer targets are large enoughNo issues found
How it was checkedMeasured in a real browser, on 145 of 145 pages.
What the scan examined
passed axe-core's "target-size" check
.skip-link
<a class="skip-link" href="#main">Skip to main content</a>Page /

passed axe-core's "target-size" check
.skip-link
<a class="skip-link" href="#main">Skip to main content</a>Page /privacy

passed axe-core's "target-size" check
.skip-link
<a class="skip-link" href="#main">Skip to main content</a>Page /terms

Page language
2 no issues found
Page language is declaredNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
declares language "en"
<html> html
<html lang="en">Page /

declares language "en"
<html> html
<html lang="en">Page /privacy

declares language "en"
<html> html
<html lang="en">Page /terms

Passages in another language are marked with their languageNo issues found
How it was checkedRead by a model, on 145 of 145 pages.
What the scan examined
The page's text was read for passages in a language other than "en": none was found without a correct lang attribute
Page /

The page's text was read for passages in a language other than "en": none was found without a correct lang attribute
Page /privacy

The page's text was read for passages in a language other than "en": none was found without a correct lang attribute
Page /terms

Predictable behavior
5 no issues found
Focusing an element does not change contextNo issues found
How it was checkedOperated in a real browser, on 145 of 145 pages.
What the scan examined
took focus and the page stayed where it was
<button> Scan my site
Page /

took focus and the page stayed where it was
<a> Skip to main content
Page /privacy

took focus and the page stayed where it was
<a> Skip to main content
Page /terms

Changing a setting does not unexpectedly change contextNo issues found
How it was checkedOperated in a real browser, on 12 of 145 pages.
What the scan examined
2 selects, radios, checkboxes and sliders were changed in a browser; none changed the page's context
Page /

1 selects, radios, checkboxes and sliders were changed in a browser; none changed the page's context
Page /lawsuits?country=US®ion=CA
Repeated navigation appears in the same order on every pageNo issues found
How it was checkedRead from the page's code, on 1 of 1 page.
What the scan examined
One page of each of 60 layouts was compared: the navigation links they share keep the same order
Page /
Components with the same function are identified the same wayNo issues found
How it was checkedRead from the page's code, on 1 of 1 page.
What the scan examined
No link or control appears under more than one name across the compared pages
Page /
Help is consistent across pagesNo issues found
How it was checkedRead by a model, on 1 of 1 page.
What the scan examined
2 help links and controls ("Demand letter help", "Support") keep the same place among each page's other items across 60…
Page /
Forms and error messages
4 no issues found2 not applicable
Errors are identified in textNo issues found
How it was checkedOperated in a real browser, on 133 of 145 pages.
What the scan examined
submitted empty or wrong in a browser that stops every write: the error was shown in text
Scan my site
Page /

submitted empty or wrong in a browser that stops every write: the error was shown in text
Scan my site
Page /ada-compliance-checker

submitted empty or wrong in a browser that stops every write: the error was shown in text
Scan my site
Page /wcag-checker

Labels and instructions are providedNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
8 visible fields looked at; none is constrained by a pattern without saying what it is
Page /

3 visible fields looked at; none is constrained by a pattern without saying what it is
Page /privacy

3 visible fields looked at; none is constrained by a pattern without saying what it is
Page /terms

Error messages suggest how to fix the inputNo issues found
How it was checkedRead by a model, on 133 of 145 pages.
What the scan examined
error "Enter your site's address." read as saying how to fix the input
Enter your site's address.
Page /

error "Enter your site's address." read as saying how to fix the input
Enter your site's address.
Page /ada-compliance-checker

error "Enter your site's address." read as saying how to fix the input
Enter your site's address.
Page /wcag-checker

Legal, financial and data submissions can be reviewed, corrected or reversedNot applicable
How it was checkedRead from the page's code, on 145 of 145 pages.
Nothing on the scanned pages for this check to apply to. This is not a checkout page, and the scan reaches no other legal, financial or data commitment (account deletion and the like sit behind a sign-in).
Information already entered is not asked for againNo issues found
How it was checkedRead by a model, on 145 of 145 pages.
What the scan examined
3 fields read: none asks again for something entered earlier in the form
#main > article > form
Page /support

2 fields read: none asks again for something entered earlier in the form
#main > div > section > form
Page /catalog
8 fields read: none asks again for something entered earlier in the form
#main > div > form
Page /lawsuits/new
Sign-in does not require a cognitive function testNot applicable
How it was checkedOperated in a real browser, on 145 of 145 pages.
Nothing on the scanned pages for this check to apply to. No password field on this page.
Compatibility with assistive technology
5 no issues found1 not applicable
Controls expose an accessible name and their stateNo issues found
How it was checkedRead from the page's code, on 12 of 145 pages.
What the scan examined
No group of buttons on the page acts as a toggle that needs to say which option is on
Page /

No group of buttons on the page acts as a toggle that needs to say which option is on
Page /rules/2-5-2-pointer-cancellation

No group of buttons on the page acts as a toggle that needs to say which option is on
Page /laws/nevada

ARIA roles are validNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
passed axe-core's "aria-deprecated-role" check
next-route-announcer #__next-route-announcer__
<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-…Page /

passed axe-core's "aria-deprecated-role" check
next-route-announcer #__next-route-announcer__
<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-…Page /privacy

passed axe-core's "aria-deprecated-role" check
next-route-announcer #__next-route-announcer__
<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-…Page /terms

Hidden content is not focusableNo issues found
How it was checkedRead from the page's code, on 145 of 145 pages.
What the scan examined
passed axe-core's "aria-hidden-focus" check
.wordmark__mark
<svg class="wordmark__mark" width="24" height="24" viewBox="0 0 48 48" fill="none" aria-hidden="true" focusable="false">Page /

passed axe-core's "aria-hidden-focus" check
.wordmark__mark
<svg class="wordmark__mark" width="24" height="24" viewBox="0 0 48 48" fill="none" aria-hidden="true" focusable="false">Page /privacy

passed axe-core's "aria-hidden-focus" check
.wordmark__mark
<svg class="wordmark__mark" width="24" height="24" viewBox="0 0 48 48" fill="none" aria-hidden="true" focusable="false">Page /terms

Frames have an accessible nameNot applicable
How it was checkedRead from the page's code, on 145 of 145 pages.
Nothing on the scanned pages for this check to apply to. No iframes on this page.
ARIA attributes, ids and nesting are validNo issues found
How it was checkedMeasured in a real browser, on 145 of 145 pages.
What the scan examined
passed axe-core's "aria-allowed-attr" check
nav[aria-label="Primary"]
<nav aria-label="Primary"><ul class="mk-nav__links"><li><a href="/#how">How it works</a></li><li><a href="/#pricing">Pricing</a></li><li><a href="/lawsuits">Lawsuit tracker</a></li><li><a href="/laws">Laws by state</a><…Page /

passed axe-core's "aria-allowed-attr" check
nav[aria-label="Primary"]
<nav aria-label="Primary"><ul class="mk-nav__links"><li><a href="/#how">How it works</a></li><li><a href="/#pricing">Pricing</a></li><li><a href="/lawsuits">Lawsuit tracker</a></li><li><a href="/laws">Laws by state</a><…Page /privacy

passed axe-core's "aria-allowed-attr" check
nav[aria-label="Primary"]
<nav aria-label="Primary"><ul class="mk-nav__links"><li><a href="/#how">How it works</a></li><li><a href="/#pricing">Pricing</a></li><li><a href="/lawsuits">Lawsuit tracker</a></li><li><a href="/laws">Laws by state</a><…Page /terms

Status messages are exposed without focusNo issues found
How it was checkedOperated in a real browser, on 12 of 145 pages.
What the scan examined
0 live regions on the page; 0 texts appeared on their own without being announced
Page /

0 live regions on the page; 0 texts appeared on their own without being announced
Page /ada-compliance-checker

0 live regions on the page; 0 texts appeared on their own without being announced
Page /wcag-checker

Pages the scan fetched. Those opened in a real browser show what it saw.
/
/privacy
/terms
/rules/2-5-2-pointer-cancellation
/cookies
/laws/nevada
/guides/best-ada-website-scanners
/guides/is-my-website-ada-compliant
/guides/ada-website-lawsuit-cost
/guides/do-accessibility-overlays-prevent-lawsuits
/guides/wcag-2-2-vs-2-1
/guides/ada-demand-letter
/ada-compliance-checker
/wcag-checker
/compare/pa11y
/accessibility
/rules/2-4-3-focus-order
/rules/3-2-6-consistent-help
/support
/laws
/laws/alabama
/laws/alaska
/laws/arizona
/laws/arkansas- /laws/california
- /laws/colorado
- /laws/connecticut
- /laws/delaware
- /laws/district-of-columbia
- /laws/florida
- /laws/georgia
- /laws/hawaii
- /laws/idaho
- /laws/illinois
- /laws/indiana
- /laws/iowa
- /laws/kansas
- /laws/kentucky
- /laws/louisiana
- /laws/maine
- /laws/maryland
- /laws/massachusetts
- /laws/michigan
- /laws/minnesota
- /laws/mississippi
- /laws/missouri
- /laws/montana
- /laws/nebraska
- /laws/new-hampshire
- /laws/new-jersey
- /laws/new-mexico
- /laws/new-york
- /laws/new-york-city
- /laws/north-carolina
- /laws/north-dakota
- /laws/ohio
- /laws/oklahoma
- /laws/oregon
- /laws/pennsylvania
- /laws/rhode-island
Earlier scans of this site.
- 145 pages
- 145 pages
- 145 pages
- 145 pages
- 145 pages
- 144 pages
- 32 pages
- 15 pages
- 10 pages
- 130 pages
- 130 pages
- 130 pages