0203 150 3141
Accessible to All including AI
Accessibility for AI Robots
AEO: Content just for AI robots
As people have switched from Google to Chat GPT or Gemini, content needs to be accessible for AI. AEO code does this. Read about AEO in plain English >
Accessibility for Everyone
WCAG Guidelines: Accessibility
For images used to illustrate, Alt text code adds descriptions . Avoid text with low colour contrast. Fully justified text is awkward read, especially for those with dyslexia >
Accessibility on Phones
Scuba Diving vs. Snorkeling
Desktop visitors deep dive to more pages. For phone users (who dip in & out): toggles keep pages short; have a get in touch link on every page. Read the case study >
Display related content in the same place.
- Categorise Projects – a tab for each category
- Courses – to show a range of courses in one place
- Or, as below – 4 tabs to show: location; services provided; opening times and staff for a specific service.
Compress Content
Reducing Scroll Fatigue
Excessive scrolling makes content harder to find. Putting content in tabs and toggles solves this issue. For FAQs in toggles add schema code to improve visibility for AI.
Ensure Pages Load Fast
Keep Humans and AI happy
Slow page loads increases abandon rates and reduces trust by AI. Main culprits: hosted on a bad server, too many videos, image not compressed (Tip: use .avif format).
Minimum 99.9% Uptime
Ensure Websites is Available
Websites available less than 99.9% of the time are assumed to be on low quality hosting or have low quality security. More about Website Security >
Articles about Accessibility for All
Business Invisible to AI?
Reading Time: 7 minutesYou need AEO to make your business crystal clear to the AI Answer Engines. Find out why.
Designing for Dyslexia
Reading Time: 8 minutesExamining if using ‘accessibility’ guidelines (BDA) makes website text clearer for everyone.
Mobile-Centric
Reading Time: < 1 minute60%+ viewed this site on phones, so access and display needed to be crystal clear.
