| 开发者 | oldrup |
|---|---|
| 更新时间 | 2026年9月7日 19:22 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<strong>, <em>, <a>, <ul>, <ol>, <li>, <img>).<h1>–<h6> elements to prevent broken heading outlines.<img> tags for compatibility with existing content.It is built for developers, agencies, and site owners who want to provide content creators with a safe, accessible, and user-friendly editing experience across custom rich-text fields.
To satisfy WCAG 2.1 (Success Criterion 1.3.1 Info and Relationships), document heading structures must follow a logical, sequential hierarchy (e.g., an H1 page title followed by an H2, then H3). Pasting arbitrary heading tags into custom field regions frequently disrupts the page's structural outline, creating navigation barriers for screen reader users and assistive technologies.
While this plugin supports <img> tags when media buttons are enabled, best practice is to use dedicated Image or Gallery custom fields for media assets. Separating media from rich text gives developers full control over responsive output, srcset attributes, and layout design on the frontend.
Under WYSIWYG Options, recommended settings include:
p, strong, b, em, i, del, strike, s, ul, ol, li, a, imgUnder the Presentation tab:
Yes. It hooks into core WordPress TinyMCE initialization filters (tiny_mce_before_init and mce_buttons), ensuring any standard WP WYSIWYG field is automatically streamlined.
Your saved content remains completely unchanged in the database. Disabling the plugin simply restores default TinyMCE toolbars for future editing sessions.
<img> tags to accommodate media upload workflows.