1. General information
This Statement has been issued by CRE8EVE Sp. z o.o. and concerns the Whispet mobile application available on the iOS platform.
CRE8EVE Sp. z o.o. strives to ensure the accessibility of its products and services by taking good mobile-accessibility practices and generally recognised guidelines (including WCAG 2.1 and the EN 301 549 standard) into account during the development of the App, treating them as reference material.
1.1. Legal status — service-providing microenterprise
CRE8EVE Sp. z o.o. is a microenterprise within the meaning of Art. 7(1)(1) of the Polish Act of 6 March 2018 — Entrepreneurs Law (Journal of Laws 2024 item 236, as amended). The Whispet application is a service within the meaning of Art. 3(17) of Directive (EU) 2019/882 (European Accessibility Act).
Pursuant to Art. 4(5) of Directive (EU) 2019/882 and Art. 4(1) of the Polish Act of 26 April 2024 on ensuring the fulfilment of accessibility requirements for certain products and services by economic operators (Journal of Laws 2024 item 731), the accessibility requirements set out in those acts do not apply to microenterprises providing services. This Statement is therefore voluntary and is issued in the spirit of transparency towards Users and good practices applicable to mobile-application providers.
The Controller reserves the right to assess the proportionality of accessibility measures implemented in relation to the scale of its business and available resources.
2. Compliance status
The Whispet application has been designed taking into account good mobile-accessibility practices, in particular the WCAG 2.1 guidelines and the EN 301 549 standard, treated as technical reference.
The Controller does not declare the App's compliance at any specific standard level (A / AA / AAA), in particular due to:
a) the legal status of a service-providing microenterprise (section 1.1) — no statutory obligation to meet EAA / 2024 Act requirements,
b) the self-assessed nature of this Statement — no certification by an independent third party,
c) the App's continuous development — accessibility features are introduced incrementally in subsequent updates.
Assessment methodology: This Statement has been drawn up on the basis of a self-assessment carried out by the Controller, including:
- an automated source-code audit for accessibility labels, hiding of decorative elements, and Reduce Motion handling,
- verification of interactive-element sizes,
- automated regression tests (audit gate
AccessibilityAuditTests), - manual testing with the VoiceOver screen reader on selected screens.
Sections 3 and 4 describe the implemented accessibility features and known limitations. The Controller strives to continuously improve accessibility in subsequent App updates.
3. Accessibility features implemented
3.1. Screen reader support (VoiceOver)
The main interactive elements — buttons, medical cards, filters, forms, date/time fields, swipe actions, context menus — as a rule have localised accessibility labels readable by VoiceOver. Pet photos and avatars have alternative descriptions. Decorative elements (gradients, separators, decorative directional icons) are largely hidden from screen readers (.accessibilityHidden(true)).
Coverage is not complete — some less-used or non-standard components may lack labels. The Controller applies an automated audit (AccessibilityAuditTests) blocking regressions for detected classes of violations, but this gate does not exhaust all possible cases. See section 4.
3.2. Contrast and colours
The App supports light mode, dark mode, and a dedicated High Contrast Mode with attention to text and interface-element readability. Status information (health, weight, trend) is duplicated with icons and text labels — it is not conveyed solely through colour.
3.3. Interactive element sizes
- Main action buttons (toolbar, share, close, FAB) are designed in line with the Apple Human Interface Guidelines recommendation for tap target size.
- Helper interactive elements (colour selectors, filter chips, small icons in lists) may have a smaller tap target — see section 4.3.
- Font scaling in App Settings — a continuous slider; the scaling also applies to interface icons together with the text.
3.4. Structure and navigation
The main navigation uses native SwiftUI components (TabView, NavigationStack) with built-in screen-reader support. Native iOS gestures (swipe-back, two-finger back on VoiceOver) are supported. Explicit focus-order management (@FocusState) is implemented in selected forms — the remaining forms use SwiftUI's default focus order (see section 4.1).
3.5. Animations and motion
Main animations (including gradient effects, list appearance) respect the system Reduce Motion setting — they are disabled or completed immediately. We do not rule out individual helper animations without that check — the Controller introduces them incrementally in subsequent updates.
3.6. Multilingual labels
Accessibility labels are localised in 6 languages (Polish, English, German, Spanish, French, Italian) and change together with the App's interface language.
3.7. Alternative data formats
Charts (body weight, the trend sparkline on the profile, and the charts in the Event Journals — line, bar, and pie) provide the VoiceOver screen reader with an audio description of the data ("Audio Graph", available in the VoiceOver rotor) and a readout of individual data-point values — as an alternative to the visual presentation. Numeric values and dates are read out in the system language.
3.8. High Contrast Mode
The High Contrast Mode (Settings → Appearance → "High contrast") provides:
- A uniform background (pure white or black) instead of a gradient
- Pure black on white (or pure white on black) for primary text, with markedly
strengthened contrast for secondary text - Prominent borders for fields, cards, and dialogs
- Decorative effects disabled
The mode works with any theme (light, dark, OLED) and is available in all 6 languages.
4. Known limitations
Despite the Controller's efforts, the following areas may not be fully accessible:
4.1. External keyboard navigation
- Forms primarily rely on SwiftUI's default focus order — explicit focus management (
@FocusState) is present only in selected text fields. - The App does not define custom keyboard shortcuts (
.keyboardShortcut); only iOS system gestures and native VoiceOver support for the rotor and one/two-finger navigation are available.
4.2. Photo grid (gallery)
- The photo grid in the gallery (masonry layout) may be difficult to navigate with a screen reader due to the irregular tile arrangement.
4.3. Helper interactive-element sizes
- Some interactive elements have a tap target smaller than the 44 × 44 pt recommended by Apple. This applies both to helper elements (colour selectors, filter chips, small icons in lists, badges) and to individual close buttons and delete buttons (e.g. removing a tag, a list option, an active filter) — in individual cases significantly smaller. The Controller introduces corrections progressively in subsequent updates.
4.4. Helper animations
- The App's main animations respect the Reduce Motion setting. Individual helper animations may not have an explicit check of that setting — the Controller introduces corrections incrementally in subsequent updates.
4.5. Screen readers in custom components
- Some less-used interactive components (e.g. selected combined gestures, custom pagination on selected screens) may not be fully optimised for VoiceOver. The main user paths (timeline, gallery, medical data, settings, Shared Care) are covered.
5. Further actions
The Controller strives to systematically improve the App's accessibility in subsequent updates and to regularly update this Statement together with changes in applicable accessibility standards (in particular the publication of EN 301 549 v4.1.1 incorporating WCAG 2.2).
The above is a description of the Controller's intent, not a contractual commitment to deliver specific functionality by a specific deadline. The current state of compliance as of the date of the last update of this document is described in sections 3 and 4.
6. Feedback and contact
If you encounter an accessibility issue in the Whispet application, please contact us:
- E-mail: hello@whispet.app
- Address: CRE8EVE Sp. z o.o., Tulipanowa 4, 72-003 Dobra, Poland
The Controller strives to respond within a reasonable time, usually no longer than 30 days from the date of the report.
7. Other user protections
Notwithstanding the Controller's legal status described in section 1.1, the User retains general consumer rights conferred by generally applicable provisions of law, including the option to use out-of-court mechanisms for resolving consumer disputes described in the Terms of Service (§15) and the EULA (§14.8).
To the extent that accessibility provisions for products and services would apply to the Controller, the market surveillance authority for e-commerce services is the minister responsible for computerisation (Art. 38(3)(2) of the Polish Act of 26 April 2024, Journal of Laws 2024 item 731), and the market surveillance system is supervised by the President of the Management Board of PFRON. For the protection of collective consumer interests, the competent authority remains the President of the Office of Competition and Consumer Protection (UOKiK) (https://uokik.gov.pl).
8. Technical information
- Platform: iOS 18+
- Technology: native iOS application built on SwiftUI, using iOS system accessibility APIs (VoiceOver, Reduce Motion, High Contrast Mode, focus management)
- Accessibility assessment method: Controller's self-assessment (section 2)
- Interface languages: Polish, English, German, Spanish, French, Italian
9. Reference materials
This Statement has been drawn up taking into account the following generally recognised mobile-accessibility guidelines, treated as reference material (and not as a source of obligations binding on the Controller — see section 1.1):
- WCAG 2.1 (Web Content Accessibility Guidelines, W3C) — guidelines for the accessibility of web content,
- EN 301 549 — European standard of accessibility requirements for ICT products and services,
- Directive (EU) 2019/882 (European Accessibility Act) and the Polish Act of 26 April 2024 on ensuring the fulfilment of accessibility requirements for certain products and services by economic operators (Journal of Laws 2024 item 731) — to the extent they apply to the Controller taking into account statutory exemptions.