Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 1 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: LinkedIn

No 192x192 icon

A 192px icon is required for PWA installation.

PWA Install Criteria Not Installable

Name LinkedIn ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗

Name LinkedIn

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 ✗

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title LinkedIn ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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+

Heading Hierarchy

17 headings

PASS

17 headings

Single H1 present

H1 Discover new opportunities
H2 Explore top LinkedIn content
H2 Find the right job or internship for you
H2 Post your job for millions of people to see
H2 Discover the best software tools
H2 Keep your mind sharp with games
H2 Let the right people know you’re open to work
H2 Conversations today could lead to opportunity tomorrow
H2 Stay up to date on your industry
H2 Connect with people who can help
H2 Learn the skills you need to succeed
H2 Who is LinkedIn for?
H2 Join your colleagues, classmates, and friends on LinkedIn
H3 General
H3 Browse LinkedIn
H3 Business Solutions
H3 Directories

Alt Text Quality

1 of 8 images have issues

PASS

1 of 8 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

5 decorative image(s) correctly marked

2 image(s) with good alt text

8 images 2 good alt text 5 decorative 1 missing

Issue	Count
missing	1 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+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

161 links, 42 buttons — all OK

PASS

161 links, 42 buttons — all OK

6 link(s) open in new tab without warning

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

Got: /legal/user-agreement?trk=linkedin-tc_auth-button_user-agreement; /legal/privacy-policy?trk=linkedin-tc_auth-button_privacy-policy; /legal/cookie-policy?trk=linkedin-tc_auth-button_cookie-policy; /legal/user-agreement?trk=linkedin-tc_auth-button_user-agreement; /legal/privacy-policy?trk=linkedin-tc_auth-button_privacy-policy; /legal/cookie-policy?trk=linkedin-tc_auth-button_cookie-policy

155 link(s) with descriptive text

161 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/legal/user-agreement?trk=linkedin-tc_au…	User Agreement	new tab	Add '(opens in new tab)' to text
/legal/privacy-policy?trk=linkedin-tc_au…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/legal/cookie-policy?trk=linkedin-tc_aut…	Cookie Policy	new tab	Add '(opens in new tab)' to text
/legal/user-agreement?trk=linkedin-tc_au…	User Agreement	new tab	Add '(opens in new tab)' to text
/legal/privacy-policy?trk=linkedin-tc_au…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/legal/cookie-policy?trk=linkedin-tc_aut…	Cookie Policy	new tab	Add '(opens in new tab)' to text

197 links and buttons have descriptive text

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

/legal/user-agreement?trk=linkedin-tc_auth-button_user-agreement; /legal/privacy-policy?trk=linkedin-tc_auth-button_privacy-policy; /legal/cookie-policy?trk=linkedin-tc_auth-button_cookie-policy; /legal/user-agreement?trk=linkedin-tc_auth-button_user-agreement; /legal/privacy-policy?trk=linkedin-tc_auth-button_privacy-policy; /legal/cookie-policy?trk=linkedin-tc_auth-button_cookie-policy

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

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 Discover new opportu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore top LinkedIn…	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Find the right job o…	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Post your job for mi…	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Discover the best so…	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Keep your mind sharp…	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Let the right people…	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Conversations today …	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Stay up to date on y…	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Connect with people …	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Learn the skills you…	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Who is LinkedIn for?	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h2 Join your colleagues…	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h3 General	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h3 Browse LinkedIn	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h3 Business Solutions	18.77:1	3.0:1	#000000	#F3F2F0	Pass
h3 Directories	18.77:1	3.0:1	#000000	#F3F2F0	Pass
title LinkedIn: Log In or …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Agree & Join LinkedI…	21.00:1	4.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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 30 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

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

●`button`, `link`, and `menuitem` elements have accessible names

●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

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

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

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