Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 3 REVIEW 7 FIX

Landmark Structure

Action

4 landmarks

FIX

4 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Link & Button Quality

Action

7 issue(s) across 101 links and 75 buttons

FIX

7 issue(s) across 101 links and 75 buttons

5 link(s) with generic text

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

Got: https://www.jetbrains.com/legal/docs/privacy/cookie-notice/ ("Learn more"); / ("Learn more"); / ("Learn more"); / ("Learn more"); / ("Learn more")

33 link(s) open in new tab without warning

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

Got: https://kotlinconf.com/registration/?utm_source=website&utm_medium=banner&utm_campaign=kotlinlangsticky; https://github.com/JetBrains/kotlin/releases/tag/v2.3.20; https://www.jetbrains.com/; https://www.jetbrains.com/; https://www.jetbrains.com/; https://www.jetbrains.com/; https://www.jetbrains.com/; https://kotlinconf.com/?utm_campaign=kc_promo&utm_medium=banner&utm_source=kotlinlang; https://blog.jetbrains.com/kotlin/2026/04/kotlinconf-26-speakers-in-conversation-with-lena-reinhard/; https://blog.jetbrains.com/kotlin/2026/03/kodees-kotlin-roundup-march-26-edition/ (+23 more)

2 button(s) with no accessible text

63 link(s) with descriptive text

101 links

0 empty

5 generic text

33 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.jetbrains.com/legal/docs/pri…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Cookie Notice
https://kotlinconf.com/registration/?utm…	Join 2000+ Kotlin devs at Kotl…	new tab	Add '(opens in new tab)' to text
https://github.com/JetBrains/kotlin/rele…	v2.3.20	new tab	Add '(opens in new tab)' to text
https://www.jetbrains.com/	jetbrains logo	new tab	Add '(opens in new tab)' to text
/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Home page
/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Home page
/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Home page
/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Home page
https://www.jetbrains.com/	jetbrains logo	new tab	Add '(opens in new tab)' to text
https://www.jetbrains.com/	jetbrains logo	new tab	Add '(opens in new tab)' to text
https://www.jetbrains.com/	jetbrains logo	new tab	Add '(opens in new tab)' to text
https://www.jetbrains.com/	jetbrains logo	new tab	Add '(opens in new tab)' to text
https://kotlinconf.com/?utm_campaign=kc_…	KotlinConf banner	new tab	Add '(opens in new tab)' to text
https://blog.jetbrains.com/kotlin/2026/0…	April 2, 2026KotlinConf’26 S…	new tab	Add '(opens in new tab)' to text
https://blog.jetbrains.com/kotlin/2026/0…	March 31, 2026Kodee’s Kotlin…	new tab	Add '(opens in new tab)' to text
https://blog.jetbrains.com/amper/2026/03…	March 31, 2026Amper 0.10 – J…	new tab	Add '(opens in new tab)' to text
https://blog.jetbrains.com/kotlin/2026/0…	March 23, 2026KotlinConf’26 …	new tab	Add '(opens in new tab)' to text
https://medium.com/mcdonalds-technical-b…	McDonald's leverages Kotlin Mu…	new tab	Add '(opens in new tab)' to text
https://open.spotify.com/episode/3jtfD8a…	AWS opted for Kotlin over Java…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/watch?v=hZPL8Qqi…	Philips utilizes Kotlin Multip…	new tab	Add '(opens in new tab)' to text
https://medium.com/adobetech/streamlinin…	Adobe Experience Platform chos…	new tab	Add '(opens in new tab)' to text
https://www.forbes.com/sites/forbes-engi…	By sharing over 80% of logic a…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/watch?v=4GkoB4hZ…	Atlassian adopted Kotlin for t…	new tab	Add '(opens in new tab)' to text
https://github.com/JetBrains/kotlin	Kotlin on GitHub	new tab	Add '(opens in new tab)' to text
https://x.com/kotlin	Kotlin on Twitter	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/kotlinlang.org	Kotlin on Bluesky	new tab	Add '(opens in new tab)' to text
https://surveys.jetbrains.com/s3/kotlin-…	Kotlin Slack	new tab	Add '(opens in new tab)' to text
https://www.reddit.com/r/Kotlin/	Kotlin on Reddit	new tab	Add '(opens in new tab)' to text
https://stackoverflow.com/questions/tagg…	Kotlin on Stack Overflow	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCP7uiEZ…	Kotlin on YouTube	new tab	Add '(opens in new tab)' to text
https://blog.jetbrains.com/kotlin/	Blog	new tab	Add '(opens in new tab)' to text
https://youtrack.jetbrains.com/issues/KT	Issue Tracker	new tab	Add '(opens in new tab)' to text
https://kotlinlang.org/docs/kotlin-brand…	Brand Assets	new tab	Add '(opens in new tab)' to text
https://job-boards.eu.greenhouse.io/jetb…	Careers	new tab	Add '(opens in new tab)' to text
https://www.jetbrainsmerchandise.com/vie…	Kotlin Merch	new tab	Add '(opens in new tab)' to text
https://jetbrains.com	jetbrains.com link	new tab	Add '(opens in new tab)' to text
https://www.jetbrains.com/	JetBrains	new tab	Add '(opens in new tab)' to text
https://github.com/JetBrains/kotlin-web-…	Apache 2 license	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

