Skip to content
https://khaleejtimes.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✗ Multiple Sizes Missing
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #001861
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 ModePartial Dark Mode
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::
1 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 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 (missing!) CONTENTINFO footer

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

B
Form Accessibility
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search" id="search">; <input type="text" name="q" id="search">; <input type="email" name="email" id="email-sign-up">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchtext(Type here to search news, photos, videos...)placeholder only
#searchtext(Type here to search news, photos, videos...)placeholder only
#email-sign-upemail(Enter your email address...)placeholder only

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

<input type="text" name="search" id="search">; <input type="text" name="q" id="search">; <input type="email" name="email" id="email-sign-up">

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

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 Khaleej Times - Dubai News, UAE News, Gulf, News, Latest news, Arab news, Gulf News, Dubai Labour News ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
a Fajr 4:29 AM
1.50:1
#000000
on
#20265D
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Follow us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Download our Mobile …21.00:13.0:1
#000000
#FFFFFF
Pass
title Khaleej Times - Duba…18.91:14.5:1
#000000
#F2F3F5
Pass
div WANT MORE KHALEEJ TI…21.00:14.5:1
#000000
#FFFFFF
Pass
div Get the latest on th…21.00:14.5:1
#000000
#FFFFFF
Pass
a VIEW14.03:14.5:1
#20265D
#FFFFFF
Pass
span Wed, Apr 22, 202621.00:14.5:1
#000000
#FFFFFF
Pass
span | Dhu al-Qadah 4, 14…21.00:14.5:1
#000000
#FFFFFF
Pass
a Fajr 4:29 AM1.50:14.5:1
#000000
#20265D
Fail
a E-Paper8.97:14.5:1
#000000
#A6A8BE
Pass
a Sign In21.00:14.5:1
#000000
#FFFFFF
Pass
span Gold21.00:14.5:1
#000000
#FFFFFF
Pass
span Forex21.00:14.5:1
#000000
#FFFFFF
Pass
strong VOICE OF THE UAE.21.00:13.0:1
#000000
#FFFFFF
Pass
p SINCE 197821.00:14.5:1
#000000
#FFFFFF
Pass
span DXB21.00:14.5:1
#000000
#FFFFFF
Pass
span 27.8°C21.00:14.5:1
#000000
#FFFFFF
Pass
span Prayer21.00:14.5:1
#000000
#FFFFFF
Pass
span Breaking21.00:14.5:1
#000000
#FFFFFF
Pass
a Abu Dhabi to introdu…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
30 headings
PASS
30 headings
Info::
Single H1 present
  • H3 Follow us
  • H3 Download our Mobile App
  • H1 LiveTrump says next round of peace talks expected in 3 days; no deadline for truce extension
  • H2 Two new Darb toll gates in Abu Dhabi to operate 24/7 starting May 4
  • H2 Sheikh Mohammed announces new Dubai Metro Gold Line, project to start immediately
  • H2 Sharjah astronomers reveal likely first day of Eid Al Adha 2026 in UAE
  • H2 The future of hiring isn’t AI - it’s trust infrastructure
  • H2 Dubai Gold Line to ease crowding on key Metro routes, cut road traffic
  • H2 UAE Lottery: Winning numbers in latest draw out; Dh30 million jackpot unclaimed
  • H2 Sheikh Hamdan visits Dubai's KHDA, reviews preparations for schools reopening
  • H2 Dubai Metro Gold Line map unveiled: High speed rail to run from Ras Al Khor to beyond Expo
  • H2 Sharjah chocolate: What are its proposed flavours? What does Qand mean?
  • H2 Watch: RAK Crown Prince performs Emirati 'Yola' dance at mass wedding in viral video
  • H2 Partner Content: Canada's next-generation entrepreneur immigration programme - Exclusive early access opportunity
  • H3 MOST POPULAR
  • H4 Don't just scroll.Know it all. Sign up for your daily UAE news fix.
  • H3 Partner Content
  • H4 AI without the hype: The new HONOR 600 redefines the smartest smartphone experience
  • H4 HRE Development commences handover of Skyhills Residences 1 By HRE - six months ahead of schedule
  • H4 Mediclinic City Hospital reinforces leadership in robotic-assisted surgery
  • H4 AVENEW Development and Wadeen Developers announce the launch of Cheval Residences at Dubai Islands
  • H4 Tiger Properties sets Sesilia Tower handover for April 20, unveils 2026 delivery pipeline
  • H4 CFI advances its operations in Egypt with Amr Abdelbaky appointed CEO of CFI Egypt
  • H3 Videos & Podcasts
  • H4 UAE launches tool to track grocery prices daily
  • H4 Global Village reopens in Dubai for Season 30
  • H4 UAE built through action not words or promises
  • H4 Saudi sets April 18 exit deadline for Umrah visas
  • H4 Gulf hiring holds steady despite regional tensions
  • H4 Watch Marisa Peer break down negative thinking
A
Alt Text Quality
2 of 54 images have issues
PASS
2 of 54 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with filename as alt text
Info::
6 decorative image(s) correctly marked
Info::
46 image(s) with good alt text
54 images 46 good alt text 6 decorative 1 generic 1 missing
IssueCount
missing1 image(s)
filename1 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

A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Khaleej Times: UAE, World News
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Khaleej Times: UAE, World News ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name Khaleej Times: UAE, World News Display Mode standalone Theme Color #20255C Background Color #20255C Icons 1 icon(s)
A
Lighthouse Accessibility Audits
Score 93/100 — 2 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.

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
body > button#__ap_gfc_consent_box_btn__ > img body > button#__ap_gfc_consent_box_btn__ > img

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

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.macos html.macos

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
●Buttons have an accessible name
●`[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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○`<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.
○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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback