Evaluate the editor with your content—not our claims.
Use the same checklist for RichTextEditor, TinyMCE, CKEditor, Froala, Tiptap, or an open-source framework. Record pass, concern, owner, and evidence for every item before price decides the shortlist. Two companion pieces: how to verify a vendor’s feature claims, and, if building is still on the table, should you build your own rich text editor?
Get it running first — two tags, nothing installed.
The checklist below asks you to test with your own content. Paste this into a CodePen or a scratch HTML file and you have somewhere to paste that content into, with no download, no build step and no account. The files come from the published npm package, mirrored on jsDelivr.
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@richscripts/[email protected]/richtexteditor/rte_theme_default.min.css" />
<script src="https://cdn.jsdelivr.net/npm/@richscripts/[email protected]/richtexteditor/rte.js"></script>
<script src="https://cdn.jsdelivr.net/npm/@richscripts/[email protected]/richtexteditor/plugins/all_plugins.min.js"></script>
<div id="editor">Paste your worst document here.</div>
<script>
var editor = new RichTextEditor("#editor");
</script>That is the full plugin set, not a trimmed demo. Serve it from cdn.richtexteditor.com instead if you would rather not add a third party to the page, or download the buildwhen you reach the checks that need your own infrastructure — CSP, uploads, collaboration and offline install all want the self-hosted copy.
Authoring quality
Paste your real Word and Google Docs samples. Check headings, lists, tables, links, images, whitespace, undo, and the saved HTML—not only the toolbar demo.
Your framework
Install the package in your production framework and build pipeline. Verify loading, form binding, route changes, SSR boundaries, CSP requirements, and bundle caching.
Customization
Recreate one real toolbar, command, dialog, upload flow, and content rule. Confirm the public API covers the workflow without editing vendor source.
Accessibility
Complete keyboard-only authoring, inspect labels and focus order with your preferred screen reader, test zoom and mobile widths, and review the current accessibility evidence.
AI and data flow
Connect a non-production resolver, inspect every outbound request, test preview and rejection paths, and document provider retention, region, logging, and failure behavior.
Collaboration and review
Test simultaneous edits, reconnects, presence, comments, tracked changes, permissions, revision recovery, and provider persistence with realistic latency.
Files and export
Exercise upload limits, type validation, storage authorization, cleanup, and your required HTML, Markdown, JSON, or DOCX round trips using representative documents.
Operations and cost
Review health checks, rate limits, audit hooks, upgrade ownership, support terms, license scope, required add-ons, and a three-year cost scenario using your actual seats and traffic.
A useful result is evidence, including a “no.”
Keep screenshots, saved output, build logs, network traces, and unresolved requirements. RichTextEditor is strongest when perpetual self-hosting, broad framework support, and included authoring workflows matter; teams requiring a published third-party VPAT should treat that as an open requirement.