Skip to content
https://avaaz.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
6
REVIEW
7
PASS
0
INFO
0
Checks
13
7 REVIEW 6 FIX
F
Alt Text Quality
Action
11 of 15 images have issues
FIX
11 of 15 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
3 image(s) with generic alt text
Info::
4 image(s) with good alt text
15 images 4 good alt text 3 generic 8 missing
IssueCount
missing8 image(s)
generic3 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

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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 65/100 — 6 failing, 13 passed
FIX
65

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header-unified-wraper-outer > div.header-unified-wraper-inner > div.header-unified > button.mobile-menu-button div.header-unified-wraper-outer > div.header-unified-wraper-inner > div.header-unified > button.mobile-menu-button
div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button
div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button
div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button
div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button
div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button
div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button
div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button div.slideshow_item > a.slideshow_content > div.slideshow_link > button.slideshow_content-more-button

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.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object
div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object
div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object
div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object
div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object
div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object
div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object div.slideshow_item > div.slideshow_image > a.slideshow_image-link > img.slideshow_image-object
div#block-accuracy-quote > div.block-inner > div.photo-inset > img div#block-accuracy-quote > div.block-inner > div.photo-inset > 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
div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link
div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link
div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link
div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link
div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link
div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link
div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link div.slideshow_wrap > div.slideshow_item > div.slideshow_image > a.slideshow_image-link
Facebook div.global-footer-connect > ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link
X div.global-footer-connect > ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link
Instagram div.global-footer-connect > ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link
TikTok div.global-footer-connect > ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link
Bluesky div.global-footer-connect > ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link
footer.global-footer > div.global-footer-inner > div.global-footer-logo > a.svg-link footer.global-footer > div.global-footer-inner > div.global-footer-logo > a.svg-link

Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more about alt text for `object` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li.global-footer-nav-item > a.svg-link > div.global-footer-nav-plus-icon > object li.global-footer-nav-item > a.svg-link > div.global-footer-nav-plus-icon > object
ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image
ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image
ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image
ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image
ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image ul.global-footer-connect-items > li.global-footer-connect-item > a.svg-link > object.global-footer-connect-image
div.global-footer-inner > div.global-footer-logo > a.svg-link > object.global-footer-logo-image div.global-footer-inner > div.global-footer-logo > a.svg-link > object.global-footer-logo-image
div.global-license > div.global-license-inner > div.global-license-icon > object div.global-license > div.global-license-inner > div.global-license-icon > object

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
By continuing you accept Avaaz's Privacy Policy which explains how your data ca… body.lang-en > div.gdpr-block > div.gdpr-block-inner > div.gdpr-content
Privacy Policy div.gdpr-block > div.gdpr-block-inner > div.gdpr-content > a
GOT IT body.lang-en > div.gdpr-block > div.gdpr-block-inner > a.gdpr-link-block
Start Your Petition Now div.content > div.do-take-action-content-mid > div.container-submit > a.do-take-action-button
UPDATED ul.global-footer-nav-links > li.global-footer-nav-item > a.global-footer-nav-link > span.badge

These are opportunities to improve the legibility of your content.

Best practices

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>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<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.
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●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 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
○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
○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">`
○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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO footer

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

B
Heading Hierarchy
14 headings
REVIEW
14 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H4 Join Avaaz!
  • H4 Welcome to Avaaz!
  • H4 Welcome to Avaaz!
  • H2 THE AVAAZ MOVEMENT:
  • H2 JOIN NOW
  • H2 HAPPENING RIGHT NOW
  • H2 Take Action
  • H3 The miracle recovery plan for our planet
  • H2 TAKE ACTION
  • H3 Start Your Own Petition
  • H2 Highlights
  • H3 Climate Change: The Beginning of the End of Fossil Fuels
  • H2 Our Community
  • H2 Commitment to Accuracy

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="CountryID" id="form-joinus-country">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="Email" id="front-community-form-email">
Info::
3 control(s) properly labeled
5 controls
3 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#frontpage-signup-form-nametextNamefor/id
#frontpage-signup-form-emailemailEmailfor/id
#form-joinus-postcodetextPostcodefor/id
#front-community-form-emailemail(Email)placeholder only
#form-joinus-countryselect(none)none

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

<select name="CountryID" id="form-joinus-country">

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="email" name="Email" id="front-community-form-email">

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✓ Manifest Icons Present
✗ Multiple Sizes Missing
B
Web Manifest
PWA-ready
REVIEW
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Avaaz
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Avaaz ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name Avaaz Display Mode standalone Icons 1 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA 3 pass AA only
div which explains how your data can be used…
2.79:1
#000000
on
#585358
needs 4.5:1 (normal text)
16px · above the fold
a Got it
1.33:1
#000000
on
#242225
needs 4.5:1 (normal text)
16px · above the fold
h4 Join Avaaz!
1.21:1
#000000
on
#1C1A1B
needs 3.0:1 (large text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 THE AVAAZ MOVEMENT:21.00:13.0:1
#000000
#FFFFFF
Pass
h2 JOIN NOW21.00:13.0:1
#000000
#FFFFFF
Pass
h2 HAPPENING RIGHT NOW21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Highlights21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Community21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Commitment to Accura…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Climate Change: The …21.00:13.0:1
#000000
#FFFFFF
Pass
title Avaaz - The World in…21.00:14.5:1
#000000
#FFFFFF
Pass
div Update your21.00:14.5:1
#000000
#FFFFFF
Pass
a Cookie Settings12.12:14.5:1
#000000
#99CCE5
Pass
div to use this feature.21.00:14.5:1
#000000
#FFFFFF
Pass
div Click21.00:14.5:1
#000000
#FFFFFF
Pass
strong 'Allow All'4.74:13.0:1
#000000
#E70680
Pass
div or just activate the4.56:14.5:1
#000000
#E2067D
Pass
strong 'Targeting Cookies'5.46:13.0:1
#000000
#897F89
Pass
div By continuing you ac…6.92:14.5:1
#000000
#9C9199
Pass
a Privacy Policy4.69:14.5:1
#000000
#7E747E
Pass
div which explains how y…2.79:14.5:1
#000000
#585358
Fail
a Got it1.33:14.5:1
#000000
#242225
Fail
h4 Join Avaaz!1.21:13.0:1
#000000
#1C1A1B
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.

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

Send Feedback