Skip to content
https://opensource.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Opensource.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA 1 pass AA only
h2 User account menu
1.51:1
#000000
on
#003044
needs 3.0:1 (large text)
24px · top of page (header area)
h2 Main navigation
1.16:1
#000000
on
#1F140D
needs 3.0:1 (large text)
24px · above the fold
title Opensource.com
2.75:1
#000000
on
#005B75
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
2.15:1
#000000
on
#004A61
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Log in
1.51:1
#000000
on
#003044
needs 4.5:1 (normal text)
16px · top of page (header area)
a RSS
1.66:1
#000000
on
#21363D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Articles
1.11:1
#000000
on
#16100D
needs 4.5:1 (normal text)
16px · above the fold
a Resources
3.08:1
#000000
on
#665852
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a What is open source?
2.80:1
#000000
on
#61514E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a The open source way
1.05:1
#000000
on
#040A0A
needs 4.5:1 (normal text)
16px · above the fold
a Organizations
2.42:1
#000000
on
#484C4E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

5 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 User account menu1.51:13.0:1
#000000
#003044
Fail
h2 Main navigation1.16:13.0:1
#000000
#1F140D
Fail
h2 Find the perfect ope…4.64:13.0:1
#000000
#EE0000
Pass
h2 About This Site4.64:13.0:1
#000000
#EE0000
Pass
h2 Legal4.64:13.0:1
#000000
#EE0000
Pass
title Opensource.com2.75:14.5:1
#000000
#005B75
Fail
a Skip to main content2.15:14.5:1
#000000
#004A61
Fail
a Log in1.51:14.5:1
#000000
#003044
Fail
a RSS1.66:14.5:1
#000000
#21363D
Fail
a Articles1.11:14.5:1
#000000
#16100D
Fail
a Resources3.08:14.5:1
#000000
#665852
Fail
a What is open source?2.80:14.5:1
#000000
#61514E
Fail
a The open source way1.05:14.5:1
#000000
#040A0A
Fail
a Projects and applica…5.35:14.5:1
#000000
#7D8184
Pass
a Organizations2.42:14.5:1
#000000
#484C4E
Fail
a Open source alternat…7.37:14.5:1
#000000
#999999
Pass
a Alternatives to Acro…7.37:14.5:1
#000000
#999999
Pass
a Alternatives to Auto…7.37:14.5:1
#000000
#999999
Pass
a Alternatives to Drea…7.37:14.5:1
#000000
#999999
Pass
a Alternatives to Gmai…21.00:14.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.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 27 passed
REVIEW
85

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
LOG IN nav#block-useraccountmenu > ul.account > li.log-in > a.account__link

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
img img
img img
img img
img img
img img
img img
img img
img img
img img
img img
img img
img img
img img
img img
img img
img img

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
body.path-frontpage > div.dialog-off-canvas-main-canvas > div.layout-container > a body.path-frontpage > div.dialog-off-canvas-main-canvas > div.layout-container > 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.

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-outerdiv016451833554543538 > div#pop-div208241168445286877 > div#pop-div304128433800824355 > iframe#pop-frame07126633672841536 div#pop-outerdiv016451833554543538 > div#pop-div208241168445286877 > div#pop-div304128433800824355 > iframe#pop-frame07126633672841536

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`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.
●Elements use only permitted ARIA attributes
●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.
●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
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<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.
○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.
A+
Landmark Structure
22 landmarks
PASS
22 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "block-useraccountmenu-menu" MAIN CONTENTINFO footer
A+
Heading Hierarchy
22 headings
PASS
22 headings
Info::
Single H1 present
  • H2 User account menu
  • H2 Main navigation
  • H1 Home Page
  • H2 New developments at Opensource.com
  • H2 A distributed database load-balancing architecture with ShardingSphere
  • H2 Edit your photos with open source artificial intelligence
  • H2 5 reasons virtual machines still matter
  • H2 New developments at Opensource.com
  • H2 Tips for running virtual, in-person, and hybrid events
  • H2 Generate web pages from Markdown with Docsify-This
  • H2 How I used guilt as a motivator for good
  • H2 3 reasons to host a docathon for your open source project
  • H2 Run a virtual conference using only open source tools
  • H2 Find the perfect open source tool
  • H2 3 key open source challenges in developing countries
  • H2 Test your Drupal website with Cypress
  • H2 5 open ways to help UX designers and developers collaborate better
  • H2 What's new in GNOME 44?
  • H2 Retry your Python code until it fails
  • H2 Learn Tcl/Tk and Wish with this simple game
  • H2 About This Site
  • H2 Legal
A+
Alt Text Quality
All 17 images OK
PASS
All 17 images OK
Info::
17 image(s) with good alt text
17 images 17 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="edit-submit-acquia-search">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#edit-searchtextSearchfor/id
#edit-submit-acquia-searchsubmit(none)none

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

<input type="submit" id="edit-submit-acquia-search">

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

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

Send Feedback