Consider an original equipment-room bulletin. Its author has typed a large bold paragraph as the title and numbered two collection steps by hand. The bulletin looks organized visually, but its document structure does not yet express a heading and an ordered list. Checking the editable content gives the author a chance to fix that structure before the bulletin enters the normal publication process.
Enable the checker with an explicit rule configuration
Use the plugin only with a TinyMCE subscription and deployment that provides it. The current official documentation identifies Accessibility Checker as a paid plugin. Keep the application's existing installation, plugin delivery, and license configuration when adding these options:
tinymce.init({
selector: '#equipment-bulletin',
plugins: 'a11ychecker lists',
toolbar: 'a11ycheck | blocks | bullist numlist',
a11ychecker_level: 'aa',
a11ychecker_html_version: 'html5'
});
The selector assumes an existing bulletin editing element. Merge the required plugin and toolbar entries with the application's real configuration instead of replacing unrelated authoring features. If the control is absent, first check that the premium plugin actually loaded and that the toolbar uses a11ycheck, while the plugin entry uses a11ychecker.
The options select the checker's documented rule configuration. They are not a statement that the bulletin conforms to every requirement at that level. The documentation describes checks against WCAG 2.1 and Section 508; avoid relabeling its report as a comprehensive audit of another standard version.
Repair the bulletin's structure
This small original fixture illustrates the authoring problem:
<p style="font-size:24px;font-weight:bold">Equipment collection</p>
<p>1. Bring the booking reference.</p>
<p>2. Collect the labeled case from the counter.</p>
Run the checker in a development copy of the real editor. Its documented rules include paragraphs used as headings and manually numbered paragraphs used as lists. Inspect the finding's highlighted element and explanation; do not replace those observations with an assumed report copied from this fixture.
Use the heading control to give the title the heading level appropriate to the final page. Convert the collection steps into an ordered list. For a bulletin embedded below a page's main heading, the intended result might be:
<h2>Equipment collection</h2>
<ol>
<li>Bring the booking reference.</li>
<li>Collect the labeled case from the counter.</li>
</ol>
The embedding page determines that heading choice. If the bulletin is a complete standalone document with its own main title, review the complete heading structure before choosing a level. The semantic HTML guide explains the role of the elements beyond their visual styling.
Read a report without opening the repair dialog
For an initialized instance held in editor, the plugin exposes a synchronous report operation:
const issues = editor.plugins.a11ychecker.getReport();
const issueSummary = issues.map(issue => ({
id: issue.id,
severity: issue.severity,
description: issue.description
}));
Use the instance for this bulletin rather than whichever editor happens to be active. The full issue objects also contain references to content elements, so choose explicit serializable fields if the application records a report. Keep the document revision and checker configuration with that record; a later edited bulletin needs a new check.
The plugin's toggleaudit() method opens or closes the checker dialog. Use that documented method if a custom interface needs to expose the existing repair experience. A report display and the repair dialog serve related but different author actions.
Retest corrections and retain meaningful exceptions
After changing the heading and list, run the checker again on the revised bulletin. Save the content through the application's usual persistence route, reopen it, and verify the structural elements remain. The TinyMCE content extraction guide covers reading the live editor's current HTML.
If the integration uses ignored rules or an issue filter, record those choices when interpreting an empty report. Suppressing a finding changes what is reported; it does not repair the source. Likewise, an author's decision to ignore a finding should retain a useful reason for the reviewer.
Read the bulletin in its final page
An editor-content check cannot observe every consequence of the final page's stylesheet, navigation, or interactive controls. W3C's evaluation-tool guidance explains why tools assist evaluation and require human judgment. Check the rendered bulletin in its actual page context, including the heading sequence and how the list is exposed to readers using assistive technology.
The accessibility review organizer covers retaining findings and untested page states. For this bulletin, keep that wider review separate from the editor's report. Close the content task by reopening the saved title and collection steps, then carry the remaining page-level observations into the publication review.