iOS Accessibility Statement

Compliance status

The Woebot iOS application is partially conformant with the WCAG 2.1 AA standard. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. These accessibility issues can be seen in the list below, along with a brief explanation of their user impact and the relevant WCAG success criteria (SC):

  • The ‘Send Message’ button cannot be focused during Onboarding. This means VoiceOver users are currently unable to complete the onboarding flow. WCAG SC: 4.1.2 Name, Role, Value.
  • Some text input fields are unlabelled. This makes it difficult for VoiceOver users to understand the purpose of the fields and what data they should write in. WCAG SC: 4.1.2 Name, Role, Value.
  • Some buttons do not announce as interactive elements. VoiceOver users would not understand that these elements can be activated, e.g. to load a new page or function. WCAG SC: 4.1.2 Name, Role, Value.
  • Some buttons announce confusingly with repetitive URL announcements. This adds a more verbose than necessary experience for VoiceOver users. WCAG SC: 4.1.2 Name, Role, Value.
  • The date picker announces without labels for the Day/Month/Year fields and with incorrect list semantics in the expanded options. VoiceOver users may encounter difficulty inputting their date of birth during onboarding. WCAG SC: 4.1.2 Name, Role, Value.
  • Some of the ‘delete attachment’ buttons are not focusable on the Send Feedback page. This makes it difficult for VoiceOver users to amend their feedback before sending. WCAG SC: 4.1.2 Name, Role, Value.
  • The ‘Reason for Contact’ field on the Send Feedback page has multiple accessible issues with labelling and focus management. This makes it difficult for VoiceOver users to understand what input is required, what input has already been entered, and how to adjust the input when needed. WCAG SC: 2.4.3 Focus Order, 4.1.2 Name, Role, Value.
  • Some of the page headings do not announce with any heading semantics. This can make understanding the page structure difficult for VoiceOver users. WCAG SC: 1.3.1 Info and Relationships.
  • Some interactive elements appear unlabelled because the label is implemented as an Accessibility Hint instead. For VoiceOver users who may have disabled the hints, this means they will not hear any label at all and will struggle to understand the purpose of the control. WCAG SC: 4.1.2 Name, Role, Value.
  • Some required fields do not announce as required. For VoiceOver users some required user input could be missed due to not realising it was required. WCAG SC 3.3.2 Labels or Instructions.
  • The application cannot be used in the landscape orientation. This may cause issues for wheelchair uses who are required to mount their device in a specific way and cannot easily change the orientation to match the application. WCAG SC 1.3.4 Orientation.
  • The accordion buttons on the Topics page do not always correctly convey their expanded or collapsed states. For VoiceOver users it can be difficult to navigate this section. WCAG SC: 4.1.2 Name, Role, Value.
  • The Woebot chat messages are not indicated as being from the chatbot during onboarding. This can make it difficult for VoiceOver users to understand the context and why this text is important. WCAG SC: 1.3.1 Info and Relationships.
  • Many of the animated images within the application cannot be paused. For users with a cognitive disability these can cause additional distractions that make it difficult to concentrate on the other elements of the page. WCAG SC 2.2.2 Pause, Stop, Hide.

If any of our content is not easily accessible, please contact us directly (see the details below).

Accessible alternatives

If you need information on this application in an alternative format like accessible PDF, large print or braille, you can contact us through the app or at support@woebothealth.com from your account’s email address. We will do our best to accommodate your request.

Accessibility feedback and contact information

We’re always looking to improve the accessibility of this application. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: 

What we’re doing to improve accessibility

We are currently working towards fixing our non-compliant content and we will revise this Accessibility Statement once improvements have been made.

Preparation of this accessibility statement

This statement was prepared on January 27, 2023.