Skip to content
https://ibaconsultingworldwide.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
13
REVIEW
3
PASS
8
INFO
0
Checks
24
8 PASS 3 REVIEW 13 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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

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

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

F
Heading Hierarchy
Action
34 headings, 3 skip(s)
FIX
34 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
6 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H3 You need three things to get to the Top... skipped
  • H4 Attitude...   Ambition...   Initiation...
  • H3 Don't Manage........ LEAD!
  • H4 (empty)
  • H3 Be an Achiever... not a performer
  • H4 (empty)
  • H3 Unleash..... your Team's Talent
  • H4 (empty)
  • H3 Building Leaders... who can LEAD
  • H4 (empty)
  • H5 Current Job Opening
  • H4 Jobs
  • H4 CEO J O B S
  • H4 CFO J O B S
  • H4 CHRO J O B S
  • H4 CMO J O B S
  • H4 CIO/CTO J O B S
  • H4 Manufacturing J O B S
  • H3 About Us
  • H3 Our Services
  • H3 Top Program
  • H3 TOP EMPLOYERS
  • H5 (empty)
  • H4 Train the TrainerP R O G R A M
  • H4 E LearningP R O G R A M
  • H4 Consulting
  • H5 Apply today
  • H5 Contact Us
  • H3 Quick Links
  • H3 Programs
  • H3 International Business Advantage
  • H3 Get Your Membership
  • H5 Contact Us skipped

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

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

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

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

F
Alt Text Quality
Action
55 of 89 images have issues
FIX
55 of 89 images have issues
Critical::
12 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
11 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
43 image(s) with generic alt text
Info::
6 decorative image(s) correctly marked
Info::
28 image(s) with good alt text
89 images 28 good alt text 6 decorative 43 generic 12 missing
IssueCount
missing12 image(s)
generic43 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
45 of 53 controls have issues
FIX
45 of 53 controls have issues
Critical::
12 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="mr">; <input type="file" name="Fichier1">; <input type="file" name="Fichier1">; <input type="file" name="Fichier1">; <select name="mr">; <textarea name="requirements">; <select>; <input type="file" name="Fichier1">; <input type="file" name="Fichier1">; <input type="file" name="Fichier1"> (+2 more)
Warning::
33 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">; <input type="text" name="name">; <input type="text" name="skype" id="skype">; <input type="text" name="location" id="location">; <input type="text" name="company" id="cname">; <input type="text" name="designation" id="designame">; <textarea name="message" id="message">; <input type="text" name="resume">; <input type="text" name="photo"> (+23 more)
Info::
8 control(s) properly labeled
53 controls
8 labeled
33 placeholder only
12 unlabeled
ControlTypeLabelMethod
#emailemailEmailfor/id
#mobiletextDescribe your requirementsfor/id
#emailemailEmailfor/id
#mobiletextDescribe your requirementsfor/id
#emailemailEmailfor/id
#mobiletextDescribe your requirementsfor/id
#emailemailEmailfor/id
#mobiletextDescribe your requirementsfor/id
#designametext(Your Designation)placeholder only
#messagetextarea(Message)placeholder only
resumetext(Upload a file...)placeholder only
phototext(Upload a photo...)placeholder only
ctctext(Upload Annual CTC Support...)placeholder only
nametext(Name)placeholder only
nametext(Name)placeholder only
nametext(Search term...)placeholder only
#skypetext(Skype ID)placeholder only
#locationtext(Your Current Location)placeholder only
#cnametext(Your Current Company)placeholder only
#designametext(Your Designation)placeholder only
#nametext(Enter Your Name)placeholder only
#phonetext(Enter Your Phone)placeholder only
#citytext(Enter Your Email)placeholder only
#commenttextarea(Enter your Message)placeholder only
inputtext(Name)placeholder only
inputtext(Search)placeholder only
#skypetext(Skype ID)placeholder only
#skypetext(Skype ID)placeholder only
#locationtext(Your Current Location)placeholder only
#cnametext(Your Current Company)placeholder only
#designametext(Your Designation)placeholder only
inputtext(Upload a file...)placeholder only
inputtext(Upload a photo...)placeholder only
inputtext(Upload Annual CTC Support...)placeholder only
inputtext(Name)placeholder only
#locationtext(Your Current Location)placeholder only
#cnametext(Your Current Company)placeholder only
#skypetext(Skype ID)placeholder only
#locationtext(Your Current Location)placeholder only
#cnametext(Your Current Company)placeholder only
#designametext(Your Designation)placeholder only
requirementstextarea(none)none
Fichier1file(none)none
Fichier1file(none)none
selectselect(none)none
mrselect(none)none
mrselect(none)none
Fichier1file(none)none
selectselect(none)none
Fichier1file(none)none
Fichier1file(none)none
Fichier1file(none)none
textareatextarea(none)none

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

