Accessibility

D

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

D

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Skip navigation link detected

Back-to-top link detected

2 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 2 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

B

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No contentinfo (footer) landmark

Skip navigation link present

Skip link target(s) don't exist on page: #ajax-content-wrap

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

B

Iframe Accessibility

2/2 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/2 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

C

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 ONE STOP RESOURCE CENTRE FOR NEW MUSLIM…

1.10:1

#000000

on

#150E0C

needs 3.0:1 (large text)

32px · mid-page

h2 YOUR

1.13:1

#000000

on

#19110F

needs 3.0:1 (large text)

24px · above the fold

h2 people championing the New Muslim Educat…

1.10:1

#000000

on

#160E0C

needs 3.0:1 (large text)

24px · mid-page

h2 Personal

1.10:1

#000000

on

#150E0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Members Portal

1.10:1

#000000

on

#150E0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Live

1.10:1

#000000

on

#150E0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Interaction

1.10:1

#000000

on

#150E0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Best Part?

1.10:1

#000000

on

#150E0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 IT’S A 100%

1.10:1

#000000

on

#150E0B

needs 3.0:1 (large text)

24px · bottom of viewport

title New Muslim Academy | New Muslim Classes …

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.04:1

#000000

on

#0D0502

needs 4.5:1 (normal text)

16px · top of page (header area)

span Menu

1.06:1

#000000

on

#160502

needs 4.5:1 (normal text)

16px · top of page (header area)

span Home

1.09:1

#000000

on

#160C09

needs 4.5:1 (normal text)

16px · top of page (header area)

span Live Events

1.08:1

#000000

on

#160A08

needs 4.5:1 (normal text)

16px · above the fold

span Blog

1.09:1

#000000

on

#160C0A

needs 4.5:1 (normal text)

16px · above the fold

span Navigation Guide

1.10:1

#000000

on

#160D0B

needs 4.5:1 (normal text)

16px · above the fold

span FAQ

1.07:1

#000000

on

#130A06

needs 4.5:1 (normal text)

16px · above the fold

span Login

1.09:1

#000000

on

#180C06

needs 4.5:1 (normal text)

16px · above the fold

strong JOIN TODAY

1.11:1

#000000

on

#190E09

needs 3.0:1 (large text)

16px · above the fold

i Press enter to begin your search

1.11:1

#000000

on

#170F0C

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 ONE STOP RESOURCE CE…	1.10:1	3.0:1	#000000	#150E0C	Fail
h2 YOUR	1.13:1	3.0:1	#000000	#19110F	Fail
h2 people championing t…	1.10:1	3.0:1	#000000	#160E0C	Fail
h2 Personal	1.10:1	3.0:1	#000000	#150E0B	Fail
h2 Members Portal	1.10:1	3.0:1	#000000	#150E0B	Fail
h2 Live	1.10:1	3.0:1	#000000	#150E0B	Fail
h2 Interaction	1.10:1	3.0:1	#000000	#150E0B	Fail
h2 The Best Part?	1.10:1	3.0:1	#000000	#150E0B	Fail
h2 IT’S A 100%	1.10:1	3.0:1	#000000	#150E0B	Fail
title New Muslim Academy \|…	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to main content	1.04:1	4.5:1	#000000	#0D0502	Fail
span Menu	1.06:1	4.5:1	#000000	#160502	Fail
span Home	1.09:1	4.5:1	#000000	#160C09	Fail
span Live Events	1.08:1	4.5:1	#000000	#160A08	Fail
span Blog	1.09:1	4.5:1	#000000	#160C0A	Fail
span Navigation Guide	1.10:1	4.5:1	#000000	#160D0B	Fail
span FAQ	1.07:1	4.5:1	#000000	#130A06	Fail
span Login	1.09:1	4.5:1	#000000	#180C06	Fail
strong JOIN TODAY	1.11:1	3.0:1	#000000	#190E09	Fail
i Press enter to begin…	1.11:1	4.5:1	#000000	#170F0C	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 87/100 — 3 failing, 24 passed

REVIEW

87

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.

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
Join Now `div.wpb_text_column > div.wpb_wrapper > a.nectar-button > span`
JOIN TODAY `div.wpb_wrapper > p > a.nectar-button > span`
© 2026 New Muslim Academy. \| Privacy Policy `div#copyright > div.container > div.col > p`
\| Privacy Policy `div.container > div.col > p > a`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wpb_wrapper > div.wpb_raw_code > div.wpb_wrapper > iframe `div.wpb_wrapper > div.wpb_raw_code > div.wpb_wrapper > iframe`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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-*]` 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

●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

●ARIA `tooltip` elements have accessible names

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

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[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 `treeitem` elements have accessible names

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Heading Hierarchy

7 headings

PASS

7 headings

Single H1 present

H2 YOUR “Day-After-Shahadah” people championing the New Muslim Education.
H1 ONE STOP RESOURCE CENTRE FOR NEW MUSLIM CLASSES ONLINE
H2 Video Classes & Webinars
H2 Personal Members Portal
H2 Live Interaction
H2 The Best Part?
H2 IT’S A 100% FREE

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 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: 2 all-caps heading(s)

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

6 image(s) with good alt text

6 images 6 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
s	text	Search	aria-label

A

Link & Button Quality

28 links, 0 buttons — all OK

PASS

28 links, 0 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://twitter.com/NewMuslimAcadem; https://www.facebook.com/NewMuslimAcademy; https://www.youtube.com/channel/UCVvdwoZyc4vpIvItUKrwzgg; https://www.instagram.com/aftershahaadah/

24 link(s) with descriptive text

28 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://twitter.com/NewMuslimAcadem	twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/NewMuslimAcadem…	facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCVvdwoZ…	youtube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/aftershahaadah…	instagram	new tab	Add '(opens in new tab)' to text

24 links and buttons have descriptive text

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

https://twitter.com/NewMuslimAcadem; https://www.facebook.com/NewMuslimAcademy; https://www.youtube.com/channel/UCVvdwoZyc4vpIvItUKrwzgg; https://www.instagram.com/aftershahaadah/

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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "s" should use type="search" (currently type="text")

Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 59 visible text node(s) render at >= 12 CSS pixels

PASS

All 59 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - New Muslim Academy ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.