Accessibility

This page covers the whole Witakare platform: patients, practitioners, in-app thread, email and SMS. It describes the state as of 12 September 2026. It is not a WCAG conformance claim.

Scope

• Public website.
• Patient journey and patient space; practitioner space.
• Practitioner portal opened from an email (one file at a time).
• Private in-app thread (both sides).
• Transactional email (file invitation, offer available, unread message, password reset).
• Transactional SMS (a notice and a link to the space, when that channel is chosen).
• This page.

Google listing and contact details

Witakare does not create a second clinic identity. Practitioner verification uses the clinic's Google listing (rating, reviews, name, address, phone shown there). When contact details must be passed on after the patient has chosen, the platform sends the same details as the listing; it does not rewrite them or invent another set.

Accessibility of the Google listing itself is Google's. Witakare is responsible for a faithful copy (same name, address and number) and for how those details appear here once contact has been shared: real text, never a star or an icon alone to carry the rating.

How to see and use the product more easily

Witakare does not add an overlay toolbar. Use your device or browser:

• enlarge text (browser zoom, up to 200%);
• contrast and text size in system settings;
• a screen reader (VoiceOver with Safari, NVDA with Firefox, TalkBack on Android);
• keyboard navigation (Tab, Shift+Tab, Enter, Space).

For email: use HTML or plain text as your client allows; the main link is always written out. For SMS: the text is short, the link is written in full, nothing essential lives only in an image.

Known gaps

Here is what we know to be missing, as of 12 September 2026, in plain words. A line that is no longer true is removed; a new line is added the day it is measured.

Practitioner side (portal, space, practitioner email)

• On a phone, the private thread with the patient sits below the response form; a link at the top of the file leads straight to it. On a computer, the two have sat side by side since 10 September 2026.
• Three screens are re-measured on every update by an automated check: portal sign-in, the file with its response form, and the list of files in the space. The other practitioner screens, including My account and password reset, are not yet; they will be.
• Practitioner account email (address change, password) has not yet had the subject and preview pass already done on the other messages. That work is on the list.

Patient side (site, journey, patient space, patient email and text messages)

• On this public site, the grey footer text is too pale against the dark background, and the white text on the orange buttons does not stand out enough. Measured on 12 September 2026, written to the journal, correction to be scheduled. This page carries neither.
• The patient journey and patient space are not yet under the automated check that re-measures the practitioner screens on every update. The same label and error-state pass as the practitioner response form remains to be done.
• An SMS cannot carry headings or image equivalents: it does not replace the space, it points to it.

This list will be dated again after practitioner account email is aligned, then after the accessibility pass on the patient journey and patient space.

Report a barrier

If a barrier stops you from opening a file, reading an offer, writing in the thread, or receiving email or SMS notice, write to contact@witakare.com, Witakare's single reply address. Tell us the page and what blocks you. We aim to reply within ten business days.

If the six-digit verification code does not reach you by text message, it can be read to you by phone call: ask for it on the code screen, or write to us.

Review

Last reviewed: 12 September 2026. Next review planned after practitioner account email is aligned, then after the accessibility pass on the patient journey and patient space.

This page informs, lists gaps and gives a contact. It does not claim ISO/IEC 30071-1 or a WCAG logo.