<select name="mr">; <input type="file" name="Fichier1">; <input type="file" name="Fichier1">; <input type="file" name="Fichier1">; <select name="mr">; <textarea name="requirements">; <select>; <input type="file" name="Fichier1">; <input type="file" name="Fichier1">; <input type="file" name="Fichier1"> (+2 more)

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">; <input type="text" name="name">; <input type="text" name="skype" id="skype">; <input type="text" name="location" id="location">; <input type="text" name="company" id="cname">; <input type="text" name="designation" id="designame">; <textarea name="message" id="message">; <input type="text" name="resume">; <input type="text" name="photo"> (+23 more)

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
12/12 eligible field(s) missing autocomplete or inputmode
FIX
12/12 eligible field(s) missing autocomplete or inputmode
Warning::
8 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: name, email.
Got: <input type="text" name="name">, <input type="text" name="name">, <input type="email" name="email" id="email">, <input type="text" name="name">, <input type="text" name="name" id="name">
Warning::
4 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">, <input type="email" name="mail" id="email">, <input type="email" id="email">, <input type="email" id="email">
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-460zos
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

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.

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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://ibaconsultingworldwide.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://ibaconsultingworldwide.com/manifest.json

Manifest contains invalid JSON.

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.
D
Lighthouse Accessibility Audits
Action
Score 67/100 — 10 failing, 23 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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
You need three things to get to the Top... ATTITUDE...   AMBITION...   INITIATI… div.col-md-12 > div.banner > div#kb > div.carousel-inner

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Leadership Coaching Solutions div.card > ul.nav > li.item > a
Impact Sales Training div.card > ul.nav > li.item > a
Soft Skill Programs div.card > ul.nav > li.item > a
University Programs div.card > ul.nav > li.item > a

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
You need three things to get to the Top... ATTITUDE...   AMBITION...   INITIATI… div.col-md-12 > div.banner > div#kb > div.carousel-inner

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form > div.input-group > span.input-group-btn > button.btn form > div.input-group > span.input-group-btn > button.btn
div#custom-search-input > div.input-group > span.input-group-btn > button.btn div#custom-search-input > div.input-group > span.input-group-btn > button.btn

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.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.col-xs-12 > div.row > div.col-md-12 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.agileits_work_grids > div.row > div.col-md-2 > img.img-responsive
div.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.row > div.col-xs-12 > a > img.img-responsive div.row > div.col-xs-12 > a > img.img-responsive
div.col-xs-12 > p > a > img.img-responsive div.col-xs-12 > p > a > img.img-responsive

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-xs-12 > div.row > div.col-xs-12 > iframe div.col-xs-12 > div.row > div.col-xs-12 > iframe
div.col-xs-12 > div.row > div.col-xs-12 > iframe div.col-xs-12 > div.row > div.col-xs-12 > iframe
div.col-xs-12 > div.row > div.col-xs-12 > iframe div.col-xs-12 > div.row > div.col-xs-12 > iframe
div.col-md-3 > ul.list-icons > li > iframe div.col-md-3 > ul.list-icons > li > iframe

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.w3l_header_left > ul > li > a div.w3l_header_left > ul > li > a
div.w3l_header_left > ul > li > a div.w3l_header_left > ul > li > a
div.w3l_header_left > ul > li > a div.w3l_header_left > ul > li > a
div.w3l_header_left > ul > li > a div.w3l_header_left > ul > li > a
div.col-md-6 > div.logo > h1 > a.navbar-brand div.col-md-6 > div.logo > h1 > a.navbar-brand
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.col-xs-12 > div.row > div.col-xs-12 > a div.col-xs-12 > div.row > div.col-xs-12 > a
div.row > div.col-xs-12 > p > a div.row > div.col-xs-12 > p > a
div.agileinfo_copy_right_right > ul.social-bnr-agileits > li > a div.agileinfo_copy_right_right > ul.social-bnr-agileits > li > a
div.agileinfo_copy_right_right > ul.social-bnr-agileits > li > a div.agileinfo_copy_right_right > ul.social-bnr-agileits > li > a
div.agileinfo_copy_right_right > ul.social-bnr-agileits > li > a div.agileinfo_copy_right_right > ul.social-bnr-agileits > li > a
div.agileinfo_copy_right_right > ul.social-bnr-agileits > li > a div.agileinfo_copy_right_right > ul.social-bnr-agileits > li > 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.

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
Apply today div.row > div.col-xs-12 > p > button#jobs
Apply today div.row > div.col-xs-12 > p.apply-button > button#ceojobs
CFO J O B S div.col-xs-12 > div.row > div.col-xs-12 > h4
J O B S div.row > div.col-xs-12 > h4 > span
CHRO J O B S div.col-xs-12 > div.row > div.col-xs-12 > h4
J O B S div.row > div.col-xs-12 > h4 > span
CIO/CTO J O B S div.col-xs-12 > div.row > div.col-xs-12 > h4
J O B S div.row > div.col-xs-12 > h4 > span
International Business Advantage is a Global Search & Business Consulting Compa… div.col-xs-12 > div.row > div.wthree-text > p
Read More.. ul.about-agile > li > p > a.btn
Leadership Coaching Solutions div.card > ul.nav > li.item > a
Register today div.row > div.col-xs-12 > p.apply-button > a.btn
Register today div.row > div.col-xs-12 > p.apply-button > a.btn
Behavioural Executive Coaching div.col-xs-12 > div.row > div.list-group > a.list-group-item
Family Business Management 1 div.col-xs-12 > div.row > div.list-group > a.list-group-item
Family Business Management 2 div.col-xs-12 > div.row > div.list-group > a.list-group-item
Inspiring Leadership div.col-xs-12 > div.row > div.list-group > a.list-group-item
Leading high performance teams div.col-xs-12 > div.row > div.list-group > a.list-group-item
Managing Role Transition:Preparing for the Next Role div.col-xs-12 > div.row > div.list-group > a.list-group-item
Sell like a Champion div.col-xs-12 > div.row > div.list-group > a.list-group-item
Power Selling div.col-xs-12 > div.row > div.list-group > a.list-group-item
Negotiation Techniques for Sales Team div.col-xs-12 > div.row > div.list-group > a.list-group-item
Customer First div.col-xs-12 > div.row > div.list-group > a.list-group-item
You are a Brand div.col-xs-12 > div.row > div.list-group > a.list-group-item
TRAIN THE TRAINER div.col-xs-12 > div.row > div.list-group > a.list-group-item
Digital Marketing Program div.col-xs-12 > div.row > div.list-group > a.list-group-item
Reinvent the inner YOU div.col-xs-12 > div.row > div.list-group > a.list-group-item
Impressive Personality for Achieving Success div.col-xs-12 > div.row > div.list-group > a.list-group-item
Business Communication Skills div.col-xs-12 > div.row > div.list-group > a.list-group-item
Hi Impact Presentation Skill Program div.col-xs-12 > div.row > div.list-group > a.list-group-item
Influencing Others div.col-xs-12 > div.row > div.list-group > a.list-group-item
Negotiation Techniques div.col-xs-12 > div.row > div.list-group > a.list-group-item
Master your Decision Making div.col-xs-12 > div.row > div.list-group > a.list-group-item
Assertiveness at work div.col-xs-12 > div.row > div.list-group > a.list-group-item
Beating Procrastination First Things First div.col-xs-12 > div.row > div.list-group > a.list-group-item
Journey to Corporate Life FOUNDATION PROGRAM div.col-xs-12 > div.row > div.list-group > a.list-group-item
How to be Employable? MASTER PROGRAM div.col-xs-12 > div.row > div.list-group > a.list-group-item
How to be Employable? SPECIALIZED PROGRAM div.col-xs-12 > div.row > div.list-group > a.list-group-item
Contact Today div.row > div.col-xs-12 > p > button.btn
Send Enquiry div.form-group > div.col-sm-12 > p > button.btn

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
You need three things to get to the Top... div.carousel-inner > div.item > div.carousel-caption > h3
div.col-xs-12 > div.row > div.w3_tittle > h5.agile-tittle div.col-xs-12 > div.row > div.w3_tittle > h5.agile-tittle

