Last Updated: 25 Feb 2026

1. Our Commitment to Accessibility

Phleekz, operated by Walson Global Inc., is committed to ensuring digital accessibility for all users, including individuals with disabilities. We believe that every person deserves equal access to the content, features, and functionality of our platform, regardless of ability or the assistive technology they use.

As a corporation incorporated in Ontario, Canada, we are guided by the principles of the Accessibility for Ontarians with Disabilities Act, 2005 (AODA) and its Integrated Accessibility Standards Regulation (O. Reg. 191/11). We strive to meet or exceed the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA conformance level, as referenced by the AODA and recognized as a global benchmark for web accessibility.

Our goal is to provide an inclusive experience that allows all users to browse, discover, create, and interact with content on Phleekz with dignity and independence.

2. Accessibility Standards We Follow

We design and develop our platform with reference to the following standards and guidelines:

• WCAG 2.1 Level AA — The Web Content Accessibility Guidelines published by the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI). These guidelines define how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, motor, speech, cognitive, language, learning, and neurological disabilities.
• AODA (Accessibility for Ontarians with Disabilities Act) — Ontario's accessibility legislation, which requires organizations to identify, remove, and prevent barriers to accessibility. We comply with the Information and Communications Standards under AODA.
• ARIA (Accessible Rich Internet Applications) — We use WAI-ARIA landmarks and attributes where appropriate to enhance the accessibility of dynamic content and advanced user interface controls.

3. Accessibility Features

Phleekz incorporates the following accessibility features across our platform:

3.1 Navigation and Structure

• Consistent and predictable navigation across all pages.
• Semantic HTML elements (headings, landmarks, lists) to provide a clear document structure for screen readers.
• Skip-to-content links to allow keyboard users to bypass repetitive navigation.
• Logical tab order that follows the visual reading sequence.

3.2 Visual Design

• Colour contrast ratios that meet or exceed WCAG 2.1 AA minimum requirements (4.5:1 for normal text, 3:1 for large text).
• Text can be resized up to 200% without loss of content or functionality.
• Information is not conveyed by colour alone; additional indicators such as icons, labels, or patterns are used.
• Responsive design that adapts to different screen sizes, zoom levels, and orientations.

3.3 Keyboard Accessibility

• All interactive elements (links, buttons, form controls, menus) are operable via keyboard alone.
• Visible focus indicators on all focusable elements.
• No keyboard traps; users can navigate freely to and from all components.

3.4 Media and Content

• Alternative text descriptions for platform-generated images and icons.
• Video player controls that are keyboard-accessible with clearly labelled buttons.
• Support for captions and subtitles on video content where provided by creators.
• No content that flashes more than three times per second in platform-generated UI.

3.5 Forms and Interactive Elements

• All form fields have associated labels and clear instructions.
• Error messages are descriptive and programmatically associated with the relevant input fields.
• ARIA roles and properties are applied to custom interactive components (modals, dropdowns, sliders).

4. Known Limitations

While we strive for full WCAG 2.1 AA compliance, we acknowledge the following known limitations:

• User-Generated Content: Phleekz is a creator-driven platform. Videos, images, and text uploaded by users may not always include alternative text, captions, or audio descriptions. We encourage creators to add descriptive titles, captions, and alt text to their uploads, but we cannot guarantee accessibility compliance for all user-generated content.
• Live and Dynamic Content: Some real-time features (such as live streaming or live chat) may present accessibility challenges. We are actively working to improve the accessibility of these features.
• Legacy Content: Older content published before our current accessibility standards were implemented may not fully conform. We are conducting an ongoing review and remediation of legacy content.
• Complex Interactive Experiences: Certain advanced features such as drag-and-drop interfaces or gesture-based controls may have limited accessibility. Where possible, alternative interaction methods are provided.
• PDF and Downloadable Documents: Some downloadable documents may not be fully accessible. We are working to ensure all new documents meet accessibility standards.

We are continuously working to identify and resolve these limitations. If you encounter an issue not listed here, please let us know using the feedback process described below.

5. Third-Party Content and Services

Phleekz may integrate with or link to third-party services, plugins, embedded content, or payment processors. While we select third-party partners with accessibility in mind, we cannot guarantee that all third-party content or services meet WCAG 2.1 AA standards.

Third-party components used on our platform may include:

• Payment processing services
• Social media embeds and sharing widgets
• Analytics and performance monitoring tools
• Content delivery networks
• Customer support and chat tools

If you experience accessibility barriers with any third-party component on our platform, please contact us so we can work with our partners to address the issue or provide an alternative means of access.

6. Feedback and Accessibility Assistance

We welcome feedback on the accessibility of Phleekz. If you encounter an accessibility barrier, have difficulty using any part of our platform, or have suggestions for improvement, please contact us. Your feedback helps us improve.

6.1 How to Report an Accessibility Issue

When reporting an accessibility issue, please provide as much of the following information as possible to help us investigate and resolve the issue promptly:

• A description of the accessibility barrier you encountered.
• The URL or page where the issue occurred.
• The device, operating system, browser, and assistive technology you were using (e.g., screen reader name and version).
• Any steps to reproduce the issue.
• Your preferred method of contact so we can follow up with you.

6.2 Our Response Commitment

We aim to acknowledge all accessibility feedback within two (2) business days and to provide a substantive response, including a proposed resolution or timeline, within ten (10) business days. If we cannot resolve an issue immediately, we will work with you to provide an alternative means of accessing the information or functionality.

6.3 Accessible Formats

Upon request, we will provide information available on our platform in an accessible format or with appropriate communication support, in accordance with AODA requirements. Please contact us to request accessible formats of any Phleekz content or documentation.

7. Ongoing Efforts

Accessibility is an ongoing effort at Phleekz. We are committed to the following initiatives:

• Regular accessibility audits conducted by internal teams and, where appropriate, third-party accessibility experts.
• Accessibility training for our design, development, and content teams.
• Incorporating accessibility testing into our development and quality assurance processes.
• Encouraging and providing tools for creators to make their content more accessible.
• Monitoring updates to WCAG guidelines and AODA regulations to ensure continued compliance.
• Engaging with users with disabilities to gather feedback and inform our accessibility roadmap.

8. Contact Information