Skip to content
https://almanac.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
7
PASS
0
INFO
0
Checks
13
7 REVIEW 6 FIX
F
Form Accessibility
Action
8 of 12 controls have issues
FIX
8 of 12 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="op" id="edit-submit">; <input type="date" name="date" id="edit-date">; <input type="submit" name="op" id="edit-submit--2">; <input type="date" name="date" id="edit-date--2">; <input type="submit" name="op" id="edit-submit--3">; <input type="submit" name="op" id="edit-submit--3">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search_api_fulltext">; <input type="text" name="search_api_fulltext">
Info::
4 control(s) properly labeled
12 controls
4 labeled
2 placeholder only
6 unlabeled
ControlTypeLabelMethod
#edit-emailemailEmail Addressfor/id
#edit-locationtextSunrise and Sunsetfor/id
#edit-location--2textMoonrise and Moonsetfor/id
#edit-email--2emailEmail Addressfor/id
search_api_fulltexttext(Search...)placeholder only
search_api_fulltexttext(Search...)placeholder only
#edit-submit--2submit(none)none
#edit-submitsubmit(none)none
#edit-date--2date(none)none
#edit-submit--3submit(none)none
#edit-datedate(none)none
#edit-submit--3submit(none)none

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

<input type="submit" name="op" id="edit-submit">; <input type="date" name="date" id="edit-date">; <input type="submit" name="op" id="edit-submit--2">; <input type="date" name="date" id="edit-date--2">; <input type="submit" name="op" id="edit-submit--3">; <input type="submit" name="op" id="edit-submit--3">

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

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

<input type="text" name="search_api_fulltext">; <input type="text" name="search_api_fulltext">

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

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
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: #455775
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
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs aria-label navigation
Search
Skip Link
Labeled Navigation 6 <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
Landmark Structure
14 landmarks
REVIEW
14 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
2 of 6 <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 "Global" 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

B
Heading Hierarchy
37 headings
REVIEW
37 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H1 What Can You Compost? A Complete Do’s and Don’ts Guide duplicate H1
  • H2 Calendar
  • H3 Today is Day 112 of 2026
  • H4 60 days until summer begins
  • H3 Question of the Day
  • H3 Upcoming Holidays
  • H3 Puzzle of the Day
  • H3 Word of the Day
  • H3 Today is the Best Day to...
  • H2 Gardening
  • H3 Planting Calendar
  • H3 Garden Tools and Calculators
  • H3 Growing Guides
  • H2 Weather
  • H3 Seasonal Outlook
  • H3 Long-Range Weather
  • H4 Get Almanac’s Daily Updates
  • H3 Free Email Newsletter
  • H2 Astronomy
  • H3 Today's Moon Phase
  • H2 Today's Moon Phase
  • H3 Next Full Moon
  • H2 Food
  • H3 Cherry Balsamic Chicken Salad With Spinach, Arugula, Fennel, and Grapes
  • H3 Corn and Black Bean Pitas
  • H3 Roasted Potato Salad
  • H3 Almanac Authors
  • H4 Andy Wilcox
  • H4 Catherine Boeckmann
  • H4 Lauren Landers
  • H4 Samantha Johnson
  • H2 About The Almanac
  • H3 About the Almanac
  • H4 Visit the The Almanac Webcam
  • H4 Get Almanac's Daily Updates
  • H2 (empty)

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
Alt Text Quality
1 of 26 images have issues
REVIEW
1 of 26 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
8 decorative image(s) correctly marked
Info::
16 image(s) with good alt text
26 images 16 good alt text 8 decorative 1 missing
IssueCount
missing1 image(s)
too long1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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 404 Error | Almanac.com Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
8 icon(s) detected
REVIEW
8 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::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 1 pass AA only
title The Old Farmer’s Almanac: Gardening, W…
4.46:1
#000000
on
#7C735B
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Today's Moon Phase5.24:13.0:1
#000000
#7F7F7F
Pass
h2 About The Almanac5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Today is5.24:13.0:1
#000000
#7F7F7F
Pass
h3 of 20265.24:13.0:1
#000000
#7F7F7F
Pass
h3 Question of the Day5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Upcoming Holidays5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Puzzle of the Day5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Word of the Day5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Today is the Best Da…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Planting Calendar5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Garden Tools and Cal…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Growing Guides5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Seasonal Outlook5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Long-Range Weather5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Free Email Newslette…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Today's Moon Phase5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Next Full Moon5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Almanac Authors5.24:13.0:1
#000000
#7F7F7F
Pass
title The Old Farmer’s A…4.46:14.5:1
#000000
#7C735B
Fail
a America’s #1 Alman…5.24:14.5:1
#000000
#7F7F7F
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, 29 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
Information from your device can be used to personalize your ad experience. Do … body.page-front > div.adthrive-comscore > div#adthrive-ccpa-link
Terms and Conditions div.bee-popup-col > div.bee-popup-block > p > a
Privacy Policy div.bee-popup-col > div.bee-popup-block > p > a

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
div.node__content > div.field > div.field__item > img.image-style-landscape div.node__content > div.field > div.field__item > img.image-style-landscape

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mylocation-form-wrapper > form#mylocation-getlocationform1 > div.js-form-item > input#edit-date div.mylocation-form-wrapper > form#mylocation-getlocationform1 > div.js-form-item > input#edit-date
div.mylocation-form-wrapper > form#mylocation-getlocationform2 > div.js-form-item > input#edit-date--2 div.mylocation-form-wrapper > form#mylocation-getlocationform2 > div.js-form-item > input#edit-date--2

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.block > div.block__content > div.field > a div.block > div.block__content > div.field > a
div.block > div.block__content > div.full-moon-block-image > a div.block > div.block__content > div.full-moon-block-image > a
div.views-view-grid-tile > div.views-field > div.field-content > a div.views-view-grid-tile > div.views-field > div.field-content > a
div.views-view-grid-tile > div.views-field > div.field-content > a div.views-view-grid-tile > div.views-field > div.field-content > a
div.views-view-grid-tile > div.views-field > div.field-content > a div.views-view-grid-tile > div.views-field > div.field-content > a
div.views-view-grid-tile > div.views-field > div.field-content > a div.views-view-grid-tile > div.views-field > div.field-content > a
div.views-view-grid-tile > div.views-field > div.field-content > a div.views-view-grid-tile > div.views-field > div.field-content > a
div.section--container > div.grid > div.social-menu > a.p-2 div.section--container > div.grid > div.social-menu > a.p-2
div.section--container > div.grid > div.social-menu > a.p-2 div.section--container > div.grid > div.social-menu > a.p-2
div.section--container > div.grid > div.social-menu > a.p-2 div.section--container > div.grid > div.social-menu > a.p-2
div.section--container > div.grid > div.social-menu > a.p-2 div.section--container > div.grid > div.social-menu > a.p-2
div.section--container > div.grid > div.social-menu > a.p-2 div.section--container > div.grid > div.social-menu > a.p-2

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.

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
Input buttons have discernible text.
`[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
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
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
ARIA IDs are unique
All heading elements contain content.
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
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<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>`.
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.

Send Feedback