Accessibility.

Papr Tools aims to make its public website and document tools usable by people with diverse visual, auditory, physical, speech, cognitive, language, learning, and neurological needs. Accessibility is treated as an ongoing product and engineering responsibility.

Current measures include:

• semantic landmarks, headings, lists, tables, labels, and native controls where practical;
• keyboard access and visible focus indicators for interactive website controls;
• descriptive page titles, link text, form labels, and image alternatives;
• responsive layouts and text that reflows across supported viewport sizes;
• contrast-conscious colors and controls that do not rely on color alone;
• reduced-motion support for users who request it through operating-system settings;
• minimum practical target sizing for primary controls; and
• automated type, build, and rendered-interface checks during development.

The accessibility of a PDF depends substantially on the source file. Tags, reading order, headings, form-field names, language metadata, text alternatives, and document structure may be missing before a file reaches Papr Tools. The current browser Tools can edit supported fields and page content but do not remediate every accessibility defect or certify a PDF as conforming to PDF/UA or WCAG.

Browser-native PDF viewers and print dialogs are controlled by the browser and operating system. Their accessibility varies. For critical documents, review the exported PDF with appropriate accessibility tools and the intended assistive technology.

• The signature drawing canvas requires pointer input and may not provide an equivalent way to create every form of signature.
• Drag-and-drop page reordering may be easier with a pointer; move-left and move-right controls provide a keyboard-operable alternative.
• PDF previews are displayed through the browser’s PDF capability and may expose content differently across browsers and assistive technologies.
• Complex or image-only PDFs may require OCR, tags, labels, or remediation outside the current browser Tools.
• Government and commerce websites opened through external links are outside Papr Tools' accessibility control.

Papr Tools is designed for current versions of major browsers and operating systems. Older browsers, embedded web views, browser extensions, custom accessibility settings, and unusual PDF implementations can affect behavior. The iPhone app also depends on supported iOS accessibility and device features.

Accessibility review should combine automated analysis, keyboard testing, zoom and reflow checks, screen-reader review, reduced-motion review, and testing with representative documents. Automated tools alone cannot establish conformance.

Papr Tools prioritizes barriers that prevent task completion, obscure critical disclosures, block navigation, or make document actions unavailable. Material product changes should be reviewed against the same accessibility targets.

Use the current method on the Contact page to describe an accessibility barrier. Helpful details include the page or feature, device, operating system, browser, assistive technology, expected result, and steps to reproduce.

Do not include a private PDF or sensitive identifier in the initial report. A non-sensitive example or description is safer.

Papr Tools links to government agencies and may integrate Apple, Shopify, payment, shipping, fulfillment, and support providers. Their accessibility is governed by their own products and policies. Papr Tools welcomes reports about a link that prevents access to an official source so the directory entry can be reviewed.

This statement may be updated as accessibility work, product features, providers, or applicable standards change. The “Last updated” date identifies the current version.