@jakobrosin That's how it has to be, at least currently. I sadly don't have enough control over screen readers to make the text field literally act like a virtual buffer/web browser, and the nav keys are the closest I've gotten so far.
@TheQuinbox Thats fine. I thought I had broken it somehow.
@TheQuinbox @jakobrosin "At least currently," they say.
*tape fast forwarding noise*
It's 2028. Quin has reimplemented both NVDA and JAWS in their own programming language, Nom. Not only do headings now speak in Paperback, but their BrailleNote Evolve hasn't said "landscape" for nine months either.
@jscholes @TheQuinbox @jakobrosin My wife is using it to read pdf files for a graduate degree and this thing is literally a life saver. I am recommending everywhere I can, from universities to accessibility auditing companies.
@jscholes Look, writing an NVDA add-on that dynamically subclasses HumanWare’s compiled pyc files via zipimport just to fix duplicate shortcut keys was a one-time thing, okay? Don’t give me ideas. :P @jakobrosin
@jscholes @jakobrosin BTW, this was a real thing, if anyone's curious how it works: https://www.dropbox.com/scl/fi/rosnipycvi4a05a1cpb18/KeysoftDialogEnhancements.nvda-addon?rlkey=b5cgpuzftchndaovvo6oc6twv&dl=1
@jscholes @TheQuinbox @jakobrosin On their own OS, of course.
@jakobrosin In case you didn't already know, for Epub, HTML, and possibly other web content, you can Open in Web View (Ctrl+Shift+V) to open the current section/document in a... uh... web view. Not only that, but it opens where your cursor is. It doesn't update the position of said cursor on close, but that's what searching is for. @jscholes @TheQuinbox
@twynn @jscholes @TheQuinbox Yep, did know that. I made this observation in a com plex pdf though. But as I said, its fine, the fact that I can read this pdf and make sense of it is something nothing else really can produce without me needing to pull out some hair of mine or others. So PB definitely wins here.
@TheQuinbox Again me with a paperback issue. So sorry :) This file from Apple shows as 0 words and no content in my paperback, but i clearly has machine readable content in it. https://www.apple.com/privacy/docs/Audio_Intelligence_Privacy_Overview_Sep_2026.pdf
@jakobrosin Thanks, not sure when I myself will be able to look at this until at least next week, but pinging @Aryan in case he has some time and desire to look at it too. Thanks for the report, I hate pDF!
@TheQuinbox @jakobrosin sure, on it.
@TheQuinbox Don't we all. Thanks for making our pain a little less intense with paperback @Aryan
hay @jakobrosin may I know which paperback version you are using? thanks. @TheQuinbox
@Aryan That would be 0.9.2, apparently the latest stable build @TheQuinbox
@jakobrosin could you try the latest dev build? i'm able to load the file just fine. @TheQuinbox
@Aryan yeppers, works with the latest dev build. The stable one showed nothing tho, so glad it was already fixed :) @TheQuinbox
@TheQuinbox If you implement the UIA text pattern yourself, you could probably get that level of exposure in an edit field. NVDA won't support browse mode (quick nav, etc.) itself in UIA without specific code, but it should report rich info provided via the UIA text pattern even in an edit field, which should work for your use case. Not sure about JAWS though. MacOS has rich text accessibility APIs as well, but they're undocumented, though well covered by all three web browser engines. @jakobrosin
@TheQuinbox Sadly, I don't think you can just use AccessKit for this, as its text implementation didn't support rich text formatting last time I checked, though it's possible that might have changed (I haven't looked in ages). @jakobrosin
@jcsteh @TheQuinbox @jakobrosin I feel like hacking on it at some point. we'll see. I barely succeed in stuff like that though.
@Aryan Given that Paperback is open source, I'm happy to provide pointers/guidance if you get stuck, as I'm fairly experienced with those APIs. I don't have the cycles to take it on myself, unfortunately. @TheQuinbox @jakobrosin