LF wants clarification of Microsoft wants with respect to any requests specific to IA2. For the child ID support, they just want copyright on the 2 new methods. Karen asked for draft language for the copyright so the LF doesn't have to interpret the Microsoft request.
In the given situation of paragraph table paragraph, it depends on what the app does with the caret. if you are on the last position of the first paragraph and you press right arrow or down arrow, does the caret move to the first cell in the table? if so, then that should be the relation: first paragraph flows to first cell, first cell flows from first paragraph. The same as the last cell in the table flows to second paragraph, second paragraph flows from last cell in table. Also of course I would expect that the flows to/from relation exists on all the table cells.
When I say table cell though, I really do mean the deepest object in that table cell that has the caret.
So really, the question is: is the flowsTo/flowsFrom relation really to show where the caret moves? If so this is good, and this is what we would wish to happen. But if flowsTo/flowsFrom was created for a different purpose, then we perhaps should make some new relations specific to the caret.
At the end of the day, screen readers such as NVDA need a way to ask any given object, for the next or previous object that would contain the caret, if it were to move there directly from this object.