Skip to content
https://apachetoday.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
40
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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

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-qjmssp
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
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://apachetoday.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://apachetoday.com/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 ✗
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.
F
Lighthouse Accessibility Audits
Action
Score 36/100 — 10 failing, 5 passed
FIX
36

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
Breaking News td > a > font > b
Preferences td > a > font > b
Contribute td > a > font > b
About td > a > font > b
Apache Module Registry tr > td > font > b
ApacheCon tr > td > font > b
Apache-Perl Integration Project tr > td > font > b
The Java Apache Project tr > td > font > b
PHP Server Side Scripting tr > td > font > b
The Apache FAQ tr > td > font > b
Apache Project tr > td > font > b
The Jakarta Project tr > td > font > b
About Triggers td > a > font > b
Media Kit td > a > font > b
Security td > a > font > b
Triggers td > a > font > b
Login td > a > font > b

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

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 > center > img body > center > img
tbody > tr > td > img tbody > tr > td > img
tbody > tr > td > img tbody > tr > td > img
tr > td > center > img tr > td > center > img
tr > td > center > img tr > td > center > img

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
td > form > font > input td > form > font > input
td > form > font > input td > form > font > input
form > p > font > input form > p > font > input
tbody > tr > td > input tbody > tr > td > input
tbody > tr > td > input tbody > tr > td > input
tr > td > form > input tr > td > form > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Right Now Yesterday 2 Days Ago 3 Days Ago 4 Days Ago 5 Days Ago 6 Days Ago 1 We… tr > td > font > select#LTTimeframe
Date Reverse Date Reads Reverse Reads Talkback Rev. Talkback tr > td > font > select#LTSortOpt

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 > center > a body > center > a
tbody > tr > td > a tbody > tr > td > a
tr > td > center > a tr > td > center > a
tr > td > center > a tr > td > center > 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
Be proactive with SiteScope. FREE trial today. tbody > tr > td > a
form > p > font > input form > p > font > input
Right Now Yesterday 2 Days Ago 3 Days Ago 4 Days Ago 5 Days Ago 6 Days Ago 1 We… tr > td > font > select#LTTimeframe
Date Reverse Date Reads Reverse Reads Talkback Rev. Talkback tr > td > font > select#LTSortOpt
-= Highlighted stories above -- Normal news below =- tr > td > center > a
tr > td > form > input tr > td > form > input

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Linux Planet Linux Today Linux Central PHPBuilder Linux Apps Apache Today Just … tbody > tr > td > table
Apache Module Registry ApacheCon Apache-Perl Integration Project The Java Apach… tbody > tr > td > table

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Linux Planet Linux Today Linux Central PHPBuilder Linux Apps Apache Today Just … tbody > tr > td > table
Apache Module Registry ApacheCon Apache-Perl Integration Project The Java Apach… tbody > tr > td > table
○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>`
●Input buttons have discernible text.
●Document has a `<title>` element
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●The page contains a heading, skip link, or landmark region
○`[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
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[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 use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○Buttons have an accessible name
○`<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
○Heading elements appear in a sequentially-descending order
○`<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 type="image">` elements have `[alt]` text
○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
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

C
Alt Text Quality
Action
5 of 17 images have issues
REVIEW
5 of 17 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
4 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
17 images 8 good alt text 4 decorative 5 missing
IssueCount
missing5 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

C
Form Accessibility
Action
13 of 13 controls have issues
REVIEW
13 of 13 controls have issues
Critical::
13 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="s_prod_name">; <input type="checkbox" name="List_Name">; <input type="text" name="email">; <input type="submit" name="Submit">; <select name="LTD" id="LTTimeframe">; <select name="LTS" id="LTSortOpt">; <input type="submit">; <input type="text" name="username">; <input type="password" name="passwd">; <input type="submit" name="login"> (+3 more)
13 controls
0 labeled
0 placeholder only
13 unlabeled
ControlTypeLabelMethod
s_prod_nametext(none)none
List_Namecheckbox(none)none
emailtext(none)none
Submitsubmit(none)none
#LTTimeframeselect(none)none
#LTSortOptselect(none)none
inputsubmit(none)none
usernametext(none)none
passwdpassword(none)none
loginsubmit(none)none
createsubmit(none)none
querytext(none)none
inputsubmit(none)none

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

<input type="text" name="s_prod_name">; <input type="checkbox" name="List_Name">; <input type="text" name="email">; <input type="submit" name="Submit">; <select name="LTD" id="LTTimeframe">; <select name="LTS" id="LTSortOpt">; <input type="submit">; <input type="text" name="username">; <input type="password" name="passwd">; <input type="submit" name="login"> (+3 more)

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

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title Apache Today - Apach…21.00:14.5:1
#000000
#FFFFFF
Pass
font Your Daily Source fo…10.17:14.5:1
#000000
#99B4F2
Pass
b Breaking News5.95:13.0:1
#000000
#BC57FF
Pass
b Preferences21.00:13.0:1
#000000
#FFFFFF
Pass
b Contribute21.00:13.0:1
#000000
#FFFFFF
Pass
b Triggers7.28:13.0:1
#000000
#7196EC
Pass
b Link Us19.77:13.0:1
#000000
#F8F8F8
Pass
b Search18.10:13.0:1
#000000
#EEEEEE
Pass
b About7.59:13.0:1
#000000
#8F9DAC
Pass
font Linux Planet21.00:14.5:1
#000000
#FFFFFF
Pass
font Linux Today19.77:14.5:1
#000000
#F8F8F8
Pass
font Linux Central18.10:14.5:1
#000000
#EEEEEE
Pass
font PHPBuilder13.32:14.5:1
#000000
#C7CFD6
Pass
font Linux Apps21.00:14.5:1
#000000
#FFFFFF
Pass
font Apache Today21.00:14.5:1
#000000
#FFFFFF
Pass
font Just Linux21.00:14.5:1
#000000
#FFFFFF
Pass
font Linux Programming21.00:14.5:1
#000000
#FFFFFF
Pass
font BSD Today15.28:14.5:1
#000000
#D5DCEC
Pass
font All Linux Devices18.10:14.5:1
#000000
#EEEEEE
Pass
font Enterprise Linux To…18.71:14.5:1
#000000
#F0F2F4
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.

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

Send Feedback