Skip to content
https://www.scala-lang.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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: #ffffff
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 MAIN CONTENTINFO footer

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

B
Heading Hierarchy
31 headings
REVIEW
31 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 A programming language that scales with you: from small scripts to large multiplatform applications.
  • H3 Expressive
  • H3 Scalable
  • H3 Safe
  • H2 Proven Use Cases
  • H3 Server-side
  • H3 Principled Concurrency
  • H3 A Mature Ecosystem of Libraries
  • H3 Case Study: Reusable Code with Tapir
  • H3 Data Processing
  • H3 Big Data Analysis
  • H3 Notebooks
  • H3 Command Line
  • H3 The power of Scala in one file
  • H3 Get productive with the Scala Toolkit
  • H3 Package to native, deploy easily
  • H3 Frontend Web
  • H3 Portable Code and Libraries
  • H3 Interoperability with JavaScript
  • H3 Powerful User Interface Libraries
  • H2 Scala runs on the following platforms...
  • H2 Ideal for teaching
  • H3 Readable and Versatile
  • H2 The Scala language is maintained by
  • H3 The Scala Center is supported by
  • H3 Documentation
  • H3 Download
  • H3 Community
  • H3 Contribute
  • H3 Scala
  • H3 Social

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

B
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff 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
h2 A programming language that scales with …
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
24px · mid-page
h2 Scala runs on the following platforms...
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Expressive
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Scalable
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Safe
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Server-side
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Principled Concurrency
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 A Mature Ecosystem of Libraries
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Case Study: Reusable Code with Tapir
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Data Processing
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Big Data Analysis
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Notebooks
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Command Line
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The power of Scala in one file
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Get productive with the Scala Toolkit
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Package to native, deploy easily
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Frontend Web
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Portable Code and Libraries
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Interoperability with JavaScript
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Powerful User Interface Libraries
2.44:1
#000000
on
#22525E
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 A programming langua…2.44:13.0:1
#000000
#22525E
Fail
h2 Scala runs on the fo…2.44:13.0:1
#000000
#22525E
Fail
h3 Expressive2.44:13.0:1
#000000
#22525E
Fail
h3 Scalable2.44:13.0:1
#000000
#22525E
Fail
h3 Safe2.44:13.0:1
#000000
#22525E
Fail
h3 Server-side2.44:13.0:1
#000000
#22525E
Fail
h3 Principled Concurren…2.44:13.0:1
#000000
#22525E
Fail
h3 A Mature Ecosystem o…2.44:13.0:1
#000000
#22525E
Fail
h3 Case Study: Reusable…2.44:13.0:1
#000000
#22525E
Fail
h3 Data Processing2.44:13.0:1
#000000
#22525E
Fail
h3 Big Data Analysis2.44:13.0:1
#000000
#22525E
Fail
h3 Notebooks2.44:13.0:1
#000000
#22525E
Fail
h3 Command Line2.44:13.0:1
#000000
#22525E
Fail
h3 The power of Scala i…2.44:13.0:1
#000000
#22525E
Fail
h3 Get productive with …2.44:13.0:1
#000000
#22525E
Fail
h3 Package to native, d…2.44:13.0:1
#000000
#22525E
Fail
h3 Frontend Web2.44:13.0:1
#000000
#22525E
Fail
h3 Portable Code and Li…2.44:13.0:1
#000000
#22525E
Fail
h3 Interoperability wit…2.44:13.0:1
#000000
#22525E
Fail
h3 Powerful User Interf…2.44:13.0:1
#000000
#22525E
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.

C
Lighthouse Accessibility Audits
Action
Score 73/100 — 5 failing, 15 passed
REVIEW
73

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.

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
LEARN INSTALL PLAYGROUND FIND A LIBRARY COMMUNITY GOVERNANCE BLOG header#site-header > div.header-background > div.wrap > nav.navigation

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
older releases, including Scala 2 div.col-lg-6 > div.inner-text > p > a
// prints: with 'a' × 1 = List(apple) div.highlight > pre.highlight > code.hljs > span.hljs-comment
// prints: with 'a' × 2 = List(avocado) div.highlight > pre.highlight > code.hljs > span.hljs-comment
// prints: with 'a' × 3 = List(banana, papaya) div.highlight > pre.highlight > code.hljs > span.hljs-comment
GET STARTED div.wrap > div.resources > div.get-started > a.button
DOCUMENTATION div.wrap > div.resources > div.learn-scala > a.button

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
div.header-background > div.wrap > nav.navigation > a.navigation-band div.header-background > div.wrap > nav.navigation > a.navigation-band
div.wrap > div.browser > div.header-browser > a div.wrap > div.browser > div.header-browser > a

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
Run in playground section#collections-ops_content > div.code-element > div.dark > button.code-snippet-button
Run in playground div.code-element > div.dark > button.code-snippet-button > a

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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 a valid value for its `[lang]` attribute
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○`[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
All 20 images OK
PASS
All 20 images OK
Info::
4 decorative image(s) correctly marked
Info::
16 image(s) with good alt text
20 images 16 good alt text 4 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="scaladex-search">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#scaladex-searchtext(e.g. database)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" id="scaladex-search">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback