Skip to content
https://audible.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 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-l7wh7n
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://audible.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://audible.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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 (missing!) MAIN ASIDE "Open Cookie Preferences Modal" 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

B
Favicon & Branding
7 icon(s) detected
REVIEW
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 23 passed
REVIEW
87

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Diseño de la portada del título La novia gitana adbl-style-scope.light > adbl-stack > adbl-product-featured-carousel > adbl-product-featured-slide
Diseño de la portada del título La red púrpura adbl-style-scope.light > adbl-stack > adbl-product-featured-carousel > adbl-product-featured-slide
Diseño de la portada del título El Niño que Perdió la Guerra adbl-style-scope.light > adbl-stack > adbl-product-featured-carousel > adbl-product-featured-slide
Diseño de la portada del título Terapia adbl-style-scope.light > adbl-stack > adbl-product-featured-carousel > adbl-product-featured-slide

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close notification banner div > div.bc-row-responsive > div.bc-col-responsive > a#notification-banner-close-button
El niño que vino del silencio de Thrity Umrigar, El misterio de la guía de ferr… adbl-stack > div.adbl-impression-emitted > adbl-two-column-hero > adbl-bookwall

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.

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.

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
Preferencias sobre cookies div.bc-row-responsive > div.bc-col-responsive > span#trustarclink > a#icon-id09569788421343545
○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
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●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
●No element has a `[tabindex]` value greater than 0
●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.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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
○Form elements have associated labels
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○`<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.
A+
Heading Hierarchy
32 headings
PASS
32 headings
Info::
Single H1 present
  • H1 Deja volar tu imaginación
  • H2 Tenemos lo que todos escuchan
  • H2 Explora nuevos mundos
  • H3 Literatura y ficción
  • H3 Biografías y memorias
  • H3 Romántica
  • H3 Policíaca, negra y suspense
  • H3 Desarrollo personal
  • H3 Salud y Bienestar
  • H3 Religión y Espiritualidad
  • H3 Negocios y profesiones
  • H3 Ciencia ficción y fantasía
  • H3 Política y ciencias sociales
  • H3 Audiolibros infantiles
  • H3 Dinero y finanzas
  • H2 Solo en Audible
  • H2 Encuentra lo que buscas
  • H2 Los miembros consiguen aún más
  • H3 Acceso ilimitado
  • H3 Escucha en cualquier parte
  • H3 Escucha sin anuncios
  • H2 Una app hecha a tu medida para escuchar
  • H3 Encuentra la velocidad ideal
  • H3 Configura un temporizador
  • H3 Escucha con el Modo Coche
  • H3 Escucha en cualquier momento y lugar
  • H2 Preguntas Frecuentes
  • H3 ¿Qué es Audible?
  • H3 ¿Cómo funciona la oferta de Amazon Prime?
  • H3 ¿Qué ocurre con mis audiolibros si cancelo mi suscripción?
  • H3 ¿Cómo puedo poner mi suscripción en pausa?
  • H3 ¿Necesitas más ayuda?
A+
Alt Text Quality
All 77 images OK
PASS
All 77 images OK
Info::
7 decorative image(s) correctly marked
Info::
70 image(s) with good alt text
77 images 70 good alt text 7 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#header-searchsearchnone
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Deja volar tu imagin…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Tenemos lo que todos…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Explora nuevos mundo…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Solo en Audible18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Encuentra lo que bus…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Los miembros consigu…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Una app hecha a tu m…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Preguntas Frecuentes18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Literatura y ficció…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Biografías y memori…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Romántica18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Policíaca, negra y …18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Desarrollo personal18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Salud y Bienestar18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Religión y Espiritu…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Negocios y profesion…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Ciencia ficción y f…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Política y ciencias…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Audiolibros infantil…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Dinero y finanzas18.10:13.0:1
#000000
#EEEEEE
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.

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

Send Feedback