Skip to content
https://alshamalmedicalcenter.com/?v=home

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
8
REVIEW
5
PASS
11
INFO
0
Checks
24
11 PASS 5 REVIEW 8 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

No landmarks detected

Screen reader users have no way to navigate by region.

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
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ 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
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 57/100 — 7 failing, 9 passed
FIX
57

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.bubble-element > div.bubble-element > div.bubble-element > button.clickable-element div.bubble-element > div.bubble-element > div.bubble-element > button.clickable-element
div.bubble-element > div.bubble-element > div.bubble-element > button.clickable-element div.bubble-element > div.bubble-element > div.bubble-element > button.clickable-element
keyboard_arrow_left div.bubble-element > div.bubble-element > div.clickable-element > button.bubble-element
add div.bubble-element > div.bubble-element > div.bubble-element > button.bubble-element
add div.bubble-element > div.bubble-element > div.bubble-element > button.bubble-element
add div.bubble-element > div.bubble-element > div.bubble-element > button.bubble-element
add div.bubble-element > div.bubble-element > div.bubble-element > button.bubble-element
add div.bubble-element > div.bubble-element > div.bubble-element > button.bubble-element
div.bubble-element > div.bubble-element > div.bubble-element > button.clickable-element div.bubble-element > div.bubble-element > div.bubble-element > button.clickable-element
keyboard_backspace div.bubble-element > div.bubble-element > div.bubble-element > button.bubble-element
copyright div.bubble-element > div.bubble-element > div.bubble-element > button.bubble-element

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.bubble-element > div.bubble-element > div.clickable-element > img div.bubble-element > div.bubble-element > div.clickable-element > img
div.bubble-element > div.bubble-element > div.clickable-element > img div.bubble-element > div.bubble-element > div.clickable-element > img
div.bubble-element > div.bubble-element > div.clickable-element > img div.bubble-element > div.bubble-element > div.clickable-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img
div.bubble-element > div.bubble-element > div.clickable-element > img div.bubble-element > div.bubble-element > div.clickable-element > img
div.bubble-element > div.bubble-element > div.bubble-element > img div.bubble-element > div.bubble-element > div.bubble-element > img

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.bubble-element > div.bubble-element > div.bubble-element > iframe div.bubble-element > div.bubble-element > div.bubble-element > iframe

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
body > div.bubble-element > div.bubble-element > a.bubble-element body > div.bubble-element > div.bubble-element > a.bubble-element
body > div.bubble-element > div.bubble-element > a.bubble-element body > div.bubble-element > div.bubble-element > a.bubble-element

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
ماذا نقدم؟ div.bubble-element > div.bubble-element > div.bubble-element > div.bubble-element
عرض جميع الخدمات div.bubble-element > div.bubble-element > div.clickable-element > div.bubble-element
اقرأ المزيد div.bubble-element > div.bubble-element > div.bubble-element > div.bubble-element
جميع الحقوق محفوظة div.bubble-element > div.bubble-element > div.bubble-element > div.bubble-element

These are opportunities to improve the legibility of your content.

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.bubble-element > div.bubble-element > div.bubble-element > button.clickable-element div.bubble-element > div.bubble-element > div.bubble-element > button.clickable-element

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.wf-barlow-n8-active html.wf-barlow-n8-active

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●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.
●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.
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○`[role]` values are valid
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<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
○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.
○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.
○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.
C
Alt Text Quality
Action
19 of 19 images have issues
REVIEW
19 of 19 images have issues
Critical::
19 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
19 images 19 missing
IssueCount
missing19 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

C
Mobile Keyboard & Autofill
Action
1/2 eligible field(s) missing autocomplete or inputmode
REVIEW
1/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email">
B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Bubble | No-code apps ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
h1 مركز الشمال الطبي
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
32px · above the fold
h2 جراحة تجميلية  . جلدية…
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
24px · mid-page
div عربي
1.00:1
#FFFFFF
on
#FFFFFF
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
div 70700450 - 44271999
1.00:1
#FFFFFF
on
#FFFFFF
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
div Al Shamal Medical Center
1.00:1
#FFFFFF
on
#FFFFFF
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

3 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 مركز الشما…1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h1 من نحن21.00:13.0:1
#000000
#FFFFFF
Pass
h1 أقسام المر…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 خدماتنا21.00:13.0:1
#000000
#FFFFFF
Pass
h1 بروفايلو21.00:13.0:1
#000000
#FFFFFF
Pass
h1 بيبي فيس21.00:13.0:1
#000000
#FFFFFF
Pass
h1 الفيلر21.00:13.0:1
#000000
#FFFFFF
Pass
h1 البوتكس21.00:13.0:1
#000000
#FFFFFF
Pass
h1 آخر التدوي…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 اشترك في ال…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 جراحة تجمي…1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h2 عيادة الجر…17.14:13.0:1
#091747
#FFFFFF
Pass
title مركز الشما…21.00:14.5:1
#000000
#FFFFFF
Pass
div عربي1.00:14.5:1
#FFFFFF
#FFFFFF
Fail
div 70700450 - 442719991.00:14.5:1
#FFFFFF
#FFFFFF
Fail
div Al Shamal Medical Ce…1.00:14.5:1
#FFFFFF
#FFFFFF
Fail
div تواصل معنا21.00:14.5:1
#000000
#FFFFFF
Pass
div المدونة20.29:14.5:1
#000000
#FBFBFB
Pass
div فريقنا الط…21.00:14.5:1
#000000
#FFFFFF
Pass
div الأقسام21.00:14.5: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.

A
Heading Hierarchy
12 headings
PASS
12 headings
Warning::
Multiple H1 headings (10 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 مركز الشمال الطبي
  • H2 جراحة تجميلية  . جلدية وتجميل . أسنان
  • H1 من نحن duplicate H1
  • H1 أقسام المركز duplicate H1
  • H2 عيادة الجراحة التجميلية
  • H1 خدماتنا duplicate H1
  • H1 بروفايلو duplicate H1
  • H1 بيبي فيس duplicate H1
  • H1 الفيلر duplicate H1
  • H1 البوتكس duplicate H1
  • H1 آخر التدوينات duplicate H1
  • H1 اشترك في القائمة البريدية 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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
12 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: 12 all-caps heading(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputemail(البريد الالكتروني)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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+
Document Language
Lang attribute set to "ar"
PASS
Lang attribute set to "ar"
Info::
<html lang="ar"> is set and valid
Got: ar
A+
Tabindex Anti-Patterns
2 explicit tabindex attribute(s) checked, no anti-patterns
PASS
2 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="//player.vimeo.com/video/920124510?title=0&byline=0&portrait=0&color=00adef&aut…")
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.
A+
Mobile-Readable Font Sizes
All 62 visible text node(s) render at >= 12 CSS pixels
PASS
All 62 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback