Accessibility Statement
Sheo Narayan — SEBI Registered Investment Advisor is committed to ensuring this website is accessible to everyone, including people with disabilities. This page documents the specific WCAG 2.1 Level AA compliance measures implemented across this website.
We follow the Web Content Accessibility Guidelines (WCAG) 2.1, published by the World Wide Web Consortium (W3C). WCAG defines three levels of compliance — A, AA, and AAA. This website targets Level AA, which covers the most impactful accessibility requirements for users with visual, auditory, motor, and cognitive disabilities.
1. Perceivable
Information and UI components must be presentable to users in ways they can perceive.
1.1 Text Alternatives (WCAG 1.1.1 — Level A)
- Every
<img> element carries a descriptive alt attribute. For example, the brand logo uses alt="Sheo Narayan logo".
- Decorative SVG icons use
aria-hidden="true" so screen readers skip them entirely.
- Contact icons (address, email, phone) are wrapped with visible text labels, so the meaning is never conveyed by the icon alone.
1.3 Adaptable Content (WCAG 1.3.1–1.3.3 — Level A)
- Semantic HTML5 elements are used throughout:
<header>, <nav>, <main>, <footer>, <section>, <article>, and <aside> provide a logical document outline.
- Heading levels (
h1 → h2 → h3) follow a strict hierarchy on every page — no levels are skipped.
- ARIA landmark roles reinforce semantic structure:
role="banner" on the header, role="contentinfo" on the footer, and aria-label attributes on all landmark regions.
- Lists use proper
<ul> / <ol> / <li> markup, never visual separators or line breaks.
- Instructions never rely on shape, colour, or position alone (e.g., "click the gold button").
1.4 Distinguishable — Colour Contrast (WCAG 1.4.1, 1.4.3, 1.4.4 — Levels A & AA)
- Body text (
#0B2341 on #ffffff): contrast ratio ≥ 15:1 — well above the 4.5:1 AA minimum for normal text.
- Muted/secondary text (
#374962 on #ffffff): contrast ratio ≥ 8:1 — exceeds AA and meets AAA threshold.
- Gold accent text (
#C89B3C) is never used as the sole carrier of meaning and is only placed on very dark navy (#0B2341) backgrounds, yielding a ratio of ≥ 4.7:1 for large / bold text.
- Footer text (light on
#0B2341 dark navy background): all text meets ≥ 4.5:1 ratio.
- Information is never conveyed by colour alone — all status indicators pair colour with text or an icon.
- Text can be resized up to 200 % without loss of content or functionality.
2. Operable
UI components and navigation must be operable by all users, regardless of input method.
2.1 Keyboard Accessible (WCAG 2.1.1, 2.1.2 — Level A)
- Every interactive element — navigation links, buttons, form fields, FAQ accordions, and CTAs — is reachable and operable using the keyboard alone (Tab, Shift+Tab, Enter, Space).
- There are no keyboard traps: focus always moves forward and can always be reversed.
- The mobile navigation toggle is keyboard-operable: pressing Enter or Space on the "Menu" button opens and closes the nav drawer.
2.1 Skip Navigation Link (WCAG 2.4.1 — Level A)
- A "Skip to main content" link is the very first focusable element on every page. It is visually hidden until it receives keyboard focus, then slides into view at the top-left corner — allowing keyboard users to bypass the repeated navigation on every page.
2.4 Navigable (WCAG 2.4.2–2.4.7 — Level AA)
- Descriptive page titles: every
<title> uniquely identifies the page and includes the site name (e.g., "Fees | Sheo Narayan SEBI RIA").
- Focus order follows the visual reading order on every page. The CSS layout does not reorder content in a way that breaks logical tab sequence.
- Descriptive link text: all links are self-describing. Phrases like "click here" and "read more" are avoided. Where context is needed,
aria-label provides a fuller description.
- Active page indicator: the current page's navigation link carries
aria-current="page", giving screen reader users an immediate orientation cue.
- Multiple navigation paths: users can reach every page via the main navigation, footer links, and contextual in-page links.
- Focus visible: all focusable elements show a 2 px solid blue (
#185FA5) outline with a 4 px offset via the :focus-visible CSS pseudo-class — visible on both light and dark backgrounds. Input elements and buttons additionally receive a gold underline shadow on hover/focus.
3. Understandable
Information and the operation of the UI must be understandable.
3.1 Readable (WCAG 3.1.1, 3.1.2 — Level A)
- The page language is declared with
<html lang="en"> on every page, enabling screen readers to apply the correct voice profile and pronunciation rules.
- No passages of foreign language text appear without an inline
lang attribute override.
3.2 Predictable (WCAG 3.2.1, 3.2.2 — Level A)
- Navigation is consistent across all pages — the same links appear in the same order in the header and footer.
- No component changes context on focus alone; actions require explicit user interaction (click or keypress).
3.3 Input Assistance (WCAG 3.3.1, 3.3.2 — Level A)
- All form fields have explicit
<label> elements linked via for / id attributes — never using placeholder text as the sole label.
- Required fields are marked with both a visual asterisk (
*) and the required HTML attribute.
- Placeholder text provides usage guidance (e.g., "Your name") without replacing the label.
- The contact form groups related fields using
<fieldset> and <legend> where applicable.
4. Robust
Content must be robust enough to be interpreted reliably by a wide variety of user agents and assistive technologies.
4.1 Compatible (WCAG 4.1.1, 4.1.2, 4.1.3 — Levels A & AA)
- Valid HTML5: all pages use proper DOCTYPE declarations and well-formed markup.
- ARIA roles and properties are applied to interactive widgets: the mobile menu button uses
aria-expanded (toggled by JavaScript) and aria-controls pointing to the nav element's id.
- Section landmarks have
aria-labelledby pointing to their visible heading, giving each section a meaningful accessible name for screen reader navigation.
- Status messages and form validation feedback are associated with their inputs programmatically.
5. Additional Accessibility Measures
Reduced Motion
- Scroll-triggered animations (fade-in-up via Intersection Observer) respect the
prefers-reduced-motion OS setting. When the user has requested reduced motion, the JavaScript observer skips adding animation classes, so elements appear immediately without movement.
- CSS transitions and
scroll-behavior: smooth do not override the user's motion preferences in supporting browsers.
Responsive Design
- The layout is fully responsive using CSS Flexbox and Grid with fluid units — there is no horizontal scrolling at any standard viewport width.
- Touch targets (buttons, links) are sized to a minimum of 44 × 44 CSS pixels on mobile viewports, meeting WCAG 2.5.5 (AAA) as a best practice.
Semantic Structure at a Glance
Landmark and semantic elements used on every page
| Element / Attribute |
Purpose |
WCAG Criterion |
<a class="skip-link"> | Bypass repeated navigation | 2.4.1 (A) |
<html lang="en"> | Declare page language | 3.1.1 (A) |
<header role="banner"> | Site-wide banner landmark | 1.3.1 (A) |
<nav aria-label="..."> | Navigation landmark with name | 1.3.1, 2.4.1 (A) |
<main id="main-content"> | Primary content landmark | 1.3.1, 2.4.1 (A) |
<footer role="contentinfo"> | Site-wide footer landmark | 1.3.1 (A) |
aria-current="page" | Active nav link indicator | 2.4.7 (AA) |
aria-expanded + aria-controls | Mobile menu state | 4.1.2 (A) |
aria-hidden="true" | Hide decorative icons from AT | 1.1.1 (A) |
aria-labelledby on sections | Name each content region | 1.3.1, 4.1.2 (A) |
alt on all images | Text alternative for images | 1.1.1 (A) |
:focus-visible outline | Visible keyboard focus | 2.4.7 (AA) |
<label for="..."> | Programmatic form labels | 1.3.1, 3.3.2 (A) |
required attribute | Required field identification | 3.3.2 (A) |
6. Known Limitations & Ongoing Work
We are committed to continuous improvement. Current areas under review include:
- Adding a
@media (prefers-reduced-motion: reduce) CSS block as a belt-and-braces complement to the JavaScript observer guard.
- Conducting periodic automated and manual audits using tools such as axe, WAVE, and NVDA screen reader testing.
- Ensuring any future embedded PDFs or downloadable documents carry accessible tags and proper reading order.
7. Feedback & Contact
We welcome feedback on the accessibility of this website. If you encounter a barrier, need content in an alternative format, or want to report an issue, please contact us:
We aim to respond to accessibility feedback within 5 business days.