creatorvalet
Files Convert, compress and reshape files — without uploading them anywhere. Metadata See what your files quietly carry, then strip exactly what you choose. Text & data Formatters, converters, and the character-encoding fixes nobody else gets right. Publishing Check how your pages read to crawlers, to people, and to language models. Codes Barcodes, QR and identifiers that keep working after you publish them. Characters Find the character you can draw but cannot name — and the font you cannot place.

Accessibility statement

Accessibility at CreatorValet

CreatorValet aims to make its pages and browser tools usable with a keyboard, assistive technology, zoom, reduced motion, and narrow screens. The target is WCAG 2.2 Level AA. This page is a dated account of the work and its limits, not a certification of conformance.

What the current implementation provides

  • A skip link and semantic header, navigation, main, footer, heading, form, and status structures.
  • Visible keyboard focus and native buttons, links, labels, inputs, and file pickers wherever the browser provides the control.
  • Text and controls designed for AA contrast, with light and dark themes and no meaning carried only by color.
  • Responsive pages reviewed at 375 CSS pixels, with tap alternatives for drag-and-drop actions.
  • A reduced-motion path for animation and progress effects.
  • Tool states and errors that remain in the document instead of existing only as visual decoration.

How it is checked

Every publication build checks the generated HTML, headings, forms, labels, loaded resources, JavaScript and CSS budgets, reduced-motion branches, and mobile overflow. Browser tests run live tool flows in Chromium and WebKit at desktop and mobile sizes. Representative pages are also reviewed manually with keyboard navigation, zoom, and their browser-native file controls.

Automated tests and a Lighthouse score can find particular defects. Neither establishes WCAG conformance, and neither replaces testing by people who use assistive technology. No independent full-site WCAG audit has been completed.

Known limitations

  • Browser-native PDF previews and file pickers differ by browser and operating system.
  • Canvas-based image editing, cropping, drawing, and visual comparison can require sight or precise pointing. An equivalent nonvisual workflow is not available for every editor.
  • A generated PDF, image, spreadsheet, or document inherits limitations in the source. These utilities do not automatically remediate a document for accessibility.
  • Very large local files can exhaust a browser tab’s memory and cause the browser to reload without a useful assistive error message.
  • There is not yet a public support inbox or public issue tracker. That is a real reporting gap; an address will be listed here only after it exists and can be monitored.

Reviewing a tool for your organization

Start with the exact workflow your users need, at the zoom level and with the input device they use. Confirm that the file picker, settings, result, error recovery, and download are all reachable. The institutional review page collects the related processing, installation, account, offline, and accessibility boundaries.

Last revised .