Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FHeading HierarchyAction98 headings, 8 skip(s)FIX
- 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.
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.
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.
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.
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.
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.
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.
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.
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.
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
DLink & Button QualityAction18 issue(s) across 48 links and 9 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /register | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_00000000000EtpRjYtBKw… | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_000000000002SW1BeNA6X… | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_000000000009mVYrg3Yki… | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_000000000007Iqs5NhAZl… | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_000000000008MPl9VpA8g… | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_00000000000FGiym6sXh0… | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_0000000000069wfhOU70p… | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_00000000000J6Wmz8tsOk… | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_000000000005CA3MBwSua… | (empty) | empty | Add link text or aria-label |
| /donor-account/usr_00000000000JIGcbE9nTe… | (empty) | empty | Add link text or aria-label |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| https://www.facebook.com/ | (empty) | empty | Add link text or aria-label |
| https://www.whatsapp.com/ | (empty) | empty | Add link text or aria-label |
| https://www.youtube.com/ | (empty) | empty | Add link text or aria-label |
| /policies | Read full policies | new tab | Add '(opens in new tab)' to text |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
/register; /donor-account/usr_00000000000EtpRjYtBKwM; /donor-account/usr_000000000002SW1BeNA6X4; /donor-account/usr_000000000009mVYrg3Yki3; /donor-account/usr_000000000007Iqs5NhAZlt; /donor-account/usr_000000000008MPl9VpA8gX; /donor-account/usr_00000000000FGiym6sXh0g; /donor-account/usr_0000000000069wfhOU70pv; /donor-account/usr_00000000000J6Wmz8tsOks; /donor-account/usr_000000000005CA3MBwSuaE (+6 more)
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
/policies
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
button.owl-dot (#120 on page); button.owl-dot (#122 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
F404 Error PageActionHTTP 403, custom pageFIX
FFavicon & BrandingAction2 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction3 landmarksREVIEW
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
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
BHeading Text Quality3 heading-text-quality issue(s) detectedREVIEW
CMobile-Readable Font SizesAction72% of visible text renders at >= 12 CSS px (29 below threshold)REVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
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)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Ongoing Food and Hea… | 1.76:1 | 3.0:1 | #000000 | #033E3C | Fail |
| h1 Ongoing War and Huma… | 1.73:1 | 3.0:1 | #000000 | #023D3B | Fail |
| h1 Ongoing Humanitarian… | 1.78:1 | 3.0:1 | #000000 | #043F3C | Fail |
| h1 Emergency Humanitari… | 1.89:1 | 3.0:1 | #000000 | #09433F | Fail |
| h1 The Most Interaction… | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 Almost Complete Camp… | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 Our Top | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 abood aboodt | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 8,560 | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 Happiness Maker | 2.47:1 | 3.0:1 | #39A715 | #265B56 | Fail |
| h1 6,972 | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 Happiness Maker | 2.47:1 | 3.0:1 | #39A715 | #265B56 | Fail |
| h1 Abo ww | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 3,200 | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 Generous Donor | 2.44:1 | 3.0:1 | #0893FE | #265B56 | Fail |
| h1 Ahmed k | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 3,000 | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 Generous Donor | 2.44:1 | 3.0:1 | #0893FE | #265B56 | Fail |
| h1 ASD Asd | 2.71:1 | 3.0:1 | #000000 | #265B56 | Fail |
| h1 2,579 | 2.71:1 | 3.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.
BLighthouse Accessibility AuditsScore 86/100 — 4 failing, 23 passedREVIEW
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.
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.
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.
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.
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.
A+Alt Text QualityAll 47 images OKPASS
A+Form AccessibilityAll 1 controls labeledPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #pmAgreeCheckbox | checkbox | I have read and agree to all the above policies. Read full policies | for/id |