Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

11 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 11 <nav> element(s)

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.

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 Learn the Latest Tech Skills; Advance Your Career | Udacity ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA

h1 Learn. Lead. Transform.

1.00:1

#000000

needs 3.0:1 (large text)

32px · top of page (header area)

h2 Skill development that drives results

1.23:1

#000000

#101D28

needs 3.0:1 (large text)

24px · above the fold

h2 Hands-on learning

1.81:1

#000000

#2D3A46

needs 3.0:1 (large text)

24px · mid-page

h2 Personalized support

1.07:1

#000000

#0A0B0F

needs 3.0:1 (large text)

24px · mid-page

h2 Measurable outcomes

1.07:1

#000000

#0A0B0F

needs 3.0:1 (large text)

24px · mid-page

p Build in-demand skills to unlock your po…

1.39:1

#000000

#321063

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a For Individuals

3.55:1

#000000

#8423F6

needs 4.5:1 (normal text)

16px · top of page (header area)

1 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
h1 Learn. Lead. Transfo…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Skill development th…	1.23:1	3.0:1	#000000	#101D28	Fail
h2 Hands-on learning	1.81:1	3.0:1	#000000	#2D3A46	Fail
h2 Personalized support	1.07:1	3.0:1	#000000	#0A0B0F	Fail
h2 Measurable outcomes	1.07:1	3.0:1	#000000	#0A0B0F	Fail
h2 Master the skills th…	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Trusted by the world…	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Success that speaks …	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Mentorship made for …	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Develop the skills t…	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Schools built for ev…	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Stay ahead of what's…	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Company	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Resources	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Udacity Schools	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Featured Programs	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h2 Only at Udacity	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 From tire shop techn…	19.95:1	3.0:1	#000000	#F9F9F9	Pass
p Build in-demand skil…	1.39:1	4.5:1	#000000	#321063	Fail
a For Individuals	3.55:1	4.5:1	#000000	#8423F6	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

34 landmarks

PASS

34 landmarks

<main> landmark present

11 <nav> landmark(s) found

All <nav> elements are properly labeled

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.

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

19 headings

PASS

19 headings

Single H1 present

H1 Learn. Lead. Transform.
H2 The MBA designed for AI product management
H2 Skill development that drives results
H2 Hands-on learning
H2 Personalized support
H2 Measurable outcomes
H2 Master the skills that matter most
H2 Trusted by the world's most innovative companies
H2 Success that speaks for itself
H3 From tire shop technician to business analyst
H2 Mentorship made for you
H2 Develop the skills that move the world forward.
H2 Schools built for every ambition
H2 Stay ahead of what's next
H2 Company
H2 Resources
H2 Udacity Schools
H2 Featured Programs
H2 Only at Udacity

A+

Alt Text Quality

All 112 images OK

PASS

All 112 images OK

76 decorative image(s) correctly marked

36 image(s) with good alt text

112 images 36 good alt text 76 decorative

All images have appropriate alt text.

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
#field-:R2ddaiknl6:	email	Submit your email to stay updated on the latest in technology	for/id

Link & Button Quality

134 links, 11 buttons — all OK

PASS

134 links, 11 buttons — all OK

10 link(s) open in new tab without warning

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

Got: https://udacity.com/blog; https://udacity.com/jobs; https://support.udacity.com/hc/en-us; https://udacity.com/blog; https://udacity.com/jobs; https://support.udacity.com/hc/en-us; https://www.facebook.com/Udacity; https://twitter.com/udacity; https://www.linkedin.com/school/udacity/; https://www.instagram.com/udacity/

124 link(s) with descriptive text

134 links

0 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://udacity.com/blog	Blog	new tab	Add '(opens in new tab)' to text
https://udacity.com/jobs	Jobs at Udacity	new tab	Add '(opens in new tab)' to text
https://support.udacity.com/hc/en-us	Help and FAQ	new tab	Add '(opens in new tab)' to text
https://udacity.com/blog	Blog	new tab	Add '(opens in new tab)' to text
https://udacity.com/jobs	Jobs at Udacity	new tab	Add '(opens in new tab)' to text
https://support.udacity.com/hc/en-us	Help and FAQ	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Udacity	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/udacity	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/udacity/	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/udacity/	Instagram	new tab	Add '(opens in new tab)' to text

135 links and buttons have descriptive text

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

https://udacity.com/blog; https://udacity.com/jobs; https://support.udacity.com/hc/en-us; https://udacity.com/blog; https://udacity.com/jobs; https://support.udacity.com/hc/en-us; https://www.facebook.com/Udacity; https://twitter.com/udacity; https://www.linkedin.com/school/udacity/; https://www.instagram.com/udacity/

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+

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

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

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

●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

●Uses ARIA roles only on compatible elements

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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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