Skip to content
notdocs
notdocs
Use itFeaturesEverything notdocs does, from the editor and query blocks to merges, search and agents, with the page that explains each.AgentsGive Claude Code, Cursor or any MCP client the workspace: tokens, tools, resources and prompts.CLIEvery notdocs command: documents, import, comments, tokens and the organization, for a local folder or a hosted workspace.TemplatesEvery built-in template with the file it starts, from a task to a data processing agreement.PricingFree for one person, Solo and Team for a few. What each plan allows.
Move inSwitch from NotionImport a Notion export as typed markdown documents in your repository.Switch from ObsidianImport an Obsidian vault and keep working on the same files.notdocs vs NotionMarkdown in your git repository or pages in Notion's database: how agents reach each, and what each tool does better.notdocs vs ObsidianBoth keep markdown files. What differs is where they live, who edits them, and how.ChangelogWhat changed in notdocs, from the CHANGELOG in the repository.
notdocsAboutWhy the repository should be the workspace, and the decisions notdocs is built on.SecurityWhere data lives, how access is scoped, and how to report a vulnerability.ContactHow to reach notdocs for support, privacy, security and legal matters.
PoliciesLegalEvery policy and agreement that applies to notdocs.
Legal

Accessibility statement

What notdocs does for accessibility, the known gaps, and how to report a barrier.

Last revised

On this page

Our commitment

The operator of notdocs described on the legal notice wants notdocs.dev and the notdocs web app to be usable by everyone, including people using assistive technology. The target is WCAG 2.1 level AA, as referenced by EN 301 549. This statement says what is in place, what is not yet, and how to tell us about a barrier.

Status

We have not had an external accessibility audit, so we do not claim conformance. What we have built:

  • Every interactive control is reachable and operable with the keyboard, and shows a visible focus ring drawn outside the element so it is never clipped.
  • Board cards can be moved between columns with the keyboard (⌥← and ⌥→), not only by dragging.
  • Text sizes and colours meet the 4.5 contrast ratio at the sizes used, in both the light and the dark theme; the theme follows your system setting and can be set by hand.
  • Motion is limited to short transitions that answer an action, and all of it is turned off when your system asks for reduced motion.
  • Dialogs are native <dialog> elements, so focus trapping and Escape are the browser's own.
  • Illustrations on the marketing pages are hidden from assistive technology and summarized in text.
  • Buttons that start an operation report it as busy while it runs.

Known gaps

  • The document editor is a rich-text surface; screen-reader announcements of formatting changes and of comment handles in the gutter are incomplete.
  • Drag-and-drop on boards has a keyboard equivalent, but column reordering and card reordering within a column do not.
  • Some settings tables convey column meaning visually only.
  • The site is in English only.

Feedback and contact

If you find something you cannot use, write to support@notdocs.dev with what you were trying to do and, if you can, which assistive technology you use. We answer within five working days and will offer another way to do what you needed while we fix it.

Enforcement

If you are in the EU and are not satisfied with our answer, you may contact the market surveillance authority responsible for the accessibility of digital services in your country. In Greece that is the authority designated under Law 5043/2023, which transposes the European Accessibility Act.