Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 14 -1-on-focusable

FIX

0 positive, 14 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

D

Favicon & Branding

Action

3 icon(s) detected

FIX

3 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

D

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 4 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

C

Heading Hierarchy

Action

38 headings, 1 skip(s)

REVIEW

38 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Explore Get Started
H2 Stay Updated
H2 Explore Platforms
H2 Featured
H2 Explore Technologies
H2 Featured
H2 Explore Community
H2 Featured
H2 Explore Documentation
H2 Release Notes
H2 Explore Downloads
H2 Featured
H2 Explore Support
H2 Featured
H2 Quick Links
H3 Sign up for Meet with Apple events
H3 Latest videos
H3 Top WWDC26 picks. Videos, events, and articles for you.
H3 For you
H2 Discover agentic coding in Xcode 26.3
H3 iOS 27
H3 iPadOS 27
H3 macOS 27
H3 tvOS 27
H3 visionOS 27
H3 watchOS 27
H2 What’s new for Apple developers
H2 Apple Developer Program
H5 Join the Apple Developer Program to reach customers around the world on the App Store for iPhone, iPad, Mac, Apple Watch, Apple TV, and Apple Vision Pro. You’ll also get access to beta software, adv skipped
H2 Developer Footer
H3 Platforms
H3 Tools
H3 Technologies
H3 Resources
H3 Support
H3 Account
H3 Programs
H3 Events

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

B

Link & Button Quality

8 issue(s) across 228 links and 19 buttons

REVIEW

8 issue(s) across 228 links and 19 buttons

8 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /account; https://appstoreconnect.apple.com; /account/resources/; /events/view/my-events; https://feedbackassistant.apple.com; /forums/; /logout/; /programs/

220 link(s) with descriptive text

228 links

8 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/account	(empty)	empty	Add link text or aria-label
https://appstoreconnect.apple.com	(empty)	empty	Add link text or aria-label
/account/resources/	(empty)	empty	Add link text or aria-label
/events/view/my-events	(empty)	empty	Add link text or aria-label
https://feedbackassistant.apple.com	(empty)	empty	Add link text or aria-label
/forums/	(empty)	empty	Add link text or aria-label
/logout/	(empty)	empty	Add link text or aria-label
/videos/play/wwdc2026/259/	Xcode, agents, and you	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/258/	What’s new in Xcode 27	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/269/	What’s new in SwiftUI	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/287/	Build next generation experien…	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/250/	Principles of great design	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/233/	Explore distributed inference …	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/212/	Rev up your CarPlay app	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/356/	Bringing Cyberpunk 2077 to M…	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/326/	Integrate on-device AI models …	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/324/	Meet Core AI	img no alt	Add alt attribute to the image
/videos/play/wwdc2026/232/	Run local agentic AI on the Ma…	img no alt	Add alt attribute to the image
/xcode/	Discover agentic coding in Xco…	img no alt	Add alt attribute to the image
/whats-new/	What’s new for Apple develop…	img no alt	Add alt attribute to the image
/programs/	(empty)	empty	Add link text or aria-label

239 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/account; https://appstoreconnect.apple.com; /account/resources/; /events/view/my-events; https://feedbackassistant.apple.com; /forums/; /logout/; /programs/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

B

Tap Target Adequacy

1 tap target(s) too small or too close together

REVIEW

1 tap target(s) too small or too close together

1 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

B

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 - Apple Developer ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 Explore Get Started

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Explore Get Started	1.00:1	3.0:1	#000000	#000000	Fail
h2 Stay Updated	8.02:1	3.0:1	#000000	#10A8FB	Pass
h2 Explore Platforms	5.07:1	3.0:1	#000000	#1877FB	Pass
h2 Featured	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Explore Technologies	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Featured	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Explore Community	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Featured	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Explore Documentatio…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Release Notes	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Explore Downloads	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Featured	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Explore Support	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Featured	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Quick Links	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Discover agentic cod…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 What’s new for App…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Apple Developer Prog…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Developer Footer	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 Sign up for Meet wit…	19.29:1	3.0:1	#000000	#F5F5F7	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 — 8 failing, 25 passed

