https://bugs.documentfoundation.org/show_bug.cgi?id=77679
--- Comment #16 from [email protected] --- This has serious impact on the accessibility of most embedded content (images, frames, etc.). And although links more or less work as they are now (see comment 20 on bug35107), but they are not standard and break as soon as something more standard is present on the same paragraph/line (actually, if there's a U+FFFC Orca's heuristics will fail). In practice, all of links, comments, images, frames, etc. will need to be fixed to get properly reported by the Hypertext interface. @michealw would you know whether all these are ad-hoc implementations that would all need to be fixed, or if there's a more generic place for this? --- Also, there's a different but related challenge for objects embedded as anything but "as character": although they are present in the a11y tree at the same level as paragraphs (not embedded), navigation do not reach them moving through the document, meaning the user never reach them unless explicitly navigating them. I'm not actually sure why those type of anchors do not link the objects to the paragraphs, given anchoring "to character" or "to paragraph" seem to still closely relate to paragraphs, doesn't it? In any case, this should also be changed, either by navigating to the objects (e.g. sending focus event to them) or by embedding them to the relevant paragraph so it's part of something that gets focused during regular document navigation. Anyone with knowledge regarding anchors is welcome to comment on why those anchoring methods should not (or should) lead to objects being children of a given paragraph. -- You are receiving this mail because: You are the assignee for the bug.
