Found a few ways in which the Braille problem with browsers could resurface. Fixed now.

README.md

@@ -508,6 +508,17 @@ Stale native placement gets one refresh and retry at the same target and offset.
 Braille routing also recognizes the temporary caret produced by clearing a
 selection, so it cannot reset the routed reading position.
 
+Browser Braille expands embedded links and preserves that text when native
+caret events repair line offsets. If a descendant read fails or reaches its
+expansion limit, a clean accessible name can recover a range covering the whole
+object. Wrapped line fragments retain their own content. Names are also stripped
+of embedded-object placeholders before calculating Braille label offsets.
+After rebuilding, check H/Shift+H in Firefox and Chromium on linked headings,
+headings containing linked images, and wrapped headings. Compare speech with
+Braille, then check arrow reading, selection, panning and ordinary text routing.
+Expanded text has no native cell routes because its offsets differ from the
+browser's raw text.
+
 Reading a final ellipsis avoids the provider's native line-boundary request:
 Chromium can calculate a boundary past truncated text and abort the browser.
 At that character, Cthulhu reads a bounded logical line using explicit line