An unresolved sub-readable style
The style sheet defines a sub-readable font size on a style that reaches text through a table style, which this engine does not resolve into runs — so the size claim could not be checked.
How the text is hidden
A table style's properties, including its w:tblStylePr conditional formatting, reach the text in the table's cells. The parser builds a run's formatting from the run's own properties and its character and paragraph styles only. A size defined that way is applied to real text and never seen by the size check.
Why a model still reads it
Nothing is concealed by this finding itself. It says a place exists where sub-readable text could be applied without the engine measuring it, so a caller does not read the absence of docx.tiny-font as proof.
What we do about it
After the parts are walked, the parser separates styles that are unused, styles that were walked into a run, and styles applied only by a w:tblStyle reference. For the last group it reads the nearest w:sz in the chain and, when it is at or below limits.subReadableMaxFontSizePt, sets a style note. The finding is named and emitted in the analyzer rather than the parser, at informational, action flagged, with no excerpt and no location — it reports that the possibility exists, not which text it is.
How often it fires
Not measured. We publish a rate only where one has been measured against a named corpus of the right format, and no figure exists for this technique yet. Absence means unknown — never low.
Check your own file
Three commands: a key, credit, a verdict.
Start with the API