Currently, as a result of adding implementations for TextRangeProvider and TextProvider for flutter/flutter#11629, a few of the unit tests for AXPlatformNodeTextRangeProviderWin, as modeled after the Chromium codebase, are left disabled for now, as they refer to or rely on functionality that we lack or do not use, such as certain attribute values or ignored state.
In particular, I believe we treat text objects and line breaking objects differently than what is assumed in Chromium's existing unit tests. I have changed the boundary behavior for finding enclosing lines and paragraphs to stop if already at a boundary instead of continuing to the final boundary, so that if the carat is at the beginning or end of a text item and the user requests the screen reader narrate the focused text, it will not skip to the previous or next text item. With the test document trees set up as for Chromium, this alters the expectations.