https://bugs.documentfoundation.org/show_bug.cgi?id=77679
--- Comment #17 from Michael Weghorn <[email protected]> --- (In reply to cwendling from comment #16) > 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? It's been a while that I started looking into this, but if I remember correctly, this might need 1) adjusting the XAccessibleHyperText/XAccessibleHyperlink UNO API interfaces to provide all relevant information 2) adjusting existing implementations of those interfaces accordingly 3) bridging interfaces properly to the corresponding platform/toolkit APIs -- You are receiving this mail because: You are the assignee for the bug.
