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

2 issue(s) across 59 links and 38 buttons

REVIEW

2 issue(s) across 59 links and 38 buttons

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.nyc-navigation__scrim-close-button (#121 on page); button.nyc-navigation__scrim-close-button (#140 on page)

59 link(s) with descriptive text

59 links

0 empty

0 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

95 links and buttons have descriptive text

Icon-only buttons need an aria-label so screen readers can announce them.

button.nyc-navigation__scrim-close-button (#121 on page); button.nyc-navigation__scrim-close-button (#140 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

HTTP 490, custom page

REVIEW

HTTP 490, custom page

Unexpected status code: HTTP 490

Expected HTTP 404 but received 490. This may confuse search engine crawlers.

Got: HTTP 490

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 490 ✗Page Title NYC ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Favicon & Branding

6 icon(s) detected

REVIEW

6 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, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA

title Official Website of New York City Govern…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Official website. How you know

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

p A .gov website belongs to an official go…

4.26:1

#000000

#7B704B

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p A lock (🔒) or https:// means you’ve…

2.69:1

#000000

#654F1F

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Latest News	9.23:1	3.0:1	#000000	#BEAC57	Pass
h2 Popular services	9.23:1	3.0:1	#000000	#BEAC57	Pass
h2 311	9.23:1	3.0:1	#000000	#BEAC57	Pass
h2 Upcoming events	9.23:1	3.0:1	#000000	#BEAC57	Pass
h2 What's new from NYC …	9.23:1	3.0:1	#000000	#BEAC57	Pass
h2 Benefit programs for…	9.23:1	3.0:1	#000000	#BEAC57	Pass
h3 Top languages	9.23:1	3.0:1	#000000	#BEAC57	Pass
h3 More languages	9.23:1	3.0:1	#000000	#BEAC57	Pass
h3 Find voting dates an…	9.23:1	3.0:1	#000000	#BEAC57	Pass
h3 Child care map	9.23:1	3.0:1	#000000	#BEAC57	Pass
h3 Register to get comp…	9.23:1	3.0:1	#000000	#BEAC57	Pass
h3 Learn about vaccinat…	9.23:1	3.0:1	#000000	#BEAC57	Pass
h3 More on nyc.gov	9.23:1	3.0:1	#000000	#BEAC57	Pass
title Official Website of …	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to main content	1.00:1	4.5:1	#000000	#000000	Fail
span Official website. Ho…	1.00:1	4.5:1	#000000	#000000	Fail
b Official websites us…	6.63:1	3.0:1	#000000	#99916D	Pass
p A .gov website belon…	4.26:1	4.5:1	#000000	#7B704B	Fail
b Secure .gov websites…	4.79:1	3.0:1	#000000	#847942	Pass
p A lock (🔒) or htt…	2.69:1	4.5:1	#000000	#654F1F	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.

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

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

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

28 headings, 1 skip(s)

PASS

28 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H4 Official website. How you know
H5 Official websites use .gov
H5 Secure .gov websites use HTTPS
H2 NYC
H3 Top languages
H3 More languages
H2 NYC
H1 Find what you need on nyc.gov
H3 Tuesday,April 21, 2026 skipped
H4 Alternate side parking
H4 Trash, recycling, and compost collection
H4 Public schools
H4 Check transit alerts
H2 Latest News
H2 Popular services
H2 311
H2 Upcoming events
H2 What's new from NYC government?
H3 Special Election
H3 Find voting dates and hours
H3 Child care map
H3 Child care map
H3 Compost Giveback Season
H3 Register to get compost
H3 Childhood Vaccines
H3 Learn about vaccination
H2 Benefit programs for you
H3 More on nyc.gov

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

All 14 images OK

PASS

All 14 images OK

1 image(s) with alt text over 125 characters

7 decorative image(s) correctly marked

6 image(s) with good alt text

14 images 6 good alt text 7 decorative

Issue	Count
too long	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
#filter	text	Filter languages	for/id

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 23 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
Tuesday, April 21, 2026 `div#nycgov-status > section.pane > div.pane--header > h3`

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

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

●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

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

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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