Accessibility Standards

#Purpose

KBY Technologies is committed to making knowledge accessible to the widest possible audience.

Accessibility is not an afterthought or a compliance exercise. It is a fundamental part of producing high-quality editorial content.

Every publication should be designed so that as many people as possible can access, understand and use the information it contains.

---

#Our Accessibility Philosophy

Knowledge has little value if people cannot access it.

We aim to remove unnecessary barriers by producing content that is:

• Easy to read.
• Easy to navigate.
• Easy to understand.
• Compatible with assistive technologies.
• Inclusive of diverse audiences.

Accessibility improves the experience for everyone.

---

#Clear Communication

Content should prioritise understanding over complexity.

Where appropriate, we should:

• Explain technical terminology.
• Avoid unnecessary jargon.
• Use descriptive headings.
• Write concise paragraphs.
• Present information logically.

Clarity is one of the most important forms of accessibility.

---

#Structured Content

Publications should use a consistent and logical structure.

This includes:

• Clear heading hierarchy.
• Descriptive section titles.
• Ordered steps where processes are explained.
• Lists where they improve readability.
• Tables only when they improve understanding.

Good structure helps both readers and assistive technologies.

---

#Visual Accessibility

Visual content should support understanding rather than create barriers.

Where applicable, we should:

• Provide meaningful alternative text for images.
• Ensure sufficient colour contrast.
• Avoid conveying information through colour alone.
• Use readable font sizes and spacing.
• Present charts and diagrams with accompanying explanations.

Information should remain understandable even if visual elements cannot be seen.

---

#Digital Accessibility

Our digital publications should aim to align with recognised accessibility best practices.

Where appropriate, we should:

• Use semantic HTML.
• Support keyboard navigation.
• Ensure compatibility with screen readers.
• Avoid unnecessary interaction barriers.
• Test accessibility as part of the publishing process.

Accessibility should be considered throughout development, not added afterwards.

---

#Inclusive Language

Language should be respectful, inclusive and free from unnecessary bias.

We should avoid assumptions based on:

• Age.
• Disability.
• Gender.
• Ethnicity.
• Religion.
• Nationality.
• Background.

Inclusive language helps ensure our publications are welcoming to a broad audience.

---

#Continuous Improvement

Accessibility is an ongoing commitment.

We should regularly review our publications, processes and technologies to identify opportunities for improvement.

Feedback from readers should be welcomed and used to improve future publications.

---

#Accessibility Checklist

Before publication, confirm that:

• The content is easy to read.
• Headings follow a logical order.
• Images include appropriate alternative text where required.
• Formatting supports readability.
• Language is inclusive.
• Information is understandable without unnecessary complexity.
• Accessibility has been considered throughout the publication.

Accessibility should be part of every editorial review.

---

#In Practice

Before publishing, ask yourself:

• Is this easy to understand?
• Can someone quickly find the information they need?
• Have unnecessary barriers been removed?
• Would this work well with assistive technologies?
• Does this reflect our commitment to making knowledge accessible?

If the answer is no, improve the publication before release.

---

#Related Documents