Skip to content
https://al-monitor.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Alt Text Quality
Action
6 of 83 images have issues
FIX
6 of 83 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
3 image(s) with generic alt text
Info::
21 image(s) with alt text over 125 characters
Info::
3 decorative image(s) correctly marked
Info::
53 image(s) with good alt text
83 images 53 good alt text 3 decorative 3 generic 3 missing
IssueCount
missing3 image(s)
generic3 image(s)
too long21 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

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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.
C
Heading Hierarchy
Action
69 headings, 1 skip(s)
REVIEW
69 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 The Middle Eastʼs leading independent news source since 2012
  • H2 Search
  • H2 Main navigation
  • H2 Secondary Navigation
  • H2 Who is Ahmad Vahidi, IRGC chief and hard-liner against nuclear compromise?
  • H2 Split over Maliki, Iraq’s Shiite bloc delays PM vote as deadline nears: What to know
  • H2 'Is it worth it?' Syria's Sharaa faces backlash over Missy Elliott performance
  • H2 Iran executes 14th person since war over alleged Mossad ties: What to know
  • H2 Iran seizes two cargo ships in Hormuz after Trump extends ceasefire
  • H3 Latest News
  • H2 Trump extends ceasefire with Iran ‘until discussions concluded’
  • H2 How are Iran-linked tankers still moving through Hormuz blockade?
  • H2 Military planners to discuss Hormuz reopening in London
  • H2 As Iran's power struggle deepens, US talks stall, who’s calling the shots in Tehran?
  • H2 Get unlimited access for as little as $2/week.
  • H3 Subscriber-Only Benefits
  • H2 Trump looks for way out on war, but Iran may not oblige
  • H2 Exclusive-US intercepts three Iranian oil tankers in Asian waters, sources say
  • H2 Trump says eight Iranian women won't be executed, Iran disputes entire account
  • H2 US wants to see unified response from Iran, White House says
  • H3 Featured Newsletters
  • H2 US forces board Iran-linked tanker
  • H2 How are tankers bypassing Hormuz blockade?
  • H2 Does the UAE need a US financial cushion?
  • H2 NEOM’s new logistics look
  • H3 Editor's choice
  • H2 Ceasefire or strategic pause? How Iran is framing war narrative amid deep mistrust
  • H2 Trump ceasefire leaves Netanyahu flustered as Iran gains politically
  • H2 Shelly Kittleson's kidnapping by suspected Iran-backed militia exposes Iraq government weakness
  • H2 Expert insight on the Middle East—delivered regularly
  • H3 Read By
  • H3 Audio
  • H2 What to make of Pakistan’s increased defense ties with Saudi Arabia
  • H2 As Iran declares Strait of Hormuz “fully open”, what does it mean for Gulf?
  • H2 Lebanon’s Ghassan Salame: Israel talks ‘not negotiations,’ Hezbollah disarmament by force ‘illusion’
  • H3 Interviews
  • H2 UAE official says opening Hormuz integral to any Iran deal, describes infrastructure damage 'manageable'
  • H2 Minister warns aid cuts to Lebanon risk empowering Hezbollah
  • H2 Despite Trump’s U-turns, US may still support Iran’s Kurds, says Komala’s Mohtadi
  • H2 Olmert: Only Israel-Lebanon deal can curb Hezbollah, occupation 'unviable'
  • H3 The City Pulse Newsletters
  • H2 Izmir opens new art center backed by Centre Pompidou
  • H2 Saudi creatives in Milan
  • H2 Rethinking fashion in Doha
  • H2 Barjeel Art Foundation unveils plans for Sharjah museum
  • H3 Analysis
  • H2 As Iran's power struggle deepens, US talks stall, who’s calling the shots in Tehran?
  • H2 Gulf energy deals face Iran war stress test as global expansion meets oil shock
  • H2 Israel sees chance of US-Iran deal as almost 'non-existent,' readies for war
  • H2 'Is it worth it?' Syria's Sharaa faces backlash over Missy Elliott performance
  • H3 Videos
  • H2 Iran War at One Month: Outlook and Implications
  • H2 Ukraine's Zelenskyy capitalizes on Iran war to ink security deal with Saudi Arabia
  • H2 French ISIS Member Convicted of Genocide Against Yazidis
  • H2 AL-MONITOR's Ezgi Akin at Turkey-Iran Border Crossing
  • H3 AL-MONITOR Live Journalism
  • H2 AL-MONITOR Global Institute hosts food security forum with Dr. Conrad Rein
  • H2 AL-MONITOR Global Institute hosts Digital Cooperation Organization Secretary-General Deemah AlYahya
  • H2 AL-MONITOR Global Institute hosts Iraqi Kurdistan Prime Minister Masrour Barzani and US Energy Secretary Chris Wright
  • H3 Our Journalists
  • H2 Samuel Wendel
  • H2 Amberin Zaman
  • H2 Adam Lucente
  • H2 Jack Dutton
  • H2 Elizabeth Hagedorn
  • H2 Ezgi Akin
  • H2 The Middle Eastʼs leading independent news source since 2012
  • H2 Sign up to our Daily Briefing
  • H5 ©2026 AL-MONITOR, LLC. All rights reserved. skipped

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="text" id="edit-text">; <input type="email" name="email" id="edit-email">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#edit-texttext(Keywords, topics and authors)placeholder only
#edit-emailemail(Email Address)placeholder only

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

