Help

Accessibility statement

Last updated

Moving a file should be easy for everyone. This statement covers this website and the Dragy apps, what we do to make them accessible, where we know we fall short, and how to tell us about a barrier.

The short version

  • We aim to meet WCAG 2.2 at level AA across the website and apps.
  • You can use Dragy with a keyboard and a screen reader, and you never have to drag anything.
  • Dragy respects reduced-motion and light/dark preferences.
  • We haven’t yet had an independent audit; we list the limitations we know about.
  • Found a barrier? Email [email protected].

1. Our commitment

Nexlla Creative Agency wants Dragy to be usable by people with disabilities, including people who are blind or have low vision, are deaf or hard of hearing, or have motor, cognitive or vestibular disabilities. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, for this website, the web app and the desktop and mobile apps (which share the web app’s interface).

2. What we do

  • No drag required. Despite the name, every action has a button: choose files with a standard file picker, share from other apps, or on desktop use the Dragy folder (and, on Windows, Explorer’s “Send to” menu).
  • Keyboard. All controls are reachable and operable with a keyboard, focus is visible, and the site has a “Skip to content” link. Menus and dialogs close with Escape.
  • Screen readers. We use semantic HTML, landmarks, headings and labelled controls; decorative graphics are hidden from assistive technology; transfer progress and notifications are announced through live regions.
  • Motion. Animations are reduced when your system asks for reduced motion, and the app has its own Reduce motion setting. Decorative animations pause when off screen.
  • Colour and contrast. Light and dark themes follow your system or your choice; we design text and controls to meet AA contrast, and never use colour alone to convey status.
  • Zoom and reflow. Pages reflow to a single column on small screens and at high zoom without horizontal scrolling, and text can be resized.
  • Alternatives to visual checks. Connection codes can be typed instead of scanning a QR code. Verification emoji are real text, not images, so screen readers can read them.
  • Plain language. We try to write clearly, including in our legal pages, which all start with a short summary.

3. Conformance status

Based on our own testing, Dragy is partially conformant with WCAG 2.2 level AA: some parts may not yet fully meet the standard. We have not had an independent accessibility audit and do not claim certification.

4. Known limitations

  • Verification emoji are read out by screen readers using the platform’s emoji names, which vary between systems and can be long. Comparing them with someone else may take more effort; you can instead connect devices with a code, or sign both devices in to your account.
  • Sign-in by QR code needs a camera. You can always sign in with your email and password instead.
  • Drag and drop onto devices is not available to keyboard users as a drag gesture, but the same action is available through buttons.
  • Native file dialogs and operating-system prompts (such as save locations or security warnings) are controlled by your browser or operating system.
  • The macOS app and the iPhone and iPad app are not yet released and have not been assessed.

We are working on these and will update this page as we fix them. To confirm

5. Compatibility

Dragy is designed to work with current versions of Chrome, Edge, Firefox and Safari, and with the screen readers built into Windows (Narrator; NVDA and JAWS are also widely used), macOS and iOS (VoiceOver) and Android (TalkBack). It relies on HTML, CSS, JavaScript and WAI-ARIA. Older browsers and assistive technologies may not work as well.

6. Feedback and help

If you find a barrier, or need information from this website in another format, email [email protected] and tell us the page or screen, what you were trying to do, and the device, browser and assistive technology you use. We aim to reply within 5 business days. To confirm

If you are not satisfied with our response, you may contact the consumer or equality authority in your country.

7. How we assessed Dragy

We assessed Dragy ourselves, using automated checks, manual keyboard testing, screen-reader spot checks and testing at different zoom levels and screen widths, while designing and building it. This statement was prepared on October 20, 2026.

Accessibility feedback: [email protected].