Skip to content
https://nysed.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
No landmarks
REVIEW
No 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
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present

No landmarks detected

Screen reader users have no way to navigate by region.

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

B
Heading Hierarchy
22 headings, 1 skip(s)
REVIEW
22 headings, 1 skip(s)
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 New York State Education Department
  • H1 Latest News
  • H2 Featured Video
  • H2 Featured Story
  • H2 Featured Story
  • H1 Trending Topics duplicate H1
  • H1 Pre-K through Grade 12 Education duplicate H1
  • H2 Resources
  • H2 P-12 News
  • H1 Program Offices duplicate H1
  • H2 Higher Education
  • H2 Adult Ed & Vocational Services
  • H2 Office of the Professions
  • H1 Cultural Institutions duplicate H1
  • H2 Get the Latest Updates!
  • H5 Sign up skipped
  • H2 Popular Topics
  • H2 How do I…?
  • H2 Quick Links
  • H2 Media Center
  • H2 CONTACT US
  • H2 EMAIL CONTACTS

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

C
Form Accessibility
Action
5 of 5 controls have issues
REVIEW
5 of 5 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">
5 controls
0 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#goog-gt-votingInputSrcLangtext(none)none
#goog-gt-votingInputTrgLangtext(none)none
#goog-gt-votingInputSrcTexttext(none)none
#goog-gt-votingInputTrgTexttext(none)none
#goog-gt-votingInputVotetext(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found | New York State Education Department ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h2 New York State Education Department
1.31:1
#000000
on
#08233B
needs 3.0:1 (large text)
24px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Latest News21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Trending Topics21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Pre-K through Grade …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Program Offices21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Cultural Institution…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 New York State Educa…1.31:13.0:1
#000000
#08233B
Fail
h2 Featured Video21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Story21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Story21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h2 P-12 News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Higher Education21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Adult Ed & Vocationa…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Office of the Profes…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get the Latest Updat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Popular Topics21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How do I…?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Quick Links21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Media Center21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CONTACT US21.00:13.0: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.

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 6 failing, 18 passed
REVIEW
79

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Graduation Measures Initiative div#home-page-slider > div.flex-viewport > ul.slides > li.clone

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.html > a.element-invisible

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
SIGN UP div.panel-pane > div.pane-content > div.newsletter > h5.button-white

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.panel-pane > div.pane-content > div.sf-accordion-toggle > a#superfish-1-toggle div.panel-pane > div.pane-content > div.sf-accordion-toggle > a#superfish-1-toggle
div.panel-pane > div.pane-content > div.sf-accordion-toggle > a#superfish-3-toggle div.panel-pane > div.pane-content > div.sf-accordion-toggle > a#superfish-3-toggle

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.

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
Regionalization div.first > div.views-field > span.field-content > a

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.js html.js

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>`
●`[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.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent 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
○Deprecated ARIA roles were not used
○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
○`[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
○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
○`<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.
○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.
○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+
Alt Text Quality
All 27 images OK
PASS
All 27 images OK
Info::
4 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
27 images 23 good alt text 4 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback