Browse & Analyze

Browse recent website audits and performance trends

Explore technology stacks detected across the web

Side-by-side technology comparisons and market share

Curated technology stacks and the sites that use them

Editorial deep-dives on the state of web performance

Browse and download favicons from analyzed websites

Learn

Common questions about BeaverCheck scores and checks

How we calculate scores across 100+ checks

The story behind BeaverCheck and the team

Practical guides to fix common web performance issues

Migration Guides

Step-by-step guides for moving between web technologies

Definitions for performance, SEO, and web platform terms

Contrast Checker

Check WCAG color contrast ratios between any two colors

Inspect HTTP response headers for any URL

Analyze SSL/TLS certificate details and chain

Look up DNS records for any domain

Redirect Checker

Trace the full redirect chain for any URL

Real-user INP and Core Web Vitals from Google's Chrome UX Report.

RESTful API for programmatic website audits

Embed an auto-updating health score badge on your site

https://www.cutsclothing.com/en-ng/

Accessibility

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

SCORE

75

GRADE

C

FIX

8

REVIEW

3

PASS

13

INFO

0

Checks

24

13 PASS 3 REVIEW 8 FIX

D

Mobile Keyboard & Autofill

Action

4/4 eligible field(s) missing autocomplete or inputmode

FIX

4/4 eligible field(s) missing autocomplete or inputmode

2 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email">, <input type="email" name="email">

2 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email">, <input type="email" name="email">

D

Tabindex Anti-Patterns

Action

0 positive, 20 -1-on-focusable

FIX

0 positive, 20 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

D

Mobile-Readable Font Sizes

Action

59% of visible text renders at >= 12 CSS px (35 below threshold)

FIX

59% of visible text renders at >= 12 CSS px (35 below threshold)

35 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <strong> 11.0px ("BLACK FRIDAY SALE"); <strong> 11.0px ("30% OFF SITEWIDE"); <strong> 11.0px ("BLACK FRIDAY SALE"); <strong> 11.0px ("30% OFF SITEWIDE"); <strong> 11.0px ("BLACK FRIDAY SALE").

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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 ✗

B

Link & Button Quality

1 issue(s) across 70 links and 14 buttons

REVIEW

1 issue(s) across 70 links and 14 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.cutsclothing.com/pages/about-us ("Learn More")

23 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://cutsmarketplace.com/; /en-eshttps:/cutsclothing.kustomer.help/lang/en_us/; https://shop.cutsclothing.com/apps/redo/account/login; /en-eshttps:/cutsclothing.kustomer.help/en_us/categories/size-fit-ryoSBbZ1v; /en-eshttps:/cutsclothing.kustomer.help/contact/contact-us-HkIWrZkZ_; /en-es/pages/careers; /en-es/pages/corporate-and-wholesale; https://marketplace.cutsclothing.com/; https://cutsmarketplace.com/; /en-eshttps:/cutsclothing.kustomer.help/lang/en_us/ (+13 more)

46 link(s) with descriptive text

70 links

0 empty

1 generic text

23 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cutsclothing.com/pages/about…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: About Us
https://cutsmarketplace.com/	Cuts Marketplace	new tab	Add '(opens in new tab)' to text
/en-eshttps:/cutsclothing.kustomer.help/…	FAQ	new tab	Add '(opens in new tab)' to text
https://shop.cutsclothing.com/apps/redo/…	Order Tracking	new tab	Add '(opens in new tab)' to text
/en-eshttps:/cutsclothing.kustomer.help/…	Size + Fit	new tab	Add '(opens in new tab)' to text
/en-eshttps:/cutsclothing.kustomer.help/…	Contact Us	new tab	Add '(opens in new tab)' to text
/en-es/pages/careers	Careers	new tab	Add '(opens in new tab)' to text
/en-es/pages/corporate-and-wholesale	Corporate and Wholesale	new tab	Add '(opens in new tab)' to text
https://marketplace.cutsclothing.com/	Cuts Marketplace	new tab	Add '(opens in new tab)' to text
https://cutsmarketplace.com/	Cuts Marketplace	new tab	Add '(opens in new tab)' to text
/en-eshttps:/cutsclothing.kustomer.help/…	FAQ	new tab	Add '(opens in new tab)' to text
https://shop.cutsclothing.com/apps/redo/…	Order Tracking	new tab	Add '(opens in new tab)' to text
/en-eshttps:/cutsclothing.kustomer.help/…	Size + Fit	new tab	Add '(opens in new tab)' to text
/en-eshttps:/cutsclothing.kustomer.help/…	Contact Us	new tab	Add '(opens in new tab)' to text
/en-es/pages/careers	Careers	new tab	Add '(opens in new tab)' to text
/en-es/pages/corporate-and-wholesale	Corporate and Wholesale	new tab	Add '(opens in new tab)' to text
https://marketplace.cutsclothing.com/	Cuts Marketplace	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Get it on Google Play	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/app/6714447215	Download on the App Store	new tab	Add '(opens in new tab)' to text
/en-eshttps:/www.instagram.com/cuts	instagram	new tab	Add '(opens in new tab)' to text
/en-eshttps:/www.tiktok.com/@cuts	tiktok	new tab	Add '(opens in new tab)' to text
/en-eshttps:/www.facebook.com/ShopCutsCl…	facebook	new tab	Add '(opens in new tab)' to text
/en-eshttps:/www.youtube.com/CUTSClothin…	youtube	new tab	Add '(opens in new tab)' to text
/en-eshttps:/x.com/cutsclothing	twitter	new tab	Add '(opens in new tab)' to text

60 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://www.cutsclothing.com/pages/about-us ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://cutsmarketplace.com/; /en-eshttps:/cutsclothing.kustomer.help/lang/en_us/; https://shop.cutsclothing.com/apps/redo/account/login; /en-eshttps:/cutsclothing.kustomer.help/en_us/categories/size-fit-ryoSBbZ1v; /en-eshttps:/cutsclothing.kustomer.help/contact/contact-us-HkIWrZkZ_; /en-es/pages/careers; /en-es/pages/corporate-and-wholesale; https://marketplace.cutsclothing.com/; https://cutsmarketplace.com/; /en-eshttps:/cutsclothing.kustomer.help/lang/en_us/ (+13 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Plus ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

title Cuts Clothing | For the Sport of Busines…

3.82:1

#000000

on

#C23333

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Skip to main content

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

strong BLACK FRIDAY SALE

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

16px · top of page (header area)

strong 30% OFF SITEWIDE

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

16px · top of page (header area)

strong BLACK FRIDAY SALE

1.96:1

#000000

on

#3E3E3E

needs 3.0:1 (large text)

16px · above the fold · over background image/gradient

strong 30% OFF SITEWIDE

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

16px · above the fold

strong BLACK FRIDAY SALE

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

16px · above the fold

strong 30% OFF SITEWIDE

1.09:1

#000000

on

#0E0E0E

needs 3.0:1 (large text)

16px · above the fold · over background image/gradient

3 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)

Element	Ratio	Required	FG	BG	Result
h1 Black Friday Sale: 3…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop Best Sellers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop Bundles & Fits	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop New Releases	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Shop	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Contact	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 #madethecut	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Shop	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Contact	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 #madethecut	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Stay Connected	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Stay Connected	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Cuts Clothing \| For …	3.82:1	4.5:1	#000000	#C23333	Fail
a Skip to main content	1.00:1	4.5:1	#000000	#000000	Fail
strong BLACK FRIDAY SALE	1.00:1	3.0:1	#000000	#000000	Fail
strong 30% OFF SITEWIDE	1.00:1	3.0:1	#000000	#000000	Fail
strong BLACK FRIDAY SALE	1.96:1	3.0:1	#000000	#3E3E3E	Fail
strong 30% OFF SITEWIDE	1.00:1	3.0:1	#000000	#000000	Fail
strong BLACK FRIDAY SALE	1.00:1	3.0:1	#000000	#000000	Fail
strong 30% OFF SITEWIDE	1.09:1	3.0:1	#000000	#0E0E0E	Fail

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+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A

Heading Hierarchy

16 headings, 1 skip(s)

PASS

16 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Black Friday Sale: 30% Off Sitewide at Cuts Clothing
H2 Shop Best Sellers
H2 Shop Bundles & Fits
H2 Shop New Releases
H4 The only shirt worth wearing skipped
H4 Suits any occasion from the boardroom to the beach and everything in between.
H4 Their ability to deliver technical yet fashionable shirts has heightened the standard of everyday attire
H4 Obsessed is an understatement–Cuts created the perfect upgrade to the standard work attire.
H3 Shop
H3 Contact
H3 #madethecut
H3 Shop
H3 Contact
H3 #madethecut
H3 Stay Connected
H3 Stay Connected

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Heading Text Quality

All 16 heading(s) have substantive, well-formed text

PASS

All 16 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A

Alt Text Quality

3 of 15 images have issues

PASS

3 of 15 images have issues

3 image(s) with generic alt text

12 image(s) with good alt text

15 images 12 good alt text 3 generic

Issue	Count
generic	3 image(s)

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
email	email	Email address for newsletter signup	aria-label
email	email	Email address for newsletter signup	aria-label

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

2 form control(s) checked, no input-semantic issues

PASS

2 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 31 passed

PASS

97

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.

ARIA

When an element 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 how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > button.w-5 > div.-ml-4 > div.hamburger-react `div.flex > button.w-5 > div.-ml-4 > div.hamburger-react`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
(0) `div#main-nav > div.flex > div.relative > button.btn-text`

○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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Elements use only permitted ARIA attributes

●ARIA toggle fields have accessible names

●Background and foreground colors have a sufficient contrast ratio

●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

●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"]`

●All heading elements contain content.

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

○Uses ARIA roles only on compatible elements

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

Send Feedback