Accessibility Statement

1. Accessibility Standards

1.1 Conformance Target

Penny strives to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web and mobile content more accessible to people with disabilities.

What This Means:

• Level A: Basic accessibility features (minimum standard)
• Level AA: Addresses common barriers (our target)
• Level AAA: Highest level (we implement where feasible)

Application Scope:

• Penny mobile application (iOS and Android)
• Penny website (pennypelvic.app)
• All user-facing features and content

1.2 Standards Referenced

We design and develop Penny in accordance with:

• WCAG 2.1: Web Content Accessibility Guidelines
• Section 508: U.S. federal accessibility standards
• ADA: Americans with Disabilities Act digital accessibility requirements
• Platform Guidelines:
  • Apple Human Interface Guidelines (iOS)
  • Material Design Accessibility (Android)

2. Accessibility Features

2.1 Visual Accessibility

Color & Contrast:

• All text meets WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text)
• Color is never the only way to convey information
• High contrast mode available in device settings
• Dark mode support for reduced eye strain

Typography:

• Minimum 16px font size for body text
• Scalable text supporting up to 200% zoom
• Clear, readable fonts (Montserrat)
• Adequate line spacing (1.5 for body text)
• No justified text (which creates uneven spacing)

Visual Design:

• Clear visual hierarchy
• Consistent layout and navigation
• Icons paired with text labels
• Status indicators use multiple cues (color + icon + text)
• No flashing or strobing content (reduces seizure risk)

Screen Reader Support:

• Semantic HTML structure
• Descriptive alt text for all images
• ARIA labels for complex interactive elements
• Proper heading hierarchy (H1, H2, H3)
• Form labels properly associated with inputs
• Status updates announced to screen readers

2.2 Motor/Physical Accessibility

Touch Targets:

• Minimum 44×44px touch targets (exceeds Apple's 44pt and Material Design's 48dp recommendations)
• Adequate spacing between interactive elements
• No gestures requiring fine motor control
• Alternative input methods for all gestures

Keyboard Navigation:

• Full keyboard navigation support
• Logical tab order
• Visible focus indicators
• Skip to main content link
• No keyboard traps

Time & Motion:

• No time limits on data entry
• Option to pause animations
• Reduced motion preference respected
• No auto-playing content

2.3 Cognitive Accessibility

Clear Language:

• Plain language throughout (Flesch Reading Ease score of 60+)
• Medical terms explained when necessary
• Consistent terminology
• Clear instructions and error messages
• Predictable navigation

Content Structure:

• Logical information hierarchy
• Short paragraphs (2-3 sentences)
• Bulleted lists for scanability
• Clear section headings
• Progress indicators for multi-step processes

Error Prevention & Recovery:

• Clear, actionable error messages
• Suggestions for fixing errors
• Confirmation prompts for destructive actions
• Easy undo/edit functionality
• Auto-save to prevent data loss

Focus & Attention:

• Minimal distractions
• No auto-playing media
• Optional push notifications
• Adjustable reminder frequency
• Ability to customize data collection (track only what matters to you)

2.4 Hearing Accessibility

Audio Alternatives:

• Text alternatives for any audio content
• Visual alerts in addition to audio alerts
• Captions for any video content (if introduced)
• No audio-only information

2.5 Platform Accessibility Features

iOS:

• VoiceOver screen reader support
• Dynamic Type for text scaling
• Voice Control compatibility
• Switch Control support
• Guided Access for focus
• AssistiveTouch compatibility

Android:

• TalkBack screen reader support
• Font size and display scaling
• Voice Access compatibility
• Switch Access support
• Select to Speak compatibility
• Android Accessibility Suite integration

3. Known Limitations

3.1 Current Limitations

We are continuously working to improve Penny's accessibility. Known areas for improvement:

In Progress:

• Enhanced screen reader descriptions for complex data visualizations
• Additional keyboard shortcuts for power users
• Voice input for symptom logging (planned)
• Haptic feedback for important actions (planned)

Third-Party Limitations:

• Some third-party libraries may not be fully accessible
• Platform-specific accessibility features vary between iOS and Android
• Older device operating systems may have limited accessibility API support

3.2 Minimum Requirements

For optimal accessibility, we recommend:

• iOS: iOS 14.0 or later
• Android: Android 9.0 (API level 28) or later
• Device Settings: Enable platform accessibility features as needed
• Screen Size: 320px width minimum (iPhone SE and equivalent)

4. Testing & Evaluation

4.1 Our Testing Methods

We evaluate Penny's accessibility through:

Automated Testing:

• Accessibility linting during development
• Automated WCAG compliance checks
• Continuous integration accessibility tests
• Color contrast analyzers

