Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

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

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Heading Hierarchy

10 headings

REVIEW

10 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Publish your passions, your way
H2 Choose the perfect design
H2 Get a domain
H2 Earn money
H2 Know your audience
H2 Hang onto your memories
H2 Join millions of others
H3 Help
H3 Community
H3 Developers

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Favicon & Branding

15 icon(s) detected

REVIEW

15 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 10 pass AA only

h3 Community

2.58:1

#000000

#19594D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Developers

2.58:1

#000000

#19594D

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Publish your passion…	5.29:1	3.0:1	#000000	#388D80	Pass
h2 Choose the perfect d…	5.29:1	3.0:1	#000000	#388D80	Pass
h2 Get a domain	5.29:1	3.0:1	#000000	#388D80	Pass
h2 Earn money	5.29:1	3.0:1	#000000	#388D80	Pass
h2 Know your audience	6.05:1	3.0:1	#000000	#479788	Pass
h2 Hang onto your memor…	5.29:1	3.0:1	#000000	#388D80	Pass
h2 Join millions of oth…	5.29:1	3.0:1	#000000	#388D80	Pass
h3 Help	7.77:1	3.0:1	#000000	#5EAB9B	Pass
h3 Community	2.58:1	3.0:1	#000000	#19594D	Fail
h3 Developers	2.58:1	3.0:1	#000000	#19594D	Fail
title Blogger.com - Create…	5.29:1	4.5:1	#000000	#388D80	Pass
a Skip to content	5.29:1	4.5:1	#000000	#388D80	Pass
span Sign in	5.29:1	4.5:1	#000000	#388D80	Pass
span Create your blog	5.29:1	4.5:1	#000000	#388D80	Pass
p Create a unique and …	5.29:1	4.5:1	#000000	#388D80	Pass
a Create your blog	5.29:1	4.5:1	#000000	#388D80	Pass
p Create a beautiful b…	5.29:1	4.5:1	#000000	#388D80	Pass
p Give your blog the p…	5.29:1	4.5:1	#000000	#388D80	Pass
p Get paid for your ha…	5.29:1	4.5:1	#000000	#388D80	Pass
p Find out which posts…	6.20:1	4.5:1	#000000	#48998B	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.

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

No <nav> landmark found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

1 of 42 images have issues

PASS

1 of 42 images have issues

1 image(s) with generic alt text

41 image(s) with good alt text

42 images 41 good alt text 1 generic

Issue	Count
generic	1 image(s)

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
#language-switch	select	Change language or region	aria-label

Link & Button Quality

16 links, 0 buttons — all OK

PASS

16 links, 0 buttons — all OK

9 link(s) open in new tab without warning

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

Got: /go/helpcenter; /go/helpforum; /go/tutorials; /go/buzz; /go/devapi; /go/devforum; /go/terms; /go/privacy; /go/contentpolicy

7 link(s) with descriptive text

16 links

0 empty

0 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/go/helpcenter	Help Center	new tab	Add '(opens in new tab)' to text
/go/helpforum	Help Forum	new tab	Add '(opens in new tab)' to text
/go/tutorials	Video Tutorials	new tab	Add '(opens in new tab)' to text
/go/buzz	Blogger Buzz	new tab	Add '(opens in new tab)' to text
/go/devapi	Blogger API	new tab	Add '(opens in new tab)' to text
/go/devforum	Developer Forum	new tab	Add '(opens in new tab)' to text
/go/terms	Terms of Service	new tab	Add '(opens in new tab)' to text
/go/privacy	Privacy	new tab	Add '(opens in new tab)' to text
/go/contentpolicy	Content Policy	new tab	Add '(opens in new tab)' to text

7 links and buttons have descriptive text

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

/go/helpcenter; /go/helpforum; /go/tutorials; /go/buzz; /go/devapi; /go/devforum; /go/terms; /go/privacy; /go/contentpolicy

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

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 21 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.

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
SIGN IN `div.header--content > div.header--buttons > a.sign-in > span`
Create a unique and beautiful blog easily. `main#maincontent > section.section > header.hero--header > p`
CREATE YOUR BLOG `main#maincontent > section.section > header.hero--header > a.cta`
Choose the perfect design `section#choose-design > header > div > h2`
Create a beautiful blog that fits your style. Choose from a selection of easy-t… `section#choose-design > header > div > p`
Get paid for your hard work. Google AdSense can automatically display relevant … `section.section > header > div > p`
Whether sharing your expertise, breaking news, or whatever’s on your mind, you’… `main#maincontent > section.section > header.millions--header > p`

These are opportunities to improve the legibility of your content.

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
Help Center `section > ul > li > a.ga-footer`
Help Forum `section > ul > li > a.ga-footer`

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

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

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

●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

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

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○Buttons have an accessible name

○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

○Links are distinguishable without relying on color.

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

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