Accessibility statement
We want everyone to be able to use this website. Here is the standard we aim for, where we know we fall short, and how to tell us about a problem.
This statement applies to the GeekMidst website. We want it to be usable by as many people as possible, including people who use screen readers, keyboard navigation, voice control, screen magnification or high-contrast settings.
The standard we aim for
We aim to meet the Web Content Accessibility Guidelines, WCAG 2.2 at level AA. We have not had the site formally audited against every success criterion, so we do not claim full conformance. We treat accessibility as ongoing work and fix issues as we find them.
In practice, that means we try to make sure you can:
- navigate every page using a keyboard alone, with a visible focus indicator
- use a screen reader to move through headings, links and the table of contents on longer guides
- zoom text up to 200% without content being cut off
- read text with sufficient colour contrast in both light and dark display modes
- understand links from their text, without relying on colour alone
What we do to support accessibility
| Practice | |
|---|---|
| Structure | One H1 per page, meaningful headings in order, and landmarks for navigation and main content |
| Images | Alternative text for informative images; decorative images hidden from assistive technology |
| Code examples | Presented as real text, not images, so they can be read, copied and enlarged |
| Forms | Visible labels, clear error messages and no reliance on placeholder text alone |
| Motion | No auto-playing video or flashing content |
| Cookie banner | Can be operated by keyboard and screen reader |
Known limitations
We know about the following issues and are working on them:
- Wide code blocks and tables may need horizontal scrolling on small screens. The content remains available, but it is harder to read.
- Older downloadable files, if any are linked, may not be fully tagged for screen readers. Ask us for an accessible version.
- Diagrams in some technical guides may convey detail that is only partly described in the surrounding text.
- Third-party content, such as embedded media or tools hosted by other providers, may not meet the same standard and is outside our direct control.
If you find something not on this list, we would like to hear about it.
How to report a problem
- 01
Email us
Write to info@geekmidst.com with the subject line Accessibility. You can also message +91 89713 50255 on WhatsApp.
- 02
Tell us where
Include the page address and a short description of what went wrong.
- 03
Tell us how you were browsing
If you are comfortable sharing it, mention your device, browser and any assistive technology, which helps us reproduce the issue.
- 04
We respond and fix
We will acknowledge your message, provide the information in another format if you need it, and plan a fix.
Alternative formats
If you need any content from this site in a different format, such as plain text or a document that works better with your assistive technology, contact us and we will do our best to provide it.
Reviewing this statement
We review this statement when we make significant changes to the site's design or templates. It was last reviewed in October 2026.
To report a problem through a form instead of email, use our contact page. Our cookie policy explains the consent banner, and the privacy policy covers how we handle any details you send us.
Found a barrier on this site?
Tell us what happened and we will look into it. Your report helps us improve the site for everyone.
