JSON Editor

Accessibility Statement

Last updated: July 22, 2026

Vektosys is committed to making JSON Editor (https://jsoneditor.vektosys.com) usable by as many people as possible, including people who rely on assistive technologies. This statement describes our goals, known limitations, and how to request help.

1. Conformance goals

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA where practicable for a developer tooling product. Our design targets include:

  • Semantic HTML structure and meaningful headings
  • Keyboard-operable navigation and controls
  • Visible focus indicators
  • Sufficient color contrast for text and interactive elements
  • Text alternatives or labels for icons and controls where needed
  • Respect for system preference for reduced motion where we control animations
  • Support for browser zoom and responsive layouts

2. Product context

JSON Editor includes code editors, tree views, and dense data UIs. Some advanced editing surfaces (for example Monaco-based editors) inherit accessibility behavior from upstream libraries. We work to wrap those surfaces with clear labels, shortcuts documentation, and fallback experiences where feasible, but parity with every assistive technology combination is an ongoing effort.

3. Compatibility

The Service is designed to work with current major browsers (Chrome, Firefox, Safari, Edge) on desktop and mobile. Accessibility support varies by browser, operating system, and assistive technology version.

4. Known limitations

  • Complex JSON tree and diff views may be slower or harder to navigate with screen readers than linear text views
  • Very large documents can strain browser performance, affecting all users including those using assistive tech
  • Third-party ads or embeds (when enabled) may not meet the same standards as our first-party UI

We prioritize fixes that unblock core tasks: pasting JSON, formatting, validating, copying results, and reaching legal/support pages.

5. Continuous improvement

Accessibility is iterative. We incorporate feedback, automated checks where useful, and manual keyboard testing into ongoing development. Legal and company pages use straightforward typography and structure to remain readable.

6. Feedback

If you encounter an accessibility barrier, please tell us:

Include the page URL, your browser and assistive technology (if any), and a short description of the issue. We will review reports and respond as soon as reasonably possible.

7. Formal complaints

If you are not satisfied with our response, you may also pursue remedies available under applicable accessibility or human-rights laws in your jurisdiction.