Accessibility Statement

Our commitment

Privacy tools should be usable by everyone, including people who rely on assistive technology. SecretPNG (secretpng.com), operated by SecretPNG (legal entity to be confirmed before launch), is committed to making both its public informational pages and its secure workspace accessible.

This statement describes the standard we target, what we have implemented, where we know we fall short during beta, and how to tell us about barriers you encounter.

Conformance target: WCAG 2.2 Level AA

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across the site, including the tools in the secure workspace. WCAG is the widely adopted international standard for web accessibility, covering perceivability, operability, understandability, and robustness.

SecretPNG is in beta, and we describe our current status as partially conformant: most content and functionality meets the target, but known gaps remain (listed below) and others may exist that we have not yet found.

Keyboard operability

The site and tools are designed to be operable by keyboard alone: interactive controls are reachable in a logical tab order, focus is visible, and tool workflows — selecting files, entering passwords, running operations, copying results — can be completed without a pointing device. If you find a control that traps focus or cannot be reached or activated by keyboard, please report it; we treat keyboard traps as high-priority defects.

Screen reader support

We use semantic HTML and ARIA where appropriate so that screen readers can identify controls, labels, and structure. Dynamic events that matter — operation progress, completion, errors, and copy-to-clipboard confirmations — are announced via live regions rather than communicated by visual change alone.

Visual design

We aim for text and interactive elements to meet WCAG 2.2 AA contrast requirements, for layouts to remain usable at 200% zoom and in reflowed narrow viewports, and for information to never be conveyed by color alone. Motion is kept minimal, and we respect the operating system's reduced-motion preference where animations exist.

Forms, errors, and time limits

Form fields (such as the contact form and tool inputs) have programmatically associated labels, and error messages identify the affected field in text. Where the service imposes time-based behavior — most notably secret links that expire — the timing is a user-chosen security property of the content, not an interface time limit; the interfaces themselves do not impose completion deadlines on you.

Known limitations during beta

We are candid that beta software has rough edges. Known and likely gap areas include:

• Some complex tool interfaces (for example, multi-step redaction and vault workflows) are still being refined for screen-reader ergonomics, and announcement wording may be inconsistent in places.
• Progress feedback for long-running local operations on very large files may be under-announced to assistive technology.
• Some third-party content on public pages (such as ads served after consent) is rendered by external providers and may not meet our target; we cannot fully control its markup.
• Documentation and guide content is being audited iteratively; older pages may have heading-structure or link-text issues until that pass completes.

Third-party content

Public informational pages may include advertising and analytics components from third parties (only after consent, as described in our Cookie Policy). We do not control the internal accessibility of third-party ad content. The secure workspace contains no third-party scripts at all, which also means its accessibility is fully within our control — and our responsibility.

How we assess accessibility

Our approach combines automated checks in development, manual keyboard-only passes over tool workflows, and screen-reader spot checks on major flows. We prioritize fixes by user impact: blockers to completing a tool workflow come first, then announcement and labeling quality, then polish.

Compatibility

SecretPNG is built for current versions of major evergreen browsers on desktop and mobile. The tools rely on modern browser cryptography and file APIs; very old browsers may not run them at all. We test against current browser and screen-reader combinations in wide use, but cannot guarantee every pairing.

Report a barrier

If you encounter an accessibility barrier anywhere on SecretPNG, email support@secretpng.com. It helps to include the page or tool, what you were trying to do, your browser and assistive technology, and what went wrong — but an incomplete report is far better than none.

We read every report. Accessibility fixes are triaged alongside security and correctness issues, and barriers that block completing a tool workflow are treated as defects, not enhancement requests.

Ongoing work

Accessibility is not a one-time audit for us; it is part of how the beta matures toward launch. We will update this statement as gaps are closed and as new features ship, and we will keep the known-limitations list honest rather than aspirational.

Draft status

This document is a draft prepared for launch and requires review by qualified legal counsel before public launch.