Skip to content
https://atom.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-u2lnqy
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://atom.io/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://atom.io/manifest.json

Manifest contains invalid JSON.

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 ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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 Missing
✓ Multiple Sizes Present
C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 7 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
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 Sunsetting Atom
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Categories
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tags:
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Written by
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More on
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Related posts
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore more from GitHub
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We do newsletters, too
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Site-wide Links
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Docs
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The ReadME Project
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 GitHub Actions
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enterprise content
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Product
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Platform
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Support
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Company
1.43:1
#000000
on
#24292F
needs 3.0:1 (large text)
19px · bottom of viewport
title Sunsetting Atom - The GitHub Blog
1.41:1
#000000
on
#212830
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.41:1
#000000
on
#212830
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to sidebar
1.41:1
#000000
on
#212830
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Sunsetting Atom1.43:13.0:1
#000000
#24292F
Fail
h2 Categories1.43:13.0:1
#000000
#24292F
Fail
h2 Tags:1.43:13.0:1
#000000
#24292F
Fail
h2 Written by1.43:13.0:1
#000000
#24292F
Fail
h2 More on1.43:13.0:1
#000000
#24292F
Fail
h2 Related posts1.43:13.0:1
#000000
#24292F
Fail
h2 Explore more from Gi…1.43:13.0:1
#000000
#24292F
Fail
h2 We do newsletters, t…1.43:13.0:1
#000000
#24292F
Fail
h2 Site-wide Links1.43:13.0:1
#000000
#24292F
Fail
h3 Docs1.43:13.0:1
#000000
#24292F
Fail
h3 The ReadME Project1.43:13.0:1
#000000
#24292F
Fail
h3 GitHub Actions1.43:13.0:1
#000000
#24292F
Fail
h3 Enterprise content1.43:13.0:1
#000000
#24292F
Fail
h3 Product1.43:13.0:1
#000000
#24292F
Fail
h3 Platform1.43:13.0:1
#000000
#24292F
Fail
h3 Support1.43:13.0:1
#000000
#24292F
Fail
h3 Company1.43:13.0:1
#000000
#24292F
Fail
title Sunsetting Atom - Th…1.41:14.5:1
#000000
#212830
Fail
a Skip to content1.41:14.5:1
#000000
#212830
Fail
a Skip to sidebar1.41:14.5:1
#000000
#212830
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, 25 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

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
body.wp-singular > div.lightbox-overlay > img.lightbox-image body.wp-singular > div.lightbox-overlay > img.lightbox-image

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Atom div.position-sticky > section.mb-7 > h2#atom-related-posts-title > a.Link--primary

These are opportunities to improve the legibility of your content.

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
How to manage cookie preferences div#wcpConsentBannerCtrl > div._1Upc2NjY8AlDn177YoVj0y > p.f6QKJD7fhSbnJLarTL-W- > a
Privacy Statement div#wcpConsentBannerCtrl > div._1Upc2NjY8AlDn177YoVj0y > p.f6QKJD7fhSbnJLarTL-W- > a
Third-Party Cookies div#wcpConsentBannerCtrl > div._1Upc2NjY8AlDn177YoVj0y > p.f6QKJD7fhSbnJLarTL-W- > a
Accept div#ghcc > div#wcpConsentBannerCtrl > div._2j0fmugLb1FgYz6KPuB91w > button._1XuCi2WhiqeWRUVp3pnFG3
Reject div#ghcc > div#wcpConsentBannerCtrl > div._2j0fmugLb1FgYz6KPuB91w > button._1XuCi2WhiqeWRUVp3pnFG3
Manage cookies div#ghcc > div#wcpConsentBannerCtrl > div._2j0fmugLb1FgYz6KPuB91w > button._1XuCi2WhiqeWRUVp3pnFG3

These are opportunities to improve keyboard navigation in your application.

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
Terms div.container-xl > ul.list-style-none > li.mr-3 > a.Link--secondary
Privacy div.container-xl > ul.list-style-none > li.mr-3 > a.Link--secondary

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
●Buttons have an accessible name
●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 attributes are used as specified for the element's role
●`[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 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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●No form fields have multiple labels
●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
○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 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
○`<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
○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.
A+
Landmark Structure
21 landmarks
PASS
21 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Secondary navigation" SEARCH MAIN ASIDE "Sidebar" CONTENTINFO footer
A+
Heading Hierarchy
26 headings
PASS
26 headings
Info::
Single H1 present
  • H2 Categories
  • H1 Sunsetting Atom
  • H2 Why are we doing this?
  • H2 What happens next?
  • H2 If I’m using Atom, what changes can I expect after the sunset?
  • H2 Thank you
  • H2 Tags:
  • H2 Written by
  • H3 GitHub Staff
  • H2 More on Atom
  • H3 Action needed for GitHub Desktop and Atom users
  • H2 Related posts
  • H3 Changes to GitHub Copilot Individual plans
  • H3 Bringing more transparency to GitHub’s status page
  • H3 Developer policy update: Intermediary liability, copyright, and transparency
  • H2 Explore more from GitHub
  • H3 Docs
  • H3 The ReadME Project
  • H3 GitHub Actions
  • H3 Enterprise content
  • H2 We do newsletters, too
  • H2 Site-wide Links
  • H3 Product
  • H3 Platform
  • H3 Support
  • H3 Company
A
Alt Text Quality
1 of 18 images have issues
PASS
1 of 18 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
9 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
18 images 8 good alt text 9 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-inputsearchSearch the blogaria-label
#search-inputsearchSearch the blogaria-label
#newsletter_emailAddressemailYour email addressfor/id
#optincheckboxcheckboxnone
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback