Accessibility Statement
FictiveBox Digital wants everyone to be able to use this website, whatever technology or ability they bring to it. This statement says what standard we build to, what is in place, how we check it, what we have not yet done, and how to tell us about a problem.
Last reviewed 13 September 2026.
What we build to
This website is built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is the level most public-sector and enterprise procurement processes require, and it is the level our own engineering standards target for the systems we build for clients.
We describe this as the standard we build to rather than a conformance claim, for the reason given under “What we have not yet done” below.
What is in place
- Keyboard first
- Every interactive element can be reached and operated with a keyboard. A skip link at the top of each page jumps straight to the main content. Tabbed interfaces support the arrow keys, Home and End.
- Screen reader semantics
- Pages use one heading per level in order, landmark regions, and definition lists for figures. Menus announce whether they are open. Decorative graphics are hidden from assistive technology; meaningful images carry text alternatives.
- Colour and contrast
- Text and interactive elements meet the WCAG AA contrast ratio against their background, including the yellow brand accent, which is placed on dark surfaces where it is used for text.
- Motion
- The animated graphic on the home page stops when your operating system or browser is set to reduce motion. Nothing on the site flashes, autoplays with sound, or moves in a way you cannot pause.
- Resizing and reflow
- The layout is fluid. Pages remain usable at 200% browser zoom and on narrow screens without horizontal scrolling. No content is locked to a fixed width.
- Labels that match
- Where two links on a page share visible text, their accessible names are extended so that voice control users can address the right one, and the visible text remains part of the accessible name.
How we check
Accessibility is checked automatically on every build. Our deployment pipeline runs Lighthouse, which includes the axe accessibility rule set, against key pages, and a deployment is blocked if a page falls below our accessibility threshold. Findings are fixed in the code, not suppressed.
Alongside that, we test manually with a keyboard alone, at 200% zoom, with reduced motion enabled, and against the accessibility tree that browsers expose to assistive technology, to catch what automated tools cannot.
What we have not yet done
This website has not yet been audited by an independent accessibility specialist, and it has not yet been tested with people who rely on screen readers, switch access or other assistive technology in their daily use. Automated tools and our own manual testing catch a great deal, but they are not a substitute for that. Until it is done, we state a target rather than claim conformance.
Our case studies currently include framed areas that will hold product screenshots. When those images are added they will each carry a text alternative that describes what the screen shows, not just what it is called.
If you encounter a barrier that is not listed here, please tell us. It is more useful to us than a clean automated score.
Reporting a barrier
If any part of this website is difficult or impossible for you to use, email info@fictivebox.com or call +91 93119 57069. Tell us the page, what you were trying to do, and the browser and any assistive technology you were using. We will reply, and where we can we will fix the issue rather than offer a workaround.
If you need the information on any page in a different format, ask and we will provide it.
See also our Privacy Policy, Terms of Use and Security pages.