Skip to content
https://www.aljazeera.net

Accessibility

· 22 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
7
REVIEW
6
PASS
9
INFO
0
Checks
22
9 PASS 6 REVIEW 7 FIX
D
Heading Hierarchy
Action
84 headings
FIX
84 headings
Info::
Single H1 present
Warning::
12 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 للجزيرة
  • H2 حرب إيران.. هدوء في هرمز وتواصل الهجمات على جنوب لبنان
  • H3 بوليتيكو: هذا ما تعلمه الجيش الصيني من ضربات أمريكا لإيران
  • H3 مسؤول إيراني يسرد تفاصيل إصابة مجتبى خامنئي وصحته
  • H3 روايتان متناقضتان لاشتباك هرمز: مَن بدأ القصف؟
  • H3 صحيفة أمريكية: من المتوقع استئناف المفاوضات الأسبوع المقبل
  • H2 مسؤول إيراني يكشف تفاصيل إصابة المرشد مجتبى خامنئي
  • H2 مسؤول إيراني يكشف تفاصيل إصابة المرشد مجتبى خامنئي
  • H2 لبنان بين التصعيد والتفاوض.. كيف يُفهم التناقض بين الميدان والدبلوماسية؟
  • H2 حزن معلّق.. عائلات مفقودي غزة تبحث عن حياة بين الموت والاعتقال
  • H2 "رسائل لإسرائيل".. نشيد مرئي جديد للجيش السوري يشعل المنصات
  • H2 ستارمر يتمسك بمنصبه بعد نكسة الانتخابات المحلية ودعوات لرحيله
  • H2 كيف تستخدم هاتفك لاكتشاف الكاميرات المخفية؟
  • H2 تأثير حرب إيران على عمالقة النفط بين مكاسب الأسعار وتعطل الإنتاج
  • H2 فيديو
  • H3 مظاهرة في فرنسا احتجاجا على مشروع حاملة الطائرات
  • H3 أسطول الصمود يستأنف مهمته مجددا نحو غزة
  • H3 طلقات طائشة تخلف قتلى خلال استقبال موقوفي قسد بسوريا
  • H3 حريق في منشأة لإعادة تدوير البلاستيك بالولايات المتحدة
  • H3 لماذا تقلص عرض يوم النصر في موسكو؟
  • H3 برلماني فرنسي: لتكف إسرائيل عن التصرف كدولة مارقة
  • H3 قوات الاحتلال تقتحم نابلس
  • H3 مظاهرة مناهضة للحكومة في ألبانيا
  • H3 أوكرانيا: التخلص من متفجرات تعود للحرب العالمية الثانية
  • H3 "من أطلق الصاروخ على مدرسة البنات في إيران؟"
  • H2 اختيارات المحررين
  • H3 يوميات المهاجر الكهل في “حكايات من بلاد القيقب”
  • H3 "سيامرابتور".. جمجمة مفترس آسيوي تروي قصة صعود عمالقة الديناصورات
  • H3 الجيل ألفا.. السكان الأصليون للعالم الرقمي
  • H2 مراسلو الجزيرة
  • H3 من "الوطني" إلى "العام".. هل تعيد طالبان صياغة خطاب الدولة في أفغانستان؟
  • H3 ملأتها بأنصارها وبالغرباء.. هل تعيد الدعم السريع سيناريو الخرطوم ...
  • H3 "ضربناكم في أعز ما تملكون".. حرب الاحتلال على أشجار الضفة بالأرقام
  • H2 اقتصاد
  • H3 إدارة ترمب تستأنف حكما يبطل رسومها الجمركية العالمية
  • H3 الفاو: ارتفاع أسعار الغذاء لأعلى مستوى في 3 سنوات مع قفزة الطاقة
  • H3 كنز في القمامة.. هل تصبح النفايات الإلكترونية "منجم" معادن نادرة بمصر؟
  • H2 مقالات الرأي
  • H3 ماذا وراء الخط الجوي بين إسرائيل والأرجنتين؟
  • H3 العرب وأجندة 2030.. اقتربنا من الفصل الأخير
  • H3 من المرجح أن تنتهي الحرب على إيران بتراجع أمريكا
  • H3 هل يكون بن غفير ملك إسرائيل القادم؟
  • H3 كيف يمكن التحكم في إيقاع الصراع مع إيران؟
  • H3 لدى باكستان الآن ما هو أهم من المفاوضات المباشرة
  • H3 اشترك في
  • H4 الأخبار العاجلة
  • H2 كيف أغرقت فرنسا الماليين في بحر من الرمال المتحركة؟
  • H2 صحافة
  • H3 ماذا تنتظر الصين بشأن تايوان؟
  • H3 نيويورك تايمز: الحرب استنزفت أمريكا وأضعفت قدرتها على ردع الصين
  • H3 المعضلة الإيرانية.. حيرة واشنطن بين إسقاط النظام والتفاوض معه
  • H3 ستارمر يترنح.. هل دخلت بريطانيا أزمة حكم مفتوحة؟
  • H3 كابوس هانتا.. قصة الفيروس الذي يثير الذعر ولا يشبه كورونا
  • H2 اشتباكات في هرمز تربك الهدنة "الهشة" وسط روايتين متضاربتين
  • H2 رياضة
  • H3 بسبب "قاعدة الساعة الواحدة".. إيقاف بطل أولمبي برازيلي عامين
  • H3 من صفعة ريبيري إلى "نطحة" مدريد.. أبرز المشاجرات بين زملاء الفريق الواحد
  • H3 سفيان بوفال: هكذا اخترت المغرب ولا أخشى الكبار في المونديال
  • H3 "في مكانها المناسب".. أرتيتا يحرج واين روني بعد انتقاده احتفالات أرسنال
  • H3 موهبة الـ 16 ربيعا.. شقيق كفاراتسخيليا يتدرب مع عملاق أوروبي
  • H2 خسارة حزب العمال عددا من مقاعده في انتخابات بريطانيا المحلية
  • H2 مدونات مختارة
  • H3 هل سقطت المقاومة أم سقط نموذجها فقط؟
  • H3 لمن لم يحج.. هذه أبواب الأجر في أيام الحج
  • H3 أطباء الترند.. حين يتحول الطب إلى استعراض!
  • H3 كيف تحقق التفوق الدراسي؟ خطوات عملية للطلاب
  • H3 ما بعد الوظيفة.. هل نفقد هويتنا بعد التقاعد؟
  • H2 واشنطن تبحث عن صاحب القرار في طهران
  • H3 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H3 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H3 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 من نحن
  • H2 تواصل معنا
  • H2 شبكتنا
  • H2 قنواتنا

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
Tabindex Anti-Patterns
Action
0 positive, 20 -1-on-focusable
FIX
0 positive, 20 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Alt Text Quality
1 of 55 images have issues
REVIEW
1 of 55 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
14 image(s) with alt text over 125 characters
Info::
10 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
55 images 30 good alt text 10 decorative 1 missing
IssueCount
missing1 image(s)
too long14 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" name="email" id="email">
C
Tap Target Adequacy
Action
5 tap target(s) too small or too close together
REVIEW
5 tap target(s) too small or too close together
Warning::
5 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.
B
Mobile-Readable Font Sizes
98% of visible text renders at >= 12 CSS px (2 below threshold)
REVIEW
98% of visible text renders at >= 12 CSS px (2 below threshold)
Info::
2 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("محمي بخدمة"); <strong> 11.0px ("reCAPTCHA").
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h1 للجزيرة
1.05:1
#000000
on
#020913
needs 3.0:1 (large text)
32px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 للجزيرة1.05:13.0:1
#000000
#020913
Fail
h2 فيديو21.00:13.0:1
#000000
#FFFFFF
Pass
h2 اختيارات ا…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 مراسلو الج…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 اقتصاد21.00:13.0:1
#000000
#FFFFFF
Pass
h2 مقالات الر…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 صحافة21.00:13.0:1
#000000
#FFFFFF
Pass
h2 رياضة21.00:13.0:1
#000000
#FFFFFF
Pass
h2 مدونات مخت…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 من نحن21.00:13.0:1
#000000
#FFFFFF
Pass
h2 تواصل معنا21.00:13.0:1
#000000
#FFFFFF
Pass
h2 شبكتنا21.00:13.0:1
#000000
#FFFFFF
Pass
h2 قنواتنا21.00:13.0:1
#000000
#FFFFFF
Pass
h3 بوليتيكو: ه…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 مسؤول إيرا…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 روايتان مت…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 صحيفة أمري…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 مظاهرة في ف…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 أسطول الصم…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 طلقات طائش…21.00:13.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.

