[
    {
        "role": "user",
        "content": "So%20in%20the%20latest%20developter%20beat%20for%20IOS%20Braille%20Screen%20input%20was%20broken%20I%20have%20reported%20it%20in%20the%20feeed%20back%20app%20but%20is%20there%20anything%20online%20about%20the%20way%20it%20could%20be%20fixed%20really%20soon%2C%20I%20mean%20is%20a%20sighted%20person%20went%20ot%20typ%20and%20discovered%20they%20had%20half%20a%20keyboard%20there%20would%20be%20uproar%20but%20if%20the%20blind%20have%20an%20issue"
    },
    {
        "role": "assistant",
        "content": "There have been several recent reports from users about Braille Screen Input (BSI) issues in iOS betas, but I couldn\u2019t find any concrete public fixes or coming updates that officially address the problem you mentioned. Below is what I've found, what people are saying might work (or at least help), and what you can do to try to speed up a resolution.\n\n---\n\n### \ud83d\udd0d What\u2019s going on based on reports\n\n- Users on **iOS 26 Developer Beta 1** report that the *activation gestures* for Braille Screen Input (like double-tap, or the usual way to trigger BSI) aren't working. ([applevis.com](https://www.applevis.com/forum/apple-beta-releases/warning-those-users-who-are-ios-26-developer-beta-1-braille-screen-input?utm_source=openai))  \n- Some users report that certain braille input gestures result unexpectedly in rotor activation (the feature that lets you swipe to select VoiceOver options). ([applevis.com](https://applevis.com/comment/202942?utm_source=openai))  \n- Others say that words or parts of them get deleted during input, especially in native keyboard/Braille input fields. ([reddit.com](https://www.reddit.com/r/Blind/comments/1t3n9aj/braille_screen_input_on_iphone_broken_since_last/?utm_source=openai))  \n\nThese issues are discussed in forums (like AppleVis and Reddit), not official Apple messages. That means Apple hasn't (as of the latest info I found) confirmed when the fix will be rolled out.\n\n---\n\n### \u26a0\ufe0f Are there any reliable workarounds?\n\nSome users have found temporary tricks that help until Apple issues a patch:\n\n- **Double-tap to edit a text field first**: After you do that, the activation gestures for BSI sometimes start working again. ([applevis.com](https://www.applevis.com/forum/apple-beta-releases/warning-those-users-who-are-ios-26-developer-beta-1-braille-screen-input?utm_source=openai))  \n- **Reset VoiceOver settings**: Some say that resetting only VoiceOver (not doing a full device reset) has helped with strange behavior. ([applevis.com](https://applevis.com/comment/202942?utm_source=openai))  \n\nThese are not guaranteed fixes, but might help reduce the frustration in the meantime.\n\n---\n\n### \ud83d\udd52 Will this be fixed *soon*?\n\nHard to say for sure. Since lots of users have reported the issue via forums and feedback channels, it seems likely Apple is aware. But I didn\u2019t find any recent release notes or developer notes explicitly confirming a fix in the next beta or update. If anything, the discussions suggest people have been waiting for a resolution for several beta cycles. ([applevis.com](https://www.applevis.com/forum/apple-beta-releases/warning-those-users-who-are-ios-26-developer-beta-1-braille-screen-input?utm_source=openai))\n\n---\n\n### \u2705 What you *can* do now to help and speed things up\n\n1. **Continue submitting feedback** via Feedback Assistant. The more reports Apple gets, especially with very specific details, the likelier they\u2019ll prioritize a fix.\n\n2. **Include detailed info** when you report:\n   - iPhone/iPad model and its generation\n   - Exact iOS version (developer beta build number)\n   - Exactly what gesture or action isn\u2019t working\n   - Whether it\u2019s happening in text fields only, or everywhere\n   - Whether any workaround you tried helped\n\n3. **Try different braille tables or contracted vs uncontracted braille**: Some users report changes depending on which braille layout/table they\u2019re using. Could be that switching temporarily helps. ([applevis.com](https://www.applevis.com/forum/apple-beta-releases/warning-those-users-who-are-ios-26-developer-beta-1-braille-screen-input?utm_source=openai))\n\n4. **Watch beta release notes**: Whenever Apple releases a new beta, check the Accessibility section (VoiceOver/Braille) to see if the bug is acknowledged.\n\n---\n\nIf you like, I can try to comb through Apple\u2019s latest (beta) documentation and developer notes to see if anything has been officially announced about a fix. Want me to pull that together for you?"
    },
    {
        "role": "user",
        "content": "no%20this%20is%20in%20ios%2027%20neta%20is%20there%20another%20way%20easier%20to%20report%20feed%20back%20on%20the%20web%20or"
    },
    {
        "role": "assistant",
        "content": "Yes \u2014 besides using the Feedback Assistant app on your device, there *are* other ways to report feedback to Apple \u2014 some easier, some less formal. Here are the alternatives and how to use them:\n\n---\n\n### \ud83d\udce7 Email Apple\u2019s Accessibility Feedback Team\n\nIf the issue is specifically about accessibility (like Braille Screen Input), you can email the Accessibility Feedback team directly. This is good for raising awareness, especially if the Feedback Assistant isn\u2019t working well for your situation. ([support.apple.com](https://support.apple.com/en-la/111749?utm_source=openai))\n\n**Email address:**  \n`accessibility@apple.com` ([support.apple.com](https://support.apple.com/en-la/111749?utm_source=openai))\n\nIn your email, you\u2019ll want to include the same kind of details you\u2019d use in a Feedback Assistant report:\n\n- Your device model and iOS version (including beta build if applicable, such as iOS 27 beta).  \n- Step-by-step description of exactly what happens (and how to reproduce it).  \n- What you expect to happen instead.  \n- Any workarounds you\u2019ve tried (e.g. double-tap, switching braille tables, etc.).  \n- Any logs or screencaptures that might show the issue.  \n- If possible, note whether the issue persists across restarts or after any updates.\n\n---\n\n### \ud83c\udf10 Use Apple\u2019s Web Feedback Form (Product Feedback)\n\nApple offers a general *Product Feedback* webpage where you can send feedback about Apple products and software. While this is less formal than Feedback Assistant, it still goes to Apple, and helps show how many people are having the issue. ([apple.com](https://www.apple.com/feedback/?utm_source=openai))\n\n**Steps:**\n\n1. Go to the Apple Product Feedback page: `apple.com/feedback` ([apple.com](https://www.apple.com/feedback/?utm_source=openai))  \n2. Select **iPhone / iPad / iOS** (whichever is relevant).  \n3. Fill out the fields \u2014 subject, description, OS version, etc.  \n4. Include that this is a beta issue (iOS 27) so they know it's pre-release.  \n\n---\n\n### \u260e\ufe0f Phone or Chat with Accessibility Support\n\nIf you want direct feedback or need help, contacting Apple\u2019s Accessibility Support by phone or chat can also work. They may not handle bugs like a software feedback tool, but they can direct your case to the correct internal team and escalate it. ([support.apple.com](https://support.apple.com/en-la/111749?utm_source=openai))\n\n**In the U.S.,** the phone number is: 1-877-204-3930 (English only) ([support.apple.com](https://support.apple.com/en-la/111749?utm_source=openai))\n\n---\n\nIf you want, I can draft a ready-to-send template email for the Accessibility Feedback Team (or feedback form) that includes all the info they\u2019ll likely need \u2014 so you won\u2019t have to build it from scratch. Do you want me to put that together?"
    }
]