Skip to content
https://keenoverseas.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
3/3 eligible field(s) missing autocomplete or inputmode
FIX
3/3 eligible field(s) missing autocomplete or inputmode
Warning::
1 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: email.
Got: <input type="email" name="email">
Warning::
2 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: tel, email.
Got: <input type="tel" name="phone">, <input type="email" name="email">
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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::
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
2 landmarks
REVIEW
2 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
Info::
No banner (header) 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 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="fullName">; <input type="tel" name="phone">; <input type="email" name="email">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
fullNametext(Full Name)placeholder only
phonetel(Mobile Number)placeholder only
emailemail(Email Address)placeholder only

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

<input type="text" name="fullName">; <input type="tel" name="phone">; <input type="email" name="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

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 This Page Does Not Exist ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
h1 & Immigration Success
2.24:1
#000000
on
#3C494A
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 Your Gateway To Global Education
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
32px · bottom of viewport
h1 & Immigration Success
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Book Your
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted Immigration Experts
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore Opportunities Worldwide
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Prepare for Success
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Student Testimonials
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Got Questions?
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Keen Overseas
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Book Your FREE Consultation
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Personalized Counseling
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Transparent Process
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Visa Expertise
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
19px · bottom of viewport
h3 End-to-End Support
1.43:1
#000000
on
#1F2A31
needs 3.0:1 (large text)
19px · bottom of viewport

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Your Gateway To Glob…7.84:13.0:1
#000000
#89A1B6
Pass
h1 & Immigration Succes…8.05:13.0:1
#000000
#8DA3B6
Pass
h1 Your Gateway To Glob…9.56:13.0:1
#000000
#A2B1BD
Pass
h1 & Immigration Succes…10.36:13.0:1
#000000
#ABB8C1
Pass
h1 Your Gateway To Glob…5.64:13.0:1
#000000
#7A8787
Pass
h1 & Immigration Succes…2.24:13.0:1
#000000
#3C494A
Fail
h1 Your Gateway To Glob…1.43:13.0:1
#000000
#1F2A31
Fail
h1 & Immigration Succes…1.43:13.0:1
#000000
#1F2A31
Fail
h2 Book Your1.43:13.0:1
#000000
#1F2A31
Fail
h2 Trusted Immigration …1.43:13.0:1
#000000
#1F2A31
Fail
h2 Explore Opportunitie…1.43:13.0:1
#000000
#1F2A31
Fail
h2 Prepare for Success1.43:13.0:1
#000000
#1F2A31
Fail
h2 Student Testimonials1.43:13.0:1
#000000
#1F2A31
Fail
h2 Got Questions?1.43:13.0:1
#000000
#1F2A31
Fail
h2 Keen Overseas1.43:13.0:1
#000000
#1F2A31
Fail
h3 Book Your FREE Consu…1.43:13.0:1
#000000
#1F2A31
Fail
h3 Personalized Counsel…1.43:13.0:1
#000000
#1F2A31
Fail
h3 Transparent Process1.43:13.0:1
#000000
#1F2A31
Fail
h3 Visa Expertise1.43:13.0:1
#000000
#1F2A31
Fail
h3 End-to-End Support1.43:13.0:1
#000000
#1F2A31
Fail

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.

B
Lighthouse Accessibility Audits
Score 80/100 — 3 failing, 13 passed
REVIEW
80

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

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
nav.sticky > div.max-w-7xl > div.flex > button.w-9 nav.sticky > div.max-w-7xl > div.flex > button.w-9
nav.sticky > div.max-w-7xl > div.flex > button.md:hidden nav.sticky > div.max-w-7xl > div.flex > button.md:hidden

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.grid > div > div.inline-flex > a.inline-flex div.grid > div > div.inline-flex > a.inline-flex
div.grid > div > div.inline-flex > a.inline-flex div.grid > div > div.inline-flex > a.inline-flex
div.grid > div > div.inline-flex > a.inline-flex div.grid > div > div.inline-flex > a.inline-flex
div.grid > div > div.inline-flex > a.inline-flex div.grid > div > div.inline-flex > a.inline-flex
body > div#root > a.fixed body > div#root > a.fixed

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
WHY CHOOSE KEEN OVERSEAS ? section.py-10 > div.max-w-7xl > div.text-center > span.text-yellow-500
STUDY DESTINATIONS section.py-10 > div.max-w-7xl > div.text-center > span.text-yellow-500
COACHING PROGRAMS section#courses > div.max-w-7xl > div.text-center > span.text-yellow-500
SUCCESS STORIES section.py-10 > div.max-w-7xl > div.text-center > span.text-yellow-500
FREQUENTLY ASKED QUESTIONS section.py-10 > div.max-w-4xl > div.text-center > span.text-yellow-500

These are opportunities to improve the legibility of your content.

○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>`
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
○`[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
○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
○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.
A
Heading Hierarchy
46 headings
PASS
46 headings
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Your Gateway To Global Education& Immigration Success
  • H1 Your Gateway To Global Education& Immigration Success duplicate H1
  • H1 Your Gateway To Global Education& Immigration Success duplicate H1
  • H1 Your Gateway To Global Education& Immigration Success duplicate H1
  • H2 0+
  • H2 0+
  • H2 0%
  • H2 0+
  • H2 Book YourFree Consultation
  • H3 Book Your FREE Consultation
  • H2 Trusted Immigration Experts
  • H3 Personalized Counseling
  • H3 Transparent Process
  • H3 Visa Expertise
  • H3 End-to-End Support
  • H2 Explore Opportunities Worldwide
  • H3 Canada
  • H3 Australia
  • H3 United Kingdom
  • H3 Germany
  • H2 Prepare for Success
  • H3 IELTS Coaching
  • H3 PTE Coaching
  • H2 Student Testimonials
  • H3 Amisha Parihar
  • H3 AmitaSingh
  • H3 AnanyaMuradia
  • H3 ArpanKamboj
  • H3 Arshdeep Singh Brar
  • H3 Ashima Sharma
  • H3 Avreen Kaur
  • H3 Baljeet Singh
  • H3 Banpreet Singh
  • H3 Chanchal
  • H3 Gagandeep Kamboj
  • H3 Gagandeep Kaur
  • H3 Gurjot Kaur
  • H3 Harshit Kandpal
  • H3 Ikrar Tyagi
  • H3 Gupinder Kaur
  • H3 Jagat Singh Parmar
  • H2 Got Questions?
  • H2 Keen Overseas
  • H3 Quick Links
  • H3 Study Destinations
  • H3 Contact Us

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H2: "0+" - H2: "0+" - H2: "0%"
Got: 3 ≤2-char heading(s)
A+
Alt Text Quality
All 26 images OK
PASS
All 26 images OK
Info::
26 image(s) with good alt text
26 images 26 good alt text
All images have appropriate alt text.
A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 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
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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 168 visible text node(s) render at >= 12 CSS pixels
PASS
All 168 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