A
Landmark Structure
28 landmarks
PASS
28 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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.
Page Structure — as a screen reader sees it
BANNER header NAV "قائمة التنقل الأساسية" MAIN ASIDE "trending-articles-heading" CONTENTINFO footer

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

A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 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="text">
Info::
3 control(s) properly labeled
4 controls
3 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#emailemailالبريد الالكترونيaria-label
control-track-progressrangeSlider to adjust track progressaria-label
control-volumerangeSlider to adjust volumearia-label
inputtext(ابحث)placeholder only

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

<input type="text">

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
4 form control(s) checked, no type mismatches
PASS
4 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 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+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title tiktok-colored-outline ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 26 passed
PASS
93

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.

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
محمي بخدمة reCAPTCHA div.l-col > section#news-feed-container > div.sib-newsletter-form > span.google-recaptcha-policy

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.gc__header-wrap > div.gc__header-meta > div.post-label > a.post-label__link
شعار قسم مدونات div.gc__header-wrap > div.gc__header-meta > div.post-label > a.post-label__link
شعار قسم مدونات div.gc__header-wrap > div.gc__header-meta > div.post-label > a.post-label__link
شعار قسم مدونات div.gc__header-wrap > div.gc__header-meta > div.post-label > a.post-label__link
شعار قسم مدونات div.gc__header-wrap > div.gc__header-meta > div.post-label > a.post-label__link

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
مظاهرة في فرنسا احتجاجا على مشروع حاملة الطائرات div#swiper-wrapper-e5d5dbe7c48cf626 > div.swiper-slide > div.vertical-videos-block__video-item > a.vertical-videos-block__video-link
○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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.
●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.
●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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●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 `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
○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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback