Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.F404 Error PageActionSoft 404 detectedFIX
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.
FFavicon & BrandingAction2 icon(s) detectedFIX
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy13 headings, 1 skip(s)REVIEW
- H1 SAHRA ALERT
- H1 تقريب شروح معلومات المناخ إلى اللهجة الحسانية للمواطن الموريتاني duplicate H1
- H3 ميثاق الشفافية وحدود المشروع التجريبي وحماية المصدر skipped
- H2 نشرة جوية: موجة حرارة حادة وتدني الرؤية بالأتربة المثارة في الشمال
- H2 كيف يُبسَّط النص المناخي مع ضوابط السلامة؟
- H3 استلام النص المصدر
- H3 الاستخلاص وضوابط الاتساق
- H3 مسار المراجعة والتحقق
- H3 العرض التوضيحي والقراءة الصوتية
- H3 النشرات والسيناريوهات المناخية
- H3 الشروح المبسطة بالحسانية
- H3 المعجم الحساني المبسط
- H2 بنية بثلاث بيئات منفصلة تماماً لعرض موثوق
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
CMobile-Readable Font SizesAction70% of visible text renders at >= 12 CSS px (29 below threshold)REVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 1 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 SAHRA ALERT | 19.09:1 | 3.0:1 | #000000 | #F7F4EB | Pass |
| h1 تقريب شروح … | 19.09:1 | 3.0:1 | #000000 | #F7F4EB | Pass |
| h2 نشرة جوية: Ù… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h2 كيف يُبسَّØ… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h2 بنية بثلاث … | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h3 ميثاق الشفØ… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h3 استلام النØ… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h3 الاستخلاص Ù… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h3 مسار المراØ… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h3 العرض التوØ… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h3 النشرات واÙ… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h3 الشروح المØ… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| h3 المعجم الحØ… | 20.12:1 | 3.0:1 | #000000 | #FDFAF1 | Pass |
| title SAHRA ALERT – مس… | 2.18:1 | 4.5:1 | #000000 | #004F3B | Fail |
| a الانتقال مØ… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span P.A.S Challenge 2026 | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span زين الدين م… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span تثمين اللهØ… | 20.48:1 | 4.5:1 | #000000 | #FEFCF7 | Pass |
| span عرض عمومي   | 20.30:1 | 4.5:1 | #000000 | #FEFBF2 | Pass |
| span تسجيل الدخÙ… | 19.78:1 | 4.5:1 | #000000 | #FBF8EF | 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.
ALandmark Structure4 landmarksPASS
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
A+Heading Text Quality1 heading-text-quality issue(s) detectedPASS
A+Alt Text QualityAll 2 images OKPASS
A+Form AccessibilityNo form controlsPASS
A+Link & Button Quality1 links, 25 buttons — all OKPASS
A+Form Input TypesNo form controls on this pagePASS
A+Form Input QualityNo form controls on this pagePASS
A+Mobile Keyboard & AutofillNo form controls -- mobile keyboard check is N/APASS
A+Document LanguageLang attribute set to "ar"PASS
A+Tabindex Anti-Patterns1 explicit tabindex attribute(s) checked, no anti-patternsPASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
A+Lighthouse Accessibility AuditsScore 98/100 — 2 failing, 23 passedPASS
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.
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 |
|---|
ميثاق الشفافية وحدود المشروع التجريبي وحماية المصدر section.bg-amber-50/90 > div.flex > div > h3.text-sm |
These are opportunities to improve keyboard navigation in your application.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
SAHRA ALERT header.sticky > div.max-w-7xl > div.flex > button.cursor-pointer |