Circlworld

Accessibility Statement

Version · Effective · Last updated 2026-05-21

Accessibility Statement

1. Our commitment

Circlworld is committed to making our platform accessible to everyone, including people with disabilities. Accessibility is part of our broader commitment to serving communities that have historically been underserved by financial technology.

We design and develop our platform with the goal of meeting Web Content Accessibility Guidelines (WCAG) 2.1 Level AA — the international standard for web accessibility.

This Statement explains:

  • The standards we follow
  • The current state of accessibility on our platform
  • Known limitations and our plans to address them
  • How to report accessibility issues
  • Your rights to accessible communication

2. The scope of this Statement

This Statement applies to:

  • The Circlworld platform at circlworld.com
  • Circlworld email communications
  • The Circlworld iOS and Android mobile applications (when launched)
  • Documentation we publish

This Statement does not apply to:

  • Third-party services we integrate with (Stripe, Onfido, Smile ID, etc.) — these are governed by their respective accessibility statements
  • Content created by our members or treasurer partners

3. The standards we follow

3.1 Web Content Accessibility Guidelines (WCAG) 2.1 Level AA

Our target is WCAG 2.1 Level AA across the platform. This includes:

  • Perceivable — content can be perceived by all users, including those who cannot see, hear, or perceive content in standard ways
  • Operable — the interface can be operated by everyone, including users who cannot use a mouse or who need additional time
  • Understandable — information and operation are understandable, with clear language and predictable behaviour
  • Robust — content works with current and future assistive technologies

3.2 Section 508 (United States)

For US-facing services (when expansion to the United States is complete), we will also align with Section 508 of the Rehabilitation Act.

3.3 European Accessibility Act (when applicable)

Where the European Accessibility Act applies to our services in EU member states, we will meet those requirements.

4. Accessibility features

Specific accessibility features we build into the platform include:

4.1 Visual accessibility

  • High colour contrast ratios meeting WCAG AA (4.5:1 for normal text, 3:1 for large text)
  • Scalable text — users can zoom up to 200% without loss of functionality
  • Alternative text on all meaningful images
  • Compatible with screen readers (JAWS, NVDA, VoiceOver, TalkBack)
  • Clear visual focus indicators
  • Sufficient spacing between interactive elements

4.2 Auditory accessibility

  • Captions on all video content
  • Transcripts available for audio content
  • No content relies solely on sound

4.3 Motor accessibility

  • All functionality available via keyboard
  • Logical keyboard navigation order
  • Skip links to main content
  • Generous touch target sizes (44x44px minimum)
  • No content requires complex gestures
  • Adjustable timeout warnings

4.4 Cognitive accessibility

  • Plain language wherever possible
  • Consistent navigation and layout
  • Predictable behaviour (no unexpected pop-ups or context changes)
  • Clear error messages with suggested corrections
  • Multiple ways to complete tasks
  • Confirmation steps for significant actions

4.5 Language accessibility

  • Currently available in English
  • Plans to add Jamaican Patois (informal contexts) and Spanish (US Caribbean diaspora) in future releases

5. Current accessibility status

5.1 Compliance level

As of the date of this Statement, the Circlworld platform is partially compliant with WCAG 2.1 Level AA. We have made significant progress but acknowledge known gaps which we are actively addressing.

5.2 Areas of strong compliance

  • Visual contrast ratios across the platform
  • Keyboard navigation throughout the application
  • Screen reader compatibility for primary flows (login, account, dashboard)
  • Mobile responsive design
  • Form labelling and error messaging

5.3 Known limitations

We are aware of the following accessibility issues. We are committed to resolving them on the timeline indicated:

| Issue | Affected area | Target resolution | |-------|---------------|-------------------| | Some interactive charts lack full screen reader descriptions | Treasurer Dashboard analytics | Q3 2026 | | Trust Report PDF generation needs improved tagging for screen readers | Trust Reports | Q4 2026 | | Some animated transitions may affect users with vestibular conditions | Various | Q3 2026 — adding reduced-motion preference | | Mobile applications not yet available; web platform must be used on mobile browsers | Mobile | Native apps launching 2027 |

5.4 Areas requiring user-initiated configuration

Some accessibility features require users to enable them in their device or browser:

  • High contrast mode (browser/OS setting)
  • Larger text size (browser/OS setting)
  • Screen reader (assistive technology software)
  • Captions on video playback (player setting)

We aim to ensure the platform works well with these user-side configurations.

6. How we maintain accessibility

6.1 Design and development

  • Accessibility considered from initial design through development
  • Component library built with accessibility primitives (using Shadcn UI and similar accessible foundations)
  • Code reviews include accessibility checks
  • Automated accessibility testing in our continuous integration pipeline
  • Manual testing with assistive technologies before significant releases

6.2 Auditing

  • Annual external accessibility audit conducted by qualified accessibility professionals
  • Quarterly internal accessibility reviews
  • User testing with people who use assistive technologies (when feasible)

6.3 Staff training

  • Engineering and design staff complete accessibility training
  • Customer support staff trained on accessibility-related queries
  • Documentation includes accessibility considerations

7. How to report accessibility issues

If you encounter an accessibility issue on the Circlworld platform, please tell us. Your feedback helps us improve.

7.1 What to include

  • A description of the issue
  • Where on the platform you encountered it (URL or screen)
  • The device, browser, and assistive technology you were using
  • Any error messages or unexpected behaviour
  • (If you wish) your contact details so we can follow up

7.2 How to report

7.3 What you can expect

  • Acknowledgment within 5 business days
  • Investigation by our accessibility team
  • Substantive response within 20 business days, including:
    • Our assessment of the issue
    • Our planned response (immediate fix, scheduled fix, or workaround)
    • Estimated timeline for resolution

If our response does not satisfy you, you may escalate through our Complaints Handling Policy.

8. Accessible alternatives

If you cannot access content on our platform due to an accessibility issue, we will provide alternative means to access the same information or service. This may include:

  • Documents in alternative formats (large print, simplified language, audio)
  • Assisted access where a Circlworld staff member helps you complete a task
  • Telephone or email alternatives to online forms

To request an alternative, contact accessibility@circlworld.com.

9. External escalation

If we cannot resolve your accessibility concern through our internal processes, you have rights to escalate.

Jamaica:

  • Jamaica Council for Persons with Disabilities — for advocacy and support
  • Office of the Information Commissioner (OIC) — for digital accessibility concerns

United Kingdom:

United States (when applicable):

  • US Access Board — Website: www.access-board.gov
  • Department of Justice — for ADA Title III complaints

10. Why accessibility matters to Circlworld

Accessibility is not an afterthought or a compliance checkbox. Circlworld exists to serve communities that have historically been excluded from formal financial systems. Many of those communities include people with disabilities who face additional barriers to participation.

When we build accessibly, we serve the people who most need the infrastructure we are building. When we do not build accessibly, we replicate the exclusion that motivates the platform's existence.

This is why accessibility is not a feature we add at the end. It is part of how we think about the platform from the beginning.

11. Updates to this Statement

We update this Statement whenever:

  • We make significant changes to the platform
  • We become aware of new accessibility issues
  • We resolve known issues
  • Accessibility standards we follow are updated

The current version is always available at circlworld.com/legal/accessibility, with the date of last update shown at the top.

12. Contact

For any questions about accessibility:

This Accessibility Statement is part of Circlworld's commitment to inclusive, responsible operation. It is read together with our Terms of Service, Privacy Notice, and Complaints Handling Policy.