Skip to content
https://bankofkhartoum.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
11
REVIEW
3
PASS
10
INFO
0
Checks
24
10 PASS 3 REVIEW 11 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 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
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 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

D
Alt Text Quality
Action
3 of 3 images have issues
FIX
3 of 3 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
3 images 3 missing
IssueCount
missing3 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Form Accessibility
Action
7 of 10 controls have issues
FIX
7 of 10 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="Country">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="Name">; <input type="text" name="cEmail">; <input type="text" name="Cno">; <textarea name="Message">
Info::
3 control(s) properly labeled
10 controls
3 labeled
4 placeholder only
3 unlabeled
ControlTypeLabelMethod
Typeradionone
Typeradionone
Typeradionone
Nametext(Name)placeholder only
cEmailtext(Email)placeholder only
Cnotext(Contact Number)placeholder only
Messagetextarea(Message)placeholder only
Countryselect(none)none
#g-recaptcha-responsetextarea(none)none
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="Country">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="Name">; <input type="text" name="cEmail">; <input type="text" name="Cno">; <textarea name="Message">

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

D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: country-name, name.
Got: <select name="Country">, <input type="text" name="Name">
D
Mobile-Readable Font Sizes
Action
69% of visible text renders at >= 12 CSS px (4 below threshold)
FIX
69% of visible text renders at >= 12 CSS px (4 below threshold)
Warning::
4 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: <a> 11.0px ("About BOK"); <a> 11.0px ("Correspondent Bank"); <a> 11.0px ("Subsidiaries"); <a> 11.0px ("Contact Us").
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 67/100 — 5 failing, 10 passed
FIX
67

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select Country div.main_content_wrapper > div.container > div.landing_link_wrap > h4

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.col-xs-7 > div.logo > a > img.img-responsive div.col-xs-7 > div.logo > a > img.img-responsive

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.row > div.col-xs-7 > div.logo > a div.row > div.col-xs-7 > div.logo > a
div.container > div.row > div.col-xs-5 > a.side_menu_toogle div.container > div.row > div.col-xs-5 > a.side_menu_toogle

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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 html

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>`
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●ARIA IDs are unique
○`[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 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
○Buttons have an accessible name
○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
○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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA 7 pass AA only
h1 Over
2.70:1
#000000
on
#025978
needs 3.0:1 (large text)
32px · bottom of viewport
title Bank of Khartoum| 100 Years of Serving S…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a About BOK
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Correspondent Bank
3.61:1
#000000
on
#0162CB
needs 4.5:1 (normal text)
16px · top of page (header area)
a Subsidiaries
3.72:1
#000000
on
#0164CE
needs 4.5:1 (normal text)
16px · top of page (header area)
a Al Fahed Valuable Assets In Transit Unit…
3.82:1
#000000
on
#0067CD
needs 4.5:1 (normal text)
16px · above the fold
a Canar Telecommunications Co.ltd
3.86:1
#000000
on
#0068CD
needs 4.5:1 (normal text)
16px · above the fold
a IRADA Microfinance Company
4.05:1
#000000
on
#006CCF
needs 4.5:1 (normal text)
16px · above the fold
a National Trading and Services Co. Ltd.
4.09:1
#000000
on
#006DCF
needs 4.5:1 (normal text)
16px · above the fold
a Sanabel Security Co.
4.19:1
#000000
on
#016FD0
needs 4.5:1 (normal text)
16px · above the fold
a SudaCash For Exchange and Money Transfer
4.28:1
#000000
on
#0171D1
needs 4.5:1 (normal text)
16px · above the fold
a Wahat Al Khartoum
4.37:1
#000000
on
#0073D1
needs 4.5:1 (normal text)
16px · above the fold
a Contact Us
4.45:1
#000000
on
#0075CF
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Over2.70:13.0:1
#000000
#025978
Fail
title Bank of Khartoum| 10…1.00:14.5:1
#000000
#000000
Fail
a About BOK1.00:14.5:1
#000000
#000000
Fail
a Correspondent Bank3.61:14.5:1
#000000
#0162CB
Fail
a Subsidiaries3.72:14.5:1
#000000
#0164CE
Fail
a Al Fahed Valuable As…3.82:14.5:1
#000000
#0067CD
Fail
a Canar Telecommunicat…3.86:14.5:1
#000000
#0068CD
Fail
a IRADA Microfinance C…4.05:14.5:1
#000000
#006CCF
Fail
a National Trading and…4.09:14.5:1
#000000
#006DCF
Fail
a Sanabel Security Co.4.19:14.5:1
#000000
#016FD0
Fail
a SudaCash For Exchang…4.28:14.5:1
#000000
#0171D1
Fail
a Wahat Al Khartoum4.37:14.5:1
#000000
#0073D1
Fail
a Contact Us4.45:14.5:1
#000000
#0075CF
Fail
a Language4.50:14.5:1
#000000
#0076D0
Pass
a About BOK4.57:14.5:1
#000000
#1577CF
Pass
a Correspondent Bank4.56:14.5:1
#000000
#2176CF
Pass
a Subsidiaries4.74:14.5:1
#000000
#3279CC
Pass
a Al Fahed Valuable As…4.67:14.5:1
#000000
#3078CB
Pass
a Canar Telecommunicat…4.52:14.5:1
#000000
#2476CA
Pass
a IRADA Microfinance C…4.63:14.5:1
#000000
#2878CA
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
5 headings, 1 skip(s)
PASS
5 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Over 100 Years of service...
  • H4 Select Country skipped
  • H4 About Us
  • H4 Contact Us
  • H4 Correspondent Banks

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

A+
Heading Text Quality
All 5 heading(s) have substantive, well-formed text
PASS
All 5 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "cEmail" should use type="email" (currently type="text")
Field name "cEmail" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
10 form control(s) checked, no input-semantic issues
PASS
10 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
3 explicit tabindex attribute(s) checked, no anti-patterns
PASS
3 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
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