Accessibility Statement
Accessibility is part of Meer Foundation's founding commitment to working with people, never for them. This statement explains the standards we hold ourselves to, the features we have implemented, and how you can give us feedback when we fall short.
A note on accessibility
Meer Foundation works in some of the most remote districts of Chhattisgarh, with communities for whom digital access is itself a daily challenge. The least we can do — in a digital medium we control — is ensure that this website is usable by everyone, including people with disabilities.
This Accessibility Statement applies to the Meer Foundation public website. It is reviewed annually, or sooner if our accessibility practices change materially. It should be read alongside our other legal pages.
Inclusive by design
Accessibility is considered at the design stage, not bolted on at the end. Every new component is checked against WCAG 2.1 AA criteria before release.
Tested with real tools
We test with NVDA, VoiceOver, and keyboard-only navigation. Automated checks run on every code change via axe-core in our CI pipeline.
Feedback welcomed
If you encounter an accessibility barrier, please tell us. We treat every report as a defect and work to resolve it promptly.
What we are committed to
Accessibility is not a checkbox. It is a continuous practice — part of how we design, build, and review everything on this website. The commitments below describe what that means in practice.
The frameworks we measure against
Our accessibility practice is anchored in internationally recognised standards. Together, they define what 'accessible' means for this website — and how we verify it.
WCAG 2.1 AA
Web Content Accessibility Guidelines 2.1, Level AA — the international standard for accessible web content. Our target is to meet every success criterion at this level.
WAI-ARIA 1.2
Web Accessibility Initiative — Accessible Rich Internet Applications. Used to communicate dynamic content, custom widgets, and live regions to assistive technologies.
Indian RPwD Act 2016
Rights of Persons with Disabilities Act 2016 — mandating accessibility of public-information resources, including websites operated by organisations working with public funds.
ISO 30071-1
Digital accessibility — building inclusive products. Used as a reference framework for our accessibility governance and design process.
What WCAG 2.1 AA means in practice
What we have built in
Accessibility features are not added later — they are baked into every component on this website. The list below describes the features you will find on every page.
Screen reader support
Every interactive element has an accessible name, role, and state. Images carry descriptive alt text. Form fields have associated labels. ARIA landmarks (banner, main, footer, navigation) are present on every page.
Keyboard navigation
The entire website can be operated with a keyboard alone. Focus is visible at all times, with a high-contrast ring. Logical tab order matches reading order. Skip-to-content links are present on every page.
Colour contrast
Our Lotus & River theme (teal #0D5B5E primary, terracotta #C2542C secondary, gold #D49B3F accent) is designed to meet WCAG 2.1 AA contrast ratios. Body text on backgrounds exceeds 4.5:1; large text exceeds 3:1.
Text scaling & reflow
Text scales up to 200% without loss of content or functionality. The responsive layout reflows for narrow viewports — including mobile phones, tablets, and zoomed desktop browsers — without horizontal scrolling.
Mobile accessibility
Touch targets are at least 44×44 CSS pixels. Gestures can be cancelled if a single pointer moves beyond 10 pixels. The site works in portrait and landscape orientation. Pinch-to-zoom is not disabled.
Dark mode
A user-selectable dark theme (powered by next-themes) reduces eye strain in low-light environments. The dark theme meets the same contrast standards as the light theme.
Reduced motion
We respect the prefers-reduced-motion media query. Where animations are present — for example, the framer-motion entrance animations on long-form pages — they are reduced or removed when the user has indicated a preference.
Semantic HTML
Pages are built with semantic HTML5 — <header>, <main>, <nav>, <article>, <section>, <footer>, <aside>. Headings (h1, h2, h3) form a logical outline. Lists are marked up as lists. Tables include scope attributes.
Known limitations
While we work to make every page accessible, some third-party content — embedded videos, social-media posts, legacy PDFs — may not yet meet WCAG 2.1 AA. Where we are aware of such limitations, we record them and provide accessible alternatives on request. If you encounter a barrier, please report it via the feedback channel below.
Tell us when we fall short
Your feedback is the most direct way for us to learn about accessibility barriers we may have missed. We treat every report seriously and act on it promptly.
Subject: Accessibility
category on our contact page
2 business days · resolution
within 7 business days
What to include in your report
- • The URL of the page where you encountered the issue.
- • A brief description of the problem and what you expected to happen.
- • The browser and device you are using (e.g., Chrome on Android, Safari on macOS).
- • The assistive technology you are using, if any (e.g., NVDA 2024, VoiceOver, ZoomText).
- • Any screenshots or recordings that help us reproduce the issue.
Frequently asked questions
Web Content Accessibility Guidelines 2.1, Level AA — the international standard published by the W3C Web Accessibility Initiative. It defines success criteria across four principles: perceivable, operable, understandable, and robust. Level AA is the target for most public-sector and large-organisation websites.