[
    {
        "role": "user",
        "content": "Is%20the%20PC%20BookShare%20app%20easy%20to%20use%20with%20JAWS%3F"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s a summary of how well Bookshare works with JAWS, including strengths, challenges, and tips. By \u201cPC BookShare app,\u201d I assume you mean the Bookshare Reader in a web browser or downloaded Bookshare content \u2013 if you meant a different desktop app, let me know and I\u2019ll cover that too.\n\n---\n\n## \u2705 What *is* Bookshare\u2019s setup and its accessibility goals\n\n- **Bookshare Reader for Web** is the primary tool for reading on PCs and laptops. It runs in modern browsers (Chrome, Edge, Firefox, etc.), and lets users search for books, download, or read directly in the browser. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/how-do-i-use-bookshare-reader-on-a-web-browser/?utm_source=openai))  \n- Bookshare offers downloads in several accessible formats: EPUB, Word (DOCX), DAISY, MP3, BRF (Braille Ready Format), etc., so users have flexibility depending on what works best with their assistive tech. ([perkins.org](https://www.perkins.org/resource/reading-bookshare-titles-with-microsoft-word/?utm_source=openai))  \n- The accessibility statement from Bookshare states that the platform strives to meet WCAG 2.2, AA level. That suggests a strong baseline for things like keyboard navigation, alt text, etc. ([bookshare.org](https://www.bookshare.org/accessibility?utm_source=openai))  \n\n---\n\n## \ud83d\udca1 How Bookshare works with JAWS\n\nHere are what users (especially those using JAWS) typically report:\n\n### Strengths\n\n1. **Web navigation and reading**  \n   - Using Bookshare Reader in a browser with JAWS generally works well. Headings, links, buttons are accessible, so you can log in, search, select \u201cRead Now,\u201d and start reading with text-to-speech. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/how-do-i-use-bookshare-reader-on-a-web-browser/?utm_source=openai))  \n   - Bookshare\u2019s Word (DOCX) downloads are a strong option. They allow full customization\u2014font, line spacing, color, etc.\u2014and JAWS handles Word documents fluently. ([perkins.org](https://www.perkins.org/resource/reading-bookshare-titles-with-microsoft-word/?utm_source=openai))  \n\n2. **File-format flexibility**  \n   - If the Web Reader isn\u2019t ideal, you can download the book in EPUB, Word, DAISY (for audio or text), or even Braille-ready file formats, then open them in whatever reader software you prefer. Many folks using JAWS prefer Word or DAISY or other external readers. ([perkins.org](https://www.perkins.org/resource/reading-bookshare-titles-with-microsoft-word/?utm_source=openai))  \n\n3. **Syncing experience**  \n   - The \u201cRead Now\u201d Web Reader tracks your position so if you switch to the mobile app later, you can pick up where you left off. That\u2019s helpful when moving between devices. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/how-do-i-use-bookshare-reader-on-a-web-browser/?utm_source=openai))  \n\n### Challenges / Areas that may need work\n\n1. **Voice quality & TTS limitations**  \n   - The voices offered when reading in the browser depend on what the browser or operating system supports. They may feel more robotic or less smooth than some high-end human-read audiobooks. Using Microsoft Edge\u2019s \u201cNatural\u201d voices or installing premium voices helps, but it\u2019s based on what\u2019s available by the platform. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/how-to-hear-higher-quality-voices-for-bookshare-books?utm_source=openai))  \n\n2. **Navigation complexity in some interfaces**  \n   - While Bookshare is committed to WCAG, some individual pages can be dense. Navigating long lists of books or browsing detailed pages might require patience. Some older/advanced features might be less obvious to find via screen reader.  \n   - Some specific parts\u2014like adding a book to a reading list\u2014were reported to be confusing in older screen readers, though users noted that this problem *did not* occur with JAWS. ([davidgoldfield.wordpress.com](https://davidgoldfield.wordpress.com/2014/08/02/using-bookshares-add-to-reading-list-feature-with-window-eyes/?utm_source=openai))  \n\n3. **Feature availability**  \n   - The Web Reader has a subset of features compared to native mobile apps or full download formats. Also things like annotation tools, highlighting, or page-based navigation (versus chapter or scroll view) might feel less smooth, depending on the browser and content layout.  \n\n---\n\n## \ud83d\udd27 Tips to Improve Experience Using Bookshare with JAWS\n\nHere are what many users do to get better performance:\n\n- Use **Microsoft Edge** on Windows, since it supports higher-quality \u201cNatural\u201d voices and tends to integrate better with system speech. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/how-to-hear-higher-quality-voices-for-bookshare-books?utm_source=openai))  \n- Download in **DOCX (Word)** format when possible if you plan on reading extensively, to use Word\u2019s built-in navigation (headings, find commands, etc.) which JAWS supports well. ([perkins.org](https://www.perkins.org/resource/bookshare-books-read-using-microsoft-word-jaws/?utm_source=openai))  \n- If reading in Web Reader, turn off unnecessary extensions which may interfere with screen reader behavior. Also check accessibility settings in the reader (contrast, font, layout) to optimize display mode. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/how-do-i-use-bookshare-reader-on-a-web-browser/?utm_source=openai))  \n- Practice using JAWS navigation commands: using heading navigation, virtual cursor mode, tabs, F6 to jump between frames or sections in Word, etc. These help speed up navigation significantly. Many Bookshare users share workflows with Word or DAISY using JAWS. ([perkins.org](https://www.perkins.org/resource/reading-bookshare-titles-with-microsoft-word/?utm_source=openai))  \n\n---\n\n## \u2696\ufe0f Bottom line\n\nYes\u2014Bookshare is generally *easy to use* with JAWS on a PC, especially for basic tasks like downloading books, navigating, reading text aloud, etc. While a few parts might require more effort (voice quality, navigating dense pages, or complicated interface bits), for people already comfortable with JAWS and accessible formats, it works quite well.\n\nIf you want, I can test current usability for a specific task\u2014like finding a title, reading a page aloud, or navigating chapters\u2014and give you a step-by-step experience using JAWS with Bookshare. Would that be helpful?"
    },
    {
        "role": "user",
        "content": "I%20have%20difficulty%20with%20BookShare%20on%20the%20iPhone.%20Do%20other%20users%20report%20this%3FIs%20BookShare%20optimized%20for%20Windows%20and%20better%20usedon%20a%20PC%3F"
    },
    {
        "role": "assistant",
        "content": "Yes\u2014many Bookshare users report having **more difficulty** using Bookshare on iPhones than on Windows PCs, and there is evidence that Windows (or the PC/Desktop + web-browser environment) tends to provide a smoother, more accessible experience. Below is a breakdown of what users are saying, how Bookshare supports platforms, and what advantages PCs tend to offer over iPhones for people using assistive tech like VoiceOver.\n\n---\n\n## \ud83d\udd0d What users report about using Bookshare on iPhones\n\n1. **Problems with VoiceOver and navigation glitches**  \n   - Some users say that while using VoiceOver on iPhone, paragraphs are sometimes repeated, or navigation jumps unexpectedly\u2014especially when there are illustrations or complex page layouts. ([reddit.com](https://www.reddit.com/r/Blind/comments/1irpgey?utm_source=openai))  \n   - Others report that some books don\u2019t show download options in certain partner apps (like Voice Dream Reader) from their iPhone, although they can be downloaded via a computer. ([mail-archive.com](https://www.mail-archive.com/viphone%40googlegroups.com/msg239788.html?utm_source=openai))  \n\n2. **Partner app limitations**  \n   - There have been complaints that certain partner apps (e.g. Voice Dream Reader, EasyReader) may have bugs or missing functionality when accessing Bookshare content on iPhone\u2014either books won\u2019t always download, or features like control over voices / reading formats are more limited. ([reddit.com](https://www.reddit.com/r/Blind/comments/1io49y0?utm_source=openai))  \n\n3. **Preference for other tools or manual workarounds**  \n   - Some users avoid the Bookshare app on iPhone altogether and instead download books via PC, then transfer them or open them with apps like Apple Books or Voice Dream. ([reddit.com](https://www.reddit.com/r/Blind/comments/1mzohde?utm_source=openai))  \n   - Ease of accessing book formats (like EPUB, Word) and navigating fully formatted text is better on PC for many. ([reddit.com](https://www.reddit.com/r/Blind/comments/1mzohde?utm_source=openai))  \n\n---\n\n## \ud83d\udee0\ufe0f How Bookshare supports iPhone vs PC\n\n- According to Bookshare\u2019s official site, their **Bookshare Reader app** is available for iOS and Android, in addition to web browsers and PCs. ([bookshare.org](https://www.bookshare.org/help-and-learning-articles/what-reading-tools-work-with-bookshare?utm_source=openai))  \n- They also list **partner apps** that integrate Bookshare content, and many are iOS-compatible (e.g. Voice Dream Reader). ([bookshare.org](https://bookshare.org/help-and-learning-articles/how-do-i-read-books-with-voice-dream-reader?utm_source=openai))  \n- Bookshare follows Web Content Accessibility Guidelines (WCAG 2.2, level AA) for its web properties and strives to support screen readers, braille displays, etc. ([bookshare.org](https://www.bookshare.org/accessibility?utm_source=openai))  \n\n---\n\n## \u2696\ufe0f PC / Windows tends to be better for users relying on assistive tech\n\nHere are reasons users generally find PCs to offer a more reliable experience:\n\n| Feature | Why PC / Web / Windows is Often Superior |\n|---------|---------------------------------------------|\n| **Stable navigation** | Web-browser versions on a PC offer more predictable behavior with keyboard input, headings navigation, and fewer forced layout changes. VoiceOver or TalkBack on phones can be more inconsistent with page breaks, images, or display resizing. |\n| **Format flexibility** | On a PC, you can download multiple formats (EPUB, Word, DAISY, MP3, etc.) and use desktop tools or readers that work nicely with these formats and assistive tech. |\n| **Screen size and layout** | A larger screen reduces layout clutter, makes buttons and headings more accessible, and generally leads to fewer navigation issues. |\n| **Voice quality and system voices** | PCs often allow installing more natural TTS voices or taking advantage of system voices that work better than what's available or allowed in iOS apps. |\n| **Bug / feature lag** | Some users find iOS apps are slower to receive fixes or features, or certain features may be limited due to Apple\u2019s restrictions. |\n\n---\n\n## \ud83c\udf1f What does this mean for you?\n\nYou\u2019re definitely not alone in being frustrated. Many users find Bookshare more usable on a PC, especially for intensive reading, downloads, and formatting control. If you need smoother navigation and fewer glitches, a PC + browser + downloaded formats tends to be more reliable.\n\n---\n\nIf you want, I can pull up recent user forum posts (2025-2026) and show specific tips or workaround steps that folks successfully use on iPhone with Bookshare. Would you like me to do that?"
    }
]