Accessibility statement · Last updated 1 October 2026
Built for WCAG 2.1 AA, and honest about the gaps.
01
Our commitment
Discover Manipur is built to be usable by as many people as possible, including people who navigate by keyboard, who use a screen reader or magnifier, who need reduced motion, or who have low vision or colour vision deficiency.
Our target is WCAG 2.1 Level AA. We believe most of the site currently meets it. We are not claiming full conformance, because parts of the site have not been independently audited and we know of specific gaps, which are listed below.
02
What is supported
Keyboard
- Every interactive control (links, buttons, filters, accordions, dialogs, selects and form fields) is reachable and operable with a keyboard alone.
- A visible focus ring is drawn on every focusable element, with a two-pixel outline and an offset so it is not swallowed by the component.
- A “Skip to content” link is the first thing in the tab order on every page.
- Dialogs trap focus while open, close on Escape, and return focus to the control that opened them.
Structure and screen readers
- Semantic landmarks throughout: a single
header,main,navandfooterper page. - One
h1per page and a heading order that does not skip levels. - Every form control has a real associated label; error messages are announced and tied to their field.
- Icon-only buttons carry an accessible name; decorative icons and images are hidden from assistive technology.
- Live regions announce filter result counts and form status so the change is not silent.
Images and media
- Photographs carry alt text that describes what is in the picture rather than repeating the headline next to it.
- Purely decorative imagery is marked as such rather than given a made-up description.
- There is no audio or video that plays automatically.
Motion
- Every animation has a reduced-motion path. If your system asks for reduced motion, scroll reveals, parallax and looping motion are disabled rather than merely shortened.
- Nothing flashes more than three times per second.
- There is no motion that starts and keeps moving without a way to stop it.
Colour, text and zoom
- The palette is chosen so body text meets at least 4.5:1 contrast, and large text and interface borders at least 3:1, in both the light and dark themes.
- Colour is never the only way information is conveyed.
- Text reflows without horizontal scrolling down to 320 pixels wide and at 200% zoom.
- Content honours your browser's font size rather than forcing a fixed pixel size.
Travel information
Accessibility is also a content problem. Each place listing carries a wheelchair-access flag and a written note, because a bare yes or no hides the gravel path, the three steps at the entrance or the absence of an accessible toilet. Where we do not know, we say we do not know rather than guessing.
03
Known limitations
We would rather list these than let you find them. We are working on all of them, and reports help us prioritise.
- Interactive maps. The map view relies on a third-party library. Panning and zooming by keyboard are limited, and map markers are not fully exposed to screen readers. Every place shown on a map is also listed as text elsewhere on the same page.
- 3D and immersive views. Panorama and 3D scenes are visual by nature. They are supplementary, never the only route to information, but they have no non-visual equivalent yet.
- AI concierge output. Generated itineraries are announced as they stream in, which can be verbose with a screen reader. A plain summary view is planned.
- Date pickers. The calendar component is keyboard operable but its announcements are terser than we would like; a text date entry alternative is planned.
- Photograph alt text. Some catalogue images use shorter descriptions than we would like. We are rewriting these listing by listing.
- Language. The interface is in English. Meetei Mayek appears for names and key terms, but the site is not yet available in Meiteilon or other local languages.
- Third-party content. We cannot control the accessibility of external sites we link to, including government permit portals.
04
How we test
- Keyboard-only walkthroughs of every route, including the whole booking flow.
- Automated checks with axe and Lighthouse in the browser, run against the built site rather than the development server.
- Manual screen reader passes with VoiceOver on macOS and iOS, and NVDA on Windows.
- Reduced-motion, forced-colours, 200% zoom and 320-pixel-width checks.
- Contrast checks on every token pairing in both the light and dark themes.
Discover Manipur is a volunteer-run, open-source project, so testing is done by its contributors rather than by an independent auditor. We are stating that plainly rather than implying a certification we do not hold.
05
Compatibility
The site is designed to work with recent versions of Chrome, Edge, Firefox and Safari on desktop and mobile, used with or without assistive technology. It should also work with your browser's own accessibility features: zoom, reader mode, custom stylesheets and increased text size.
If you are using an older browser or an unusual combination and something breaks, tell us which combination it is; that detail is usually what makes a bug fixable.
06
Report a problem
If you hit a barrier anywhere on this site, we want to hear about it, including small things. Accessibility reports are triaged ahead of feature work.
- Open an issue on GitHub and mention accessibility in the title.
- Or tell the maintainers on the community Discord.
It helps enormously if you can tell us:
- the page address;
- what you were trying to do;
- what happened instead;
- your browser, operating system and any assistive technology you were using, with versions if you know them.
The maintainers are volunteers. We aim to acknowledge reports within five working days and to tell you what we intend to do about it, including if the honest answer is that we cannot fix it soon.
07
If we do not get it right
If you are not satisfied with our response, reply and say so; it escalates to all the maintainers rather than one person. As a non-commercial community project we are not subject to a formal enforcement procedure, but we take reports seriously and we will tell you honestly what we can and cannot do.