Accessibility Statement

Conformance target

obfus.link aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, motor, auditory, and cognitive limitations. Conformance is an ongoing effort, not a one-time milestone — we review the site as we ship changes.

Measures we take

• Semantic structure. Each page has a single descriptive <h1>, landmark regions (<main>, <nav>, <footer>), and a logical heading order.
• Skip link. A “Skip to main content” link is the first focusable element on every page, so keyboard users can bypass the header.
• Status announcements. When a tool produces a result or an error, the outcome is announced to screen readers through an ARIA live region (polite for results, assertive for errors) without forcing sighted users' focus to move.
• Labeled controls. Every form control — text inputs, selects, checkboxes — has a programmatic label or accessible name.
• Visible focus. All interactive elements show a high-contrast aquamarine focus ring (2px, offset) so keyboard position is always clear on the dark background.
• Keyboard operability. Tools run from the keyboard (including Ctrl/Cmd+Enter to execute), and the command palette implements ARIA combobox semantics.
• Color contrast. Body, label, and metadata text meet the WCAG AA contrast ratio (at least 4.5:1 for normal text) against the dark background.
• Decorative content is hidden. The ASCII-art wordmark and ornamental sparkles are marked aria-hidden so they are not read aloud or indexed as text.
• Respects motion preferences. Animations are reduced or disabled when the operating system requests reduced motion.

Known limitations

We are honest about where we fall short. As of the date below, we are aware of the following:

• Some advanced tool outputs (for example, the Tree-Shaking Analyzer's Mermaid dependency diagram) are rendered visually and may not be fully described to screen-reader users. The underlying data is also available in text form via the tool's other output fields and the machine-readable /tool/[slug]/json surface.
• obfus.link has not yet undergone a formal third-party accessibility audit. Our conformance claim is based on internal review and automated testing (axe / Lighthouse).
• When advertising is enabled in the future, third-party ad content is outside our direct control; we will require an accessible, consent-based ad experience before turning it on.

If you encounter a barrier that is not listed here, please tell us — see below.

Feedback & contact

If you have trouble using any part of obfus.link, or you want to report an accessibility problem, email accessibility@obfus.link. Please include the page URL, the assistive technology and browser you were using, and a short description of the problem. We aim to acknowledge accessibility reports within five business days.

Assessment approach

We evaluate obfus.link using a combination of automated tooling (axe DevTools and Lighthouse), manual keyboard testing, and screen-reader spot checks. Accessibility is re-reviewed whenever we make significant changes to the interface.