Skip to content
https://getnajdah.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
8
REVIEW
5
PASS
11
INFO
0
Checks
24
11 PASS 5 REVIEW 8 FIX
F
Heading Hierarchy
Action
98 headings, 8 skip(s)
FIX
98 headings, 8 skip(s)
Warning::
Multiple H1 headings (62 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Ongoing Food and Health Crisis
  • H1 Ongoing War and Humanitarian Crisis duplicate H1
  • H1 Ongoing Humanitarian Crisis and War duplicate H1
  • H1 Emergency Humanitarian Needs duplicate H1
  • H2 Sunday, June 7th 2026, 9:10 PM
  • H2 Monday, October 13th 2025, 11:09 AM
  • H2 Monday, October 13th 2025, 11:07 AM
  • H2 Monday, October 13th 2025, 11:04 AM
  • H2 Yemen
  • H2 Ukraine - Kyiv
  • H2 Sudan - Darfur
  • H2 Palestine - Gaza_Strip
  • H1 The Most Interactions Campaigns duplicate H1
  • H1 Almost Complete Campaigns duplicate H1
  • H1 Our Top duplicate H1
  • H2 Donors
  • H1 abood aboodt duplicate H1
  • H1 8,560 duplicate H1
  • H1 Happiness Maker duplicate H1
  • H1 m duplicate H1
  • H1 6,972 duplicate H1
  • H1 Happiness Maker duplicate H1
  • H1 Abo ww duplicate H1
  • H1 3,200 duplicate H1
  • H1 Generous Donor duplicate H1
  • H1 4 duplicate H1
  • H1 Ahmed k duplicate H1
  • H1 3,000 duplicate H1
  • H1 Generous Donor duplicate H1
  • H1 5 duplicate H1
  • H1 ASD Asd duplicate H1
  • H1 2,579 duplicate H1
  • H1 Generous Donor duplicate H1
  • H1 6 duplicate H1
  • H1 abood aboodt duplicate H1
  • H1 1,988 duplicate H1
  • H1 Generous Donor duplicate H1
  • H1 7 duplicate H1
  • H1 Mr Donor duplicate H1
  • H1 1,010 duplicate H1
  • H1 Generous Donor duplicate H1
  • H1 8 duplicate H1
  • H1 AbOoD Tab duplicate H1
  • H1 401 duplicate H1
  • H1 Generous Donor duplicate H1
  • H1 9 duplicate H1
  • H1 sdfkjds sadlkjajsg duplicate H1
  • H1 204 duplicate H1
  • H1 Generous Donor duplicate H1
  • H1 10 duplicate H1
  • H1 bashar duplicate H1
  • H1 101 duplicate H1
  • H1 New Donor duplicate H1
  • H1 Donate And Get duplicate H1
  • H2 Valuable Rewards
  • H1 30000 duplicate H1
  • H3 Legendary donation reward skipped
  • H1 15000 duplicate H1
  • H3 Community Hero Reward skipped
  • H1 5000 duplicate H1
  • H3 Heartlight Frame skipped
  • H2 Education
  • H2 Disabilities
  • H2 Health Care
  • H2 Poverty
  • H2 Environment
  • H2 Orphans
  • H1 Our Top duplicate H1
  • H2 Categories
  • H1 Mobile App duplicate H1
  • H2 To find campaigns near you and suitable for you
  • H3 Download the App and Make
  • H1 The application is being updated duplicate H1
  • H2 It will be back soon !!
  • H1 An duplicate H1
  • H2 Overview
  • H1 Of Our Website And duplicate H1
  • H2 FAQ
  • H1 About It duplicate H1
  • H1 About Najdah duplicate H1
  • H1 Most Frequently Asked Questions duplicate H1
  • H1 What information is required to register as a donor or a requester? duplicate H1
  • H3 The Answer: The form requires a valid email, a password from 6 to 128 characters, a phone number in international format, geographic location (latitude/longitude), plus first and last name, gender, da skipped
  • H1 How do I know who has thanked me as a donor? duplicate H1
  • H3 The Answer: You can review a list of the most recent people who sent you a thank-you message as a donor from a dedicated section within your account. skipped
  • H1 How do I thank someone who donated to my campaign? duplicate H1
  • H3 The Answer: As a campaign owner, you can view a list of the most recent non-anonymous donors to your campaigns, and send a thank-you message directly to any of them. skipped
  • H1 How do I save a campaign to view later (favorites)? duplicate H1
  • H3 The Answer: Any logged-in user can save a specific campaign with a single click directly from its card, and later review all saved campaigns from a dedicated tab within the "All Campaigns" page, with skipped
  • H1 What file formats are supported for uploads? duplicate H1
  • H3 The Answer: Common image formats (JPG, JFIF, PNG, GIF, and WebP) are accepted across all upload forms, in addition to MP4 video and PDF files specifically for verification documents and licenses. skipped
  • H1 Get In Touch duplicate H1
  • H2 Palestine - Gaza Strip
  • H2 (PS)059=547-6300
  • H2 noreply@getnajdah.com
  • H2 Usage Policy Consent
  • H3 🍪 Cookie Policy v3.0.0-direct-en
  • H3 Sessions

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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
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: #005653
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 ✗
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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 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
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 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 Text Quality
3 heading-text-quality issue(s) detected
REVIEW
3 heading-text-quality issue(s) detected
Info::
3 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H1: "m" - H1: "4" - H1: "5"
Got: 3 ≤2-char heading(s)
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 200 chars - H3: 149 chars - H3: 165 chars
Got: 3 >120-char heading(s)
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
C
Mobile-Readable Font Sizes
Action
72% of visible text renders at >= 12 CSS px (29 below threshold)
REVIEW
72% of visible text renders at >= 12 CSS px (29 below threshold)
Warning::
29 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <h1> 10.0px ("8,560"); <h1> 10.0px ("Happiness Maker"); <h1> 10.0px ("6,972"); <h1> 10.0px ("Happiness Maker"); <h1> 10.0px ("3,200").
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 Ongoing Food and Health Crisis
1.76:1
#000000
on
#033E3C
needs 3.0:1 (large text)
32px · mid-page · over background image/gradient
h1 Ongoing War and Humanitarian Crisis
1.73:1
#000000
on
#023D3B
needs 3.0:1 (large text)
32px · mid-page · over background image/gradient
h1 Ongoing Humanitarian Crisis and War
1.78:1
#000000
on
#043F3C
needs 3.0:1 (large text)
32px · mid-page · over background image/gradient
h1 Emergency Humanitarian Needs
1.89:1
#000000
on
#09433F
needs 3.0:1 (large text)
32px · mid-page · over background image/gradient
h1 The Most Interactions Campaigns
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Almost Complete Campaigns
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Our Top
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 abood aboodt
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 8,560
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Happiness Maker
2.47:1
#39A715
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 6,972
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Happiness Maker
2.47:1
#39A715
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Abo ww
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 3,200
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Generous Donor
2.44:1
#0893FE
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Ahmed k
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 3,000
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Generous Donor
2.44:1
#0893FE
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 ASD Asd
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport
h1 2,579
2.71:1
#000000
on
#265B56
needs 3.0:1 (large text)
32px · bottom of viewport

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Ongoing Food and Hea…1.76:13.0:1
#000000
#033E3C
Fail
h1 Ongoing War and Huma…1.73:13.0:1
#000000
#023D3B
Fail
h1 Ongoing Humanitarian…1.78:13.0:1
#000000
#043F3C
Fail
h1 Emergency Humanitari…1.89:13.0:1
#000000
#09433F
Fail
h1 The Most Interaction…2.71:13.0:1
#000000
#265B56
Fail
h1 Almost Complete Camp…2.71:13.0:1
#000000
#265B56
Fail
h1 Our Top2.71:13.0:1
#000000
#265B56
Fail
h1 abood aboodt2.71:13.0:1
#000000
#265B56
Fail
h1 8,5602.71:13.0:1
#000000
#265B56
Fail
h1 Happiness Maker2.47:13.0:1
#39A715
#265B56
Fail
h1 6,9722.71:13.0:1
#000000
#265B56
Fail
h1 Happiness Maker2.47:13.0:1
#39A715
#265B56
Fail
h1 Abo ww2.71:13.0:1
#000000
#265B56
Fail
h1 3,2002.71:13.0:1
#000000
#265B56
Fail
h1 Generous Donor2.44:13.0:1
#0893FE
#265B56
Fail
h1 Ahmed k2.71:13.0:1
#000000
#265B56
Fail
h1 3,0002.71:13.0:1
#000000
#265B56
Fail
h1 Generous Donor2.44:13.0:1
#0893FE
#265B56
Fail
h1 ASD Asd2.71:13.0:1
#000000
#265B56
Fail
h1 2,5792.71:13.0:1
#000000
#265B56
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 86/100 — 4 failing, 23 passed
REVIEW
86

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.carousel-box > div.owl-carousel > div.owl-dots > button.owl-dot div.carousel-box > div.owl-carousel > div.owl-dots > button.owl-dot
div.carousel-box > div.owl-carousel > div.owl-dots > button.owl-dot div.carousel-box > div.owl-carousel > div.owl-dots > button.owl-dot
div.carousel-box > div.owl-carousel > div.owl-dots > button.owl-dot div.carousel-box > div.owl-carousel > div.owl-dots > button.owl-dot
div.carousel-box > div.owl-carousel > div.owl-dots > button.owl-dot div.carousel-box > div.owl-carousel > div.owl-dots > button.owl-dot

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
header#header-sec > nav > div.search-and-contact > a#controlPanelBtn header#header-sec > nav > div.search-and-contact > a#controlPanelBtn
div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website
div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website
div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website
div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website
div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website
div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website div.top-donor-box > div.account-desc > div.rank-and-thanks-btn > a.btn-website
section.main-icon > ul > li.face > a section.main-icon > ul > li.face > a
section.main-icon > ul > li.whats > a section.main-icon > ul > li.whats > a
section.main-icon > ul > li.youtube > a section.main-icon > ul > li.youtube > 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.

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
Donate div.flex-top-donor-content > div.top-donor-content > div.donate-now-btn-box > a.btn-website
See All Categories div.flex-top-categorie > div.top-categories-content > div.btn-top-categories > a.btn-website
Najdah (نجدة) is a community fundraising platform based in Gaza, Palestine. Exp… div.container > div.main-content-about-us > div.sub-content > p.about-us-dec
About the platform div.container > div.main-content-about-us > div.sub-content > a#homeAboutLink
عن نجدة بالعربية div.container > div.main-content-about-us > div.sub-content > a#homeAboutAlternate
The Answer: div.faq-boxes > div.faq-box > h3#answer-0 > span
The Answer: div.faq-boxes > div.faq-box > h3#answer-1 > span
The Answer: div.faq-boxes > div.faq-box > h3#answer-2 > span
The Answer: div.faq-boxes > div.faq-box > h3#answer-3 > span
The Answer: div.faq-boxes > div.faq-box > h3#answer-4 > span

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Legendary donation reward div.rewards > div.rewards-boxes > div.reward-one > h3
Community Hero Reward div.rewards > div.rewards-boxes > div.reward-two > h3
Heartlight Frame div.rewards > div.rewards-boxes > div.reward-three > h3
The Answer: The form requires a valid email, a password from 6 to 128 character… div.container > div.faq-boxes > div.faq-box > h3#answer-0
The Answer: You can review a list of the most recent people who sent you a than… div.container > div.faq-boxes > div.faq-box > h3#answer-1
The Answer: As a campaign owner, you can view a list of the most recent non-ano… div.container > div.faq-boxes > div.faq-box > h3#answer-2
The Answer: Any logged-in user can save a specific campaign with a single click… div.container > div.faq-boxes > div.faq-box > h3#answer-3
The Answer: Common image formats (JPG, JFIF, PNG, GIF, and WebP) are accepted a… div.container > div.faq-boxes > div.faq-box > h3#answer-4

These are opportunities to improve keyboard navigation in your application.

○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
●Image elements have `[alt]` attributes
●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
●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.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[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
○No form fields have multiple labels
○`<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.
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
○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+
Alt Text Quality
All 47 images OK
PASS
All 47 images OK
Info::
10 decorative image(s) correctly marked
Info::
37 image(s) with good alt text
47 images 37 good alt text 10 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#pmAgreeCheckboxcheckboxI have read and agree to all the above policies. Read full policiesfor/id
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback