Accessibility Statement

Nonkera exists so that everyday tasks — merging a PDF, checking a password, converting a unit — don't require an account, a download, or a payment. We think that promise is incomplete if the site itself can't be operated by someone using a keyboard, a screen reader, or other assistive technology. This page describes the standard we build to, what that looks like in practice, and what to do if something falls short.

The standard we follow

We build Nonkera to follow the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, using Google's web.dev accessibility guidance as a practical reference for what to check and how. This reflects an internal, ongoing review of our own code — not a certified third-party audit — and we'd rather describe our actual effort accurately than claim a level of compliance we haven't had independently verified.

What's implemented across the site

• Keyboard access: every link, button, form field, and drag-and-drop upload area can be reached with Tab and operated with Enter or Space, with a visible focus indicator.
• Skip navigation:every page includes a skip link so keyboard and screen reader users can jump past the repeated header navigation straight to the page's content.
• Screen reader support: interactive elements have real accessible names (not just placeholder text or a visual-only label), and results that appear after an action — like a validation check — are announced automatically.
• Color and contrast:text and the borders of interactive controls meet WCAG's minimum contrast ratios in both light and dark mode, and states like a selected filter are never conveyed by color alone.
• Reduced motion: smooth scrolling and other motion effects are turned off automatically if your operating system is set to reduce motion.
• Semantic structure: pages use proper heading levels and landmark regions (header, navigation, main content, footer) so the page can be navigated by structure, not just top to bottom.

How this shows up in our tools

These aren't just page-level features — they're built into the tools themselves. Drag-and-drop upload areas (used by the PDF and image tools) are real keyboard-operable controls, not just mouse targets. Tools with repeated rows of the same field, like the GPA Calculator's course list, give every row its own accessible name even where the visual design only shows a column header once. For a deeper, more technical walkthrough, see how Nonkera is built for accessibility.

Compatibility

Nonkera is built on standard HTML, CSS, and ARIA, designed to work with modern browsers and standards-based assistive technology such as screen readers, screen magnifiers, and voice control software. We test primarily against current versions of Chrome, Safari, Firefox, and Edge; we haven't formally verified every assistive-technology and browser combination, so if something doesn't behave as expected in yours, we'd genuinely like to know.

Known limitations

Accessibility is an ongoing effort, not a one-time checklist. As we add new tools and features, some may temporarily fall short of this standard before we catch and fix it — and older parts of the site may not yet reflect every improvement we've made elsewhere. If you run into something that doesn't work the way it should, please tell us; it gets fixed directly rather than filed away.

Feedback and contact

If you experience an accessibility barrier anywhere on Nonkera, please reach out through our Contact page with the page or tool involved and what happened. We treat accessibility reports as real bugs.