A rich text editor for public-sector content
Government sites have to be accessible, multilingual and procured carefully. RichTextEditor is self-hosted, comes with a perpetual license, and has tools that help authors publish accessible content.
Where it is used
Public websites and CMS
Editors write pages and news with headings, tables and images. The accessibility checker flags problems before publishing.
Forms and case systems
Rich text fields inside existing forms and case-management applications, posted with the rest of the form.
Multilingual content
Language-of-parts markup, right-to-left interfaces and editor language packs for official-language requirements.
Internal documents
Track changes, comments and templates for drafting policies and briefings.
Features that matter here
All of these are in every license. Each card links to the documentation, so you can check how it works before you commit.
Accessibility checker
Built in, with 18 content rules such as missing alt text, low contrast and skipped heading levels. Most problems have a one-click repair.
Accessibility checker →Language of parts (WCAG 3.1.2)
Marks a passage in another language with lang, so screen readers switch voice and pronunciation.
Text part language →Right-to-left interface
Mirrors the toolbar, menus and dialogs for Arabic, Hebrew, Persian and Urdu users.
Right-to-left interface →Keyboard and screen-reader support
Documented keyboard operation and assistive-technology behaviour for the editor itself.
Accessibility documentation →Self-hosted, no telemetry
Runs in your infrastructure. Uploads, collaboration and AI providers are chosen and operated by you.
Security and procurement →Perpetual license
Buy once and keep using the purchased version. One year of updates is included, and renewal is optional, which suits fixed budgets.
Perpetual license →What the editor does not do for you
We would rather you find the limits here than during an audit.
- Accessibility status is self-assessed against WCAG 2.2 AA, with known gaps listed. No third-party VPAT or certification is currently published, and self-testing is not certification.
- Section 508, EN 301 549 and similar requirements apply to your whole site. The editor helps authors produce accessible content but cannot guarantee it.
- No FedRAMP or similar authorization applies, because there is no Richscripts-hosted service to authorize. You host the editor.
Evaluation checklist
Run the in-browser accessibility and security checks on the trust page.
Test keyboard-only and screen-reader editing with your own assistive technology.
Check the language packs and RTL support for your official languages.
Send procurement and security questionnaires to support.
For a full evaluation plan, see the evaluation checklist.
Customer stories
We only publish customer stories that the customer has agreed to, and none from this sector is published yet. If you use RichTextEditor in government, tell us how. We will write it up with you and publish it only after you approve it.
Related
Accessibility (WCAG 2.2 AA) · Security and procurement · License terms · Other sectors: Education, Healthcare
Try it with your own documents
Perpetual licenses from $129, one-time. Every feature in every license.