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

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

2 headings

REVIEW

2 headings

No H1 heading found

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

H2 Try Dart in your browser
H3 Want more practice? Learn the language, explore the core libraries, or build a command-line app.

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

Link & Button Quality

Action

3 issue(s) across 200 links and 34 buttons

REVIEW

3 issue(s) across 200 links and 34 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

2 link(s) with generic text

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

Got: https://policies.google.com/technologies/cookies ("Learn more"); https://blog.dart.dev/announcing-dart-3-11-b6529be4203a ("Learn more")

14 link(s) open in new tab without warning

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

Got: https://codelabs.developers.google.com/codelabs/dart-patterns-records; https://docs.flutter.dev/ai/mcp-server; https://genkit.dev/docs/dart/get-started/; https://blog.dart.dev; https://api.dart.dev; https://dartpad.dev; https://flutter.dev; https://pub.dev; https://blog.dart.dev; https://github.com/dart-lang (+4 more)

183 link(s) with descriptive text

200 links

1 empty

2 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://policies.google.com/technologies…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Cookies
https://codelabs.developers.google.com/c…	Applied tutorialopen_in_new	new tab	Add '(opens in new tab)' to text
https://docs.flutter.dev/ai/mcp-server	Dart and Flutter MCP serverope…	new tab	Add '(opens in new tab)' to text
https://genkit.dev/docs/dart/get-started…	Genkit for Dartopen_in_new	new tab	Add '(opens in new tab)' to text
https://blog.dart.dev	Dart Blogopen_in_new	new tab	Add '(opens in new tab)' to text
https://api.dart.dev	API referenceopen_in_new	new tab	Add '(opens in new tab)' to text
https://dartpad.dev	DartPad (online editor)open_in…	new tab	Add '(opens in new tab)' to text
https://flutter.dev	Flutteropen_in_new	new tab	Add '(opens in new tab)' to text
https://pub.dev	Package siteopen_in_new	new tab	Add '(opens in new tab)' to text
https://blog.dart.dev/announcing-dart-3-…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Announcing Dart 3 11 B6529be4203a
	(empty)	empty	Add link text or aria-label
https://blog.dart.dev	Dart's Medium publication	new tab	Add '(opens in new tab)' to text
https://github.com/dart-lang	Dart's GitHub organization	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/dart.dev	Dart's Bluesky (Twitter) profi…	new tab	Add '(opens in new tab)' to text
https://twitter.com/dart_lang	Dart's X (Twitter) profile	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://jaspr.site	This site is built with the Ja…	new tab	Add '(opens in new tab)' to text

217 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://policies.google.com/technologies/cookies ("Learn more"); https://blog.dart.dev/announcing-dart-3-11-b6529be4203a ("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://codelabs.developers.google.com/codelabs/dart-patterns-records; https://docs.flutter.dev/ai/mcp-server; https://genkit.dev/docs/dart/get-started/; https://blog.dart.dev; https://api.dart.dev; https://dartpad.dev; https://flutter.dev; https://pub.dev; https://blog.dart.dev; https://github.com/dart-lang (+4 more)

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

5 icon(s) detected

REVIEW

5 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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 Try Dart in your browser

1.40:1

#000000

#202731

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Want more practice?

1.40:1

#000000

#202731

needs 3.0:1 (large text)

19px · bottom of viewport

h3 , explore the

1.40:1

#000000

#202731

needs 3.0:1 (large text)

19px · bottom of viewport

h3 , or

1.40:1

#000000

#202731

needs 3.0:1 (large text)

19px · bottom of viewport

title Dart programming language

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · top of page (header area)

p dart.dev uses cookies from Google to del…

2.21:1

#000000

#134488

needs 4.5:1 (normal text)

16px · top of page (header area)

a Learn more

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · top of page (header area)

button OK, got it

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · above the fold

span Dart

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · above the fold

a Overview

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · above the fold

span Docs

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · above the fold

a Blog

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · above the fold

a Community

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · above the fold

a Learn

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · above the fold

a Try Dart

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · above the fold

a Get Dart

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · above the fold

span search

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · mid-page

span apps

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · mid-page

span Dart

1.40:1

#000000

#1C2834

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Try Dart in your bro…	1.40:1	3.0:1	#000000	#202731	Fail
h3 Want more practice?	1.40:1	3.0:1	#000000	#202731	Fail
h3 , ex…	1.40:1	3.0:1	#000000	#202731	Fail
h3 , or	1.40:1	3.0:1	#000000	#202731	Fail
title Dart programming lan…	1.40:1	4.5:1	#000000	#1C2834	Fail
a Skip to main content	1.40:1	4.5:1	#000000	#1C2834	Fail
p dart.dev uses cookie…	2.21:1	4.5:1	#000000	#134488	Fail
a Learn more	1.40:1	4.5:1	#000000	#1C2834	Fail
button OK, got it	1.40:1	4.5:1	#000000	#1C2834	Fail
span Dart	1.40:1	4.5:1	#000000	#1C2834	Fail
a Overview	1.40:1	4.5:1	#000000	#1C2834	Fail
span Docs	1.40:1	4.5:1	#000000	#1C2834	Fail
a Blog	1.40:1	4.5:1	#000000	#1C2834	Fail
a Community	1.40:1	4.5:1	#000000	#1C2834	Fail
a Learn	1.40:1	4.5:1	#000000	#1C2834	Fail
a Try Dart	1.40:1	4.5:1	#000000	#1C2834	Fail
a Get Dart	1.40:1	4.5:1	#000000	#1C2834	Fail
span search	1.40:1	4.5:1	#000000	#1C2834	Fail
span apps	1.40:1	4.5:1	#000000	#1C2834	Fail
span Dart	1.40:1	4.5:1	#000000	#1C2834	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+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

17 image(s) with good alt text

17 images 17 good alt text

All images have appropriate alt text.

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	search	Search	aria-label
#search-side	search	Search	aria-label

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 25 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

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to main content `body.homepage > a#skip-to-main`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Dart `body.homepage > header#site-header > nav.navbar > a#site-primary-logo`

○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

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

●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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Heading elements appear in a sequentially-descending order

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

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

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