Skip to content
https://jetbrains.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Heading Hierarchy
Action
104 headings, 10 skip(s)
FIX
104 headings, 10 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 JETBRAINS IDEs
  • H5 AI TOOLS
  • H5 .NET & VISUAL STUDIO
  • H5 TEAM TOOLS
  • H5 LANGUAGES & FRAMEWORKS
  • H5 Not sure which tool is best for you?
  • H3 JetBrains Air
  • H3 Junie by JetBrains
  • H5 LEARN skipped
  • H5 TEACH
  • H5 FREE LICENSES
  • H5 COMMUNITY
  • H3 JetBrains Academy
  • H5 BY INDUSTRY & TECHNOLOGY skipped
  • H5 RECOMMENDED
  • H3 Developer Tools for Your Business
  • H3 JetBrains for Data
  • H5 PRODUCT & TECHNICAL SUPPORT skipped
  • H5 FREQUENT TASKS
  • H3 Download and Install
  • H3 Contact us
  • H5 DEVELOPER TOOLS skipped
  • H5 SERVICES & PLUGINS
  • H5 TEAM TOOLS
  • H5 LEARNING TOOLS
  • H5 SALES SUPPORT
  • H3 All Products Pack
  • H5 JETBRAINS IDEs skipped
  • H5 AI TOOLS
  • H5 .NET & VISUAL STUDIO
  • H5 TEAM TOOLS
  • H5 LANGUAGES & FRAMEWORKS
  • H5 Not sure which tool is best for you?
  • H3 JetBrains Air
  • H3 Junie by JetBrains
  • H5 LEARN skipped
  • H5 TEACH
  • H5 FREE LICENSES
  • H5 COMMUNITY
  • H3 JetBrains Academy
  • H5 BY INDUSTRY & TECHNOLOGY skipped
  • H5 RECOMMENDED
  • H3 Developer Tools for Your Business
  • H3 JetBrains for Data
  • H5 PRODUCT & TECHNICAL SUPPORT skipped
  • H5 FREQUENT TASKS
  • H3 Download and Install
  • H3 Contact us
  • H5 DEVELOPER TOOLS skipped
  • H5 SERVICES & PLUGINS
  • H5 TEAM TOOLS
  • H5 LEARNING TOOLS
  • H5 SALES SUPPORT
  • H3 All Products Pack
  • H1 Purpose-Built IDEs for Every Language and Stack
  • H2 For {developers}
  • H3 A rich suite of tools that provide an exceptional developer experience
  • H4 DataGrip
  • H4 WebStorm
  • H4 Rider
  • H4 CLion
  • H4 IntelliJ IDEA
  • H4 PyCharm
  • H3 Trusted by more than 15M developers
  • H4 Ready for actual use right out of the box
  • H4 Complex tasks become easy
  • H4 Built-in tools
  • H4 Customizable and extendable
  • H3 Ready for actual use right out of the box
  • H3 Complex tasks become easy
  • H3 Built-in tools
  • H3 Customizable and extendable
  • H2 The JetBrains Kotlin Ecosystem
  • H2 For teams
  • H3 Ensure efficient collaboration and maintain quality codebases with a fast software delivery flow
  • H4 TeamCity
  • H4 YouTrack
  • H4 Qodana
  • H4 Datalore
  • H3 Many of the world's most dynamic teams find that JetBrains tools make them more creative and effective
  • H3 TeamCity
  • H3 Our products are technology agnostic and support a mix of languages and other tools that your team and project may be using now or tomorrow.
  • H2 For businesses
  • H2 Solutions that scale with you as you grow
  • H4 Boost developer experience skipped
  • H4 Stay competitive
  • H4 Minimize risks
  • H4 Control costs
  • H3 Trusted by more than 300,000 organizations
  • H2 Discover more
  • H3 Choose your IDE
  • H3 Contact support
  • H3 Speak to sales
  • H3 Annual Highlights
  • H2 AI
  • H2 Developer Tools
  • H2 Solutions
  • H2 Initiatives
  • H2 Education
  • H2 Store
  • H2 Support
  • H2 Resources
  • H2 Community
  • H2 Company

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

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

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

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

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

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

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

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

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

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

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #000000
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 2 <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.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: JetBrains
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name JetBrains ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name JetBrains Display Mode standalone Theme Color #000000 Background Color #000000 Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Purpose-Built IDEs for Every Language an…
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
32px · bottom of viewport
h2 For
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The JetBrains Kotlin
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ecosystem
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Solutions that scale with you as you g…
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Discover more
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Developer Tools
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Solutions
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Initiatives
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Education
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Store
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Support
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Community
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Company
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 JetBrains Air
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Junie by JetBrains
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 JetBrains Academy
1.20:1
#000000
on
#19191C
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Purpose-Built IDEs f…1.20:13.0:1
#000000
#19191C
Fail
h2 For1.20:13.0:1
#000000
#19191C
Fail
h2 The JetBrains Kotlin1.20:13.0:1
#000000
#19191C
Fail
h2 Ecosystem1.20:13.0:1
#000000
#19191C
Fail
h2 For1.20:13.0:1
#000000
#19191C
Fail
h2 For1.20:13.0:1
#000000
#19191C
Fail
h2 Solutions that scale…1.20:13.0:1
#000000
#19191C
Fail
h2 Discover more1.20:13.0:1
#000000
#19191C
Fail
h2 Developer Tools1.20:13.0:1
#000000
#19191C
Fail
h2 Solutions1.20:13.0:1
#000000
#19191C
Fail
h2 Initiatives1.20:13.0:1
#000000
#19191C
Fail
h2 Education1.20:13.0:1
#000000
#19191C
Fail
h2 Store1.20:13.0:1
#000000
#19191C
Fail
h2 Support1.20:13.0:1
#000000
#19191C
Fail
h2 Resources1.20:13.0:1
#000000
#19191C
Fail
h2 Community1.20:13.0:1
#000000
#19191C
Fail
h2 Company1.20:13.0:1
#000000
#19191C
Fail
h3 JetBrains Air1.20:13.0:1
#000000
#19191C
Fail
h3 Junie by JetBrains1.20:13.0:1
#000000
#19191C
Fail
h3 JetBrains Academy1.20:13.0:1
#000000
#19191C
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 24 passed
REVIEW
84

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wt-container > div.wt-row > div.wt-col > button._main_10h2pj3_62 div.wt-container > div.wt-row > div.wt-col > button._main_10h2pj3_62
div.wt-container > div.wt-row > div.wt-col > button._main_10h2pj3_62 div.wt-container > div.wt-row > div.wt-col > button._main_10h2pj3_62

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English Deutsch Español Français 日本語 한국어 Русский 简体中文 Português do Brasil div._main_s9jmmi_16 > div > div._wrapper_s9jmmi_20 > select._select_s9jmmi_24

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.

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
Boost developer experience div.wt-container > div.wt-row > div._tile_17150hd_245 > h4._rs-h2_1owszn1_1

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

○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
●Image elements have `[alt]` attributes
●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
●`<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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○`<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
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
A
Alt Text Quality
2 of 45 images have issues
PASS
2 of 45 images have issues
Warning::
2 image(s) with generic alt text
Info::
11 decorative image(s) correctly marked
Info::
32 image(s) with good alt text
45 images 32 good alt text 11 decorative 2 generic
IssueCount
generic2 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Favicon & Branding
7 icon(s) detected
PASS
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback