Querencia Accessibility Statement

Last reviewed: 20 September 2026

Querencia helps you keep a personal record of symptoms and medication doses between appointments. It is designed primarily for iPhone. The app also targets iPad, but current validation is focused on iPhone and does not establish equivalent iPad coverage. This statement describes the current development implementation, not an App Store certification or release announcement.

Features implemented

• VoiceOver: contextual control labels, selected states, headings, chart descriptions and audio-graph descriptors, and dated text alternatives for report values. A privacy cover hides the covered record from accessibility navigation.
• Voice Control: standard controls and contextual input labels for repeated actions.
• Larger Text: semantic text styles, flexible rows, scrollable forms, and report layouts that reflow at accessibility text sizes.
• Dark Interface: adaptive app colors and launch appearance.
• Differentiate Without Color Alone: written severity and dose states, selection checkmarks, chart outlines, and dated values.
• Sufficient Contrast: tested text and chart-mark color pairs, including light, dark, and increased-contrast palettes. Native overlays and composed pixels still need review.
• Reduced Motion: app-controlled spatial animations and transitions respond to the system Reduce Motion setting.

Current content contains no prerecorded audio or video, so captions and audio descriptions are not applicable. External reference websites are separate destinations with their own accessibility behavior.

Reports and recovery

Reports can be shared as selectable, tagged PDFs or complete text reports, using the same displayed date interval. PDF files are prepared only when you choose Export as PDF. Privacy also provides an authenticated full clinical JSON export and confirmed local-data deletion. Text exports provide an alternative for readers that reflow text independently of fixed PDF pages. Reading order and navigation still need testing with assistive technologies in receiving applications.

Forms preserve entered choices when saving fails. Loading, missing records, failed exports, and a failed database open have explicit states or recovery actions. Device authentication, permission sheets, notifications, Siri, and share destinations include interfaces provided by Apple or another app and require evaluation as part of the whole task.

What has been verified

Development checks have covered seven iPhone UI flows, domain regressions, persistence recovery, PDF structure, and extracted report content. The privacy implementation added focused regression checks and reran the affected onboarding, privacy-control/deletion-cancellation, and PDF-sharing flows on an existing iPhone simulator. Automated UI audits gate touch regions, descriptions, traits, and clipped text for tested configurations. They also record contrast, Dynamic Type, and element-detection diagnostics that are not all resolved.

These checks do not replace eyes-free task completion, Voice Control operation, braille, keyboard interaction, Switch Control use, or testing with people who depend on assistive technologies. Physical-device evaluation, older supported iOS versions, system permission/authentication flows, and a complete iPad evaluation remain incomplete. See the known issues and evaluation gaps.

Standards and App Store declarations

We use Apple’s Accessibility Nutrition Labels guidance to organize feature evaluation and WCAG 2.2 as a reference for applicable presentation criteria. We do not claim complete WCAG conformance or feature-wide App Store support from automated checks alone. App Store declarations must reflect the final shipping build and completed applicable task evaluation.

Report a barrier

Report an accessibility barrier, including the task, device, app/iOS versions, and assistive technology or settings involved. A GitHub account is required to submit a report. Issues are public; use invented data and omit medical details or identifying screenshots.

Ariel Tyson maintains this statement and reviews reports. Developer information is available at arieljtyson.com. You can review the statement’s public history and the privacy policy.