Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 6 REVIEW 4 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-6exuxm

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://web.app/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://web.app/manifest.json

Manifest contains invalid JSON.

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

12 landmarks

REVIEW

12 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

7 <nav> landmark(s) found

1 of 7 <nav> elements are unlabeled

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

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Alt Text Quality

Action

4 of 11 images have issues

REVIEW

4 of 11 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 decorative image(s) correctly marked

6 image(s) with good alt text

11 images 6 good alt text 1 decorative 4 missing

Issue	Count
missing	4 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Link & Button Quality

3 issue(s) across 169 links and 14 buttons

REVIEW

3 issue(s) across 169 links and 14 buttons

3 link(s) with generic text

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

Got: /docs/hosting/web-request-logs-and-metrics ("Read more"); /docs/hosting/github-integration ("Read more"); /docs/hosting/i18n-rewrites ("Read more")

2 link(s) open in new tab without warning

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

Got: https://policies.google.com/technologies/cookies?hl=en; https://genkit.dev/

164 link(s) with descriptive text

169 links

0 empty

3 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://policies.google.com/technologies…	Learn more about how Google us…	new tab	Add '(opens in new tab)' to text
/docs/hosting/web-request-logs-and-metri…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Web Request Logs And Metrics
/docs/hosting/github-integration	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Github Integration
/docs/hosting/i18n-rewrites	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: I18n Rewrites
https://genkit.dev/	Genkit	new tab	Add '(opens in new tab)' to text

178 links and buttons have descriptive text

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

/docs/hosting/web-request-logs-and-metrics ("Read more"); /docs/hosting/github-integration ("Read more"); /docs/hosting/i18n-rewrites ("Read 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://policies.google.com/technologies/cookies?hl=en; https://genkit.dev/

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

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #a8c7fa ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA

span firebase.google.com uses cookies from Go…

1.26:1

#000000

#1E1E1E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Learn more

1.26:1

#000000

#1E1E1E

needs 4.5:1 (normal text)

16px · top of page (header area)

button OK, got it

1.26:1

#000000

#1E1E1E

needs 4.5:1 (normal text)

16px · above the fold

a Build

1.26:1

#000000

#1E1E1E

needs 4.5:1 (normal text)

16px · above the fold

li Build

1.26:1

#000000

#1E1E1E

needs 4.5:1 (normal text)

16px · above the fold

li Get to market quickly and securely with …

1.26:1

#000000

#1E1E1E

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Fast, secure hosting…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h2 Optimized for static…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Fast and secure, out…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Preview and share ch…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Multiple frameworks,…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Start now, and pay a…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Learn to do more wit…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Documentation	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Pricing	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Learn	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Stay connected	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Support	18.33:1	3.0:1	#000000	#E8F0FE	Pass
title Firebase Hosting \| F…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	8.53:1	4.5:1	#000000	#A5A5A5	Pass
span firebase.google.com …	1.26:1	4.5:1	#000000	#1E1E1E	Fail
a Learn more	1.26:1	4.5:1	#000000	#1E1E1E	Fail
button OK, got it	1.26:1	4.5:1	#000000	#1E1E1E	Fail
a Build	1.26:1	4.5:1	#000000	#1E1E1E	Fail
li Build	1.26:1	4.5:1	#000000	#1E1E1E	Fail
li Get to market quickl…	1.26:1	4.5:1	#000000	#1E1E1E	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.

A+

Heading Hierarchy

16 headings

PASS

16 headings

Single H1 present

H5 Firebase Hosting
H1 Fast, secure hosting for static websites
H2 Optimized for static and single-page web apps. Deploy static websites in seconds using a global CDN. Preview, deploy, and roll back with the Firebase CLI.
H3 Fast and secure, out of the box
H3 Preview and share changes
H3 Multiple frameworks, one command
H3 Start now, and pay as you go
H3 Learn to do more with Hosting
H3 Documentation
H3 Pricing
H4 All Firebase products
H5 Build
H5 Run
H3 Learn
H3 Stay connected
H3 Support

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	Search	aria-label
input	text	Type to filter	aria-label

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 29 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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.side-side-wrapper__right-container > div.content > div.content__illo > img `div.side-side-wrapper__right-container > div.content > div.content__illo > img`
div.side-side-wrapper__left-container > div.content > div.content__illo > img `div.side-side-wrapper__left-container > div.content > div.content__illo > img`
div.side-side-wrapper__right-container > div.content > div.content__illo > img `div.side-side-wrapper__right-container > div.content > div.content__illo > img`
div.side-side-wrapper__left-container > div.content > div.content__illo > img `div.side-side-wrapper__left-container > div.content > div.content__illo > img`

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

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

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

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

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

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