Accessibility Statement Policy

Flinque Accessibility Statement Policy

The short version, so you know where we stand

We want Flinque to be usable by everyone, including people who rely on screen readers, keyboard navigation, high-contrast modes, voice control, or other assistive technologies. We target WCAG 2.1 Level AA as our conformance standard, and we are actively working toward full conformance across our website and platform.

This statement explains what we have done, what we are still working on, where we fall short today, and how to report accessibility issues. We treat accessibility as ongoing work, not a one-time checkbox, and we welcome feedback from users who rely on assistive technologies.

If you encounter a barrier using Flinque, please tell us through the contact page.

1. Our Commitment
2. Conformance Standard
3. Scope of This Statement
4. Supported Assistive Technologies
5. Accessibility Features We Have Implemented
6. Keyboard Navigation
7. Known Limitations
8. Alternative Access Methods
9. Ongoing Improvements
10. Testing and Assessment
11. Third-Party Content
12. Regulatory Compliance
13. Reporting Accessibility Issues
14. Response and Resolution
15. Contact for Accessibility

1. Our Commitment

Flinque is committed to making its influencer marketing platform accessible to people with disabilities. We believe that accessible design benefits everyone and that removing barriers to access is a core part of building quality software.

Specifically, we commit to:

• Building new features with accessibility considered from the start
• Auditing existing features for accessibility barriers and fixing them
• Training our team on accessibility principles and best practices
• Testing our platform with real assistive technologies, not just automated tools
• Responding promptly and respectfully to accessibility feedback
• Being honest about what works, what does not, and what we are working on

We view accessibility as an ongoing responsibility, not a one-time project.

2. Conformance Standard

We target the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our conformance standard. WCAG 2.1 AA is the internationally recognized benchmark for digital accessibility and covers four key principles:

• Perceivable: information and UI components must be presentable in ways users can perceive (text alternatives, captions, adaptable layouts, distinguishable colors)
• Operable: UI components and navigation must be operable (keyboard accessible, sufficient time, no seizure-inducing content, navigable)
• Understandable: information and UI operation must be understandable (readable, predictable, with input assistance)
• Robust: content must be robust enough for assistive technologies (compatible with current and future tools)

We currently describe Flinque as partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that some parts of our platform fully meet the accessibility standard, while others are still being improved.

We review our conformance status regularly and update this statement as we make progress.

3. Scope of This Statement

This accessibility statement covers:

• The Flinque marketing website at flinque.com
• The Flinque customer application at platform.flinque.com
• Product documentation and help content
• Marketing emails and transactional notifications sent by Flinque
• Webinar registration and playback experiences listed on our Upcoming Webinars and On-Demand pages

This statement does not cover third-party content embedded in our platform (such as external videos, third-party analytics dashboards, or partner widgets). Third-party accessibility is the responsibility of the providers, and we request accessibility compliance when selecting vendors.

4. Supported Assistive Technologies

We test and design Flinque to work with the following assistive technologies:

4.1 Screen readers

• NVDA on Windows with Firefox and Chrome
• JAWS on Windows with Chrome and Edge
• VoiceOver on macOS with Safari
• VoiceOver on iOS with Safari
• TalkBack on Android with Chrome

4.2 Keyboard navigation

Full keyboard support using Tab, Shift+Tab, Enter, Space, arrow keys, and Escape.

4.3 Browser zoom and text resizing

Our layouts remain usable at up to 200% zoom without requiring horizontal scrolling on most views.

4.4 Voice control

Voice Control on macOS and Dragon NaturallySpeaking on Windows are supported for most common actions.

4.5 Operating system accessibility features

High contrast modes, reduced motion settings, larger text preferences, and OS-level color filters are respected where technically feasible.

5. Accessibility Features We Have Implemented

Current accessibility features across Flinque include:

• Semantic HTML structure with proper headings, landmarks, and lists
• Alternative text for informative images
• Descriptive link text (avoiding “click here” and similar)
• Form labels associated with input fields
• Error messages linked to the fields they describe
• Color contrast ratios meeting WCAG AA thresholds for text and UI components
• Information conveyed without relying solely on color
• Visible focus indicators for keyboard navigation
• Skip-to-content links on key pages
• Logical reading and tab order
• ARIA attributes where native HTML semantics are insufficient
• Support for prefers-reduced-motion for users sensitive to animation
• Accessible modal dialogs with keyboard focus management
• Language attributes set on page and content elements

New features shipped to production are reviewed against these criteria before release.

6. Keyboard Navigation

Flinque can be navigated entirely with a keyboard. Common keyboard shortcuts:

A visible focus indicator shows which element currently has keyboard focus. If you lose track of focus at any point, pressing Tab returns you to the keyboard navigation flow.

7. Known Limitations

We are honest about where Flinque falls short of our accessibility goals. Current known limitations include:

7.1 Complex data visualizations

Some charts, graphs, and visual audience breakdowns rely on color and shape encoding that is difficult to convey through screen readers. We provide tabular data alternatives where possible but coverage is not yet universal.

7.2 Creator profile media

Creator profile images and video previews sourced from social platforms do not always include descriptive alternative text from the creator’s original post. We display these as supporting content and provide the creator’s bio and metrics as text-based context.

7.3 Older content

Older blog posts and case studies published before our accessibility program began may not meet current standards. We are auditing and remediating legacy content progressively.

