Sharkforce Inc. wants everyone to be able to send, read, and sign documents with Docshark. This statement explains the accessibility standard we target, what we have done so far, the limitations we know about, and how to ask for help or an alternative way to complete a task.
1. Our commitment
We design and build Docshark to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as our target standard. Accessibility is an ongoing effort rather than a one-time project: we review new features against this standard and work to fix issues as we find them or as they are reported to us. We treat accessibility as part of building a product that works for the widest possible range of people and assistive technologies.
2. What we've done
We build Docshark so that interactive elements can be reached and operated with a keyboard, with visible focus indicators that show where you are on the page. We use semantic HTML and ARIA labels so that screen readers can announce buttons, links, form fields, and document controls, and we aim for sufficient color contrast on text and essential interface elements. We provide right-to-left (RTL) layout and Arabic-language support across the product and these legal pages. These are the practices we follow rather than a guarantee that every screen meets them; where something falls short, the limitations in section 4 and the help in section 5 apply.
3. Signing accessibility
The signing flow is built so that a signer can review the document, provide consent, and complete signing using only a keyboard and a screen reader. If you are a sender, please allow recipients extra time to complete a document where they may be using assistive technology, and be ready to make alternative arrangements on request - for example, sending the document by another method or providing an accessible copy. If a signer cannot complete signing for any accessibility reason, they can contact the sender, and either party can contact us for help.
4. Known limitations
Some content is harder to make fully accessible. Certain third-party or embedded content (for example, documents that customers upload or external services we integrate) is outside our direct control and may not always meet the same standard. The decorative animated hero on our marketing pages is presentational only; it has a non-interactive, static fallback and conveys no information needed to use Docshark. We note these limitations so you know what to expect and so you can ask for an alternative if something blocks you.
5. Feedback and accommodations
If you encounter an accessibility barrier, or you need an accommodation or an alternative way to complete a task, email us at support@doc-shark.com. Please tell us the page or document, what you were trying to do, and the assistive technology or browser you were using, if you can. We aim to respond promptly, help you complete the task, and provide an alternative way to do so where needed.
6. Ongoing improvement
We keep improving accessibility as the product changes. We use feedback and our own testing to prioritize fixes, and we update this statement as our practices and the product evolve. If a barrier is not yet resolved, we will work with you to find a workable alternative in the meantime.