Caribbean builders and community
Public Wi-Fi becomes useful when a resident can complete a task on it. Start with the page they need after connecting: current status, opening hours, what to bring and a usable contact route. A coverage map alone cannot answer those questions.
A small page worth testing
| Field | Example |
|---|---|
| Location | Community hall; text address before any map |
| Status | Connection unavailable; checked 10:15 on the stated date |
| Task | Read the document checklist without signing in |
| Alternative | Printed checklist and an assisted counter |
| Privacy | No identity number required to view public information |
Keep essential information in HTML text, compress images and avoid autoplay media. Show when status was last checked rather than presenting an old “open” label as live. Preserve a phone or assisted route for people who cannot use the page.
Test with residents
- Try a low-cost phone on a slow connection and with images disabled.
- Check keyboard use, zoom, labels and screen-reader order.
- Ask residents to find opening hours and the alternative contact without coaching.
- Record failed tasks and revise the page; do not infer accessibility from a checklist alone.
Use W3C accessibility tutorials as implementation guidance. Catch Da Bus is a Caynetic community project in development; it is not evidence of a deployed public Wi-Fi service. No resident test results are claimed here.