Accessibility Statement
Tool Nectar is a set of tools people rely on to get real work done, so we want it to be usable regardless of how you navigate the web — with a mouse, a keyboard, a screen reader, or assistive technology.
Our Commitment
We build toward WCAG 2.1 AA as an ongoing effort, not a one-time checklist.
Our Approach
We build toward the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as our target standard. This is an ongoing effort rather than a one-time checklist — every new tool and page we ship is checked for keyboard operability, form labeling, and readable contrast before it goes live, and we continue improving pages that were built earlier.
What's In Place Today
- Semantic HTML structure (headings, landmarks, lists) on tool and content pages.
- Keyboard-operable navigation, including the mobile menu and header search.
- Labeled form fields on calculator inputs, with descriptive input names rather than placeholder-only labels.
- A breadcrumb trail with
aria-labelandaria-currentfor orientation on every calculator and tool page. - Text that resizes with your browser's zoom/font-size settings rather than being locked to a fixed pixel layout.
Known Limitations
We're not claiming full, verified conformance yet. Areas we know need continued work include: some decorative icons that should be marked aria-hidden but aren't yet; color-contrast ratios on a handful of older pages that haven't been individually audited against WCAG AA's 4.5:1 text ratio; and drag-and-drop file upload zones (used on PDF tools) that need a fully equivalent keyboard/file-picker path verified across all tools, not just some. We are working through these systematically rather than all at once.
Compatibility
The site is built to work with recent versions of major browsers (Chrome, Firefox, Safari, Edge) and their built-in accessibility features, and with common screen readers such as NVDA, JAWS, and VoiceOver. If you encounter a specific incompatibility, please tell us the browser/assistive-technology combination — that detail helps us reproduce and fix it.
Reporting an Accessibility Barrier
If you run into something on this site that's difficult or impossible to use with assistive technology, please tell us. Include the page URL, what you were trying to do, and the browser/screen reader/device you were using if possible. We treat accessibility reports as bugs, not feature requests, and prioritize them accordingly.
Found an Accessibility Barrier?
Tell us the page, what you were trying to do, and your browser/assistive-technology combination.