Manual Testing:

• Screen reader testing (VoiceOver, TalkBack)
• Keyboard-only navigation testing
• Zoom and magnification testing
• Real device testing across platforms

User Testing:

• Feedback from users with disabilities
• Beta testing with accessibility advocates
• Ongoing user research
• Accessibility-focused user interviews

4.2 Third-Party Audits

We plan to conduct:

• Annual accessibility audits by third-party experts
• Penetration testing for security accessibility
• Compliance verification against WCAG 2.1 AA
• User experience studies with diverse ability groups

5. Assistive Technologies Supported

5.1 Screen Readers

Tested and Supported:

• iOS VoiceOver
• Android TalkBack
• (Future: JAWS, NVDA for web interface)

Features:

• Logical reading order
• Descriptive labels for all interactive elements
• Alternative text for images and icons
• Landmarks for page regions
• Form field labels and instructions
• Error identification and suggestions

5.2 Voice Control

Supported Commands:

• Open Penny
• Navigate to [section name]
• Add new entry
• Show [data type] history
• Export data
• Platform-specific voice commands

5.3 Switch Control

Full support for:

• iOS Switch Control
• Android Switch Access
• Single-switch scanning
• Multi-switch direct selection
• Adjustable timing

5.4 Magnification

Support for:

• Platform zoom features (up to 200%+)
• Text scaling
• Screen magnification
• No loss of content or functionality when zoomed

6. Content Accessibility

6.1 Text Content

All Text Content:

• Written in clear, plain language
• Minimum 16px font size
• Adequate contrast (WCAG AA)
• Resizable up to 200%
• No text in images (except logos)

Headings:

• Logical hierarchy (H1 → H2 → H3)
• Descriptive and unique
• Never skip levels
• Used for structure, not styling

6.2 Images & Icons

All Images Include:

• Descriptive alt text
• Context-appropriate descriptions
• Decorative images marked as such
• Icons paired with text labels

Complex Graphics:

• Detailed descriptions provided
• Data tables for charts/graphs
• Text alternatives for infographics

6.3 Forms & Inputs

All Forms Include:

• Clear, descriptive labels
• Labels visually associated with inputs
• Labels programmatically associated (for attribute)
• Required fields clearly marked
• Input purpose identified
• Error messages associated with fields
• Instructions provided before input
• Help text available as needed

Form Validation:

• Errors clearly identified
• Suggestions for correction
• Error summary at top of form
• Errors announced to screen readers
• No validation on focus loss

6.4 Data Visualizations

Charts & Graphs:

• Alternative text descriptions
• Data tables provided
• High contrast colors
• Patterns in addition to colors
• Keyboard accessible
• Screen reader friendly

7. Mobile-Specific Accessibility

7.1 Touch & Gestures

Accessible Touch Targets:

• 44×44px minimum (iOS) / 48×48dp minimum (Android)
• Adequate spacing between targets
• Visible tap states
• No accidental activation

Gesture Alternatives:

• All gestures have button alternatives
• Simple, standard gestures only
• Gestures can be performed with one hand
• No multi-finger gestures required

7.2 Device Features

Support for:

• Device rotation (portrait/landscape)
• Text-to-speech
• Speech-to-text (future feature)
• Haptic feedback
• Platform accessibility shortcuts

7.3 Notifications

Accessible Notifications:

• Multiple notification methods (visual + audio + haptic)
• Adjustable notification settings
• Clear, concise notification text
• Actionable notifications where appropriate

8. Documentation Accessibility

8.1 Help & Support

Accessible Support Resources:

• Help documentation in plain language
• Step-by-step guides with images
• Video tutorials with captions (future)
• Multiple contact methods
• Accessible FAQ format

8.2 Legal Documents

This document and all legal policies:

• Available in accessible HTML format
• Clear headings and structure
• Plain language summaries
• Available on request in alternative formats

9. Feedback & Reporting Issues

9.1 How to Report Accessibility Issues

We welcome feedback about Penny's accessibility. If you encounter any accessibility barriers, please let us know:

Email:

• Accessibility Issues: accessibility@baig-innovations.com
• General Support: hello@baig-innovations.com

What to Include:

• Description of the accessibility barrier
• Steps to reproduce the issue
• Device and OS version
• Assistive technology used (if applicable)
• Screenshots (if relevant)

Response Time:

• Acknowledgment within 2 business days
• Initial response within 5 business days
• Resolution timeline provided based on severity

9.2 Priority Levels

We prioritize accessibility issues as:

Critical (1-2 weeks):

• Blocks essential functionality
• Prevents use for users with disabilities
• WCAG Level A failures

