Skip to content
https://ask.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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
A
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO footer
A
Heading Hierarchy
20 headings, 1 skip(s)
PASS
20 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Home
  • H3 Beyond Dogs and Cats: Famous Stars Who Opt for Extraordinary Pets skipped
  • H2 Question of the day
  • H2 Editorial Features
  • H3 10 Best Documentaries of 2022 — So Far
  • H3 20 Best Podcasts of 2022 — So Far
  • H3 20 Best Survival Horror Games to Play This Halloween
  • H3 The Best E-reader of 2022: Kindle Cloud Reader vs. Kindle Paperwhite
  • H3 “High School” Review: Tender, Indie Look at ‘90s Teens Tegan and Sara
  • H3 Headspace App 101: Is Headspace Worth It?
  • H3 13 Films That Capture Hispanic American Experiences
  • H3 World Mental Health Day: 12 Shows That Depict Mental Illness (Mostly) …
  • H2 latest articles
  • H2 Centro de preferências de privacidade
  • H3 Gerir preferências de cookies
  • H4 Cookies de publicidade
  • H4 Cookies estritamente necessários
  • H4 Cookies de funcionalidade
  • H4 Cookies de desempenho
  • H3 Lista de cookies

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+
Alt Text Quality
All 30 images OK
PASS
All 30 images OK
Info::
21 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
30 images 9 good alt text 21 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 9 controls labeled
PASS
All 9 controls labeled
Info::
9 control(s) properly labeled
9 controls
9 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtextSearcharia-label
#ot-group-id-C0004checkboxCookies de publicidadefor/id
#ot-group-id-C0003checkboxCookies de funcionalidadefor/id
#ot-group-id-C0002checkboxCookies de desempenhofor/id
#vendor-search-handlertextPesquisa de lista de cookiesaria-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
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 Home21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Question of the day21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Editorial Features21.00:13.0:1
#000000
#FFFFFF
Pass
h2 latest articles21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Centro de preferênc…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gerir preferências …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Lista de cookies21.00:13.0:1
#000000
#FFFFFF
Pass
title Ask.com - What's You…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content20.29:14.5:1
#000000
#FBFBFB
Pass
span Site Logo21.00:14.5:1
#000000
#FFFFFF
Pass
a Ask.com21.00:14.5:1
#000000
#FFFFFF
Pass
span Site Logo21.00:14.5:1
#000000
#FFFFFF
Pass
span TV & Movies21.00:14.5:1
#000000
#FFFFFF
Pass
span Awards Season21.00:14.5:1
#000000
#FFFFFF
Pass
span Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
span Spotlight21.00:14.5:1
#000000
#FFFFFF
Pass
span Streaming21.00:14.5:1
#000000
#FFFFFF
Pass
span News21.00:14.5:1
#000000
#FFFFFF
Pass
span Big Stories21.00:14.5:1
#000000
#FFFFFF
Pass
span Tech Talk21.00:14.5:1
#000000
#FFFFFF
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
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 21 passed
PASS
92

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ask Money div.footer_con > div > span > a
Reference div.footer_con > div > span > a
The Health Feed div.footer_con > div > span > a

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul > li#post-162292 > div.img-wrap > a ul > li#post-162292 > div.img-wrap > a
ul > li#post-157994 > div.img-wrap > a ul > li#post-157994 > div.img-wrap > a
ul > li#post-150050 > div.img-wrap > a ul > li#post-150050 > div.img-wrap > a
ul > li#post-164092 > div.img-wrap > a ul > li#post-164092 > div.img-wrap > a
ul > li#post-166487 > div.img-wrap > a ul > li#post-166487 > div.img-wrap > a
ul > li#post-166330 > div.img-wrap > a ul > li#post-166330 > div.img-wrap > a
ul > li#post-9398 > div.img-wrap > a ul > li#post-9398 > div.img-wrap > a
ul > li#post-15538 > div.img-wrap > a ul > li#post-15538 > div.img-wrap > a

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.

○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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Identical links have the same purpose.
○`[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
○`<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.
○No element has a `[tabindex]` value greater than 0
○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.
○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.

Send Feedback