Accessibility

D

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

No banner (header) landmark

No contentinfo (footer) landmark

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

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

Heading Hierarchy

Action

35 headings, 12 skip(s)

FIX

35 headings, 12 skip(s)

Multiple H1 headings (21 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 INTERNATIONAL WOMEN'S DAY 2026: GIVE TO GAIN
H4 IWD 2026 campaign theme is GIVE TO GAIN #IWD2026 | #GiveToGain | #March8 skipped
H1 (empty)
H4 (empty)
H1 IWD 2026 CAMPAIGN THEME IS 'GIVE TO GAIN' duplicate H1
H4 #GiveToGain | #IWD2026 skipped
H1 HELP MAKE IWD ONE OF THE BIGGEST ANNUAL GIVING DAYS duplicate H1
H4 IWD GIVING means fundraising, elevating visibility, providing knowledge, and more. skipped
H1 FREE IWD TOOLKIT AND RESOURCES duplicate H1
H4 Download FREE planning tools and guidance for an impactful IWD. skipped
H1 INTERNATIONAL WOMEN'S DAY 2026 EVENTS duplicate H1
H4 Register for events | Secure speakers | Source women-owned business suppliers skipped
H1 WOMEN CREATIVES ARE THE PULSE OF INSPIRATION duplicate H1
H4 IWD lettering challenge | Art | Spoken word poetry | Sing for equality skipped
H1 ALL IWD ACTIVITY IS VALID AND INVITED duplicate H1
H4 Since the first IWD in 1911, IWD belongs to all those who are compelled to care. skipped
H1 IWD COLLABORATIONS ARE INVITED duplicate H1
H4 From grassroots groups to global brands, gender equality is forged through synergy. skipped
H1 #IWD2026 | #GiveToGain duplicate H1
H4 Imagine a gender equal world. A world free of bias, stereotypes, and discrimination. A world that's diverse, equitable, and inclusive. A world where difference is valued and celeb skipped
H4 International Women's Day (IWD) has been around for over a hundred years, as have many of the issues still impacting women's advancement. Since 1911, IWD belongs to all who care about gender equality.
H1 IWD 2026 GIVE TO GAIN duplicate H1
H1 Free IWD Resources & Toolkit duplicate H1
H1 SEARCH IWD EVENTS duplicate H1
H1 IWD FUNDRAISING duplicate H1
H1 Plan and amplify your IWD Giving activity duplicate H1
H4 Together, let's make International Women's Day one of the biggest GIVING DAYS of the year. Imagine the impact if all IWD events nominated a women-focused charity as recipient of f skipped
H1 IWD GIVING DIRECTORY duplicate H1
H1 IWD GIVING NEWS duplicate H1
H1 ABOUT IWD GIVING duplicate H1
H1 GET INVOLVED WITH IWD 2026 duplicate H1
H1 Collaboration is key to advancing gender equality duplicate H1
H4 IWD is a global movement powered by collective effort. Looking to explore a potential collaboration? Get in touch. skipped
H2 International Women's Day is powered by the collective efforts of all
H1 Join the global IWD Community duplicate H1

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

D

Link & Button Quality

Action

16 issue(s) across 77 links and 10 buttons

FIX

16 issue(s) across 77 links and 10 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /Register; https://www.facebook.com/InternationalWomensDay; https://twitter.com/womensday; https://www.instagram.com/internationalwomensday_global/; https://www.linkedin.com/showcase/internationalwomensday/; https://www.youtube.com/channel/UCO0slFdmiod2KmJztaQQV4w; https://www.tiktok.com/@internationalwomensday/

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.seattletimes.com/opinion/herersquos-to-the-memory-of-gloria-stein…

9 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.active (#109 on page); button (#110 on page); button (#111 on page); button (#112 on page); button (#113 on page); button (#114 on page); button (#115 on page); button (#116 on page); button (#117 on page)

69 link(s) with descriptive text

77 links

7 empty

0 generic text

1 new tab

9 empty buttons

Element	Text	Issue	Suggested Fix
https://www.seattletimes.com/opinion/her…	once explained	new tab	Add '(opens in new tab)' to text
/Register	(empty)	empty	Add link text or aria-label
https://www.facebook.com/InternationalWo…	(empty)	empty	Add link text or aria-label
https://twitter.com/womensday	(empty)	empty	Add link text or aria-label
https://www.instagram.com/internationalw…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/showcase/intern…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/channel/UCO0slFd…	(empty)	empty	Add link text or aria-label
https://www.tiktok.com/@internationalwom…	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

70 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/Register; https://www.facebook.com/InternationalWomensDay; https://twitter.com/womensday; https://www.instagram.com/internationalwomensday_global/; https://www.linkedin.com/showcase/internationalwomensday/; https://www.youtube.com/channel/UCO0slFdmiod2KmJztaQQV4w; https://www.tiktok.com/@internationalwomensday/

Why this matters

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.

https://www.seattletimes.com/opinion/herersquos-to-the-memory-of-gloria-stein…

Why this matters

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.active (#109 on page); button (#110 on page); button (#111 on page); button (#112 on page); button (#113 on page); button (#114 on page); button (#115 on page); button (#116 on page); button (#117 on page)

Why this matters

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

F

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-7gni7y

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

D

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://internationalwomensday.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://internationalwomensday.com/manifest.json

Manifest contains invalid JSON.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #47296e

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

D

Lighthouse Accessibility Audits

Action

Score 68/100 — 8 failing, 13 passed

FIX

68

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.col-sm-12 > div#carouselHome > div.carousel-indicators > button.active `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button.active`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > 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.row > div.col-12 > div > img.img-fluid `div.row > div.col-12 > div > img.img-fluid`
div.row > div.col-12 > div > img.img-fluid `div.row > div.col-12 > div > img.img-fluid`

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.row > div.col-12 > h1.text-white > a.btn `div.row > div.col-12 > h1.text-white > a.btn`
div.col-12 > div.row > div.col-md-1 > a `div.col-12 > div.row > div.col-md-1 > a`
div.col-12 > div.row > div.col-md-1 > a `div.col-12 > div.row > div.col-md-1 > a`
div.col-12 > div.row > div.col-md-1 > a `div.col-12 > div.row > div.col-md-1 > a`
div.col-12 > div.row > div.col-md-1 > a `div.col-12 > div.row > div.col-md-1 > a`
div.col-12 > div.row > div.col-md-1 > a `div.col-12 > div.row > div.col-md-1 > a`
div.col-12 > div.row > div.col-md-1 > a `div.col-12 > div.row > div.col-md-1 > 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
Imagine a gender equal world. A world free of bias, stereotypes, and discrimina… `div.container-fluid > div.row > div.col-12 > h4.mt-5`
International Women's Day (IWD) has been around for over a hundred years, as ha… `div.container-fluid > div.row > div.col-12 > h4.mt-5`
Together, let's make International Women's Day one of the biggest GIVING DAYS o… `div.container > div.row > div.col-12 > h4.my-4`
IWD is a global movement powered by collective effort. Looking to explore a pot… `div.container > div.row > div.col-12 > h4.my-4`

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
Imagine a gender equal world. A world free of bias, stereotypes, and discrimina… `div.container-fluid > div.row > div.col-12 > h4.mt-5`
Together, let's make International Women's Day one of the biggest GIVING DAYS o… `div.container > div.row > div.col-12 > h4.my-4`
IWD is a global movement powered by collective effort. Looking to explore a pot… `div.container > div.row > div.col-12 > h4.my-4`

These are opportunities to improve keyboard navigation in your application.

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
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button.active `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button.active`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`
div.col-sm-12 > div#carouselHome > div.carousel-indicators > button `div.col-sm-12 > div#carouselHome > div.carousel-indicators > button`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MENU `form#form1 > nav#nav_bar > div.container-fluid > button.navbar-toggler`

○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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●`[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.

●Image elements do not have `[alt]` attributes that are redundant text.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○`[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

○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

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<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

○Identical links have the same purpose.

○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.

B

Alt Text Quality

2 of 20 images have issues

REVIEW

2 of 20 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

18 image(s) with good alt text

20 images 18 good alt text 2 missing

Issue	Count
missing	2 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

A+

Form Accessibility

No form controls

PASS

No form controls

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)

Element	Ratio	Required	FG	BG	Result
h1 INTERNATIONAL WOMEN'…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 IWD 2026 CAMPAIGN TH…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 HELP MAKE IWD ONE OF…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 FREE IWD TOOLKIT AND…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 INTERNATIONAL WOMEN'…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 WOMEN CREATIVES ARE …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 ALL IWD ACTIVITY IS …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 IWD COLLABORATIONS A…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 #IWD2026 \| #Give…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 IWD 2026 GIVE TO GAI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Free IWD Resources &…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 SEARCH IWD EVENTS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 IWD FUNDRAISING	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Plan and amplify you…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 IWD GIVING DIRECTORY	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 IWD GIVING NEWS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 ABOUT IWD GIVING	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 GET INVOLVED WITH IW…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Collaboration is key…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Join the global IWD …	21.00:1	3.0: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.