Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

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 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

No favicon.ico at site root

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

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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 ✗

Heading Hierarchy

10 headings

REVIEW

10 headings

No H1 heading found

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

H2 Advanced capabilities for everyday use
H2 Secure and scale your PC fleet
H2 Graphics built for the age of AI
H2 The next era of computing starts now
H2 Advanced capabilities for everyday use
H2 See the latest news
H3 Intel named one of America's Most Innovative Companies
H3 The Verge reviews Intel’s latest laptop leap
H3 A breakthrough moment for Intel
H2 We break barriers so builders can move faster, from prototype to global scale. That’s the power of Intel Inside®

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

Link & Button Quality

1 issue(s) across 141 links and 28 buttons

REVIEW

1 issue(s) across 141 links and 28 buttons

3 link(s) open in new tab without warning

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

Got: https://newsroom.intel.com/corporate/intel-named-one-of-americas-most-innovat…; https://www.theverge.com/tech/867214/intel-core-ultra-x9-panther-lake-388h-la…; https://www.youtube.com/watch?v=Xjkzb-j6nKI

1 button(s) with no accessible text

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

Got: button.nav-btn (#494 on page)

138 link(s) with descriptive text

141 links

0 empty

0 generic text

3 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://newsroom.intel.com/corporate/int…	Innovation …	new tab	Add '(opens in new tab)' to text
https://www.theverge.com/tech/867214/int…	Performance …	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/watch?v=Xjkzb-j6…	Productivity …	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

165 links and buttons have descriptive text

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

https://newsroom.intel.com/corporate/intel-named-one-of-americas-most-innovat…; https://www.theverge.com/tech/867214/intel-core-ultra-x9-panther-lake-388h-la…; https://www.youtube.com/watch?v=Xjkzb-j6nKI

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.

button.nav-btn (#494 on page)

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

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+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

1 decorative image(s) correctly marked

4 image(s) with good alt text

5 images 4 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#ighf-search-input	text	Ask Intel	aria-label
#find-results	select	Find results with	for/id
#show-results-from	select	Show results from	for/id
#search_title	checkbox	Title	for/id
#search_description	checkbox	Description	for/id
#search_id	checkbox	Content ID	for/id

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
h2 Advanced capabilitie…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Secure and scale you…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Graphics built for t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The next era of comp…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Advanced capabilitie…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We break barriers so…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Intel named one of A…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The Verge reviews In…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A breakthrough momen…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Intel Inside - Built…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip To Main Content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Toggle Navigation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Products	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Products Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Processors	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Intel® Core™ Ultr…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Intel® Core™ Proc…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Intel® Xeon® Proce…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Intel® Xeon® CPU M…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Intel Atom® Process…	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 96/100 — 1 failing, 26 passed

PASS

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.

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
Performance `div#animatedhero-adeec2c52d > section#slide-0 > div.cmp-animated-hero__bg-slide-info > div.cmp-animated-hero__bg-title`

These are opportunities to improve the legibility of your content.

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

●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

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

○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

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

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

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

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