Accessibility statement

We want everyone to be able to view, edit, fill and sign documents with PDFZyro, whatever their abilities and whatever technology they use. Our goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the whole app: the website, the app you use when signed in, the signing pages people open from an email, and shared links.

Status: PDFZyro partially conforms to WCAG 2.2 AA. Most of the app meets the guidelines; the parts that don't yet are listed under Known limitations.

• Keyboard. The tools are designed to be used with a keyboard alone, with a visible focus outline and a “Skip to content” link on every page. Each mode has shortcuts (zoom, tools, undo, save…); press ? to list them. They are also on the Help page.
• Screen readers. Pages use headings and landmarks, buttons and fields have labels, menus and dialogs follow the standard keyboard patterns, and progress, errors and results are announced.
• Alternatives to dragging. In Organize pages, pages can be moved with Move left, Move right and Move to position…, or Alt+← / →. Files to merge can be reordered with arrow buttons, and a form's tab order with buttons or Alt+↑ / ↓. Comments, stamps, signatures, form fields and redaction boxes can be placed with Enter (in the middle of the page), moved with the arrow keys and resized with Alt+arrow keys.
• Signatures without drawing. You can type your name in a handwriting style or upload a picture of your signature instead of drawing it. People signing a document you sent are guided from field to field with Start and Next, and fill in real form controls.
• Not by colour alone. Compare marks differences with colour and a pattern (struck through, underlined, dashed or dotted frames, stripes) and explains them in a legend and a list.
• Light and dark mode. Choose light, dark or your system's setting. Text is designed to have a contrast of at least 4.5:1 in both.
• Zoom and small screens. Pages work on phones and tablets and reflow down to 320 CSS pixels wide (400% zoom) without scrolling sideways, except the PDF pages themselves and wide tables, which scroll inside their own box. Buttons and links are at least 24 by 24 pixels.
• Reduced motion. If your device asks for reduced motion, PDFZyro turns off animations. Nothing flashes, and no information depends on movement.
• No time pressure. Your work has no time limit, and the editors keep unsaved changes as a draft. Some limits exist only for security: you are asked to sign in again after a while, a signing session ends and is restarted by opening the email link again, download links work for a few minutes (download again to get a new one), and after several wrong passwords or codes you wait 15 minutes. We don't use CAPTCHAs.
• Accessible forms. Forms you build in PDFZyro can give every field a tooltip that screen readers announce in PDF readers, and a tab order you choose.

• Automated checks with axe-core (WCAG 2.0, 2.1 and 2.2 A and AA rules) on about 40 pages, including every document mode, the signing pages and shared links, in light and dark mode, on a desktop window and a 375-pixel phone screen, together with a check for sideways scrolling.
• Manual checks: keyboard-only use of each tool, focus order and visibility, zoom and narrow screens (375 and 320 pixels wide), and the contrast of the colour themes.
• Every new feature is checked with the keyboard and on a phone-sized screen before release.

We have not yet finished a full test with screen readers such as NVDA, JAWS, VoiceOver and TalkBack. It is planned, and this statement will be updated with the results.

• The PDFs themselves. How accessible a document is depends on how it was made: its tags, reading order and descriptions of pictures. PDFZyro shows documents as they are; it doesn't yet check or repair a PDF's accessibility tags, and edits may not update them.
• The page view. PDF pages are drawn as pictures with the document's text laid over them (pdf.js), so text can be read, searched and selected. Screen readers read that text in the order it is stored in the file, which may differ from the visual layout. Scanned pages have no text until you make them searchable (OCR).
• Placing things on a page (comments, form fields, signatures, redaction boxes, edits) is visual by nature. The keyboard alternatives above work, but choosing an exact spot is easiest with a mouse, pen or finger.
• Compare's Visual view shows the two documents in red and blue. Use the list of differences, which describes every change in words.
• Recognized text and AI answers can contain mistakes. Files converted to Word, Excel or PowerPoint get headings, lists and tables where PDFZyro can recognize them, but should be checked.
• Pages from other companies: checkout and the billing portal are provided by our payment provider, Stripe, and how emails look depends on your email app.

If something in PDFZyro is hard or impossible for you to use, please tell us: email indusmedline@gmail.com. When you're signed in you can also use Help → Contact support. Tell us the page, what you were trying to do, and the browser and any assistive technology you use.

We aim to reply within 5 working days, and we will help you get the task done another way while we fix the problem.

PDFZyro is a web app built with HTML, CSS, JavaScript and WAI-ARIA. It is designed for recent versions of Chrome, Edge, Firefox and Safari, with the assistive technologies that work with them.