Skip to content
https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8?form_factor=desktop

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
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 header MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8?form_factor=desktop/_/PagespeedUi/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8?form_factor=desktop/_/PagespeedUi/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
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Alt Text Quality
16 of 76 images have issues
REVIEW
16 of 76 images have issues
Warning::
16 image(s) with filename as alt text
Info::
56 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
76 images 4 good alt text 56 decorative 16 generic
IssueCount
filename16 image(s)
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
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 ✗
B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 23 passed
REVIEW
83

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#kO001e > span.yTTzpb > div.VfPpkd-dgl2Hf-ppHlrf-sM5MNb > button.VfPpkd-LgbsSe header#kO001e > span.yTTzpb > div.VfPpkd-dgl2Hf-ppHlrf-sM5MNb > button.VfPpkd-LgbsSe

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.

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
https://accounts.google.com/v3/signin/identifier?continue= div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
%3D1*18jxoze*_up*MQ..%26gclid%3DCjwKCAjwhZDUBhBGEiwAbi5bjoetsyty1ASr_fSL6o5Qwbl… div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
https://aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044?_gl%3D div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
%26 div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
%3D div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
%26 div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
%3D div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
%26 div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
%3Dtrue&passive div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
1209600&flowName=GlifWebSignIn&flowEn div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
y=S div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad
rviceLogin&dsh=S-518547135:1787240865721924 div.YjemHe > div.RtY7Qc > span.h1llh > span.Toa1ad

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
record a trace div.lh-perf-audits > div.lh-audit-group > span.lh-audit-group__description > a
directly affect div.lh-perf-audits > div.lh-audit-group > span.lh-audit-group__description > a
conducting an accessibility review div#accessibility > div.lh-audit-group > span.lh-audit-group__description > a

These are opportunities to improve the legibility of your content.

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●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
●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
●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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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.
○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.
A+
Heading Text Quality
No headings to evaluate -- check is N/A
PASS
No headings to evaluate -- check is N/A
Info::
No headings to evaluate -- check is N/A
A+
Form Accessibility
All 33 controls labeled
PASS
All 33 controls labeled
Info::
33 control(s) properly labeled
33 controls
33 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#i2textnone
#c19checkboxToggle the display of histogram breakdownsaria-label
#c22checkboxToggle the display of histogram breakdownsaria-label
#lh-metrics-toggle0checkboxToggle the display of metric descriptionsaria-label
#metric-All-3radioAllfor/id
#metric-FCP-3radioFCPfor/id
#metric-LCP-3radioLCPfor/id
#metric-TBT-3radioTBTfor/id
#metric-CLS-3radioCLSfor/id
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
#c25checkboxToggle the display of histogram breakdownsaria-label
#c28checkboxToggle the display of histogram breakdownsaria-label
#lh-metrics-toggle4checkboxToggle the display of metric descriptionsaria-label
#metric-All-8radioAllfor/id
#metric-FCP-8radioFCPfor/id
#metric-LCP-8radioLCPfor/id
#metric-TBT-8radioTBTfor/id
#metric-CLS-8radioCLSfor/id
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
A+
Form Input Types
33 form control(s) checked, no type mismatches
PASS
33 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
33 form control(s) checked, no input-semantic issues
PASS
33 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="mobile_tab">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 13 visible text node(s) render at >= 12 CSS pixels
PASS
All 13 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
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
div PageSpeed Insights21.00:14.5:1
#000000
#FFFFFF
Pass
span Copy Link21.00:14.5:1
#000000
#FFFFFF
Pass
span Docs21.00:14.5:1
#000000
#FFFFFF
Pass
title PageSpeed Insights21.00:14.5:1
#000000
#FFFFFF
Pass
span This site uses cooki…21.00:14.5:1
#000000
#FFFFFF
Pass
span Learn More.21.00:14.5:1
#000000
#FFFFFF
Pass
span Ok, Got it.21.00:14.5:1
#000000
#FFFFFF
Pass
div Report from Aug 20, …21.00:14.5:1
#000000
#FFFFFF
Pass
p Enter a valid URL21.00:14.5:1
#000000
#FFFFFF
Pass
span Analyze21.00:14.5:1
#000000
#FFFFFF
Pass
i smartphone21.00:14.5:1
#000000
#FFFFFF
Pass
span Mobile21.00:14.5:1
#000000
#FFFFFF
Pass
i computer21.00:14.5:1
#000000
#FFFFFF
Pass
span Desktop21.00:14.5:1
#000000
#FFFFFF
Pass
span Showing results for …21.00:14.5:1
#000000
#FFFFFF
Pass
span https://accounts.goo…21.00:14.5:1
#000000
#FFFFFF
Pass
span https://aistudio.goo…21.00:14.5:1
#000000
#FFFFFF
Pass
span %3D21.00:14.5:1
#000000
#FFFFFF
Pass
span 1*18jxoze*_up*MQ..21.00:14.5:1
#000000
#FFFFFF
Pass
span %2621.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.

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

Send Feedback