Accessibility
Official forms are exactly the documents where being unable to complete something yourself costs the most — in time, in privacy, and in having to ask someone else to do it for you. That is the reason accessibility matters here specifically, rather than as a general principle.
Novus PDF Studio targets WCAG 2.2 Level AA.We test with keyboard-only operation, and our end-to-end suite runs axe-core against every one of our standard pages, plus one representative tool page and one representative article — the route shapes that back their peers — scoped to the WCAG 2.2 A and AA rules. Any finding at serious or critical impact fails the build, with no exception list. When that scan first ran it found four such defects, and they were fixed rather than recorded. The suite also checks structural basics on every route: a single h1, a main landmark, and working skip-link focus. What that does not mean is conformance. Automated rules catch roughly a third of WCAG, and none of them can tell you whether a label reads sensibly or whether a workflow makes sense without sight. The sections below describe both what we do deliver and where it currently falls short.
Version 1.2 · Effective August 7, 2026 · Last updated August 25, 2026
Every tool, form control and navigation element is reachable and operable by keyboard. A skip link at the top of each page jumps straight past the navigation to the main content. Filling a form is deliberately Tab-driven: after you complete a field, focus moves to the next empty one, so a simple form can be finished without touching a pointer at all.
Pages use real landmarks and a single, correct heading level per page. Controls carry accessible names rather than relying on an icon alone, and status changes — a scan completing, an export finishing, a search returning results — are announced through live regions instead of appearing silently.
Body text and interactive controls are designed to meet WCAG 2.2 AA contrast. Colour is never the only way information is conveyed: states that use colour also carry text or an icon. Both light and dark themes are held to the same standard, and the theme follows your system preference by default.
Interactive targets are sized for touch as well as a mouse, and the editor's canvas gestures are forgiving of small movements — a short press is treated as a click rather than a failed drag, which matters a great deal for anyone with a tremor.
The site uses small entrance and hover animations. All of them respect the prefers-reduced-motion setting: turn reduced motion on in your operating system and transforms are removed rather than merely shortened. Nothing on the site auto-plays, flashes, or moves without you initiating it.
These are the places where the experience is currently worse, listed so you can decide whether the tool will work for your task before you invest time in it.
Placing a field at an exact spot on a page is a spatial task. Numeric X and Y controls exist for every element so placement never requires dragging, but reviewing an unfamiliar document's layout without sight remains genuinely difficult, and we are not going to pretend otherwise.
A PDF that is a photograph of paper initially has nothing for a screen reader or field detection to read. The local OCR tool can add a searchable text overlay in English, French, or Spanish, with low-confidence results held for review. It does not create form fields, a tagged-PDF structure tree, or a guarantee of correct reading order, so OCR output still needs inspection.
Exports preserve real, selectable text wherever the source allows it, which is the single biggest factor in whether a PDF can be read aloud. They do not currently carry a full tagged-PDF structure tree, so reading order in a complex export may not be ideal.
Advertising is served by Adsterra and its markup is outside our control. It is consent-gated where required and can be disabled everywhere from cookie preferences; an active Global Privacy Control signal also blocks it.
If something here blocked you, we want to know — a specific report is far more useful than an audit score. Email pdf@novusstreamsolutions.com with the page, what you were trying to do, and the assistive technology and browser you were using. Accessibility reports are treated as bugs, not feature requests, and aim for a first reply within one business day.
You can also reach us through the contact page.