Skip to content
https://esignature.com.np/website-design-development-nepal

Accessibility

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

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" id="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: email.
Got: <input type="email" name="email" id="email">, <input type="email" name="news_email" id="newsLetter">
F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Temporarily Unavailable ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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: #1748c5
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Favicon & Branding
32 icon(s) detected
REVIEW
32 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Heading Hierarchy
33 headings
PASS
33 headings
Info::
Single H1 present
  • H2 Technology Solutions Partner
  • H1 Affordable Website Design & Development in Nepal
  • H2 There are Reasons to Choose E-Signature, Among the Top Web Development Companies in Nepal
  • H2 What We Bring To The Table?
  • H2 Want to get noticed online?
  • H2 Our Agile Process for Website Design and Development Services
  • H3 Initiation
  • H3 Iterative UX/UI Design
  • H3 Website Design and Development
  • H3 Maintenance + Optimization
  • H2 Let’s get started!
  • H3 Benefits of Developing Your Website with E-Signature
  • H3 Meet Our Few Key Team Member
  • H3 FAQs
  • H3 What our clients say about us
  • H4 CARLOS YONG www.3tierlogic.com
  • H4 Mark Simmons https://www.espn.com/
  • H4 Kevin McIntosh www.powerautomedia.com
  • H4 Daniel Dori (President) https://www.blacklinere.com/
  • H4 Max Keeler www.fool.com
  • H4 Fouad Sabry Reqlax
  • H4 Jacob Shriar www.officevibe.com
  • H4 Shamiul Mowla Prankdail & Ghostcall
  • H4 Ryan Silver http://www.originalfly.com/
  • H4 LES OTTOLENGHI https://www.fuze.com/
  • H2 We can build your story
  • H3 Services
  • H2 Contact Info
  • H3 Hire
  • H3 Services
  • H3 About Us
  • H3 NewsLetter
  • H2 Useful Links
A+
Heading Text Quality
All 33 heading(s) have substantive, well-formed text
PASS
All 33 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 34 images OK
PASS
All 34 images OK
Info::
34 image(s) with good alt text
34 images 34 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 10 controls have issues
PASS
1 of 10 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">
Info::
9 control(s) properly labeled
10 controls
9 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#Mobile ApplicationcheckboxMobile Applicationfor/id
#Website DevelopmentcheckboxWebsite Developmentfor/id
#Staff LeasingcheckboxStaff Leasingfor/id
#Strategic Digital MarketingcheckboxStrategic Digital Marketingfor/id
#99checkboxOthersfor/id
#user_nametextNamefor/id
#emailemailEmailfor/id
#descriptiontextareaProject Detailsfor/id
#newsLetteremailyour email namearia-label
#g-recaptcha-responsetextarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response">

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

A+
Form Input Types
10 form control(s) checked, no type mismatches
PASS
10 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
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
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/3 iframe(s) missing title; 0 placeholder(s)
PASS
1/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
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.
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 140 visible text node(s) render at >= 12 CSS pixels
PASS
All 140 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: E-Signature
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name E-Signature ✓192×192 icon ✓512×512 icon ✗Start URL /index.html ✓Display Mode standalone ✓
Name E-Signature Display Mode standalone Theme Color #1748c5 Background Color #1748c5 Icons 18 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Affordable Website21.00:13.0:1
#000000
#FFFFFF
Pass
h1 in Nepal21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Technology Solutions…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 There are Reasons to…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Companies in Nepal21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What21.00:13.0:1
#000000
#FFFFFF
Pass
h2 To The Table?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Want to get noticed …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Agile Process fo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Let’s get started!21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We can build your st…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Contact Info21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Useful Links21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Initiation21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Iterative UX/UI Desi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Website Design and D…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Maintenance + Optimi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Your Website with E-…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Meet Our Few Key21.00:13.0:1
#000000
#FFFFFF
Pass
h3 FAQs21.00:13.0: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+
Lighthouse Accessibility Audits
Score 95/100 — 3 failing, 25 passed
PASS
95

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We start by trying to understand your objectives, business requirements, and ex… article.list-section__article > div.details > div.service-list > li
Our expert web designers and developers suggest you the best choice of tech sel… article.list-section__article > div.details > div.service-list > li
The next step is to sign an NDA (Non-disclosure Agreement) to secure your web d… article.list-section__article > div.details > div.service-list > li
Finally, we design a sitemap and wireframe of the website which gives a basic i… article.list-section__article > div.details > div.service-list > li
We conduct a comprehensive custom website development workshop to analyze all c… article.list-section__article > div.details > div.service-list > li
From there, our experienced UI/UX team will create website pages based on the p… article.list-section__article > div.details > div.service-list > li
You will get involved and updated continuously throughout the process. Based on… article.list-section__article > div.details > div.service-list > li
The website starts to take shape as we begin the actual website design and deve… article.list-section__article > div.details > div.service-list > li
The world project will be divided into numerous sprints. article.list-section__article > div.details > div.service-list > li
Our website design, and development team with QAs and Scrum masters work in eac… article.list-section__article > div.details > div.service-list > li
We start by designing the home page and then gradually the rest of the web page… article.list-section__article > div.details > div.service-list > li
The QA team tests the website from start to finish until the website is issue-f… article.list-section__article > div.details > div.service-list > li
You'll get a regular CMS and plugin update. article.list-section__article > div.details > div.service-list > li
We provide ongoing web server maintenance and repair services. article.list-section__article > div.details > div.service-list > li
We will help you build a customer service strategy and refine your website serv… article.list-section__article > div.details > div.service-list > li

These are opportunities to improve the experience of reading tabular or list data using 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 html

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read More div.row > div.col-12 > div.card > button.btn
Read More div.row > div.col-12 > div.card > button.btn
Read More div.row > div.col-12 > div.card > button.btn
Read More div.row > div.col-12 > div.card > button.btn
○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
●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 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>`).
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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