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

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

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 ✗

Link & Button Quality

15 issue(s) across 317 links and 2 buttons

REVIEW

15 issue(s) across 317 links and 2 buttons

1 link(s) with no accessible text

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

Got: /en/summit

14 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /en/topics/ai ("Read more"); /en/topics/api ("Read more"); /en/topics/automation ("Read more"); /en/topics/cloud-computing ("Read more"); /en/topics/cloud-computing/what-are-cloud-services ("Read more"); /en/topics/containers ("Read more"); /en/topics/devops ("Read more"); /en/topics/edge-computing ("Read more"); /en/topics/integration ("Read more"); /en/topics/linux ("Read more") (+4 more)

302 link(s) with descriptive text

317 links

1 empty

14 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/en/summit	(empty)	empty	Add link text or aria-label
/en/topics/ai	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Ai
/en/topics/api	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Api
/en/topics/automation	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Automation
/en/topics/cloud-computing	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Cloud Computing
/en/topics/cloud-computing/what-are-clou…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: What Are Cloud Services
/en/topics/containers	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Containers
/en/topics/devops	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Devops
/en/topics/edge-computing	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Edge Computing
/en/topics/integration	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Integration
/en/topics/linux	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Linux
/en/topics/microservices	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Microservices
/en/topics/middleware	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Middleware
/en/topics/security	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Security
/en/topics/virtualization	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Virtualization

304 links and buttons have descriptive text

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

/en/summit

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

Generic link text like 'click here' doesn't describe the destination.

/en/topics/ai ("Read more"); /en/topics/api ("Read more"); /en/topics/automation ("Read more"); /en/topics/cloud-computing ("Read more"); /en/topics/cloud-computing/what-are-cloud-services ("Read more"); /en/topics/containers ("Read more"); /en/topics/devops ("Read more"); /en/topics/edge-computing ("Read more"); /en/topics/integration ("Read more"); /en/topics/linux ("Read more") (+4 more)

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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 404 - Red Hat ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

A+

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

81 headings

PASS

81 headings

Single H1 present

H3 Overview
H3 Products
H3 Engage & learn
H3 Platform solutions
H3 Use cases
H3 Solutions by industry
H3 Discover cloud technologies
H3 Platforms
H3 Featured
H3 Try & buy
H3 Services & support
H3 Training & certification
H3 Featured
H3 Services
H3 Build your skills
H3 More ways to learn
H3 For developers
H3 For customers
H3 For partners
H3 Build solutions powered by trusted partners
H3 I'd like to:
H3 Help me find:
H3 I want to learn more about:
H3 Recommended
H3 Get more with a Red Hat account
H3 [[name]]
H2 From here, every direction is open
H2 Featured
H3 Your customized Red Hat Summit 2026 experience awaits
H3 Navigate virtual machine (VM) migration and modernization with Red Hat
H3 Red Hat launches Red Hat AI Enterprise to power AI from metal to agents
H3 Red Hat AI Factory with NVIDIA: Co-engineered to drive production AI
H3 Why should your organization standardize on Red Hat Enterprise Linux today?
H1 Red Hat is the leading provider of enterprise open source software solutions
H2 Build on a reliable foundation. Take your apps anywhere.
H3 Red Hat AI
H3 Red Hat Enterprise Linux
H3 Red Hat OpenShift
H3 Red Hat Ansible Automation Platform
H3 Red Hat OpenShift Virtualization Engine
H2 Organizations succeeding with Red Hat
H2 Building enterprise-ready solutions with open source
H2 Tech topics worth exploring
H3 Understanding AI
H4 Articles
H3 Understanding APIs
H4 Articles
H3 Understanding automation
H4 Articles
H3 Understanding cloud computing
H4 Articles
H3 What are cloud services?
H4 Articles
H3 Understanding Linux containers
H4 Articles
H3 Understanding DevOps
H4 Articles
H3 Understanding edge computing
H4 Articles
H3 Understanding enterprise integration
H4 Articles
H3 Understanding Linux
H4 Articles
H3 Understanding microservices
H4 Articles
H3 Understanding middleware
H4 Articles
H3 Understanding IT security
H4 Articles
H3 Understanding virtualization
H4 Articles
H2 Welcome, [Name]
H2 Get more with a Red Hat account
H3 Platforms
H3 Tools
H3 Try, buy, & sell
H3 Communicate
H3 About Red Hat
H3 Change page language
H3 Red Hat legal and privacy links
H3 Red Hat legal and privacy links

A+

Alt Text Quality

All 61 images OK

PASS

All 61 images OK

11 decorative image(s) correctly marked

50 image(s) with good alt text

61 images 50 good alt text 11 decorative

All images have appropriate alt text.

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

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

Got: <select id="lang-selection-footer">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#edit-search-field	text	Search	aria-label
#lang-selection	select	Change page language	for/id
#lang-selection	select	Change page language	for/id
#lang-selection-footer	select	(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+

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 Red Hat is the leadi…	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 From here, every dir…	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Featured	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Build on a reliable …	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Organizations succee…	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Building enterprise-…	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Tech topics worth ex…	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Welcome, [Name]	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Get more with a Red�…	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Overview	6.92:1	3.0:1	#000000	#949494	Pass
h3 Products	6.66:1	3.0:1	#000000	#919191	Pass
h3 Engage & learn	6.66:1	3.0:1	#000000	#919191	Pass
h3 Platform solutions	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Use cases	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Solutions by industr…	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Platforms	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Featured	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Try & buy	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Services & support	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Training & certifica…	4.64:1	3.0:1	#000000	#EE0000	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 97/100 — 1 failing, 33 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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#pop-outerdiv09572915171168688 > div#pop-div207661802437580503 > div#pop-div305080814559014604 > iframe#pop-frame025590354404637383 `div#pop-outerdiv09572915171168688 > div#pop-div207661802437580503 > div#pop-div305080814559014604 > iframe#pop-frame025590354404637383`

These are opportunities to improve keyboard navigation in your application.

○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

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

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

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●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

○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

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

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

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