Purpose and scope
Accessibility in Pocket Genes means people should be able to physically operate the product and understand complex genetic, privacy, security, report-access, and community concepts. The statement covers the public website, Trust Center, mobile-centered product experience, report-access flows, community features, and Pocket Genes-controlled pages.
Provider reports, app stores, linked websites, embedded booking tools, external organization resources, and third-party files may follow their own accessibility and support processes.
Who this statement applies to
- People using Pocket Genes public pages, Trust Center, app screens, report-access flows, account workflows, or community features.
- People using assistive technology such as screen readers, keyboard navigation, switch controls, zoom, text scaling, captions, or alternative input.
- Caregivers, providers, organizations, and support contacts helping someone access Pocket Genes.
Definitions
WCAG
Web Content Accessibility Guidelines, the W3C standard used to evaluate web accessibility.
Assistive technology
Technology such as VoiceOver, TalkBack, screen readers, magnifiers, keyboard navigation, switch control, captions, voice input, or browser accessibility features.
Support path
A practical route for help, explanation, accessible copy, or assisted access when a user needs a different format.
Accessibility standard
Pocket Genes aims to meet WCAG 2.2 Level AA for public web experiences and applies corresponding accessible-design principles to mobile applications.
Accessibility review is part of product design, content review, support intake, and release work for Pocket Genes-controlled experiences.
Last accessibility review date for this statement: August 14, 2026.
Supported accessibility features
- Semantic headings, landmarks, lists, tables, links, and buttons for public web pages.
- Keyboard navigation and visible focus indicators where controls are present on public pages.
- Readable contrast, responsive layout, non-color indicators, and stable text wrapping.
- VoiceOver and TalkBack-friendly labels for mobile app controls where native implementation permits.
- Dynamic Type and text scaling principles for mobile layouts.
- Clear form labels, validation messages, error states, and recovery paths.
- Touch targets sized for mobile use and layouts that avoid requiring a specific orientation when possible.
- Reduced-motion consideration for non-essential animation.
- Plain-language labels and alternatives for charts, tables, genomic visuals, and dense scientific content.
- Captions, transcripts, or text alternatives where Pocket Genes publishes media that needs them.
Review methods
Pocket Genes accessibility review includes semantic markup checks, keyboard checks for public pages, responsive layout review, color-contrast review, content readability review, and user-support feedback.
Product review may include automated tools, manual keyboard review, screen-reader review, text scaling, contrast checks, mobile device review, and feedback from people using assistive technology.
Support options
| Area | Support option | Contact route | Product action |
|---|---|---|---|
| Provider reports and external resources | Request an accessible copy or alternate path when a provider-controlled format is difficult to use. | Contact Pocket Genes or the provider listed for the report. | Route the request and coordinate accessible alternatives where available. |
| Embedded booking or third-party widgets | Use direct email when a scheduling component is not the preferred format. | Email support@goldencrowvs.com. | Keep a direct contact path alongside third-party tools. |
| Visual genomic information | Request an explanation or alternate format for dense charts or tables. | Email support@goldencrowvs.com. | Use structured summaries and non-color labels for genomic displays. |
Support process
Accessibility support requests can be sent to support@goldencrowvs.com. Include the page, screen, workflow, device, browser, operating system, app version, assistive technology, and the task you want to complete.
Pocket Genes reviews accessibility requests by user impact and can provide an alternative format or assisted path where feasible.
Pocket Genes responsibilities
- Use WCAG 2.2 Level AA as the public web target for Pocket Genes-controlled pages.
- Keep accessibility review connected to product, content, and support work.
- Provide feedback channels and alternative access paths.
- Prioritize requests involving account, report, authorization, community, security, or support workflows.
User, integrator, and organization responsibilities
- Users can share the page, screen, device, and task so support can respond efficiently.
- Integrators and providers should make provider reports and linked resources accessible where they control the content.
- Organizations should publish resources and events in accessible formats and provide alternatives when requested.
External scope notes
- Provider reports, external websites, app stores, embedded tools, and user-generated content may be controlled by third parties.
- Some accessibility requests are routed to the provider, organization, platform, or tool that controls the affected resource.
- Security or privacy constraints may limit assisted access until identity is verified.
How to make a request or report a problem
Privacy, account, deletion, accessibility, safety, trusted-organization, and security requests can be sent to support@goldencrowvs.com. Use a subject line that identifies the issue, the affected Pocket Genes account or workflow, and whether the request is urgent.
Pocket Genes may need to verify the requester before changing or disclosing account information. Verification is handled proportionally to the request, the sensitivity of the information, and the risk of giving account access or private information to the wrong person.
Effective date, version, and review history
| Item | Value |
|---|---|
| Effective date | August 14, 2026 |
| Version | 1.1 |
| Last reviewed | August 2026 |
| Material changes | Expanded Trust Center format, operator identity, data-map boundaries, request paths, and responsibility sections. |
| Previous version | July 2026 Trust Center overview copy. |