<input type="text" name="text" id="edit-text">; <input type="email" name="email" id="edit-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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - AL-MONITOR: The Middle Eastʼs leading independent news source since 2012 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
22 icon(s) detected
REVIEW
22 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 23 passed
REVIEW
86

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
The Middle Eastʼs leading independent news source since 2012 div.footer__inner > div.footer__top > div.footer__footer_logo > h2.h2

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
©2026 AL-MONITOR, LLC. All rights reserved. footer.footer > div.footer__inner > div.footer__bottom > h5.h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.section--content > div.split-60-40 > div.split-60-40__region > img.image div.section--content > div.split-60-40 > div.split-60-40__region > img.image

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.header__primary > div.header__primary_content > div.header__search_nav > a#toggle-expand div.header__primary > div.header__primary_content > div.header__search_nav > a#toggle-expand
div.awp-micro-table-wrapper > div.awp-left > div.awp-brand-logo > a.awp-series-link div.awp-micro-table-wrapper > div.awp-left > div.awp-brand-logo > a.awp-series-link
div.awp-micro-table-wrapper > div.awp-left > div.awp-brand-logo > a.awp-series-link div.awp-micro-table-wrapper > div.awp-left > div.awp-brand-logo > a.awp-series-link
div.awp-micro-table-wrapper > div.awp-left > div.awp-brand-logo > a.awp-series-link div.awp-micro-table-wrapper > div.awp-left > div.awp-brand-logo > a.awp-series-link
div.card__meta > div.byline > div.byline__media > a div.card__meta > div.byline > div.byline__media > a
div.byline > div.byline__media > div.time_watch > a div.byline > div.byline__media > div.time_watch > a
div.card__meta > div.byline > div.byline__media > a div.card__meta > div.byline > div.byline__media > a
div.byline > div.byline__media > div.time_watch > a div.byline > div.byline__media > div.time_watch > a
div.card__meta > div.byline > div.byline__media > a div.card__meta > div.byline > div.byline__media > a
div.byline > div.byline__media > div.time_watch > a div.byline > div.byline__media > div.time_watch > a
div.card__meta > div.byline > div.byline__media > a div.card__meta > div.byline > div.byline__media > a
div.byline > div.byline__media > div.time_watch > a div.byline > div.byline__media > div.time_watch > 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.

○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
●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.
●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
●Touch targets have sufficient size and spacing.
●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 `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>`.
○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
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "block-alm-main-menu-menu" MAIN CONTENTINFO footer

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

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)
ElementRatioRequiredFGBGResult
h2 The Middle Eastʼs l…6.06:13.0:1
#000000
#808B98
Pass
h2 Search6.26:13.0:1
#000000
#808E9B
Pass
h2 Main navigation5.55:13.0:1
#000000
#788498
Pass
h2 Secondary Navigation19.13:13.0:1
#000000
#F6F4F1
Pass
h2 Get unlimited access…19.13:13.0:1
#000000
#F6F4F1
Pass
h2 Expert insight on th…19.13:13.0:1
#000000
#F6F4F1
Pass
h2 The Middle Eastʼs l…19.13:13.0:1
#000000
#F6F4F1
Pass
h2 Sign up to our Daily…19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Latest News19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Subscriber-Only Bene…19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Featured Newsletters19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Editor's choice19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Read By19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Audio19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Interviews19.13:13.0:1
#000000
#F6F4F1
Pass
h3 The City Pulse Newsl…19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Analysis19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Videos19.13:13.0:1
#000000
#F6F4F1
Pass
h3 AL-MONITOR Live Jour…19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Our Journalists19.13:13.0:1
#000000
#F6F4F1
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback