WolfP2P accessibility
For:All users
No technical knowledge required.Accessibility target—not a conformance claim
Exist.Dev LLC wants WolfP2P's information and browser-based transfer workflow to be usable by people with disabilities. WCAG 2.2 Level AA is the internal accessibility acceptance target for the US English launch.
What the target covers
Accessibility review includes:
- keyboard-only navigation and operation;
- visible, logical focus order;
- headings, labels, instructions, and control names;
- screen-reader announcements for status, progress, errors, reconnection, and completion;
- color contrast and meaning that does not depend on color alone;
- zoom, text spacing, orientation, and reflow;
- reduced-motion preferences;
- file, folder, permission, invitation, consent, and transfer controls;
- tables, links, help content, legal notices, and privacy choices; and
- dispute, opt-out, copyright, security-notice, and privacy-request workflows.
Automated testing is only one part of the review. Keyboard, screen-reader, zoom/reflow, and representative user-flow testing must also be performed before WolfP2P describes a conformance level publicly.
Report an accessibility barrier
Use the Accessibility Barrier Report form to identify the page or task and describe what made it difficult or impossible to use. Naming a browser or assistive technology is optional. A reporter is not asked to submit transferred files, file contents, credentials, live tunnel codes, a diagnosis, or unnecessary personal information.
The report may ask for:
- the page or workflow where the barrier occurred;
- the task the person was trying to complete;
- what happened;
- browser and operating system, if the reporter chooses to provide them;
- assistive technology, if the reporter chooses to provide it;
- an email address for a response; and
- optional non-sensitive diagnostic detail entered as text.
You do not need to provide proof of disability, a diagnosis, medical history, transferred files, filenames, folder contents, tunnel codes, credentials, peer information, or unrelated personal information.
Response and remediation
Exist.Dev will acknowledge an accessibility report within five business days and provide an initial assessment or meaningful status update within 30 calendar days. This is not a promise that every barrier will be corrected within 30 days. Critical barriers will be escalated immediately, and Exist.Dev will provide a reasonable alternative way to complete the task when one is practical.
Accessibility cases are prioritized as follows:
- Critical: prevents a core transfer action, access to privacy or legal rights, or understanding of a serious warning, with no reasonable alternative.
- High: makes a core action possible only with substantial difficulty or assistance.
- Moderate: materially impairs access to content or a secondary function.
- Low: an improvement that does not materially prevent access.
Exist.Dev will attempt to reproduce the issue, assign it to the responsible content or product owner, test the correction using the affected interaction method, communicate the outcome, and add regression coverage where practical.
A minimized accessibility-case record may be retained for no more than three years after closure, unless a documented dispute, investigation, or legal hold requires longer retention. It must not be joined to analytics or advertising profiles.
Reporting a barrier will not reduce access to WolfP2P or affect privacy choices. Submitting a report does not waive the reporter's legal rights, and receiving one is not by itself an admission that Exist.Dev violated a legal requirement.
General contact information is available on the Contact page, and transfer troubleshooting is available in the Help Centre.