136 links and buttons have descriptive text

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

https://www.jetbrains.com/legal/docs/privacy/cookie-notice/ ("Learn more"); / ("Learn more"); / ("Learn more"); / ("Learn more"); / ("Learn 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

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

https://kotlinconf.com/registration/?utm_source=website&utm_medium=banner&utm_campaign=kotlinlangsticky; https://github.com/JetBrains/kotlin/releases/tag/v2.3.20; https://www.jetbrains.com/; https://www.jetbrains.com/; https://www.jetbrains.com/; https://www.jetbrains.com/; https://www.jetbrains.com/; https://kotlinconf.com/?utm_campaign=kc_promo&utm_medium=banner&utm_source=kotlinlang; https://blog.jetbrains.com/kotlin/2026/04/kotlinconf-26-speakers-in-conversation-with-lena-reinhard/; https://blog.jetbrains.com/kotlin/2026/03/kodees-kotlin-roundup-march-26-edition/ (+23 more)

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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ 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

2 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

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Heading Hierarchy

Action

29 headings, 2 skip(s)

REVIEW

29 headings, 2 skip(s)

Multiple H1 headings (5 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

H2 Cookie Settings
H1 Kotlin
H3 Multiplatform skipped
H3 Backend
H3 Android
H3 AI
H3 Start Kotlin tour
H1 Kotlin duplicate H1
H1 Kotlin duplicate H1
H1 Kotlin duplicate H1
H3 Multiplatform skipped
H3 AI development
H3 Backend
H3 Android
H3 Kotlin Tour
H1 Kotlin duplicate H1
H2 Latest news
H3 KotlinConf’26 Speakers: In Conversation With Lena Reinhard
H3 Kodee’s Kotlin Roundup: Kotlin 2.3.20, Interview With Josh Long, and More
H3 Amper 0.10 – JDK Provisioning, a Maven Converter, Custom Compiler Plugins, and More
H3 KotlinConf’26 Speakers: In Conversation with Josh Long
H2 Kotlin in action
H2 Share code on your terms and for different platforms
H2 Kotlin + AI
H3 What you get with Kotlin + AI
H3 Build your own AI agents with Koog
H2 Big, friendly and helpful community
H2 Kotlin Foundation
H2 Start using Kotlin today!

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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 Kotlin Programming Language ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 Kotlin

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Kotlin

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Kotlin

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Kotlin

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Kotlin

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Cookie Settings

1.80:1

#000000

#352B7F

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Latest news

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kotlin in action

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Share code on your terms and for diffe…

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kotlin + AI

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Big, friendly and helpful community

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kotlin Foundation

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Start using

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kotlin today!

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Multiplatform

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Backend

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Android

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Start Kotlin tour

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Multiplatform

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI development

1.07:1

#000000

#0C0C0E

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Kotlin	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h1 Kotlin	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h1 Kotlin	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h1 Kotlin	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h1 Kotlin	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h2 Cookie Settings	1.80:1	3.0:1	#000000	#352B7F	Fail
h2 Latest news	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h2 Kotlin in action	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h2 Share code on your …	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h2 Kotlin + AI	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h2 Big, friendly and he…	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h2 Kotlin Foundation	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h2 Start using	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h2 Kotlin today!	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h3 Multiplatform	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h3 Backend	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h3 Android	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h3 Start Kotlin tour	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h3 Multiplatform	1.07:1	3.0:1	#000000	#0C0C0E	Fail
h3 AI development	1.07:1	3.0:1	#000000	#0C0C0E	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.

A+

Alt Text Quality

All 47 images OK

PASS

All 47 images OK

3 decorative image(s) correctly marked

44 image(s) with good alt text

47 images 44 good alt text 3 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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

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

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

●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

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

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

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