- Homepage
- /
- Accessibility statement
LeGAL
Accessibility statement
What we do so that everyone can use this site, and how to tell us if something is in the way.
Last updated 9 September 2026 · Applies to spinah.com and every site Spinah hosts for clients.
on this page
Our standard
This site is built to meet WCAG 2.1 level AA. Every colour pairing is checked against the 4.5:1 contrast ratio for text, every image has a text alternative, every page has one heading that names it, and every control works with a keyboard. Body text is 17 pixels with generous line spacing, links are underlined or clearly coloured, and nothing flashes. The one thing that moves on its own, the client screenshots on the homepage, has a pause button, holds still while you point at it or tab into it, and does not cycle at all if your device asks for reduced motion.
Why it matters to us
About one in ten people using a website has a disability that affects how they read, see, hear or move, and many more are on a small screen in bright sunlight with one hand free. A site that works for a screen reader also works for a search engine, and a site that works with a keyboard works on a cracked phone. Accessibility is part of how we build, not a feature we add.
What we tested
Keyboard navigation of the menus, forms and accordions; screen-reader announcements of headings, links and form errors; text resizing to 200 per cent; and reduced-motion preferences, which turn off transitions and stop the homepage screenshots cycling.
Known limits
Third-party embeds such as the booking calendar follow their provider’s accessibility. Screenshots of client websites are described in text but their contents are not transcribed. PDF documents in the reports library are tagged where the source allows; where a PDF is not accessible we provide the same content as a web page on request.
How we keep it this way
Every template is checked against the same list before it goes live: contrast, headings, alternative text, keyboard order, focus visibility, form labels and error messages. The check is automated in our build and run by hand on a phone with a screen reader once a quarter. Client sites we build are held to the same standard, and the handoff to a client’s own team includes the checklist.
Tell us
If anything on this site is hard to use, email hello@spinah.com or message WhatsApp. We reply within two business days and fix what we can within ten. If you tell us which page and what happened, we can usually fix it the same week.
Questions about this?
Email hello@spinah.com or use the contact page. We reply within 14 days to legal requests and within one business day to everything else.
Related Guides
-
21 Aug 2026The Top 10 Best and Secure Email Hosting Providers for Your Personal Domain
-
21 Aug 2026
-
21 Aug 2026Setting Up WordPress with Docker Containers: A Step-by-Step Guide
-
19 Aug 2026SiteGround Hosting: The Ultimate Beginner's Guide
-
19 Aug 2026How to Choose the Right Web Hosting Service for Your Needs
Related WORK
Isreal Oyarinde
Case Study
CareBridge Foundation
Case Study