Accessibility Statement
1. Our commitment
CleanSpot is committed to ensuring that our products are accessible to people with disabilities, including (but not limited to) people with visual impairments, hearing impairments, motor impairments, and cognitive differences.
Our target conformance level is Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, which is the standard referenced by the European Accessibility Act.
This statement covers three surfaces:
- The CleanSpot citizen mobile app (iOS and Android)
- The CleanSpot municipal dashboard (web)
- The cleanspot.cc marketing and information website
2. Conformance status
2.1 Citizen mobile app — partial conformance
The mobile app partially conforms to WCAG 2.1 Level AA. Most content and functionality meets the standard; specific items below do not yet fully conform.
What works well:
- Native iOS / Android accessibility APIs are integrated throughout (VoiceOver on iOS, TalkBack on Android)
- Tap targets are at least 44×44 points on most controls
- Text scaling: the app respects the OS-level "larger text" setting (capped at 1.3× to prevent layout breaks)
- Colour is not the sole means of conveying information (severity uses colour AND shape AND text)
- The app has been built with NativeWind / Tailwind tokens, meaning colour-contrast is consistently checked via the design system
- The biometric gate at app launch can be turned off for users who can't or don't want to use biometrics
Known partial-conformance items:
| Issue | Impact | Plan |
|---|---|---|
| Some custom map markers don't expose accessibility labels | Screen-reader users may not hear the spot's title when the marker is focused | Add accessibility labels to all marker components |
| Map screen relies on visual cues for severity / type | Users with low vision may struggle to differentiate pin types | Add a list-view alternative to the map (already exists as the Discover tab — to be cross-linked from Map) |
| Some onboarding screens lack VoiceOver focus order optimisation | Screen-reader navigation is functional but not ideal | Improve focus order in onboarding overlay |
| RankCrest SVG text may fall back to system font on Android | Visual rendering issue, not a screen-reader issue | Tracked in Android readiness audit |
| Hit-slop is too small on some icon-only buttons (login eye, comment overflow, avatar action button) | Difficult tap targets on small Android devices | Increase hit-slop to ≥48px (tracked in Android readiness audit M2) |
2.2 Municipal dashboard — partial conformance
The dashboard partially conforms to WCAG 2.1 Level AA.
What works well:
- Semantic HTML throughout (proper heading hierarchy, landmarks, lists)
- All form inputs have associated labels
- All images have
altattributes (descriptive for content images, empty for decorative) - Tab order is logical and follows visual layout
- Keyboard navigation is fully supported on every interactive element
- Focus indicators are visible on all focusable elements
- Colour-contrast meets AA on all text and UI components
- Tables are properly marked up with
<th>and scope attributes - The map view has a tabular alternative (the Inbox screen)
- Sign-in does not rely on visual CAPTCHA
Known partial-conformance items:
| Issue | Impact | Plan |
|---|---|---|
| Drag-and-drop on the Assignments kanban does not have a keyboard alternative | Users who can't use a mouse cannot reorder cards | Add a keyboard-accessible "move card" menu |
| Some data tables don't announce row updates to screen readers | Live updates may be missed by screen-reader users | Add aria-live regions to dynamic table sections |
| Tooltips on dense KPI tiles are mouse-hover only | Touch and keyboard users miss the explanation | Convert tooltips to focus-triggered popovers |
| Mermaid-rendered diagrams in some reports lack text alternatives | Visual-only content for screen-reader users | Add long-description text alongside each diagram |
| Loading skeletons are not consistently announced | Status of asynchronous loads is not always clear | Add screen-reader announcements for major loading states |
2.3 cleanspot.cc website — partial conformance
The marketing website partially conforms to WCAG 2.1 Level AA. Specific limitations are similar to the dashboard plus marketing-specific items (hero illustrations need alt-text refinement; video content, when added, requires captions and audio descriptions).
3. What we're doing about partial conformance
The known issues listed above are tracked in our internal accessibility backlog. Remediation is sequenced as follows:
| Quarter | Focus |
|---|---|
| Q3 2026 | Mobile app: marker accessibility labels, hit-slop fixes (alongside Android readiness pass) |
| Q4 2026 | Dashboard: kanban keyboard alternative, table aria-live regions |
| Q1 2027 | Website: full WCAG audit by external consultant; remediation plan from findings |
| Ongoing | Every new feature is reviewed for accessibility before shipping |
4. Compatibility
4.1 Browsers (dashboard and website)
The dashboard and website are tested on:
- Chrome (current and current-1)
- Firefox (current and current-1)
- Safari (current and current-1)
- Edge (current)
Combined with screen-reader testing on:
- NVDA (Windows / Firefox + Chrome)
- VoiceOver (macOS / Safari)
- JAWS (where available)
4.2 Mobile devices
The mobile app is tested for accessibility on:
- iOS 16+ with VoiceOver
- iOS 16+ with Dynamic Type at large sizes
- Android API 26+ with TalkBack
- Android API 26+ with system font scaling
5. Technical specifications
The CleanSpot products use standard web and mobile technologies:
- Mobile app: React Native + Expo, NativeWind for styling
- Dashboard: Next.js 16 (React 19), Tailwind CSS v4
- Website: Next.js, Tailwind CSS
These technologies support accessibility features when used correctly. We follow accessibility-conscious patterns in the design system (tokenised colours with verified contrast, semantic component primitives).
6. Known assistive-technology compatibility
We've tested with the assistive technologies listed above. We have not yet conducted formal compatibility testing with:
- Screen magnifiers (ZoomText, Windows Magnifier)
- Switch-control devices
- Voice control (Dragon NaturallySpeaking, Voice Control)
Compatibility with these is on our roadmap for the Q1 2027 audit.
7. Limitations
Some content is outside the scope of this statement:
- User-generated content (photos uploaded by citizens; descriptions written by users) — we cannot guarantee the accessibility of content created by third parties
- Third-party services we link to (App Store / Play Store listings, OpenStreetMap map tiles) — these have their own accessibility statements
- Embedded videos from external sources (we currently embed none, but if we ever do, captions and transcripts will be required)
8. Feedback and contact
We welcome feedback on accessibility. If you encounter an accessibility barrier in any of our products:
- Email:
accessibility@cleanspot.cc - Subject: please describe the issue clearly (e.g. "Cannot navigate kanban with keyboard on Assignments screen")
- We aim to respond within 5 business days
- We aim to provide a remediation plan within 20 business days, or an explanation if remediation is not possible
If you are dissatisfied with our response, you may contact your country's accessibility complaints authority. In Portugal, this is the Plataforma para a Cidadania, Igualdade e Inclusão (or successor body); in other EU countries, the equivalent national body.
9. Enforcement (EU Accessibility Act)
Under the European Accessibility Act, EU member states are required to designate enforcement authorities. Citizens who believe a digital service is non-compliant may file a complaint with the relevant authority in their country.
10. About this statement
| Item | Detail |
|---|---|
| Statement publication date | 2026-04-28 |
| Last reviewed | 2026-04-28 |
| Last technical update | 2026-04-28 |
| Next scheduled review | Annually, or sooner if a material accessibility issue is identified |
| Methodology | Self-assessment by the development team, supplemented by manual screen-reader testing on key flows; no third-party audit conducted yet |
The next major review is scheduled following the Q1 2027 external audit.
This Accessibility Statement is published by the operator of CleanSpot — an individual sole trader based in Portugal — in compliance with applicable EU and national accessibility legislation.