The converted checklist has boxes, but clicking them does nothing. That may be the intended output. Decide whether the HTML represents recorded Markdown state or an editable task application. Enabling a checkbox is not the same as writing its changed value back to the source.
Use a fictional equipment handoff with two entries:
Open the complete example · Download the full HTML source
- [x] Count the supplied cables.
- [ ] Confirm the receiving desk.
The source records one completed check out of two. A reading copy should preserve that distinction without implying that the receiving desk has now confirmed anything.
Render the task notation with the chosen plugin
The markdown-it-task-lists README documents checkbox generation from list items beginning with [ ] or [x]. In a browser with the parser and plugin loaded:
const parser = window.markdownit({html: false})
.use(window.markdownitTaskLists);
const readingHtml = parser.render(source);
The plugin disables the rendered checkboxes by default. That is useful when the file is a reading copy of the source state. Make the purpose visible with a sentence such as “Recorded checklist; change the Markdown original to revise these checks.”
Do not make the disabled control look like a broken submission form. It is a displayed result, not a request for the reader to complete a task in the page.
Treat enabled controls as a separate design decision
The plugin accepts {enabled: true} to remove its disabled state. Its documentation also describes label options. Those options affect the generated HTML; they do not implement a storage service or a Markdown serializer.
If you enable boxes for a local exercise, name the state boundary. A changed DOM checkbox is a temporary reading interaction until your application deliberately captures it. Re-rendering the original Markdown can restore its original checked state because that source has not changed.
For a real editable task system, decide who may edit, where the state is stored, and which revision the recipient should receive. The existing single-file todo list builds application state and browser storage. That is a different task from converting recorded Markdown checks.
Reconcile the delivered checklist
For this source, inspect two generated checkboxes, one checked and both disabled. Verify the two task labels as well as the count. A count of one completed item cannot establish which task was completed.
Change the source to mark the desk confirmation complete and render again. The new reading copy should contain two checked entries. Keep the revised Markdown with that export so the record can be explained later.
The Markdown conversion guide covers the surrounding page and styles. Retain those along with the generated checklist when sending one HTML file.
For review in NOS, ask whether “Confirm the receiving desk” is still unresolved. Keep a discussion about the wording separate from any claim that a reader's click updated the operational handoff record.