Inspect the working example
Creating, saving and opening a file form a sequence in this example. The editor and browser are a set of tools: exchanging their positions does not change what is needed. Native list structure can express this without inserting decorative numbers into every label.
| Case | Input or inspection | Result and meaning |
|---|---|---|
| Procedure | Read the ol in DOM order | Create → save → open; three ordered items |
| Tools | Inspect the ul | Two items with no prescribed first or second tool |
| Visual markers | Change list marker styling | Element type and source order remain ol/ul and the original sequence |
Follow the browser mechanism
Choose ol when rearranging items changes the meaning of the list. Choose ul when the list is a collection whose order is not part of the meaning. Browser-generated markers can be styled without rewriting item labels. The source sequence remains available even if a stylesheet suppresses markers.
Typed numbers do not make an ordered list
This alternative uses ul and adds numbers to its text. It combines an unordered structure with a sequence written into labels. Repair the element type, then remove redundant typed numbering.
<ul><li>1. Create the file.</li><li>2. Save the file.</li><li>3. Open the file.</li></ul>It has no ol and retains typed numbers as part of the text. The working procedure has an ol with three li elements and no typed number prefixes.
Try the repair
You add a “Keep the backup copy” tool note whose position does not affect the procedure. Should it automatically become step four?
Show the worked answer
No. Put a backup-copy item in the relevant unordered materials list. Only add a procedure step when it represents an action with an intended place in the sequence.
- Assert three li children of ol and two of ul in this fixed fixture.
- Keep decorative ordinals out of unordered labels.