Skip to content
https://json.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
8
REVIEW
1
PASS
4
INFO
0
Checks
13
4 PASS 1 REVIEW 8 FIX
D
Landmark Structure
Action
No landmarks
FIX
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
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.

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

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
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 NOT FOUND ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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.
D
Lighthouse Accessibility Audits
Action
Score 67/100 — 4 failing, 9 passed
FIX
67

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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#spec > div#text > center > img div#spec > div#text > center > img
div#spec > div#text > center > img div#spec > div#text > center > img
div#spec > div#text > center > img div#spec > div#text > center > img
div#spec > div#text > center > img div#spec > div#text > center > img
div#spec > div#text > center > img div#spec > div#text > center > img
div#spec > div#text > center > img div#spec > div#text > center > 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.

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
العربية body > div > small > a
Български body > div > small > a
中文 body > div > small > a
Český body > div > small > a
Dansk body > div > small > a
Nederlands body > div > small > a
Esperanto body > div > small > a
Deutsch body > div > small > a
Ελληνικά body > div > small > a
עברית body > div > small > a
Magyar body > div > small > a
Indonesia body > div > small > a
Italiano body > div > small > a
日本 body > div > small > a
한국어 body > div > small > a
Norsk body > div > small > a
Polski body > div > small > a
Português body > div > small > a
Română body > div > small > a
Српско-хрватски body > div > small > a
Slovenščina body > div > small > a
Español body > div > small > a
Svenska body > div > small > a
Türkçe body > div > small > a
Українська body > div > small > a
Tiếng Việt body > div > small > a
JSON for ASP li > ul > li > a
JSON ASP utility class li > ul > li > a
JSON.awk li > ul > li > a
rhawk li > ul > li > a
mu_json li > ul > li > a
JSON_checker li > ul > li > a
YAJL li > ul > li > a
LibU li > ul > li > a
json-c li > ul > li > a
json-parser li > ul > li > a
jsonsl li > ul > li > a
WJElement li > ul > li > a
M's JSON parser li > ul > li > a
cJSON li > ul > li > a
Jansson li > ul > li > a
jsmn li > ul > li > a
parson li > ul > li > a
ujson4c li > ul > li > a
frozen li > ul > li > a
microjson li > ul > li > a
mjson li > ul > li > a
progbase li > ul > li > a
lwjson li > ul > li > a
cisson li > ul > li > a
nanoJSONc li > ul > li > a
JSON-BUILD li > ul > li > a
JSONKit li > ul > li > a
jsonme-- li > ul > li > a
ThorsSerializer li > ul > li > a
JsonBox li > ul > li > a
jvar li > ul > li > a
rapidjson li > ul > li > a
minijson li > ul > li > a
jsoncons li > ul > li > a
jsoncpp li > ul > li > a
univalue li > ul > li > a
jsovon li > ul > li > a
ArduinoJson li > ul > li > a
QJson li > ul > li > a
CAJUN li > ul > li > a
libjson li > ul > li > a
nosjob li > ul > li > a
qmjson li > ul > li > a
JSON Support in Qt li > ul > li > a
JsonWax for Qt li > ul > li > a
progbase li > ul > li > a
Qentem-Engine li > ul > li > a
fastJSON li > ul > li > a
JSON_checker li > ul > li > a
Json.NET li > ul > li > a
JSON for .NET li > ul > li > a
Manatee Json li > ul > li > a
FastJsonParser li > ul > li > a
LightJson li > ul > li > a
Liersch.Json li > ul > li > a
Liersch.JsonSerialization li > ul > li > a
progbase li > ul > li > a
JSON Essentials li > ul > li > a
std.json li > ul > li > a
asdf li > ul > li > a
Delphi Web Utils li > ul > li > a
JSON Delphi Library li > ul > li > a
json-fortran li > ul > li > a
YAJL-Fort li > ul > li > a
jsonff li > ul > li > a
RJson package li > ul > li > a
json package li > ul > li > a
JSON-java li > ul > li > a
esson li > ul > li > a
JSONUtil li > ul > li > a
jsonp li > ul > li > a
Json-lib li > ul > li > a
Stringtree li > ul > li > a
SOJO li > ul > li > a
json-taglib li > ul > li > a
Flexjson li > ul > li > a
Argo li > ul > li > a
jsonij li > ul > li > a
fastjson li > ul > li > a
mjson li > ul > li > a
jjson li > ul > li > a
json-simple li > ul > li > a
json-io li > ul > li > a
google-gson li > ul > li > a
FOSS Nova JSON li > ul > li > a
Corn CONVERTER li > ul > li > a
Apache johnzon li > ul > li > a
Genson li > ul > li > a
cookjson li > ul > li > a
progbase li > ul > li > a
jackson li > ul > li > a
MOXy li > ul > li > a
JSON li > ul > li > a
json2.js li > ul > li > a
clarinet li > ul > li > a
Oboe.js li > ul > li > a
progbase li > ul > li > a
JSONlab li > ul > li > a
20565 li > ul > li > a
23393 li > ul > li > a
NSJSONSerialization li > ul > li > a
json-framework li > ul > li > a
JSONKit li > ul > li > a
yajl-objc li > ul > li > a
TouchJSON li > ul > li > a
Public.Parser.JSON li > ul > li > a
Public.Parser.JSON2 li > ul > li > a
simplejson li > ul > li > a
pyson li > ul > li > a
Yajl-Py li > ul > li > a
ultrajson li > ul > li > a
metamagic.json li > ul > li > a
progbase li > ul > li > a
rjson li > ul > li > a
jsonlite li > ul > li > a
Serde JSON li > ul > li > a
json-rust li > ul > li > a
yajl-ruby li > ul > li > a
json-stream li > ul > li > a
progbase li > ul > li > a
MZScheme li > ul > li > a
JSON-struct li > ul > li > a
Jshon li > ul > li > a
JSON.sh li > ul > li > a
jwalk li > ul > li > a
VB-JSON li > ul > li > a
PW.JSON li > ul > li > a
progbase li > ul > li > a
fwJSON li > ul > li > a
JSON li > ul > li > a
vfpjson li > ul > li > a
Videos about JSON div > ul > li > a
Videos about the JSON Logo div > ul > li > a
Heresy & Heretical Open Source: A Heretic's Perspective div > ul > li > a
Nota Message Format div > ul > li > 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 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-hidden="true"]` is not present on the document `<body>`
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has a valid value for its `[lang]` attribute
○`<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">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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.
C
Alt Text Quality
Action
6 of 7 images have issues
REVIEW
6 of 7 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 image(s) with good alt text
7 images 1 good alt text 6 missing
IssueCount
missing6 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

