Matterhorn 16-003 · PDF/UA-1 UA1:7.6-2

Bulleted content that is not tagged as a list

Bulleted or numbered content is a run of paragraphs, with the bullet characters sitting in the text as literal glyphs.

What a screen reader actually does

The reader does not announce "list of 7 items" and cannot jump item to item. Bullets are read aloud as "black circle".

What a real list looks like

Four element types, nested in a fixed shape:

30 0 obj  << /Type /StructElem /S /L  /K [31 0 R 34 0 R] /A <</O /List /ListNumbering /Decimal>> >>
31 0 obj  << /Type /StructElem /S /LI /P 30 0 R /K [32 0 R 33 0 R] >>
32 0 obj  << /Type /StructElem /S /Lbl   /P 31 0 R /K [ 4 ] >>   % "1."
33 0 obj  << /Type /StructElem /S /LBody /P 31 0 R /K [ 5 ] >>   % the item text

<L> contains <LI> elements. Each <LI> contains an optional <Lbl> and an <LBody>. That is the whole grammar, and ISO 32000-1 Table 336 does not permit anything else at those positions.

The failure this page covers is the absence of all of it: the items are a run of <P> elements, and the bullet characters are literal glyphs sitting at the start of each one’s text.

What the user loses

Three things, all of which a list-aware reader would have given them:

The count. “List with seven items” tells the reader how much is coming, and whether to skip it. Without the structure there is no announcement at all.

Navigation. L in NVDA jumps to the next list; I moves between items. Neither works on paragraphs.

Silence about the marker. The bullet is announced. • is read as “black circle” or “bullet” depending on the reader and the verbosity setting, before every single item. A properly tagged list puts the marker in <Lbl>, which readers announce as a position rather than a glyph — or suppress entirely.

How to fix it free, in Acrobat Pro

This is the tedious one. Acrobat can do it and the steps work, but there is no bulk path.

1. Open the Tags panel.
2. Select the run of <P> elements that make up the list.
3. Right-click → New Tag → type L. This creates an <L> and puts the selection inside it.
4. For each item: select its <P>, right-click → New Tag → LI, then inside that create an <LBody> and move the <P>’s content into it.
5. If the bullet glyph is part of the text, split it: use the Reading Order tool to select just the bullet, tag it separately, and move that tag into an <Lbl>.
6. Set the numbering: right-click the <L> → Properties → Attributes → add ListNumbering with the right value (Decimal, UpperRoman, LowerRoman, UpperAlpha, LowerAlpha).

Step 5 is where the time goes. On a twenty-item list this is a solid half hour.

Upstream is dramatically faster and is genuinely free. A list made with Word’s or InDesign’s list feature — not typed bullets, the actual list style — exports as a complete <L>/<LI>/<Lbl>/<LBody> structure with ListNumbering already set. If your source document has typed bullets, converting them to a real list style takes a minute and fixes every list in the file at once.

That is the recommendation: if you have the source, do not do this in Acrobat.

Where Taggart differs

Taggart looks for what a person looks for — consecutive lines starting with a bullet glyph or an enumerator, on a page with no <L> element:

Page 1 has 3 consecutive lines that start with a bullet or an enumerator, but the page contains no <L> list structure.

It reports the bounding box of the run and quotes the first few items, so you can see immediately whether it has found a list or a coincidence.

Building the structure is a semantic claim — these paragraphs form one list, these two are separate lists — so Taggart requires you to confirm the grouping. Given the groups, it builds the full <L>/<LI>/<LBody> structure, moves each paragraph’s content into its LBody rather than copying it, splices the new <L> in where the first item was, and infers ListNumbering from the label text.

Setting ListNumbering on a list that already has the right structure is mechanical and ships in “Fix All Safe” — that is conditions 16-001 and 16-002.

How Taggart handles it

The protocol marks this condition as needing human judgement, so no validator can decide it outright. Taggart applies a heuristic to find the likely cases and reports them as warnings for you to confirm — it never passes them silently, and it never fails them silently either.

The fix is Build list structure. It changes what the document means, so Taggart proposes it and waits for your approval rather than applying it unattended.

Where this sits in the standards

Related conditions

• 09-005 A list-related structure element does not conform to ISO 32000-1, Table 336 The list grammar is broken: an LI outside an L, an Lbl or LBody outside an LI, a list item with no LBody.
• 16-001 Ordered list has no ListNumbering attribute An L element whose items are numbered lacks the /ListNumbering attribute that tells the reader the numbering scheme.
• 16-002 ListNumbering value is not one of the permitted values ListNumbering is present but carries a value outside the permitted set — often /None or /Disc on a genuinely ordered list.
• 01-005 Content is neither marked as Artifact nor tagged as real content Every text-showing, image-painting and path-painting operator on a page must sit either inside a marked-content sequence that maps to the structure tree, or inside an artifact sequence. Content that is in neither is orphaned.

Other conditions in checkpoint 16

Checkpoint 16 covers lists. These are its other failure conditions; the ones without a link are in the rule set but do not have a written page yet.

• 16-001 Ordered list has no ListNumbering attribute An L element whose items are numbered lacks the /ListNumbering attribute that tells the reader the numbering scheme.
• 16-002 ListNumbering value is not one of the permitted values ListNumbering is present but carries a value outside the permitted set — often /None or /Disc on a genuinely ordered list.

Verified against a real document on 2026-09-06 . Last updated 2026-09-08 .