These are opportunities to improve keyboard navigation in your application.

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 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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes are valid and not misspelled
●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
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
●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 `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○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>`.
○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.
B
Form Input Types
4 input(s) using type=text where a specific type would help
REVIEW
4 input(s) using type=text where a specific type would help
Info::
Input "name" should use type="search" (currently type="text")
Field name "name" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "Search" should use type="search" (currently type="text")
Field name "Search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "mobile" should use type="tel" (currently type="text")
Field name "mobile" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
Info::
Input "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
C
Iframe Accessibility
Action
4/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
4/4 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.youtube.com/embed/Hwn_W-X2Rds?ecver=1")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.youtube.com/embed/oMBLyCxfgkw?ecver=1")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.youtube.com/embed/8snbL_kVmXw?ecver=1")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d224563.67561642965!2d76.8…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
title International Business Advantage
1.36:1
#000000
on
#0C2544
needs 4.5:1 (normal text)
16px · top of page (header area)
a Login
1.36:1
#000000
on
#0C2544
needs 4.5:1 (normal text)
16px · top of page (header area)
a Employer Zone
1.36:1
#000000
on
#0C2544
needs 4.5:1 (normal text)
16px · top of page (header area)
a business@ibasearch.com
1.36:1
#000000
on
#0C2544
needs 4.5:1 (normal text)
16px · top of page (header area)
a +91 8802756666,
1.36:1
#000000
on
#0C2544
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 You need three thing…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Don't Manage........…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Be an Achiever... no…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Unleash..... your Te…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Building Leaders... …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 About Us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Our Services21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Top Program21.00:13.0:1
#000000
#FFFFFF
Pass
h3 TOP EMPLOYERS21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Quick Links21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Programs21.00:13.0:1
#000000
#FFFFFF
Pass
h3 International Busine…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get Your Membership21.00:13.0:1
#000000
#FFFFFF
Pass
title International Busine…1.36:14.5:1
#000000
#0C2544
Fail
a Login1.36:14.5:1
#000000
#0C2544
Fail
a Employer Zone1.36:14.5:1
#000000
#0C2544
Fail
a business@ibasearch.c…1.36:14.5:1
#000000
#0C2544
Fail
a +91 8802756666,1.36:14.5:1
#000000
#0C2544
Fail
a +91-880270666621.00:14.5:1
#000000
#FFFFFF
Pass
span Filter by21.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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
6 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 6 all-caps heading(s)
A+
Form Input Quality
53 form control(s) checked, no input-semantic issues
PASS
53 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
4 explicit tabindex attribute(s) checked, no anti-patterns
PASS
4 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
Mobile-Readable Font Sizes
All 90 visible text node(s) render at >= 12 CSS pixels
PASS
All 90 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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