Accessibility Statement

Conformance status

We target Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for our public web properties and Apple Human Interface Guidelines / Material Design 3 accessibility patterns for the mobile and desktop applications. As of the date below, OpenDrop's public web properties are partially conformant with WCAG 2.1 Level AA, meaning the majority of the content meets the standard, but some content does not yet fully conform.

What works well today

Web

• Semantic HTML5 throughout, proper landmarks (<nav>, <main>, <article>, <footer>) and heading hierarchy.
• Color palette meets WCAG 2.1 contrast ratio AA on body text (≥ 4.5:1) and large headings (≥ 3:1) across the canonical OpenDrop Brand palette (cerulean blue on dark navy).
• Keyboard navigation works on every interactive element; focus indicators are visible.
• All icons have alt text or aria-label; decorative-only images use alt="".
• Forms have programmatic <label> associations and required-field indicators.
• Cookie banner is reachable via Tab, is dismissible via Accept or Reject, and respects browser Global Privacy Control (GPC), see the Privacy Policy.
• Pages reflow at 320 px viewport width without horizontal scrolling.
• prefers-reduced-motion is honored where motion is used.

Mobile (iOS / Android)

• VoiceOver and TalkBack labels on every interactive control; logical reading order.
• Dynamic Type (iOS) and system Font Size / Display Size (Android) cause UI text to scale to user-set sizes; layout reflows.
• Reduce Motion (iOS) disables card animations and transition transforms.
• Color is never the only carrier of meaning, status icons pair color with shape/text.
• Tap targets are at least 44×44 pt (iOS) / 48×48 dp (Android).
• The QR-code pairing screen offers a visible text fallback URL for users who can't see the camera viewfinder.

Desktop

• Qt accessibility bridge enables screen-reader navigation on Windows (NVDA, JAWS), macOS (VoiceOver), and Linux (Orca via AT-SPI).
• Full keyboard navigation, every action that can be done with the mouse can also be done with the keyboard.
• OS-level "Reduce motion" / "Reduce transparency" / dark-mode settings are honored.
• Themed color palettes include high-contrast options.

Known gaps we are working on

• Blog post code blocks on nfdgames.com don't carry an aria-label announcing the language; this can make code samples harder for screen-reader users to skim.Web
• Marketing-page coverflow carousel (the 3D screenshot stack on the OpenDrop landing page) is decorative; its underlying screenshots are reachable but the carousel controls are not keyboard-focusable. We plan to add focusable previous/next buttons and a pause-rotation control.Web
• Cupertino dialogs on iOS 16 can occasionally announce stale focus after dismissal. The 1.0 build mitigates this by re-focusing the previously-active element; it is not perfect.iOS
• File-thumbnail grid on mobile announces "image" rather than a more descriptive label. We will add filename + size announcements.Mobile
• Drag-and-drop on desktop requires a pointing device for some operations (e.g., reordering tabs). Keyboard equivalents are planned for a follow-up release.Desktop
• Custom color-palette editor on desktop does not yet preview contrast ratios for the colors you choose. Until that ships, please prefer a built-in palette if you rely on contrast.Desktop

Standards we follow

• WCAG 2.1 Level AA for web. w3.org/TR/WCAG21
• WAI-ARIA 1.2 for ARIA roles, states, and properties. w3.org/TR/wai-aria-1.2
• Apple Human Interface Guidelines, Accessibility for iOS and macOS. developer.apple.com
• Material Design 3, Accessibility for Android. m3.material.io
• EN 301 549 (the European Accessibility Act baseline standard) for the EU, we track its requirements as we add features.
• Section 508 of the U.S. Rehabilitation Act. We are not a federal contractor, but our targets align with the 508 refresh that adopted WCAG 2.0 AA.

How to request an accommodation or report a barrier

If you encounter an accessibility barrier, anywhere in the OpenDrop apps, on nfdgames.com, in our policy pages, or in our purchase flow, we want to hear about it. Please contact:

• Email: support@nfdgames.com with the subject line "Accessibility."
• Support form: nfdgames.com/OpenDrop/support.html, pick "Accessibility" as the topic.
• What to include: the platform you're on (browser + OS, or iOS/Android version), the URL or screen, what assistive technology you use (screen reader, magnifier, switch control, etc.), and what behavior you expected.

Our commitment: we acknowledge accessibility reports within 3 business days. Critical barriers that prevent access to a paid feature you have purchased are prioritized for a same-week fix.

If we are unable to resolve a barrier, you may also reach out to your local accessibility-rights authority, for example, in the EU under the Web Accessibility Directive 2016/2102, or in the United States under the Americans with Disabilities Act (ADA).

How this statement was prepared

This statement was prepared on 2026-06-04 based on a self-evaluation by NFDGames LLC. The evaluation methods included automated testing with axe DevTools and Apple's Accessibility Inspector, manual keyboard navigation, screen-reader spot-checks with VoiceOver (macOS, iOS) and NVDA (Windows), and color-contrast verification with the WebAIM Contrast Checker. The mobile and desktop apps are also exercised against the OS-level accessibility scanner on every build.

This statement will be reviewed at least once per year, and after any major feature release.