Our approach
We follow the principles of the Web Content Accessibility Guidelines (WCAG) and aim for WCAG 2.2 AA across core pages and learning flows. Plain language, predictable layouts and keyboard operability guide our decisions.
Accessibility and plain-English writing aren't separate goals for us — they're the same goal. A guide that's technically WCAG-compliant but still full of unexplained jargon isn't genuinely accessible to someone reading it for the first time, regardless of what assistive technology they're using. So alongside the technical checklist below, every guide is also written to be understandable on a first read, with one instruction per sentence and each technical term explained the first time it appears.
If anything prevents you from using a page or guide, please tell us. We will provide the same information in a format you can use.
How we design for access
Vision
Readable body text (18px minimum), strong colour contrast, and no reliance on colour alone to convey meaning — for example, an error state is marked with text and an icon, not just a red border.
Motor / mobility
Every interactive element — buttons, links, form fields, cookie controls — is reachable and operable by keyboard alone, with a clearly visible focus outline so you always know where you are on the page.
Cognitive load
Guides are broken into short, numbered steps rather than long paragraphs, with one action per step and a clear indication of what "done" looks like before moving on — reducing the working-memory demand of following instructions.
Screen reader use
Semantic HTML headings and landmarks let screen reader users jump directly to the section they need, rather than listening through an entire page linearly. Meaningful images carry text alternatives; purely decorative images are hidden from assistive tech so they don't add noise.
- Readable body text (18 px), clear headings and logical page structure.
- Contrast checks and no reliance on colour alone to convey meaning.
- Form fields with labels, hints and understandable error messages.
- Interactive elements reachable by keyboard with a visible focus state.
- Text alternatives for meaningful images; decorative images are ignored by assistive tech.
- Cookie preferences that can be managed with keyboard and screen reader.
Compatibility & assistive tech
Pages are built with semantic HTML, CSS and lightweight JavaScript and are intended to work on current browsers and operating systems with common assistive tools. If something fails in your environment or configuration, let us know and we will investigate.
| Category | What we test against |
|---|---|
| Screen readers | NVDA and JAWS on Windows; VoiceOver on macOS and iOS |
| Browsers | Current versions of Chrome, Edge, Firefox and Safari |
| Magnification | Browser zoom up to 200% without loss of content or function |
| Input methods | Keyboard-only navigation, and touch on mobile devices |
This isn't an exhaustive compatibility guarantee — it reflects what we actively test against. If you use a combination outside this list and hit a problem, we still want to hear about it.
Areas we're improving
We monitor the site for issues and continue to improve. Current focus areas include:
- Third-party components that load with consent (e.g. analytics/ads) might not fully inherit our accessibility styling.
- Older PDFs may not include complete tagging. We can provide HTML or large-print versions on request.
- During edits, heading levels may briefly fall out of sequence. We correct these as we spot them.
We'd rather list known gaps honestly than claim a perfect score we haven't actually verified — an accessibility statement is only useful if it reflects the real, current state of the site rather than an aspiration.
Get information in a different format
Tell us the page URL and the format you prefer. We can share:
- High-contrast or large-print versions of notes and checklists.
- Plain-text or HTML alternatives to PDFs.
- An educational call-back to talk through steps by phone.
We do not provide remote access. All help is educational and remains in user-controlled formats.
What happens after you ask
We aim to acknowledge a format request within two working days and provide the alternative, or a clear timeline for it, within five. If a request needs longer — for example, converting a long PDF guide into fully tagged HTML — we'll tell you that upfront rather than leaving you waiting without an update.
Share feedback
Your comments help us remove barriers. Please include the page address, device, browser/OS and any assistive technology used.
- Email: info@guideaxis.online
- UK information line: +44-808 531 0585
- Contact form: /contact
If you need to escalate
If our response does not resolve your concern, you can use our Complaints & Dispute Resolution route. GuideAxis is operated by Connecgen Global LLP, an India-registered Limited Liability Partnership (GSTIN 09AAWFC5769J1ZH). For UK data-rights matters you may also contact the Information Commissioner's Office (ICO).
How we review this page
- First published: 27 August 2025
- Method: self-assessment against WCAG 2.2 AA, checks with automated tools, and keyboard-only navigation.
- Review schedule: twice a year, or sooner after major design changes.
Quick tips
- Headings and landmarks are used consistently for easier navigation.
- Link text describes the destination (we avoid "click here").
- You can change cookie choices any time at Cookie Preferences.