Accessibility statement

01Our commitment

Accessibility is part of how we think about engineering, not a project we tick off once. Augusta Software House aims to make every page on augusta.co.ke usable by people regardless of disability — with screen readers, keyboard-only input, voice control, magnification, or any other assistive technology.

We design and build to Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and we audit ourselves against that standard twice a year.

02Standards we follow

• WCAG 2.1 Level AA — the four POUR principles (perceivable, operable, understandable, robust).
• WAI-ARIA 1.2 — for interactive components where native HTML doesn't carry enough semantics.
• Kenya Persons with Disabilities Act — Augusta is a Kenyan company and we operate within its provisions for accessibility.

03Accessibility features built into augusta.co.ke

• Semantic HTML throughout — proper headings, landmarks, lists, and form labels.
• "Skip to main content" link as the first focusable element on every page.
• Keyboard navigation for every interactive element — focus states are visible.
• Colour contrast meets or exceeds WCAG 2.1 AA on text and interactive components.
• Images use descriptive alt text or are marked as decorative.
• Forms use proper labels and provide error messages that name the affected field.
• The site degrades gracefully — content is readable without JavaScript.
• Layouts reflow at 320px viewport width without loss of information or functionality.
• Animation respects the user's prefers-reduced-motion setting.

04Known issues we're working on

We test continuously, and we're transparent about gaps:

• A small number of older blog-post images don't yet have detailed alt text — we're remediating these on a rolling basis.
• The interactive case-study filters announce filter changes via a live region, but the announcement text could be more descriptive. On the backlog.
• Embedded third-party content (YouTube, Google Maps) inherits its provider's accessibility characteristics, which we don't fully control.

05Testing and review

We use a combination of approaches:

• Automated tools — axe-core, Lighthouse, Pa11y — run in our CI pipeline so accessibility regressions block deployment.
• Manual keyboard-only testing — every page is walked through with the keyboard before release.
• Screen-reader testing — VoiceOver on macOS / iOS, NVDA on Windows, TalkBack on Android.
• Twice-yearly external review — an independent accessibility audit each February and August.

06Reporting accessibility issues

If you encounter a problem, please tell us. We aim to respond to accessibility reports within 2 business days and to remediate critical issues within 10 business days.

• Email: [email protected]
• Phone: +254 790 509 427
• Post: see address below

If reasonable, please include the page URL, the assistive technology you're using, and a description of what didn't work as expected.

07Contact us

Accessibility questions and reports go to our UX/UI lead.