Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 4 REVIEW 3 FIX

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.

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 ✗

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

No <nav> landmark found

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: American Arbitration Association

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name American Arbitration Association ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name American Arbitration Association Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 The World’s Leading Provider of Disput…

1.00:1

#000000

needs 3.0:1 (large text)

32px · mid-page

h2 Alternative Dispute Resolution

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our services

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A Legacy of Expertise & Experience

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why AAA?

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Latest

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 News

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Missing Layer in AI-Driven Commerce:…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AI Arbitrator

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Industry-Specific ADR

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our practice areas

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Democratizing Dispute Resolution through…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 InnovAAAtion

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Educational programs

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Have questions?

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Q&A

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 About Us

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Start Your Case

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Visit other AAA Sites

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Arbitration

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The World’s Leadin…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Alternative Dispute …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Our services	1.00:1	3.0:1	#000000	#000000	Fail
h2 A Legacy of Expertis…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Why AAA?	1.00:1	3.0:1	#000000	#000000	Fail
h2 The Latest	1.00:1	3.0:1	#000000	#000000	Fail
h2 News	1.00:1	3.0:1	#000000	#000000	Fail
h2 The Missing Layer in…	1.00:1	3.0:1	#000000	#000000	Fail
h2 AI Arbitrator	1.00:1	3.0:1	#000000	#000000	Fail
h2 Industry-Specific AD…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Our practice areas	1.00:1	3.0:1	#000000	#000000	Fail
h2 Democratizing Disput…	1.00:1	3.0:1	#000000	#000000	Fail
h2 InnovAAAtion	1.00:1	3.0:1	#000000	#000000	Fail
h2 Educational programs	1.00:1	3.0:1	#000000	#000000	Fail
h2 Have questions?	1.00:1	3.0:1	#000000	#000000	Fail
h2 Q&A	1.00:1	3.0:1	#000000	#000000	Fail
h2 About Us	1.00:1	3.0:1	#000000	#000000	Fail
h2 Start Your Case	1.00:1	3.0:1	#000000	#000000	Fail
h2 Visit other AAA Site…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Arbitration	1.00:1	3.0:1	#000000	#000000	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.

Heading Hierarchy

38 headings

PASS

38 headings

Single H1 present

3 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 The World’s Leading Provider of Dispute Solutions
H2 Alternative Dispute Resolution
H2 Our services
H3 Arbitration
H3 Mediation
H3 Online Dispute Resolution
H2 A Legacy of Expertise & Experience
H2 Why AAA?
H3 580,000 cases
H3 $29 billion
H3 Over 4,900
H3 3x faster
H2 The Latest
H2 News
H2 The Missing Layer in AI-Driven Commerce: A Trust Framework for Agentic Commerce Disputes
H3 New! AAAi Chatbook: Mediation Practice
H3 Governance Is the Key: How Legal Teams Are Learning to Move Fast Without Breaking Trust
H3 Trust Is the Product
H3 ODR.com Joins Court–Stanford Effort to Build Online Case Resolution System
H2 AI Arbitrator
H3 Use for a Simulated Decision or a Binding Award
H2 Industry-Specific ADR
H2 Our practice areas
H2 Democratizing Dispute Resolution through Innovation
H2 InnovAAAtion
H3 Technology Enhancements
H3 New Products and Services
H3 Advancing ADR Rules, Procedures, and Processes
H2 Educational programs
H3 Supporting the Education of Advocates and Panelists
H2 Have questions?
H2 Q&A
H3 (empty)
H3 (empty)
H3 (empty)
H2 About Us
H2 Start Your Case
H2 Visit other AAA Sites

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Method
#osano-cm-dialog-toggle--category_MARKETING	checkbox	none
#osano-cm-dialog-toggle--category_PERSONALIZATION	checkbox	none
#osano-cm-dialog-toggle--category_ANALYTICS	checkbox	none

A+

Link & Button Quality

5 links, 6 buttons — all OK

PASS

5 links, 6 buttons — all OK

1 link(s) open in new tab without warning

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

Got: /privacypolicy

4 link(s) with descriptive text

5 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/privacypolicy	Cookie Policy	new tab	Add '(opens in new tab)' to text

10 links and buttons have descriptive text

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

/privacypolicy

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

Favicon & Branding

7 icon(s) detected

PASS

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

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 26 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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
button.closed `button.closed`

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Targeted Advertising `div#a23cb917-6ce2-4862-bce9-fdd2a4dc1ef7 > div.osano-cm-dialog__content > ul.osano-cm-dialog__list > li.osano-cm-list__list-item`
Personalization `div#a23cb917-6ce2-4862-bce9-fdd2a4dc1ef7 > div.osano-cm-dialog__content > ul.osano-cm-dialog__list > li.osano-cm-list__list-item`
Analytics `div#a23cb917-6ce2-4862-bce9-fdd2a4dc1ef7 > div.osano-cm-dialog__content > ul.osano-cm-dialog__list > li.osano-cm-list__list-item`

These are opportunities to improve the experience of reading tabular or list data using 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
Arbitration `article.cardParent > a.hyperlink`
Mediation `article.cardParent > a.hyperlink`
Online Dispute Resolution `article.cardParent > a.hyperlink`

○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

●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

●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 are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

○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

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

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