Our commitment
A grant-maker whose website excludes the people most likely to apply has a problem. We design tratok.org to meet WCAG 2.2 Level AA as a baseline, and we treat accessibility issues as defects rather than feedback.
What we've built in
- Semantic HTML. Headings, landmarks, lists, and tables use the right elements so assistive tech can navigate the page structure.
- Skip link. A keyboard-visible skip link jumps past the header straight to the main content.
- Keyboard operability. Every link, button, and form control is reachable and usable with the keyboard alone, with a visible focus ring.
- Reduced motion. The site respects the operating-system reduced-motion preference and switches off non-essential animation.
- Zoom and reflow. Layouts reflow to 320 px without horizontal scrolling and at 200 % browser zoom without content loss.
- Alt text. Decorative images are marked as such; informative images carry concise alt text.
- Contrast. Body text and primary actions meet AA contrast against the dark canvas.
- Language. The document
langattribute is set. A language-switcher offers English, Arabic (RTL), Spanish, and French; more on request.
Known limitations
We try to be honest about what we haven't fixed yet:
- Accent colour contrast. A handful of decorative accent strings (eyebrows over headings) sit at AA-large rather than AA-normal. They are not load-bearing for meaning.
- Non-English content. Translations into Arabic, Spanish, and French are now live; Swahili, Portuguese, and additional languages will follow as the Foundation's grantee footprint expands.
- PDF artefacts. Where we publish PDFs (for example future audited financials), some legacy documents are not yet tagged. We are migrating to tagged outputs and will provide accessible HTML alternatives where possible.
- Rich content widgets. The on-chain balance card relies on a third-party RPC; if that RPC is slow we render a loading state. Screen-reader users will hear the loading status; keyboard users may need to wait one second before tabbing past it.
Testing
The site is tested by the core team on:
- Recent versions of Chrome, Firefox, Safari, and Edge on macOS and Windows.
- VoiceOver (macOS, iOS), NVDA (Windows), and TalkBack (Android).
- Keyboard-only navigation.
- Reduced-motion and forced-colors modes.
- Automated audits via axe-core and Lighthouse on every release branch.
We plan to commission an independent audit once the first grant cycle is approved by Tratok Tower governance, and to publish the findings here alongside our remediation log.
Report a barrier
If you encounter a problem using this site with assistive technology — or if any content is not legible, audible, or operable for you — we want to know.
Email accessibility@tratok.org with:
- The page URL where you hit the problem.
- The assistive technology, browser, and operating system you were using (if relevant).
- A description of what happened and what you expected instead.
Response SLA: we acknowledge within 5 working days and aim to fix critical barriers in the next release.
Alternative contact
If email is not accessible to you, ask a third party (a friend, an advocate, a community organisation) to relay the message — we will treat that submission with the same priority. Once the secretariat is operational, we will publish a postal address and additional channels here.