High (2-4 weeks):

• Significantly impacts usability
• Difficult workarounds
• WCAG Level AA failures

Medium (1-2 months):

• Impacts user experience
• Workable alternatives exist
• Enhancement opportunities

Low (Ongoing improvements):

• Minor inconveniences
• Exceeding WCAG AA (AAA)
• Nice-to-have features

10. Ongoing Improvements

10.1 Our Commitment

Accessibility is not a one-time project but an ongoing commitment. We continuously work to:

Short-Term (Next 3 months):

• Address all reported accessibility issues
• Improve screen reader support for data visualizations
• Enhance keyboard navigation shortcuts
• Expand testing with diverse user groups

Medium-Term (3-12 months):

• Implement voice input for symptom logging
• Add more haptic feedback
• Create video tutorials with captions
• Conduct formal accessibility audit

Long-Term (1+ year):

• Achieve WCAG 2.2 compliance when published
• Explore emerging assistive technologies
• Build accessibility into product roadmap
• Establish accessibility advisory board

10.2 Training & Awareness

Internal Commitment:

• Accessibility training for all team members
• Accessibility champions in each department
• Regular accessibility reviews
• User empathy exercises

11. Accessibility Resources

11.1 Learning About Accessibility

General Resources:

• W3C Web Accessibility Initiative: w3.org/WAI
• WebAIM: webaim.org
• A11Y Project: a11yproject.com
• Deque University: dequeuniversity.com

Platform-Specific:

• Apple Accessibility: apple.com/accessibility
• Android Accessibility: android.com/accessibility
• iOS Human Interface Guidelines: developer.apple.com/design/human-interface-guidelines/accessibility
• Material Design Accessibility: material.io/design/usability/accessibility

11.2 Assistive Technology Support

Getting Help with Assistive Tech:

• iOS Accessibility Support: support.apple.com/accessibility
• Android Accessibility Help: support.google.com/accessibility
• Platform-specific accessibility forums
• Assistive technology vendor support

12. Legal & Compliance

12.1 Regulatory Compliance

Penny strives to comply with:

United States:

• Americans with Disabilities Act (ADA) Titles II and III
• Section 508 of the Rehabilitation Act
• 21st Century Communications and Video Accessibility Act (CVAA)

State Laws:

• California Unruh Civil Rights Act
• Florida Civil Rights Act
• New York Human Rights Law

12.2 Industry Standards

We follow:

• WCAG 2.1 Level AA (minimum)
• ISO 40500:2012 (identical to WCAG 2.0)
• EN 301 549 (European accessibility standard)
• Platform-specific accessibility guidelines

13. Third-Party Content & Services

13.1 Third-Party Accessibility

Our Vendors:

We require our service providers to maintain accessible services where they interact with users. However, we cannot guarantee the accessibility of:

• Third-party websites we link to
• External resources and articles
• Payment processing interfaces
• Third-party login services (if implemented)

If you encounter accessibility issues with third-party content, please let us know so we can work with our vendors or find alternatives.

13.2 External Links

Links to external websites (educational resources, support groups) may not meet Penny's accessibility standards. We:

• Evaluate external resources for accessibility when possible
• Provide warnings for inaccessible content
• Seek accessible alternatives
• Are working to curate an accessible resource library

14. Alternative Formats

14.1 Available Formats

This accessibility statement and other legal documents are available in:

• Accessible HTML (default)
• Plain text
• Large print (upon request)
• Other formats upon request

To request an alternative format:

Email hello@baig-innovations.com with:

• Document name
• Preferred format
• Any specific requirements

We will provide the requested format within 5 business days.

15. Contact Information

Questions or Concerns About Accessibility?

Email:

• Accessibility Issues: accessibility@baig-innovations.com
• General Support: hello@baig-innovations.com

Mailing Address:
Baig Innovations, LLC
Orange County, Florida

Response Time:

• Acknowledgment within 2 business days
• Detailed response within 5 business days
• Resolution plan within 10 business days

16. Acknowledgments

We appreciate the work of accessibility advocates, organizations, and users who help us identify and address accessibility barriers.

Special Thanks To:

• The W3C Web Accessibility Initiative
• WebAIM (Web Accessibility In Mind)
• The A11Y Project
• Our beta testers who provide accessibility feedback
• The disability community for ongoing education and advocacy

17. Changes to This Statement

17.1 Updates

We update this Accessibility Statement:

• When we make significant accessibility improvements
• When we discover accessibility issues
• At least annually as part of our accessibility review
• When standards or regulations change

17.2 Version History

• Version 1.0 (January 1, 2025): Initial accessibility statement

Previous versions available upon request.