[
    {
        "role": "user",
        "content": "I%20want%20to%20read%20a%20book%20on%20my%20Dot%20Pad%20X%20and%20iPhone%2016%20running%20iOS%2026.%20I%20have%20tried%20this%20with%20Dolphin%20EasyReader%20and%20BookShare%20and%20in%20all%20of%20them%20focus%20is%20a%20problem.%20Previous%20screens%20come%20back%20after%20scrolling%20a%20bit.%20DotBook%20does%20not%20have%20this%20problem%20but%20it%20doesn%27t%20work%20when%20the%20phone%20is%20locked%20and%20the%20phone%20is%20detecting%20no%20movement%20so%20mine%20locks%20after%205%20minutes%20which%20I%20cannot%20change%20because%20of%20work%20software%20on%20my%20computer."
    },
    {
        "role": "assistant",
        "content": "It sounds like you're bumping into two different kinds of issues: one with the reading apps (EasyReader, Bookshare, Dolphin, etc.) losing focus while scrolling, and another with DotBook not working when your iPhone locks\u2014and you can\u2019t change the lock timeout because of work restrictions.\n\nI've dug into both problems and possible workarounds. Here's what I found, and what you can try.\n\n---\n\n## 1. The \u201cFocus Hops Back\u201d Bug in VoiceOver / Screen-Reader Mode\n\nFrom experiences by many users with iPhone on iOS 26, there is a known bug where VoiceOver focus \u201cjumps back\u201d\u2014e.g. after scrolling a bit or interacting with content, focus returns to the top of the page or another part of the UI unexpectedly. ([reddit.com](https://www.reddit.com/r/Blind/comments/1osyzkh?utm_source=openai))\n\n### What\u2019s known:\n\n- It happens in many apps\u2014not just reading apps. ([applevis.com](https://www.applevis.com/comment/137483?utm_source=openai))  \n- The behavior tends to worsen with continuous scrolling, or when there\u2019s motion (even slight, like lifting the phone) or auto-scrolling of content.  \n- Multiple users report it across iOS 26 (including in updates like 26.1/26.2). Shell fixes are reported in iOS 27 for some issues, but not universally for all users. ([reddit.com](https://www.reddit.com/r/Blind/comments/1osyzkh?utm_source=openai))\n\n### Why this might happen:\n\n- A regression in how iOS 26 handles VoiceOver focus when content dynamically loads or screen layout changes (due to scrolling, scrolling fade, or font adjustments).  \n- Some reading apps use their own rendering and scrolling logic (sometimes re-laying out paragraphs or lines as text is modified/adjusted), which could confuse the VoiceOver focus engine.  \n\n---\n\n## 2. DotBook Issue When iPhone Locks\n\nYou mention that DotBook doesn\u2019t work when the phone is locked (assuming with the screen off or locked), and your phone auto-locks in 5 minutes (which cannot be changed due to work policies).\n\nHere\u2019s what I found:\n\n- DotBook version 1.0.9 added support for up to 10 lines of braille on screen at once, adjustable in settings. That helps reduce frequent navigation, but doesn\u2019t directly address what happens when the phone is locked. ([blog.dotincorp.com](https://blog.dotincorp.com/read-up-to-10-lines-of-braille-with-dot-book-on-ios?utm_source=openai))\n- Lock screen behavior for reading apps depends heavily on whether they declare *background audio* permissions, or use \u201caudio plus text-underlaid\u201d that keeps reading active when locked. If the app isn\u2019t doing that, locking the screen can suspend or pause the app\u2019s rendering / reading process.\n\n---\n\n## 3. Potential Workarounds\n\nHere are several things you could try, given your constraints (like phone locking after 5 minutes, inability to change that timer):\n\n| Problem | Possible Solution |\n|---------|----------------------|\n| **VoiceOver focus jumping back / losing place** | \u2022 Update iOS to latest patch\u2014some reports say iOS 27 fixes certain focus / notification reading bugs. <br>\u2022 In the reading app, try switching modes: e.g., use \u201cScreen Reader View\u201d if available (e.g. in EasyReader, that mode can change UI behavior). <br>\u2022 Reduce dynamic layout changes: set font size, margins, line spacing, style settings such that minimal re-layout occurs during reading. <br>\u2022 Slow motions: scroll more gently; avoid rapid swipes. <br>\u2022 If using DotBook, use its setting for showing 10 lines to reduce navigation. |\n| **Reading interrupted when phone locks** | \u2022 Use an app which supports background audio + lock-screen controls. For example, reading apps (or audiobook apps) that are audio-based plus highlight-follows-audio tend to keep going when locked. <br>\u2022 Try Murmura (app): in recent updates, it states \u201cBackground audio and lock-screen controls\u201d as part of its features. ([apps.apple.com](https://apps.apple.com/us/app/murmura-ai-audiobook-reader/id6761295449?platform=watch&utm_source=openai)) <br>\u2022 Check if enabling any \u201cStay Awake\u201d or \u201cGuided Access\u201d options is possible (maybe via settings or accessibility). If Guided Access lets you keep app active, screen locks may behave differently. <br>\u2022 As a small workaround: use something to keep screen from locking (e.g. external power, or temporary override) when reading sessions are longer\u2014but you said lock time setting is locked by work, so might be limited. |\n\n---\n\n## 4. Apps Alternative You Might Try\n\nIf EasyReader and DotBook are giving you trouble, here are a few alternatives that might give you better control:\n\n- **Murmura** \u2014 supports background audio and lock-screen controls. ([apps.apple.com](https://apps.apple.com/us/app/murmura-ai-audiobook-reader/id6761295449?platform=watch&utm_source=openai))  \n- **Continuum Reader** \u2014 full support for audio playback, including lock screen, and read-along/audiobook sync. ([continuumreader.app](https://continuumreader.app/?utm_source=openai))  \n\nThese apps might handle focus and locking more robustly.\n\n---\n\n## 5. What to do Next\n\nHere\u2019s what I suggest as a plan:\n\n1. **Check for iOS Update**: If possible, update to the latest patch version (or iOS 27 if available to you) \u2014 to see if your bug is addressed.  \n\n2. **Test with Alternatives**: Try Murmura or Continuum with a small book to see if lock behavior works better.  \n\n3. **Adjust App Settings**: In EasyReader, DotBook, etc.:\n\n   - Turn off extra dynamic UI effects (styling changes, line fading, etc.).  \n   - Use reader modes that don\u2019t cause reflow of text.  \n   - Keep display of lines full-screen or maximum lines (minimizing navigation).  \n\n4. **Report the Bug**: If this behavior persists, report to Apple (via Feedback / Accessibility) and to the developers of the reading apps. The more reports they collect, the more likely a fix will come.\n\n---\n\nIf you like, I can walk you through checking your specific EasyReader / DotBook settings on your device, helping you pick the ones that might stop focus from jumping or keep reading going with lock. Do you want me to guide you through that?"
    },
    {
        "role": "user",
        "content": "I%20do%20not%20want%20audio.%20I%20want%20only%20braille.%20I%20have%20all%20audio%20turned%20off.%20Further%2C%20I%20am%20not%20swiping%20on%20my%20phone%20so%20there%20is%20no%20Gentle%20Scrolling.%20I%20am%20using%20F4%20on%20the%20Dot%20Pad%20X%20to%20move%20forward%20and%20F1%20to%20move%20backward."
    },
    {
        "role": "assistant",
        "content": "Thanks for clarifying\u2014only braille, no audio, using F4/F1 for forward/back movement. I found more specific info that relates to exactly your setup (iOS 26, braille display, reading apps, and the focus/back-jumping bug), plus more focused suggestions.  \n\n---\n\n## What the Community is Saying\n\nThese issues aren\u2019t unique to you\u2014others who read using braille display with speech turned off report similar problems:\n\n- Many users with iPhones on **iOS 26** say that VoiceOver focus *regresses* to earlier content during reading, or jumps back to the top of the screen or to some earlier position without tapping or swiping. ([mail.applevis.com](https://mail.applevis.com/forum/ios-ipados/voiceover-focus-regressions-ios-26?utm_source=openai))  \n- There's a known bug where the **braille cursor jumps around** while you\u2019re reading, especially with speech off. The cursor sometimes goes back to the beginning of a screen or moves unexpectedly when you're navigating with standard braille display commands (like F1/F4). ([applevis.com](https://applevis.com/forum/ios-ipados/i-am-extremely-frustrated-voiceover-braille-display-cursor?utm_source=openai))  \n\nSo what you\u2019re experiencing is consistent with known VoiceOver/Braille bugs in iOS 26\u2014not app-specific (though specific apps may behave worse depending on how they\u2019re coded).\n\n---\n\n## Why It Happens When Only Using Braille and Speech Off\n\nWhen you use a braille display with VoiceOver\u2014and turn speech off\u2014you're relying entirely on the braille cursor and display focus to track where you are. \n\n- Many apps are built to update or re-render text as you navigate, or adjust layout dynamically, causing the focus cursor to reset or move unexpectedly. Crawling through long\u2010form text (ebooks or PDFs) is especially prone to this.  \n- If the app isn't using standard \u201ctext elements\u201d (UIKit text views, etc.) or doesn\u2019t support continuous navigation between paragraphs/lines properly, the system can lose track of the correct focus position.  \n- iOS 26 introduced changes (some under development or being patched) that impact braille support, focus behavior, continuous reading, and cursor stability. ([applevis.com](https://www.applevis.com/comment/195627?utm_source=openai))  \n\n---\n\n## What You Can Try To Mitigate the \u201cFocus Jumps Back\u201d When Using Only Braille\n\nHere are some targeted workarounds for reading using only your braille display with focus movement via F4/F1, and speech off:\n\n| Technique | Why It Might Help | How To Do It |\n|-----------|--------------------|---------------|\n| **Update iOS to the latest patch version** | Sometimes problems get fixed in incremental updates. The community found some VoiceOver / focus bugs resolved in 26.0.1 and later. ([applevis.com](https://www.applevis.com/comment/195627?utm_source=openai)) | Go to *Settings \u2192 General \u2192 Software Update* and install if available. |\n| **Use Apple\u2019s Books (or Apple Books) app** | Books tends to have better built-in support for VoiceOver + Braille and uses text objects, which are less likely to lose focus unexpectedly than custom readers. | Load your book into Apple Books. Turn on VoiceOver, and in some cases mute speech if possible (or set speech rate to zero, or similar). Check if the cursor stays more stable when moving with F4/F1. |\n| **Mute Speech, Keep VoiceOver On** | Many users do exactly this: VoiceOver must stay active for braille displays to work, but muting speech can reduce distraction and may reduce system load that contributes to focus issues. ([applevis.com](https://www.applevis.com/forum/braille-apple-products/trouble-having-pages-turn-automatically-when-reading-braille-display?utm_source=openai)) | Mute VoiceOver speech via *Settings \u2192 Accessibility \u2192 VoiceOver \u2192 Speech \u2192 Volume = 0* or via a faster toggle if available. |\n| **Avoid apps with heavy layout changes, animations, or embedded media** | These tend to trigger reflow or screen updates, which often reset or move cursor focus. | Stick to clean, simple text files (e.g. BRF, ePub) without fancy graphics or layout elements. |\n| **Open text in the Accessibility Reader, if supported** | iOS 26 introduced *Accessibility Reader*, which takes text\u2010based content and simplifies it for easier reading. Apps that use the standard text flow may allow you to launch their text in Accessibility Reader, which may help focus stay steady. ([developer.apple.com](https://developer.apple.com/videos/play/wwdc2026/219/?utm_source=openai)) | If the reading app or the content supports it, trigger Accessibility Reader via Control Center or via app\u2019s share/open options. |\n\n---\n\n## What to Watch Out for (and Report Back)\n\nEven with these fixes, some behaviors may persist. Here's what to check and possibly report if you contact Apple or app developers:\n\n- Exactly when the focus jumps back: after pressing F4, or after turning a page, or after idle periods?\n- Whether it happens only in certain books/formats (PDF, BRF, ePub) or all formats.\n- Which versions of iOS and readings app you're using (e.g. EasyReader version, DotBook version).\n- Any specific gestures or actions (e.g. page turns via display versus app-buttons) that trigger the issue more.\n\n---\n\nIf you want, I can help you test a specific reading app or ebook file on your setup (Dot Pad X + iPhone 16 + a sample ePub or BRF) to see whether we can isolate exactly where the focus jumps back, and maybe craft a workaround custom to your reading materials. Do you want me to walk you through that?"
    },
    {
        "role": "user",
        "content": "Does%20Apple%27s%20Books%20app%20support%20BRF%20or%20DAISY%20files"
    },
    {
        "role": "assistant",
        "content": "I checked current documentation and the DAISY Consortium\u2019s resources, and I couldn\u2019t find any indication that Apple Books supports BRF (Braille Ready Format) or DAISY files directly. Here\u2019s what I found:\n\n---\n\n## What *Apple Books* Does Support\n\n- Apple Books supports **EPUB** and **PDF** formats for text-based books. ([daisy.org](https://daisy.org/info-help/guidance-training/reading-systems/apple-books-overview/?utm_source=openai))  \n- It also supports **audiobooks** from the Apple Books Store. ([daisy.org](https://daisy.org/info-help/guidance-training/reading-systems/apple-books-overview/?utm_source=openai))  \n\n---\n\n## What *Apple Books* Does *Not* Support (According to Available Sources)\n\n- **BRF files** \u2014 there\u2019s no official indication that BRF (Braille Ready Format) can be opened or rendered by Apple Books.  \n- **DAISY files** \u2014 similarly, there is no evidence that Apple Books can directly import or use DAISY format, whether text-only DAISY or DAISY with SMIL audio synchronization. DAISY is mentioned in the context of other reading systems or specialized apps, not Apple\u2019s built-in Books app. ([daisy.org](https://daisy.org/info-help/guidance-training/reading-systems/?utm_source=openai))  \n\n---\n\n## Why That Matters\n\nBecause Microsoft, DAISY Consortium, and assistive technology groups list other apps (like EasyReader, Thorium Reader, Bookshare Reader) as supporting DAISY or BRF, but *not* Apple Books. So these formats are typically served by specialized accessibility-focused applications rather than the general reader. ([daisy.org](https://daisy.org/info-help/guidance-training/reading-systems/?utm_source=openai))  \n\n---\n\nIf you want, I can help you find apps that *do* reliably support BRF and DAISY formats, work well with only braille display (speech turned off), and behave well under iOS 26 + your lock timeout constraint."
    },
    {
        "role": "user",
        "content": "Can%20I%20add%20an%20epub%20book%20to%20the%20Books%20app%3F%20If%20so%2C%20how%3F"
    },
    {
        "role": "assistant",
        "content": "Yes \u2014 you *can* add an .epub book to Apple Books on your iPhone. Here are several methods that work, depending on where your .epub file is (Files app, email, Mac, etc.):\n\n---\n\n## Ways to Add an EPUB to Apple Books on iPhone\n\n| Starting place | What to do |\n|----------------|------------|\n| **Files app (iCloud Drive, \u201cOn My iPhone\u201d, etc.)** | 1. Open the **Files** app and locate the .epub file. <br>2. Tap and hold the file, or tap it once to preview, then tap the **Share** button (square with an up arrow). <br>3. In the Share Sheet, choose **Copy to Books** or **Open in Books**. That sends it to Apple Books. ([idownloadblog.com](https://www.idownloadblog.com/2026/04/27/fix-epub-file-issues-ios/?utm_source=openai)) |\n| **Mail (an email with an .epub attachment)** | 1. Open the email, download the attachment so it's stored locally. <br>2. Tap the .epub file. <br>3. Tap the **Share** button, then choose **Books**. That adds it to your Books library. ([toolkit.bot](https://toolkit.bot/blog/apple-books-epub?utm_source=openai)) |\n| **Safari or other browser** | 1. Tap a link to the .epub to download it. <br>2. In the download manager or Files, tap the .epub. <br>3. Use the Share button \u2192 **Copy to Books**. It should open in Books automatically. ([idownloadblog.com](https://www.idownloadblog.com/2026/04/27/fix-epub-file-issues-ios/?utm_source=openai)) |\n| **Mac** | 1. Save the .epub file to your Mac\u2019s drive. <br>2. Open the **Books** app on the Mac. <br>3. Drag the .epub file into the Books window or use **File \u2192 Add to Library**. It will then sync via iCloud to your iPhone if Books syncing is enabled. ([stephenhunt.net](https://stephenhunt.net/getting-your-e-book-onto-apple-books?gi=e84afdaaaf935ceda5a5cd260fb4984c584ab4de&utm_source=openai)) |\n\n---\n\n## What to Check If It Doesn\u2019t Seem to Work\n\n- Make sure the file is **DRM-free** \u2014 if it's locked or protected, Books might not accept it. ([stephenhunt.net](https://stephenhunt.net/getting-your-e-book-onto-apple-books?gi=e84afdaaaf935ceda5a5cd260fb4984c584ab4de&utm_source=openai))  \n- Ensure the file has the **.epub** extension. If it doesn\u2019t, rename it in **Files** to include \u201c.epub\u201d at the end. ([idownloadblog.com](https://www.idownloadblog.com/2026/04/27/fix-epub-file-issues-ios/?utm_source=openai))  \n- Check that **Books sync** is on (in iCloud settings: your name \u2192 iCloud \u2192 Books ON). That helps files added on Mac show up on the iPhone. ([toolkit.bot](https://toolkit.bot/blog/apple-books-epub?utm_source=openai))  \n\n---\n\nIf you like, I can also check if the Apple Books version on iOS 26 has any special quirks with .epub files and braille navigation, so you can see whether it might work better for your setup."
    },
    {
        "role": "user",
        "content": "Apple%20Books%20does%20the%20same%20goddamn%20thing"
    },
    {
        "role": "assistant",
        "content": "I\u2019m sorry to hear that Apple Books is doing the same frustrating focus issue for you. Based on what I found, this is a known bug or regression affecting VoiceOver users, especially in iOS 26, and it\u2019s not just unique to your setup. Here are some specifics and possible next steps.\n\n---\n\n## What I Found: Focus-Jumping Bug Is Widespread\n\nPeople have reported almost exactly your problem:\n\n- On iPhones updated to **iOS 26**, many VoiceOver users say the focus **jumps back to the top of the page** while reading \u2014 especially when using Apple Books. ([reddit.com](https://www.reddit.com/r/Blind/comments/1osyzkh?utm_source=openai))  \n- Others describe the focus cursor wandering or regressing unexpectedly across the system and in various apps. ([mail.applevis.com](https://mail.applevis.com/forum/ios-ipados/voiceover-focus-regressions-ios-26?utm_source=openai))  \n- Within Apple Books, a bug reported in the iOS 27 beta (but likely rooted in iOS 26 changes) causes the app to keep reading the *first page of a chapter*, even after turning the page. It appears that VoiceOver continues to read the same page\u2019s content, even though visually the book moves forward. ([atlas-entry.applevis.com](https://atlas-entry.applevis.com/comment/213269?utm_source=openai))  \n\nSo this is not just a one-off annoyance\u2014it\u2019s being experienced by many people, particularly after updating to iOS 26 or 26.x.  \n\n---\n\n## Why It Happens (Probable Causes)\n\nWhile there\u2019s no full public fix yet, here are what users and developers suspect are underlying issues:\n\n- Changes in how VoiceOver handles focus or active item detection in iOS 26 are causing delays or mistaken resets of focus.  \n- Layout/rendering changes in Books (or in text\u2010flow after a page turn) may not notify VoiceOver correctly, so the cursor loses track or stays stuck on older content.  \n- If the reading involves images, headers, or formatting like double-page layouts, VoiceOver often misinterprets where focus should be, which can trigger jumping.  \n\n---\n\n## What You Can Try Right Now (Workarounds)\n\nUntil Apple fixes it, these community-suggested workarounds might help reduce how often it happens:\n\n1. **Lower text complexity**  \n   Use books with simpler formatting\u2014fewer images, simpler layouts, fewer columns or double-page spreads.\n\n2. **Portrait orientation**  \n   Especially on iPads but sometimes helpful on phones\u2014books with two-page layouts are more likely to confuse focus. Taking it into \u201cportrait\u201d may force single column page layout. ([applevis.com](https://www.applevis.com/forum/ios-ipados/voiceover-skips-text-apple-boox-ipad?utm_source=openai))  \n\n3. **Ensure your lock-out timer is as long as possible**  \n   Longer time before sleep or lock helps reduce disruptions that might trigger focus loss.\n\n4. **Try adjusting Braille settings**  \n   In VoiceOver settings, sometimes settings like whether the braille display \u201cfollows\u201d the VoiceOver cursor or whether you use word wrap or certain routing behavior can affect how well focus stays in place.  \n\n5. **Restart Books app / device**  \n   Occasionally, closing Books and reopening helps reset focus. Rebooting the phone helps too, but tends to be temporary relief.  \n\n6. **Provide feedback to Apple (and report via Bug Reporter)**  \n   The more reports they get, the more likely this bug gets higher priority. Include details: iOS version, device model, when exactly the focus jumps (after page turns, after idle, etc.), whether with speech off, and the braille model.  \n\n---\n\nIf you'd like, I can look up whether the *latest update* (iOS 26.x or iOS 27 beta) includes a fix for your particular issue\u2014and show some links where you can see community feedback specific to your phone model. Would you prefer me to pull that together?"
    },
    {
        "role": "user",
        "content": "Does%20Braille%20Access%20Mode%20on%20the%20iPhone%20support%20multiline%20displays"
    },
    {
        "role": "assistant",
        "content": "No \u2014 Braille Access Mode on the iPhone *currently* does *not* support multiline displays (like two-line or more refreshable braille displays) for the Braille Access menus. That\u2019s what both Apple\u2019s documentation and community reports indicate. Below is a full breakdown with sources.\n\n---\n\n## What Apple Says\n\n- The \u201cAccessibility\u201d features page confirms that Apple *devices* support multiline text braille displays when using VoiceOver. ([apple.com](https://www.apple.com/accessibility/features/?utm_source=openai))  \n- However, in Apple\u2019s article on \u201cUse Braille Access with a braille display,\u201d there\u2019s *no mention* of multiline output being supported in **Braille Access menus**. The instructions assume a standard one-line (or single-line) display. ([support.apple.com](https://support.apple.com/guide/iphone/use-braille-access-with-a-braille-display-iph5953d3c7a/27/ios/27?utm_source=openai))  \n\n---\n\n## What the Community Reports\n\n- Users have specifically pointed out that multiline display support *isn\u2019t available* in Braille Access's menu interface, even when using displays that *can* handle multiple lines. For example, Dot Pad, Monarch, Orbit Slate, etc. ([applevis.com](https://www.applevis.com/comment/206553?utm_source=openai))  \n- The suggestion thread on AppleVis states clearly: \u201cthis lack of multi-line support for Braille Access is not available on any multi-line displays\u2026.\u201d ([applevis.com](https://www.applevis.com/comment/206553?utm_source=openai))  \n\n---\n\n## What *Does* Work / What *Is* Supported\n\n- Multiline braille displays *are* supported under VoiceOver (outside of Braille Access menus). When reading text in apps, VoiceOver can output across multiple lines. ([apple.com](https://www.apple.com/accessibility/features/?utm_source=openai))  \n- In Braille settings you can adjust options like Word Wrap, Item Overview, etc., but those relate to text reading in VoiceOver, not to the Braille Access launcher/menu. ([uw-product.cc](https://uw-product.cc/_/https/support.apple.com/guide/iphone/use-a-braille-display-iph73b8c43/ios?utm_source=openai))  \n\n---\n\nIf you want, I can check if there are any upcoming betas or feature plans that say multiline support *will* be added to Braille Access \u2014 just in case."
    },
    {
        "role": "user",
        "content": "best%20way%20to%20read%20a%20book%20from%20bookshare%20using%20JAWS"
    },
    {
        "role": "assistant",
        "content": "Here are best practices and step\u2010by\u2010step tips for reading Bookshare books with **JAWS**, optimized to keep your workflow smooth and accessible. I\u2019ll cover which file formats work best, how to set preferences, and how to navigate content using JAWS efficiently.\n\n---\n\n## Formats Bookshare Offers & Which Ones Work Best with JAWS\n\nBookshare provides several download/read formats:  \n- EPUB 3.0 (text)  \n- DAISY (text or audio)  \n- MP3 (audio)  \n- Braille Ready Format (BRF)  \n- Microsoft Word (DOCX) ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/what-format-are-bookshare-books-available-in?utm_source=openai))\n\nFor use with JAWS, the two most practical formats are:  \n\n1. **Microsoft Word (DOCX)** \u2013 Highest compatibility. JAWS handles Word docs well, including navigation via headings, bookmarks, find page, etc. ([perkins.org](https://www.perkins.org/resource/bookshare-books-read-using-microsoft-word-jaws/?utm_source=openai))  \n2. **DAISY\u2020 Text Formats** \u2013 Also very good if you want to use structured navigation by chapter/title sections, especially using DAISY text mode. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/what-format-are-bookshare-books-available-in?utm_source=openai))\n\n*(\u2020Note: DAISY Audio is less ideal if you want to browse text, because it\u2019s just audio.)*\n\n---\n\n## Step by Step: Setting Up & Using DOCX with JAWS\n\nHere\u2019s a workflow many users found effective:\n\n1. **Set your Download Preferences** in Bookshare to default to Word (DOCX) format. That ensures most books will arrive in a format that's easy for JAWS. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/how-can-i-modify-download-preferences?utm_source=openai))  \n2. **Download the book**, unzip if needed. The DOCX files sometimes come in multiple volumes. ([perkins.org](https://www.perkins.org/resource/bookshare-books-read-using-microsoft-word-jaws/?utm_source=openai))  \n3. **Open with Microsoft Word**. If you get a message about \u201cProtected View,\u201d enable editing. JAWS works more smoothly that way. ([perkins.org](https://www.perkins.org/resource/bookshare-books-read-using-microsoft-word-jaws/?utm_source=openai))  \n4. **Using JAWS navigation tools** inside Word:\n\n   - **Headings (H key)**: Use headings navigation if the book has proper heading markup (for chapters, sections). The JAWS Headings List can help jump directly. ([perkins.org](https://www.perkins.org/resource/bookshare-books-read-using-microsoft-word-jaws/?utm_source=openai))  \n   - **Find (Ctrl-F)** to jump to a chapter name, page number (if indicated), or other visible marker. ([perkins.org](https://www.perkins.org/resource/bookshare-books-read-using-microsoft-word-jaws/?utm_source=openai))  \n   - **Resume Reading (Shift+F5)** if you\u2019re returning to where you left off. Or use \u201cResume Reading\u201d buttons if available. ([perkins.org](https://www.perkins.org/resource/bookshare-books-read-using-microsoft-word-jaws/?utm_source=openai))  \n\n5. **Adjust settings for better reading**:\n\n   - Font size, line spacing, and contrast in Word itself if needed.  \n   - Customize JAWS verbosity and navigation settings, so it reads headings, lists, images alt-text as desired.  \n\n---\n\n## Using DAISY Text with JAWS\n\nIf for some reason DOCX isn\u2019t available or doesn\u2019t suit you, DAISY text is a good fallback.\n\n- Download DAISY Text format from Bookshare.  \n- Open with a DAISY-compatible reading application or tool that works with screen readers.  \n- Use JAWS to navigate via headings or via the DAISY navigation panel if the reader supports that.\n\n---\n\n## What to Avoid or Be Wary Of\n\n- Books that are only **DAISY Audio or MP3** won\u2019t allow you to browse text\u2014navigation is much more limited.  \n- Sometimes the document comes in *multiple volumes* without clear labeling; you\u2019ll need to check file names to know where to pick up between volumes. ([perkins.org](https://www.perkins.org/resource/bookshare-books-read-using-microsoft-word-jaws/?utm_source=openai))  \n- Formatting inconsistencies\u2014some Word books may lack headings or proper structure, which hampers navigation.  \n\n---\n\n## Bonus Tips for Efficient Reading\n\n- If you often switch devices, **use Bookshare Reader (web or mobile)** to access books and then switch to Word downloads for offline study. Reading positions are synced across devices. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/how-do-i-use-bookshare-reader-for-mobile?utm_source=openai))  \n- Keep a notebook or digital note to mark where you left off or important bookmarks within books, in case you switch formats.  \n- If reading academic material, check whether math content is formatted in MathML in EPUB or Word to make sure JAWS announces it properly. Sometimes it's not correctly formatted. ([reddit.com](https://www.reddit.com/r/Blind/comments/m0te7c?utm_source=openai))  \n\n---\n\nIf you tell me which device you're using (Windows version, Word version), or whether your goal is reading textbooks vs fiction, I can suggest more customized keystroke shortcuts or workflow tweaks."
    },
    {
        "role": "user",
        "content": "anything%20I%20should%20know%20about%20reading%20with%20DotPad%20X%20and%20docx%20files%20from%20bookshare%20and%20jaws"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s what to know when reading Bookshare **DOCX** files with **Dot Pad X** and **JAWS**\u2014tips, features, limitations, and settings that make for the best experience.\n\n---\n\n## About Dot Pad X & JAWS: Key Specs\n\n- The Dot Pad X is a multiline braille display paired with a tactile graphics overlay, effectively giving users real-time tactile access to both **text** and **images/graphs**. ([dotincorp.com](https://www.dotincorp.com/en/product/dotpadx?utm_source=openai))  \n- Under Windows with JAWS, it supports multiline braille, table and spreadsheet navigation, and multiple \u201csplit view\u201d modes. ([freedomscientific.com](https://www.freedomscientific.com/webinars/dot-pad-x-and-jaws-expanding-opportunities-with-multiline-braille/?utm_source=openai))  \n- You can use a layout with up to **8 lines**, each having 20 cells; plus a dedicated tactile graphics display area of 300 cells. ([device.report](https://device.report/manual/18928585?utm_source=openai))  \n\n---\n\n## Using Bookshare DOCX Files with Dot Pad X + JAWS: What Works Well\n\nDOCX is arguably the best format from Bookshare for structured reading and editing. Here\u2019s how Dot Pad X + JAWS makes the most of that:\n\n- **Rich Document Structure**: Properly formatted DOCX books with headings, lists, tables, images, captions, etc., translate well. JAWS will allow you to navigate via headings, object navigation (e.g. images, links), and jump between elements\u2014then Dot Pad X can display several lines for context.  \n- **Tables & Spreadsheets**: When embedded in a DOCX, tables are more navigable. Dot Pad X\u2019s multiline support improves how much of a table you see without constant panning. ([dotincorp.com](https://www.dotincorp.com/en/service/sr?utm_source=openai))  \n- **Split Braille Views**: Use multiple lines to see more content in context\u2014large sections, page progress, or even side-by-side content (e.g. comparing text while reviewing notes) is made more efficient. ([device.report](https://device.report/manual/18928585?utm_source=openai))  \n\n---\n\n## Setup & Workflow Tips\n\nTo get the best experience:\n\n1. **Enable Dot Pad X in JAWS**  \n   - Add the device in Braille Basic Settings: ALT+O \u2192 Options \u2192 Braille \u2192 Add Display \u2192 select \u201cDot Pad,\u201d etc. A restart of JAWS is required. ([manuals.plus](https://manuals.plus/m/71156c4c9d6b53b17d492d2580bde7a14aadd14372ecb655ce4f6a707e1a16fd_optim.pdf?utm_source=openai))  \n\n2. **Choose the Right Display Mode**  \n   - Use multiline mode with JAWS Split Braille. Dot Pad X supports dividing content into multiple views/regions so you can see more of the document at once. ([device.report](https://device.report/manual/18928585?utm_source=openai))  \n   - If dealing with images (figures, math), ensure the graphics-to-braille conversion or tactile graphics view is active, so diagrams show up in the graphics area. ([dotincorp.com](https://www.dotincorp.com/en/product/dotpadx?utm_source=openai))  \n\n3. **PDFs vs. DOCX**  \n   - If a book is only available as a PDF (or contains pages scanned), converting to Word can help but may introduce layout issues. Bookshare\u2019s DOCX version usually preserves most text structure unless pages are images. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/what-format-are-bookshare-books-available-in?utm_source=openai))  \n\n4. **Math & Equations**  \n   - DOCX versions sometimes embed math as objects/images. If they\u2019re converted to MathML or accessible markup, JAWS + Dot Pad X handle them better. Otherwise, tactile graphics and the graphics panel may show the equation visually/tactilely. ([braillists.org](https://www.braillists.org/uncategorised/from-dot-watch-now-jaws-dot-pad-x-webinar/?utm_source=openai))  \n\n5. **Font Sizes & Styles**  \n   - If the DOCX uses small text or tight line spacing, increasing font size or line spacing helps improve comprehension in Braille. It often helps to tweak settings in Word before reading.  \n\n---\n\n## Things to Watch Out For / Limitations\n\n- **Formatting Gaps**  \n  If headings, captions, or alt texts are missing, navigation will suffer\u2014even if Dot Pad X is capable of multiline, you need the structure.  \n\n- **Large Documents**  \n  Very long books (many images, many pages) may load slowly or feel bulky. Sometimes it helps to split into smaller volumes or chapters.  \n\n- **Graphic/Image Quality**  \n  Tactile representation can lose detail. Fine images, complex math diagrams may be harder to interpret with the fidelity you\u2019d see visually.  \n\n- **Switching Between Modes**  \n  Moving between multiline and single-line, graphics-enabled vs not, may require button combinations or menu navigation on the Dot Pad X. Familiarize yourself with the F-keys and panning keys. ([device.report](https://device.report/manual/18928585?utm_source=openai))  \n\n- **Device Critical Updates**  \n  Keep firmware/software up to date for Dot Pad X and the latest version of JAWS, since support for tactile graphics, table layout, and multiline features have improved recently. ([linkedin.com](https://www.linkedin.com/posts/dotinc_dotpad-braille-tactilegraphics-activity-7504448885667426305-e7uM?utm_source=openai))  \n\n---\n\nIf you like, I can pull up a comparison of another device and whether it handles Bookshare DOCX + JAWS differently, just so you have backup options. Do you want that?"
    }
]