Accessibility Statement

1. Our Commitment to Accessibility

Paglipat is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards to ensure we provide equal access to all of our users.

We believe that everyone should be able to search for and book flights, regardless of ability. Accessibility is not just a legal requirement—it's the right thing to do, and it makes our service better for everyone.

This statement reflects our ongoing efforts to make Paglipat accessible and usable by the widest possible audience, including people who:

• Are blind or have low vision
• Are deaf or hard of hearing
• Have limited mobility or dexterity
• Have cognitive or learning disabilities
• Use assistive technologies such as screen readers, voice recognition, or alternative input devices

2. Accessibility Standards

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards issued by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible for people with disabilities.

WCAG 2.1 Principles

Our accessibility efforts are guided by the four core principles of WCAG:

• Perceivable: Information and user interface components must be presentable to users in ways they can perceive (e.g., text alternatives for images, captions for videos)
• Operable: User interface components and navigation must be operable (e.g., keyboard accessible, sufficient time to read content)
• Understandable: Information and operation of the user interface must be understandable (e.g., readable text, predictable navigation)
• Robust: Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies

Additional Standards

We also reference:

• Section 508 of the Rehabilitation Act (United States)
• EN 301 549 (European standard for digital accessibility)
• Americans with Disabilities Act (ADA) Title III

3. Accessibility Features

We have implemented numerous accessibility features throughout our Service to ensure it can be used by everyone:

Keyboard Navigation

• All interactive elements can be accessed using only a keyboard
• Logical tab order throughout the site
• Visible focus indicators on all focusable elements
• Skip navigation links to bypass repetitive content
• Keyboard shortcuts for common actions

Screen Reader Support

• Semantic HTML markup for proper content structure
• ARIA labels and landmarks for navigation
• Descriptive link text (no "click here" links)
• Alternative text for all meaningful images
• Form labels properly associated with inputs
• Error messages announced to screen readers
• Live regions for dynamic content updates

Visual Design

• High contrast color combinations (minimum 4.5:1 ratio for normal text)
• Color is not the only means of conveying information
• Text can be resized up to 200% without loss of functionality
• Clear visual hierarchy with proper heading structure (h1, h2, h3)
• Consistent navigation and layout across pages
• Sufficient spacing between interactive elements (minimum 44x44 pixels)

Forms and Inputs

• Clear labels for all form fields
• Helpful placeholder text where appropriate
• Inline validation with descriptive error messages
• Error summaries at the top of forms
• Required fields clearly marked
• Autocomplete attributes for common fields

Multimedia

• Text alternatives for images and icons
• Captions for video content (when applicable)
• Transcripts for audio content (when applicable)
• Control over auto-playing content

Mobile Accessibility

• Responsive design that works on all screen sizes
• Touch targets sized appropriately for mobile devices
• Support for mobile screen readers (TalkBack, VoiceOver)
• Pinch-to-zoom enabled
• Orientation support (portrait and landscape)

Content

• Plain language used throughout the site
• Clear and concise instructions
• Consistent terminology
• Expandable sections for complex information
• Table of contents for long documents

4. Assistive Technologies We Support

Paglipat is designed to work with commonly used assistive technologies. We regularly test our Service with the following tools:

Screen Readers

• JAWS (Job Access With Speech) - Windows
• NVDA (NonVisual Desktop Access) - Windows
• VoiceOver - macOS, iOS
• TalkBack - Android
• Narrator - Windows

Browser Compatibility

Our Service is tested and optimized for accessibility with the latest versions of:

• Google Chrome
• Mozilla Firefox
• Safari (macOS and iOS)
• Microsoft Edge

Other Assistive Technologies

• Voice recognition software (Dragon NaturallySpeaking, Voice Control)
• Screen magnification software (ZoomText, Windows Magnifier)
• Switch controls and alternative input devices
• Browser extensions for accessibility (high contrast modes, dyslexia-friendly fonts)

5. Conformance Status

The Web Content Accessibility Guidelines (WCAG) define requirements to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

What This Means

• The majority of our Service meets WCAG 2.1 Level AA standards
• Some areas are still being improved to meet full conformance
• We are committed to achieving full conformance by Q2 2026
• Known issues are documented in Section 6 below

6. Known Limitations and Issues

Despite our best efforts to ensure accessibility, there may be some limitations. Below is a list of known issues we are actively working to address:

Current Known Issues

Third-Party Content

Some content on our Service is provided by third parties (airline websites, booking platforms). While we encourage our partners to maintain accessible platforms, we cannot guarantee the accessibility of third-party content. If you encounter accessibility barriers on a partner site, please:

• Contact the third-party provider directly
• Let us know at [email protected]
• Request assistance from our support team

7. How We Test Accessibility

We take a multi-faceted approach to testing and maintaining accessibility:

Automated Testing

• axe DevTools: Automated accessibility testing in CI/CD pipeline
• Lighthouse: Google's automated accessibility audits
• WAVE: Web accessibility evaluation tool
• Pa11y: Automated testing for WCAG compliance

Manual Testing

• Keyboard-only navigation testing
• Screen reader testing with JAWS, NVDA, and VoiceOver
• Color contrast verification
• Magnification testing (up to 400%)
• Mobile accessibility testing on iOS and Android

User Testing

• Testing with users who have disabilities
• Feedback from accessibility advocates
• Regular user surveys about accessibility

Third-Party Audits

• Last audit: Planned for Q4 2025
• Auditor: To be determined
• Next audit: Scheduled annually

8. Ongoing Improvement Efforts

Accessibility is an ongoing process, not a one-time project. We are committed to continuous improvement:

Our Roadmap

• Q4 2025: Complete third-party accessibility audit
• Q1 2026: Address all high-priority issues from audit
• Q2 2026: Achieve full WCAG 2.1 Level AA conformance
• Q3 2026: Begin work toward WCAG 2.2 compliance
• Ongoing: Regular testing, user feedback, and iterative improvements

Training and Awareness

• All developers receive accessibility training
• Design team follows accessible design principles
• QA team includes accessibility checks in testing protocols
• Regular internal accessibility reviews

9. Feedback and Contact

We welcome your feedback on the accessibility of Paglipat. If you encounter accessibility barriers, have suggestions for improvement, or need assistance, please let us know:

Contact Options

• Email: [email protected]
• Phone: +1 (800) 123-4567 (Mon-Fri, 9 AM - 6 PM EST)
• Support Form: Contact Us
• Mail: Paglipat Accessibility Team, [Address to be added]

When Reporting Issues

To help us address your concern quickly, please include:

• The web page or feature where you encountered the issue
• A description of the problem
• The assistive technology you were using (if applicable)
• Your browser and operating system
• Screenshots or recordings if possible

Our Response

We aim to respond to all accessibility feedback within 2 business days. For urgent accessibility issues, we will prioritize a resolution within 5 business days.

10. Formal Complaints

If you are not satisfied with our response to your accessibility concern, you have the right to file a formal complaint:

United States

• Department of Justice (DOJ): File an ADA Complaint
• Section 508: Section 508 Program

European Union

• Contact your national enforcement body for the Web Accessibility Directive
• European Commission: EU Complaint Form