Skip to content
https://indymedia.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 REVIEW 7 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
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 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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
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.
C
Lighthouse Accessibility Audits
Action
Score 76/100 — 3 failing, 9 passed
REVIEW
76

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.

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.

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
https://www.indybay.org/newsitems/2019/11/30/18828519.php body > ul > li > a
https://www.democracynow.org/2019/11/27/1999_wto_protests_20_years_later body > ul > li > a
https://archive.is/03tV4 body > ul > li > a
Indymedia 20th Anniversary Encuentro body > ul > li > a
https://www.historylink.org/File/2142 body > ul > li > a
Antwerpen body > p > a
Athens body > p > a
Barcelona body > p > a
Belarus body > p > a
Belgium body > p > a
Brussels body > p > a
Bulgaria body > p > a
Estrecho / madiaq body > p > a
Germany body > p > a
Grenoble body > p > a
Ireland body > p > a
Istanbul body > p > a
Italy body > p > a
La plana body > p > a
Lille body > p > a
Linksunten body > p > a
Lombardia body > p > a
Nantes body > p > a
Netherlands body > p > a
Norway body > p > a
Nottingham body > p > a
Paris/Île-de-france body > p > a
Patras body > p > a
Piemonte body > p > a
Poland body > p > a
Portugal body > p > a
Romania body > p > a
Russia body > p > a
Sardegna body > p > a
Scotland body > p > a
Switzerland body > p > a
Ukraine body > p > a
United kingdom body > p > a
Valencia body > p > a.indypagebody
Atlanta body > p > a
Big muddy body > p > a
Boston body > p > a
Buffalo body > p > a
Chicago body > p > a
Colorado body > p > a
Columbus body > p > a
DC body > p > a
Hawaii body > p > a
La body > p > a
Miami body > p > a
Minneapolis/st. paul body > p > a
Portland body > p > a
Rochester body > p > a
Rogue valley body > p > a
San francisco bay area body > p > a
Santa cruz, ca body > p > a
United states body > p > a
Urbana-champaign body > p > a
print body > a
radio body > a
satellite tv body > a
video body > a
abruzzo body > a
alacant body > a
andorra body > a
antwerpen body > a
armenia body > a
athens body > a
austria body > a
barcelona body > a
belarus body > a
belgium body > a
bristol body > a
brussels body > a
bulgaria body > a
calabria body > a
cyprus body > a
emilia-romagna body > a
euskal herria body > a
galiza body > a
germany body > a
grenoble body > a
ireland body > a
istanbul body > a
italy body > a
la plana body > a
liege body > a
liguria body > a
lille body > a
linksunten body > a
lombardia body > a
london body > a
madrid body > a
malta body > a
marseille body > a
nantes body > a
napoli body > a
netherlands body > a
nice body > a
northern england body > a
nottingham body > a
paris/île-de-france body > a
patras body > a
piemonte body > a
poland body > a
portugal body > a
romania body > a
russia body > a
sardegna body > a
sverige body > a
switzerland body > a
torun body > a
toscana body > a
toulouse body > a
ukraine body > a
valencia body > a
argentina body > a
bolivia body > a
chiapas body > a
chile body > a
chile sur body > a
cmi brasil body > a
colombia body > a
ecuador body > a
mexico body > a
peru body > a
puerto rico body > a
qollasuyu body > a
rosario body > a
santiago body > a
tijuana body > a
uruguay body > a
valparaiso body > a
aotearoa body > a
darwin body > a
atlanta body > a
austin body > a
austin indymedia body > a
big muddy body > a
binghamton body > a
boston body > a
buffalo body > a
charlottesville body > a
chicago body > a
cleveland body > a
colorado body > a
columbus body > a
dc body > a
hawaii body > a
houston body > a
hudson mohawk body > a
kansas city body > a
la body > a
madison body > a
maine body > a
michigan body > a
milwaukee body > a
minneapolis/st. paul body > a
new jersey body > a
new mexico body > a
new orleans body > a
north carolina body > a
nyc body > a
philadelphia body > a
pittsburgh body > a
portland body > a
richmond body > a
rochester body > a
rogue valley body > a
san diego body > a
san francisco body > a
san francisco bay area body > a
santa cruz, ca body > a
sarasota body > a
seattle body > a
tennessee body > a
urbana-champaign body > a
worcester body > a
armenia body > a
beirut body > a
israel body > a

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.

○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>`
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●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
●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
○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
○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.
○Image elements have `[alt]` attributes
○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">`
○`[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
○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+
Heading Hierarchy
9 headings
PASS
9 headings
Info::
Single H1 present
  • H1 Indymedia.org
  • H2 Global Independent Media Centre Network
  • H3 Europe:
  • H3 Latin america:
  • H3 Oceania:
  • H3 South asia:
  • H3 United states:
  • H3 Process:
  • H3 Projects:
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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
h1 Indymedia.org21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Global Independent M…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Europe:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Latin america:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Oceania:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 South asia:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 United states:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Process:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Projects:21.00:13.0:1
#000000
#FFFFFF
Pass
title Indymedia.org21.00:14.5:1
#000000
#FFFFFF
Pass
p Indymedia.org is bei…21.00:14.5:1
#000000
#FFFFFF
Pass
p The Global Network o…21.00:14.5:1
#000000
#FFFFFF
Pass
p It's now been 20 yea…21.00:14.5:1
#000000
#FFFFFF
Pass
p These are articles t…21.00:14.5:1
#000000
#FFFFFF
Pass
a https://www.indybay.…21.00:14.5:1
#000000
#FFFFFF
Pass
a https://www.democrac…21.00:14.5:1
#000000
#FFFFFF
Pass
a https://archive.is/0…21.00:14.5:1
#000000
#FFFFFF
Pass
a https://www.democrac…19.54:14.5:1
#000000
#F6F6FF
Pass
p Events:21.00:14.5:1
#000000
#FFFFFF
Pass
a Indymedia 20th Anniv…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.

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

Send Feedback