7.4 Third-party embeds

Embedded content from third parties (video players, analytics widgets, payment forms) may have accessibility issues outside our direct control. We flag these to providers and seek alternatives where needed.

7.5 PDF documents

Some downloadable PDF reports may not be fully tagged for screen reader navigation. We provide HTML alternatives for critical documentation and are improving PDF tagging across our resource library.

8. Alternative Access Methods

If you cannot access specific content or features due to an accessibility barrier, we will work with you to provide the information another way.

Alternative access options include:

• Emailed text-based summaries of visualizations you cannot perceive
• One-on-one platform walkthroughs with a team member
• Data exports in accessible formats (CSV, accessible PDF)
• Help with account setup, team invitations, and billing via phone or email where self-serve options are not accessible
• Alternative formats for specific documents on request

Request alternative access through our contact page with the category “Accessibility”. We aim to respond to accessibility access requests within 2 business days.

9. Ongoing Improvements

Accessibility improvements are tracked as a continuous workstream. Current priorities include:

• Adding accessible tabular alternatives for all chart and graph views
• Improving ARIA support in complex interactive components (search filters, bulk-action menus, multi-select lists)
• Enhancing keyboard shortcuts for power users
• Adding captions and transcripts to all webinar recordings
• Auditing and remediating legacy blog and case study content
• Improving color contrast in a small number of UI states flagged during recent audits
• Extending mobile accessibility testing coverage

Accessibility improvements are announced in our Release Notes as they ship.

If a specific barrier blocks your work, let us know. User-reported issues are prioritized when they affect real workflows, regardless of the severity under internal audit scoring.

10. Testing and Assessment

Our accessibility testing approach combines automated and manual methods:

10.1 Automated testing

Automated accessibility scans run against new code before it reaches production. Automated tools catch many common issues (missing alt text, incorrect heading order, insufficient contrast) but cannot catch everything.

10.2 Manual testing

Our team regularly tests features with keyboard only, with screen readers, and at high zoom levels. Manual testing catches issues automated tools miss, including logical reading order, meaningful link text, and semantic structure.

10.3 User feedback

User feedback from people who rely on assistive technologies provides the most valuable accessibility input. Real-world use surfaces barriers that laboratory testing misses.

10.4 External audits

We commission periodic external accessibility audits to validate our internal work and identify improvement areas. Audit summaries are available to Enterprise customers on request through our contact page.

11. Third-Party Content

Flinque displays data and content from third-party sources including Instagram, TikTok, YouTube, X, and integration partners. Accessibility of this content is controlled by those third parties, not by Flinque.

Examples of third-party content we surface:

• Creator profile photos and posts pulled from social platforms
• Video content embedded from creator social accounts
• Widgets from tools listed on our Integrations page
• Payment forms powered by Stripe
• Webinar playback from our video hosting partner

Where third-party content creates barriers, we provide text alternatives when possible and flag the issue to the provider. We prefer vendors with strong accessibility practices and consider accessibility when selecting new partners.

12. Regulatory Compliance

Because Flinque is used globally, our accessibility work aligns with multiple regulatory frameworks:

12.1 United States (ADA)

We work to ensure flinque.com and platform.flinque.com meet the accessibility expectations of the Americans with Disabilities Act (ADA) and related guidance from the US Department of Justice.

12.2 European Union

We align our work with the European Accessibility Act (EAA) and EN 301 549, which references WCAG 2.1 for digital services. EU customers expecting full EAA compliance from their suppliers should contact us to discuss specifics.

12.3 United Kingdom

We align with UK accessibility expectations including the Public Sector Bodies Accessibility Regulations for work with UK public sector customers.

12.4 Canada

Our work aligns with the Accessible Canada Act at the federal level and provincial requirements including the Accessibility for Ontarians with Disabilities Act (AODA).

12.5 Other jurisdictions

Where customers operate under other accessibility frameworks (Australian DDA, Japanese JIS X 8341, and similar), we are happy to discuss conformance through our contact page.

13. Reporting Accessibility Issues

If you encounter accessibility barriers using Flinque, we want to know. Your reports help us improve the platform for everyone.

To report an accessibility issue, use our contact page or the Report an Issue page with the category set to “Accessibility”. Useful details include:

• Which page or feature you were using
• What you were trying to do
• What happened or did not happen
• Which assistive technology you use (screen reader, keyboard only, zoom level, voice control)
• Which browser and operating system
• Your preferred contact method for follow-up

You do not need to diagnose the cause or provide technical detail. A plain description of the barrier is enough for our team to investigate.

14. Response and Resolution

Our commitments for accessibility issue handling:

• Acknowledgment: within 2 business days
• Initial response: we confirm we understand the issue, propose workarounds where available, and estimate a timeline for a permanent fix
• Workaround offered: where possible, we offer alternative access while we work on the permanent fix
• Status updates: we keep you informed as the issue progresses
• Resolution notice: we confirm when the fix ships and invite you to verify

Critical barriers that block entire workflows are escalated for priority handling. Lower-severity improvements are scheduled into our accessibility workstream.

If you are not satisfied with our response, you can escalate through the contact page, and we will bring the issue to our leadership team for review.

15. Contact for Accessibility

For accessibility questions, issue reports, or alternative access requests, contact our team. We take accessibility feedback seriously and treat it as a priority.