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 3 REVIEW 4 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.

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 ✗

Link & Button Quality

3 issue(s) across 27 links and 2 buttons

REVIEW

3 issue(s) across 27 links and 2 buttons

3 link(s) with generic text

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

Got: https://www.google.com/ads/adtrafficquality/invalid-activity/ ("Learn More"); https://www.google.com/ads/adtrafficquality/how-we-prevent-it/ ("Learn More"); https://www.google.com/ads/adtrafficquality/what-you-can-do/ ("Learn More")

7 link(s) open in new tab without warning

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

Got: https://blog.google/products/ads-commerce/; https://twitter.com/GoogleAds; https://www.youtube.com/user/learnwithgoogle; https://policies.google.com/terms; https://policies.google.com/privacy; https://about.google/; https://about.google/products/

17 link(s) with descriptive text

27 links

0 empty

3 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.google.com/ads/adtrafficqual…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Invalid Activity
https://www.google.com/ads/adtrafficqual…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: How We Prevent It
https://www.google.com/ads/adtrafficqual…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: What You Can Do
https://blog.google/products/ads-commerc…	Follow us on blogger	new tab	Add '(opens in new tab)' to text
https://twitter.com/GoogleAds	Follow us on twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/learnwithgo…	Follow us on youtube	new tab	Add '(opens in new tab)' to text
https://policies.google.com/terms	Terms	new tab	Add '(opens in new tab)' to text
https://policies.google.com/privacy	Privacy	new tab	Add '(opens in new tab)' to text
https://about.google/	About Google	new tab	Add '(opens in new tab)' to text
https://about.google/products/	Google Products	new tab	Add '(opens in new tab)' to text

19 links and buttons have descriptive text

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

https://www.google.com/ads/adtrafficquality/invalid-activity/ ("Learn More"); https://www.google.com/ads/adtrafficquality/how-we-prevent-it/ ("Learn More"); https://www.google.com/ads/adtrafficquality/what-you-can-do/ ("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://blog.google/products/ads-commerce/; https://twitter.com/GoogleAds; https://www.youtube.com/user/learnwithgoogle; https://policies.google.com/terms; https://policies.google.com/privacy; https://about.google/; https://about.google/products/

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

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 Error 404 (Not Found)!!1 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Heading Hierarchy

5 headings, 1 skip(s)

PASS

5 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

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

H1 We protect you from invalid activity and advertising fraud
H4 We work hard to get you real results from advertising. skipped
H3 What is invalid activity?
H3 How does Google defend its ad systems against invalid activity?
H3 How can you prevent invalid activity?

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

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#lang-selector	select	Change language or region	for/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)

Element	Ratio	Required	FG	BG	Result
h1 We protect you from …	20.82:1	3.0:1	#000000	#FEFEFE	Pass
h3 What is invalid acti…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How does Google defe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How can you prevent …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Google Ad Traffic Qu…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Ads	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Traffic Quality	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Overview	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Invalid activity	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a How we prevent it	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a What you can do	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Resources for Advert…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Resources for Publis…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Ads	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Traffic Quality	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Overview	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Invalid activity	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a How we prevent it	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a What you can do	21.00:1	4.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 98/100 — 1 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We work hard to get you real results from advertising. `section.page > section.hero > div.center-column > h4.hero_description_heading`

These are opportunities to improve keyboard navigation in your application.

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

●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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○Image elements have `[alt]` attributes

○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

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