Accessibility
We want trywelaka.com to work for everyone who visits it. Last updated [PLACEHOLDER — NOT LEGAL COPY: publication date, set at launch after the Phase 9 audit]
Our commitment
We build trywelaka.com to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard most widely used to make websites usable for people with disabilities.
Accessibility is not a one-time task. We check our work against this standard before we launch and again when we make significant changes, and we treat the reports we get from real users as the most important signal of all.
What we have done
We build this site so that:
- It works without a mouse. Every link, button, and form control can be reached and used with a keyboard, and the item you are on is always visibly outlined.
- It works with a screen reader. We use plain, semantic page structure — real headings, real lists, real buttons — so assistive software can make sense of it.
- It reads clearly. We check text and background colours for sufficient contrast.
- It respects motion settings. This site uses ambient motion. If your device is set to reduce motion, that motion turns off and the site stays fully usable.
- It describes its images. Images that carry meaning have text alternatives.
- It works without JavaScript. The content and the core actions do not depend on scripts to load.
Tell us if something does not work
If any part of this site is hard to use — a control you cannot reach, text you cannot read, motion that does not stop, anything — please tell us. It is the fastest way to get it fixed, and we treat it as a priority.
[PLACEHOLDER — NOT LEGAL COPY: the accessibility contact address. The mailbox is not yet created; a dedicated monitored address is best practice. Do not publish a dead address on the one page whose entire purpose is giving a blocked user a way through.]
We aim to respond quickly and to work with you on an alternative way to get what you need in the meantime.
Where we know we fall short
[PLACEHOLDER — NOT LEGAL COPY: this section is written AFTER the Phase 9 accessibility audit, from its findings. If the audit is clean, it says so briefly; if gaps ship, they are disclosed here honestly. Populate from the audit output — do not ship generic filler and do not delete the section.]
How we check
We test with automated tools and by hand — keyboard-only walkthroughs, screen-reader checks, contrast measurement, and a render check with scripts turned off — and we measure against WCAG 2.1 AA.