A+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 Introducing JSON
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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
h1 Introducing JSON21.00:13.0:1
#000000
#FFFFFF
Pass
title JSON18.67:14.5:1
#000000
#FAF0E6
Pass
a العربية21.00:14.5:1
#000000
#FFFFFF
Pass
a Български21.00:14.5:1
#000000
#FFFFFF
Pass
a 中文19.58:14.5:1
#000000
#FCF6F0
Pass
a Český18.67:14.5:1
#000000
#FAF0E6
Pass
a Dansk18.67:14.5:1
#000000
#FAF0E6
Pass
a Nederlands18.67:14.5:1
#000000
#FAF0E6
Pass
a English18.67:14.5:1
#000000
#FAF0E6
Pass
a Esperanto18.67:14.5:1
#000000
#FAF0E6
Pass
a Français20.05:14.5:1
#000000
#FDF9F5
Pass
a Deutsch21.00:14.5:1
#000000
#FFFFFF
Pass
a Ελληνικά21.00:14.5:1
#000000
#FFFFFF
Pass
a עברית21.00:14.5:1
#000000
#FFFFFF
Pass
a Magyar21.00:14.5:1
#000000
#FFFFFF
Pass
a Indonesia21.00:14.5:1
#000000
#FFFFFF
Pass
a Italiano21.00:14.5:1
#000000
#FFFFFF
Pass
a 日本21.00:14.5:1
#000000
#FFFFFF
Pass
a 한국어21.00:14.5:1
#000000
#FFFFFF
Pass
a فارسی21.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