Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 3 REVIEW 3 FIX

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.

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.

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 Page not found | Better Business Bureau® ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA 1 pass AA only

h2 Cookies on BBB.org

2.18:1

#000000

#474446

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Cookie Preferences

2.62:1

#000000

#0047BB

needs 3.0:1 (large text)

24px · above the fold

h3 Necessary Cookies

2.62:1

#000000

#0047BB

needs 3.0:1 (large text)

19px · above the fold

h3 Functional Cookies

2.62:1

#000000

#0047BB

needs 3.0:1 (large text)

19px · mid-page

p We use cookies to give users the best co…

2.64:1

#000000

#545051

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 TRUST, BUILT LOCALLY…	12.64:1	3.0:1	#000000	#C8C9C7	Pass
h2 Cookies on BBB.org	2.18:1	3.0:1	#000000	#474446	Fail
h2 Cookie Preferences	2.62:1	3.0:1	#000000	#0047BB	Fail
h2 Navigation menu	12.64:1	3.0:1	#000000	#C8C9C7	Pass
h2 Select a Language	12.64:1	3.0:1	#000000	#C8C9C7	Pass
h2 Find trusted partner…	12.64:1	3.0:1	#000000	#C8C9C7	Pass
h2 Do business, better	12.64:1	3.0:1	#000000	#C8C9C7	Pass
h2 For Consumers	12.64:1	3.0:1	#000000	#C8C9C7	Pass
h2 For Businesses	12.64:1	3.0:1	#000000	#C8C9C7	Pass
h2 Affiliated Programs	12.64:1	3.0:1	#000000	#C8C9C7	Pass
h3 Necessary Cookies	2.62:1	3.0:1	#000000	#0047BB	Fail
h3 Functional Cookies	2.62:1	3.0:1	#000000	#0047BB	Fail
h3 Performance Cookies	12.64:1	3.0:1	#000000	#C8C9C7	Pass
h3 Marketing Cookies	12.64:1	3.0:1	#000000	#C8C9C7	Pass
title BBB \| Better Busines…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p We use cookies to gi…	2.64:1	4.5:1	#000000	#545051	Fail
a Privacy Policy	8.89:1	4.5:1	#000000	#D49A9B	Pass
p to learn more.	8.55:1	4.5:1	#000000	#D39693	Pass
button Accept All Cookies	6.13:1	4.5:1	#000000	#7D89B7	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+

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H2 Cookies on BBB.org
H2 Cookie Preferences
H3 Necessary Cookies
H3 Functional Cookies
H3 Performance Cookies
H3 Marketing Cookies
H2 Navigation menu
H2 Select a Language
H1 TRUST, BUILT LOCALLY.™
H2 Find trusted partners
H2 Do business, better
H2 For Consumers
H2 For Businesses
H2 Affiliated Programs

A+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

9 decorative image(s) correctly marked

4 image(s) with good alt text

13 images 4 good alt text 9 decorative

All images have appropriate alt text.

Form Accessibility

1 of 13 controls have issues

PASS

1 of 13 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

12 control(s) properly labeled

13 controls

12 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#functional-input-0	radio	Use functional cookies	for/id
#functional-input-1	radio	Do not use functional cookies	for/id
#performance-input-0	radio	Use performance cookies	for/id
#performance-input-1	radio	Do not use performance cookies	for/id
#marketing-input-0	radio	Use marketing cookies	for/id
#marketing-input-1	radio	Do not use marketing cookies	for/id
#find_text	input	Find	for/id
#find_loc	input	Near	for/id
#find_text-mobile	input	Find	for/id
#find_loc-mobile	input	Near	for/id
#downshift-«R1kpm»-input	input	Find	for/id
#downshift-«R2kpm»-input	input	Near	for/id
#g-recaptcha-response-100000	textarea	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Link & Button Quality

67 links, 27 buttons — all OK

PASS

67 links, 27 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://www.bbb.org/all/privacy-policy#cookies; https://x.com/bbb_us; https://www.linkedin.com/company/better-business-bureau/; https://www.facebook.com/BetterBusinessBureau; https://www.instagram.com/betterbusinessbureau_/

62 link(s) with descriptive text

67 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.bbb.org/all/privacy-policy#c…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://x.com/bbb_us	our Twitter (opens in a new ta…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/better-…	our LinkedIn (opens in a new t…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/BetterBusinessB…	our Facebook (opens in a new t…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/betterbusiness…	our Instagram (opens in a new …	new tab	Add '(opens in new tab)' to text

89 links and buttons have descriptive text

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

https://www.bbb.org/all/privacy-policy#cookies; https://x.com/bbb_us; https://www.linkedin.com/company/better-business-bureau/; https://www.facebook.com/BetterBusinessBureau; https://www.instagram.com/betterbusinessbureau_/

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

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: https://assets.bbb.org/header-footer/f111c7bc405f3123c9ddb906388820f3abd4c764/assets/css/print.css

Print Stylesheet ✓ Print Optimized

Print stylesheet https://assets.bbb.org/header-footer/f111c7bc405f3123c9ddb906388820f3abd4c764/assets/css/print.css ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 23 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.

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
Get a Quote `div > ul > li > a.active-underline`
Start a Review `div > ul > li > a.active-underline`
File a Complaint `div > ul > li > a.active-underline`
Get Your Business Listed `div > ul > li > a.active-underline`
BBB Accreditation `div > ul > li > a.active-underline`
Apply for BBB Accreditation `div > ul > li > a.active-underline`
BBB Institute for Marketplace Trust `div > ul > li > a.active-underline`
BBB Wise Giving Alliance (Give.org) `div > ul > li > a.active-underline`
BBB National Programs `div > ul > li > a.active-underline`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

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

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

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