PDFLab
Private

Accessibility

Accessibility Statement

Last updated: April 2025

Our commitment

Actwise is committed to ensuring that PDF Lab is accessible to the widest possible audience, regardless of ability or technology. We are actively working towards conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. This page describes our current status, known limitations, and how to contact us with accessibility feedback.

1. Measures to support accessibility

Actwise takes the following measures to ensure accessibility of PDF Lab:

  • Include accessibility as part of our development and design review process.
  • Test UI components with keyboard-only navigation and screen-reader software during development.
  • Assign clear remediation owners and timelines when accessibility issues are reported.
  • Respond to all accessibility feedback received at legal@act-wise.com within 14 business days.

2. Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility. WCAG 2.1 has three conformance levels: A, AA, and AAA. PDF Lab is partially conformant with WCAG 2.1 Level AA.

“Partially conformant” means that some parts of the content do not yet fully conform to the accessibility standard. We are actively working to address outstanding issues across all tools on the site.

3. Technical specifications

PDF Lab relies on the following technologies for conformance with WCAG 2.1:

  • HTML5 — semantic markup is used throughout, with appropriate landmark roles (main, nav, footer, etc.).
  • WAI-ARIA — ARIA attributes are used to label interactive controls, announce dynamic content updates, and communicate state changes (such as file-processing progress) to assistive technologies.
  • CSS — focus indicators are preserved and enhanced. All interactive elements have a visible :focus-visible outline. Color contrast for primary text against the page background meets the WCAG AA 4.5:1 ratio requirement.
  • JavaScript — used for all PDF processing, but designed to degrade gracefully. Key interactive elements (file inputs, buttons, tool controls) are functional via keyboard alone.

4. Keyboard and screen-reader support

PDF Lab is designed to be fully operable using a keyboard alone:

  • Tab / Shift+Tab moves focus between interactive elements in logical document order.
  • Enter / Space activates buttons and links.
  • File inputs are accessible via keyboard; you can activate the file picker with Enter/Space and navigate the resulting system dialog normally.
  • Processing status and error messages are announced using aria-live regions so screen-reader users receive timely feedback without needing to poll the page.

PDF Lab has been manually tested with NVDA + Firefox and VoiceOver + Safari during development.

5. Known limitations

Despite our efforts, the following known limitations exist. We are working to fix them:

  • PDF preview canvases. The in-browser PDF page previews rendered by pdf.js are bitmap canvases. They do not expose the text layer to screen readers. We are investigating adding text-layer overlays and accessible labels to preview regions.
  • Drag-and-drop page reordering. The visual drag-and-drop interface for the Organize Pages tool is not fully operable by keyboard alone. We are adding keyboard-driven move controls (up/down arrow or explicit “Move up / Move down” buttons) as a full alternative.
  • Signature drawing canvas. The hand-drawn signature pad in the Sign PDF tool is a canvas element and is not accessible to assistive technologies. The “Type signature” tab provides a fully accessible text-based alternative.
  • Redaction crop tool. The mouse-driven redaction box drawing interface requires pointer input. A coordinate-input fallback (specifying redaction regions by entering page, x, y, width, height values) is planned.
  • Color contrast in some secondary text. Certain helper labels and placeholder texts in form fields may not meet the 4.5:1 contrast ratio at all viewport sizes. We are auditing and correcting these.

6. Feedback and contact

We welcome your feedback on the accessibility of PDF Lab. If you experience an accessibility barrier, or if you need content in a different format or an alternative means of accessing a tool, please let us know:

Actwise — Accessibility

Email: legal@act-wise.com
Please include “Accessibility” in the subject line, describe the barrier you encountered, and specify the URL of the page or tool affected.

We aim to respond to all accessibility feedback within 14 business days and to provide a resolution or a reasonable accommodation where technically feasible.

7. Formal complaints

If you are not satisfied with our response to an accessibility concern, you may escalate your complaint using the following routes:

  • United States users: The U.S. Department of Justice Civil Rights Division handles complaints about websites that are covered by the Americans with Disabilities Act (ADA). Information is available at www.ada.gov.
  • EU / EEA users: The EU Web Accessibility Directive (Directive 2016/2102) establishes enforcement bodies in each EU Member State. You can contact the accessibility enforcement body in your country. A list of national enforcement bodies is maintained by the European Commission at ec.europa.eu. Note: the EU Web Accessibility Directive applies primarily to public-sector bodies; PDF Lab is a private-sector service, but we nonetheless commit to the same standards.
  • UK users: The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Equality Act 2010. More information is available at equalityhumanrights.com.

8. Assessment approach

Actwise assessed the accessibility of PDF Lab using the following approaches:

  • Self-evaluation — manual keyboard-navigation testing and screen-reader checks performed by Actwise developers.
  • Automated tooling — Lighthouse and axe DevTools are used during development builds to identify common WCAG violations.

9. Updates to this statement

This Accessibility Statement will be reviewed and updated at least annually, and whenever significant changes are made to the site. The “Last updated” date at the top of this page reflects the most recent revision.