REVIEW

79

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Download now Xcode 27 beta Bring your ideas to life faster using coding agents… `div#media-card-gallery > div.media-gallery-wrapper > div.gallery > ul.card-set`

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Download now Xcode 27 beta Bring your ideas to life faster using coding agents… `section#priority-router > div#media-card-gallery > div.media-gallery-wrapper > div.gallery`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
September 8-9, 2026 · Online appointment `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
September 10-11, 2026 · Online appointment `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
September 15-16, 2026 · Online appointment `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
September 17-18, 2026 · Online appointment `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
September 23, 2026 · Online appointment `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
October 7, 2026 · Online session `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
October 7-8, 2026 · In-person session `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
October 7, 2026 · Online appointment `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
October 19, 2026 · Online appointment `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
October 29, 2026 · Online session `ul.sc-gallery__card-set > li.sc-gallery__item > a.sc-gallery__card > p.pc-card__gl-datetime`
Read the latest news. Get the Apple Developer app. Follow us on bilibili, Linke… `div.footer-content > section.footer-mini > div.footer-mini-news > div.copy`
Read the latest news. `section.footer-mini > div.footer-mini-news > div.copy > div.footer-mini-legal-link`
Get the Apple Developer app. `section.footer-mini > div.footer-mini-news > div.copy > div.footer-mini-legal-link`
Light `div.content > div.color-scheme-toggle > label > div.text`
Dark `div.content > div.color-scheme-toggle > label > div.text`
Copyright © 2026 Apple Inc. All rights reserved. `div.footer-content > section.footer-mini > div.footer-mini-legal > div.footer-mini-legal-copyright`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Apple Inc. `section.footer-mini > div.footer-mini-legal > div.footer-mini-legal-copyright > a`

These are opportunities to improve the legibility of your content.

Navigation

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
App Review appointment `li.sc-gallery__item > a.sc-gallery__card > div.pc-card__gl-top > h5.pc-card__title`
Join the Apple Developer Program to reach customers around the world on the App… `div.section-content > div.row > div.column > h5.subhead`

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
main.main > section.section > div.unit-wrapper > a.unit-link `main.main > section.section > div.unit-wrapper > a.unit-link`

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
Privacy Policy `section.footer-mini > div.footer-mini-legal > div.footer-mini-legal-links > a.footer-mini-legal-link`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Try it now `div.caption-container > div.caption-container-inner > div.media-card-gallery-ctas > a.button`

○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]`s are contained by their required parent element

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

●Select elements have associated label elements.

●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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●`[lang]` attributes have a valid value

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

○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

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

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

○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

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

4 <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 Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H5: 198 chars

Got: 1 >120-char heading(s)

A+

Alt Text Quality

All 33 images OK

PASS

All 33 images OK

27 decorative image(s) correctly marked

6 image(s) with good alt text

33 images 6 good alt text 27 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 13 controls labeled

PASS

All 13 controls labeled

13 control(s) properly labeled

13 controls

13 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	input	Ask Apple Developer	aria-label
#footer-directory-column-section-state-platform	checkbox	Platforms	for/id
#footer-directory-column-section-state-tools	checkbox	Tools	for/id
#footer-directory-column-section-state-topics	checkbox	Technologies	for/id
#footer-directory-column-section-state-resources	checkbox	Resources	for/id
#footer-directory-column-section-state-support	checkbox	Support	for/id
#footer-directory-column-section-state-account	checkbox	Account	for/id
#footer-directory-column-section-state-programs	checkbox	Programs	for/id
#footer-directory-column-section-state-events	checkbox	Events	for/id
input	radio		none
input	radio		none
input	radio		none
select	select	Language Dropdown	aria-label

A+

Form Input Types

13 form control(s) checked, no type mismatches

PASS

13 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

13 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+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

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

PASS

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

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

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.