Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

18 PASS 4 REVIEW 2 FIX

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

Action

3 issue(s) across 54 links and 6 buttons

REVIEW

3 issue(s) across 54 links and 6 buttons

15 link(s) open in new tab without warning

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

Got: https://go.microsoft.com/fwlink/?LinkId=521839; https://aka.ms/3rdpartycookies; https://slack.engineering/typescript-at-slack-a81307fa288d; https://angular.io/; https://vuejs.org/; https://jestjs.io/; https://redux.js.org/; https://ionicframework.com/; https://probot.github.io/; https://deno.land/ (+5 more)

3 button(s) with no accessible text

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

Got: input[type="submit"] (#89 on page); button#language-recommendation-open; button#language-recommendation-no-more

39 link(s) with descriptive text

54 links

0 empty

0 generic text

15 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://go.microsoft.com/fwlink/?LinkId=…	Privacy Statement	new tab	Add '(opens in new tab)' to text
https://aka.ms/3rdpartycookies	Third-Party Cookies	new tab	Add '(opens in new tab)' to text
https://slack.engineering/typescript-at-…	Read	new tab	Add '(opens in new tab)' to text
https://angular.io/	Angular	new tab	Add '(opens in new tab)' to text
https://vuejs.org/	Vue	new tab	Add '(opens in new tab)' to text
https://jestjs.io/	Jest	new tab	Add '(opens in new tab)' to text
https://redux.js.org/	Redux	new tab	Add '(opens in new tab)' to text
https://ionicframework.com/	Ionic	new tab	Add '(opens in new tab)' to text
https://probot.github.io/	Probot	new tab	Add '(opens in new tab)' to text
https://deno.land/	Deno	new tab	Add '(opens in new tab)' to text
https://github.com/vercel/vercel	Vercel	new tab	Add '(opens in new tab)' to text
https://yarnpkg.com/	Yarn	new tab	Add '(opens in new tab)' to text
https://github.com/desktop/desktop/	GitHubDesktop	new tab	Add '(opens in new tab)' to text
https://insights.stackoverflow.com/surve…	Stack Overflow 2020 Developer …	new tab	Add '(opens in new tab)' to text
https://2020.stateofjs.com/en-US/technol…	2020 State of JS	new tab	Add '(opens in new tab)' to text
<input>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

42 links and buttons have descriptive text

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

https://go.microsoft.com/fwlink/?LinkId=521839; https://aka.ms/3rdpartycookies; https://slack.engineering/typescript-at-slack-a81307fa288d; https://angular.io/; https://vuejs.org/; https://jestjs.io/; https://redux.js.org/; https://ionicframework.com/; https://probot.github.io/; https://deno.land/ (+5 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

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

input[type="submit"] (#89 on page); button#language-recommendation-open; button#language-recommendation-no-more

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

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found · GitHub Pages ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

18 icon(s) detected

REVIEW

18 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 Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 #3178c6 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Skip link target(s) don't exist on page: #site-content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

15 headings

PASS

15 headings

Single H1 present

H1 TypeScript is JavaScript with syntax for types.
H2 What is TypeScript?
H3 JavaScript and More
H3 A Result You Can Trust
H3 Safety at Scale
H2 Get Started
H2 Adopt TypeScript Gradually
H3 Describe Your Data
H2 TypeScript becomes JavaScript via the delete key.
H2 TypeScript Testimonials
H3 Open Source with TypeScript
H2 Loved by Developers
H2 Get Started
H3 Using TypeScript
H3 Community

A+

Heading Text Quality

All 15 heading(s) have substantive, well-formed text

PASS

All 15 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search-box-top	search	Search the TypeScript site	aria-label
input	submit	(none)	none

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

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

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

2 form control(s) checked, no input-semantic issues

PASS

2 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

6 explicit tabindex attribute(s) checked, no anti-patterns

PASS

6 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 295 visible text node(s) render at >= 12 CSS pixels

PASS

All 295 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: TypeScript Documentation

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name TypeScript Documentation ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name TypeScript Documentation Display Mode standalone Theme Color #3178C6 Background Color white Icons 8 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

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)

Element	Ratio	Required	FG	BG	Result
h1 TypeScript is	4.63:1	3.0:1	#000000	#3178C6	Pass
h2 What is TypeScript?	4.63:1	3.0:1	#000000	#3178C6	Pass
h2 Get Started	4.63:1	3.0:1	#000000	#3178C6	Pass
h2 Adopt TypeScript Gra…	4.63:1	3.0:1	#000000	#3178C6	Pass
h2 TypeScript becomes J…	4.63:1	3.0:1	#000000	#3178C6	Pass
h2 TypeScript Testimoni…	4.63:1	3.0:1	#000000	#3178C6	Pass
h2 Loved by Developers	4.63:1	3.0:1	#000000	#3178C6	Pass
h2 Get Started	4.63:1	3.0:1	#000000	#3178C6	Pass
h3 JavaScript and More	4.63:1	3.0:1	#000000	#3178C6	Pass
h3 A Result You Can Tru…	4.63:1	3.0:1	#000000	#3178C6	Pass
h3 Safety at Scale	4.63:1	3.0:1	#000000	#3178C6	Pass
h3 Describe Your Data	4.63:1	3.0:1	#000000	#3178C6	Pass
h3 Open Source with Typ…	4.63:1	3.0:1	#000000	#3178C6	Pass
h3 Using TypeScript	4.63:1	3.0:1	#000000	#3178C6	Pass
h3 Community	4.63:1	3.0:1	#000000	#3178C6	Pass
title TypeScript: JavaScri…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
p We use optional cook…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Privacy Statement	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Third-Party Cookies	18.76:1	4.5:1	#000000	#F2F2F2	Pass
button Accept	18.76:1	4.5:1	#000000	#F2F2F2	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 28 passed

PASS

100

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.

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

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