Accessibility

Asotele's mission is closing the financial-information gap for Nigerians excluded from English-only economic discourse. That mission does not stop at language. This page documents what we've built into the site and the platform to be usable by people who navigate the web with screen readers, keyboards, magnifiers, high-contrast modes, or reduced-motion preferences — and what we have not yet shipped, named honestly.

Our commitment

Asotele's free SME tier will be voice-first and screen-reader-compatible. Voice input (Hausa, Yoruba, Igbo, Pidgin via the NaijaVoices Lacuna Fund speech corpus) and audio output (BibleTTS and project-built Pidgin TTS) are committed work, sequenced against the LINGUA Africa scope. This commitment stands regardless of any specific grant outcome. The substrate exists; the integration is what funding accelerates.

Current standards conformance

The public site at asotele.apexgridapps.com targets WCAG 2.1 Level AA. The advisor portal (Cloudflare Access gated) is held to the same target.

What's shipped today

  • Skip-to-content link on every page, focusable on first Tab press.
  • Semantic headings in clean hierarchy (h1 → h2 → h3, no skipped levels).
  • Named landmarks — <main>, <nav aria-label>, <footer> — for screen-reader landmark navigation.
  • Forms with explicit <label for> ↔ <input id> wiring, aria-required, aria-describedby hints, and live regions (aria-live="polite" on success, aria-live="assertive" on errors).
  • Visible focus ring on keyboard navigation — high-contrast green, 2px outline, 2px offset. Bumped to 3px in prefers-contrast: more mode.
  • Color contrast — body text 5.7:1 on background, primary green 7.4:1; named-state indicators (BOOM, STRESS, CRISIS) include text labels alongside color.
  • Demo video on the home page ships with a written transcript (expandable via <details>) AND WebVTT captions via <track kind="captions">. The video has no spoken audio; every on-screen text frame is captioned.
  • External-link warnings — every link that opens in a new tab announces "(opens in new tab)" to screen readers and shows a visible "↗" arrow.
  • Reduced motion respected via prefers-reduced-motion: reduce — animations and transitions effectively disabled for users who request it.
  • High contrast mode respected via prefers-contrast: more — focus ring thickens, link underlines become permanent, muted text deepens to full contrast.
  • Tables in blog posts have <thead> + <th scope="col"> for screen-reader column-header announcement.
  • No-script fallbacks on JavaScript-dependent forms — text + email alternative is offered if JS is disabled.

What's planned but not yet shipped

Honesty matters more than a perfect-sounding statement. Items committed but not yet live:

  • Voice-first SME tier (Hausa / Yoruba / Igbo / Pidgin speech input and audio briefings). Scoped under the LINGUA Africa workstreams; substrate (NaijaVoices, BibleTTS) is in hand.
  • Multilingual interface — language switcher across the four target languages plus English. Awaits native-speaker-reviewed interface copy.
  • Nigerian-language phrase tagging — <span lang="ha|yo|ig|pcm"> on Nigerian-language words in blog posts so screen readers pronounce them correctly. In progress on most-recent posts.
  • Sign-language considerations — Nigerian Sign Language (NSL) is a future workstream and depends on community partnership.
  • Custom modal dialog replacing native alert()/confirm() in the advisor portal's founder-only workflows. Native dialogs are accessible but the design could be more consistent.

Known limitations

  • The advisor portal requires JavaScript and an authenticated session via Cloudflare Access. A no-script email alternative is documented; users unable to use either are encouraged to write directly.
  • Some legacy blog posts (pre-2026-06-16) may have Nigerian-language phrases without explicit lang attributes; the sweep is rolling forward from most-recent posts first.
  • Caption timing on the demo video is currently approximate; a frame-accurate re-cut is on the maintenance queue.

Reporting an accessibility issue

If you hit something that doesn't work with your assistive technology, or you notice something this page omits, please write to francis.oyakhire@gmail.com with the page URL, the technology you're using (screen reader / browser / OS), and a short description. We respond within a few business days. Accessibility issues are treated as bugs, not feature requests.

Standards & references

Updates

Last updated: 2026-06-16