Hello again speaking of this M Braille app, on iOS we can make a in app purchase within this app, and we can set this as a default keyboard method however I don't like the layout of this app. I prefer the braille screen input. The typing layout is very odd with MBraille. One more thing, I will not pay for this. I don't see the point.
Cheers. Join our WhatsappGroups for Apple users And Android users, We provide assistance from an accessibility point of view. to join our Groups kindly contact me on+61424787863. or MRNitin on +919725661243. . Sincerely, Sagar Sent from my iPhone > On 29 Aug 2015, at 13:21, Shek Mohammad Ali <[email protected]> wrote: > > that is the limitation of m braille. > ----- Original Message ----- From: "sagar sagar" <[email protected]> > To: "Dedicated AccessIndia list for discussing accessibility of mobile > phonesand Tabs." <[email protected]> > Sent: Friday, August 28, 2015 6:40 PM > Subject: Re: [Mobile.AI] Braille Screen input on iOS. > > >> hai again, >> as far as my understanding is concerned what I gathered from your previous >> message as it's an app not a keyboard which means we cannot define this as a >> default input method. >> Cheers. >> >> Join our WhatsappGroups for Apple users And Android users, We provide >> assistance from an accessibility point of view. to join our Groups kindly >> contact me on+61424787863. or MRNitin on +919725661243. >> >> . >> Sincerely, >> Sagar >> >> >> >> >> Sent from my iPhone >> >>> On 28 Aug 2015, at 19:15, sanjay <[email protected]> wrote: >>> >>> Of course. I used it. What I meant by my previous mail was that we cannot >>> use it as default keyboard. Therefore, we cannot use MBraille for typing >>> facebook, whatsappp messages and for many other purposes not excluding >>> for typing passwords. >>> >>> ----- Original Message ----- From: "Sagar" <[email protected]> >>> To: "Dedicated AccessIndia list for discussing accessibility of mobile >>> phonesand Tabs." <[email protected]> >>> Sent: Friday, August 28, 2015 11:45 AM >>> Subject: Re: [Mobile.AI] Braille Screen input on iOS. >>> >>> >>>> Hello Sanjay, >>>> just for your information MBraille is available for android also its a >>>> third party keyboard which lets you type in braille. >>>> kindly check the play store. >>>> hope this helps. >>>> cheers. >>>> >>>> Join our WhatsappGroups for Apple users And Android users, >>>> We provide assistance from an accessibility point of view. >>>> to join our Groups kindly contact me on+61424787863. >>>> or MRNitin on +919725661243. >>>> >>>> sencerely, >>>> Sagar. >>>> sent using OS X Mail. >>>> >>>> >>>> >>>>> On 27 Aug 2015, at 6:25 pm, sanjay <[email protected]> wrote: >>>>> >>>>> Good development indeed for Ios Gadgets. I still wonder why google is >>>>> not giving a default braille keypad option for android users. >>>>> ----- Original Message ----- From: "Sagar" <[email protected]> >>>>> To: "Dedicated AccessIndia list for discussing accessibility of mobile >>>>> phonesand Tabs." <[email protected]> >>>>> Sent: Thursday, August 27, 2015 2:08 PM >>>>> Subject: [Mobile.AI] Braille Screen input on iOS. >>>>> >>>>> >>>>>> Hey everyone, >>>>>> kindly see this useful article taken from AppleVis. >>>>>> >>>>>> hope this helps. >>>>>> >>>>>> In iOS8, you can write braille on your iOS device, similar to apps like >>>>>> MBraille or Braille Touch. The difference is that this is global, >>>>>> available anywhere you have a keyboard. No switching apps and pasting >>>>>> text, you simply use braille instead of the on-screen keyboard. If you >>>>>> prefer to listen, you can hear an audio demonstration of braille input >>>>>> in iOS8 here. >>>>>> <http://www.applevis.com/podcast/episodes/new-ios-8-braille-screen-input> >>>>>> While this new braille input system is a wonderful feature, it does have >>>>>> a few caveats you need to know about. Note that I assume you are already >>>>>> familiar with braille, and the basic VoiceOver gestures of swiping with >>>>>> one or more fingers and double tapping to activate items. >>>>>> >>>>>> Setting It Up >>>>>> Enabling Braille Screen Input >>>>>> When you first get iOS8, braille will not be available by default. You >>>>>> can easily enable it, though: open the Settings app, go to General, then >>>>>> Accessibility, then VoiceOver, then Rotor. Find the "Braille screen >>>>>> input" option and double tap to select it (if it is already selected for >>>>>> some reason, simply leave it alone). In the initial release of iOS8, >>>>>> this option is the very last one in the list. Once it is selected, you >>>>>> are set to start using braille input. Please note that moving this item >>>>>> around in your rotor will not affect its position, as it always appears >>>>>> to the right of whichever rotor item you are currently on. This makes it >>>>>> quick to switch to so you can starthtyping without needing to move >>>>>> through a bunch of rotor items first. >>>>>> >>>>>> Setting Your Default Code >>>>>> To choose the default braille table, contracted status, or 8 dot braille >>>>>> (iPad only), follow the below steps. Remember that you can change the >>>>>> code in use with a three-finger swipe right or left while you are using >>>>>> the on-screen braille keyboard; these instructions are to set the code >>>>>> used when you first switch to braille. >>>>>> >>>>>> Open Settings, then go to General, Accessibility, VoiceOver, Braille >>>>>> (note that this is not the Braille option in the rotor) >>>>>> Find the "Braille Screen Input" button, which will have the currently >>>>>> selected code after it. Double tap this button. >>>>>> You are now in a screen where all the available input codes are >>>>>> presented. Choose from "uncontracted 6 dot braille", "uncontracted 8 dot >>>>>> braille" (iPad only), or "contracted braille", then activate the "Back" >>>>>> button. >>>>>> Now that you've set your default input type, make sure the translation >>>>>> table is correct. I am in the United States, so I can't speak to how >>>>>> this will work in other locales. Here, we have both UEB, U.S. English >>>>>> (what many call Grade II), or UK English for contracted braille tables. >>>>>> The default seems to be UEB, what iOS calls "English (Unified)", which I >>>>>> prefer. Many people don't know UEB, though, and will want to change to a >>>>>> different option. Fortunately, doing so is simple. Note that this will >>>>>> set the braille translation table, which is not changed with the >>>>>> three-finger swipe gesture like contracted/uncontracted braille is. In >>>>>> other words, you can turn contractions on or off at any time, but the >>>>>> table used to interpret your contractions will remain set until you >>>>>> decide to change it by following the below steps. >>>>>> >>>>>> From VoiceOver's braille settings screen (see the previous section on >>>>>> setting your input code), choose "Braille Translation". >>>>>> The resulting screen lists all the available codes for your region. >>>>>> Simply double tap the one you want, and you're done. >>>>>> Typing Feedback >>>>>> Setting the amount of feedback you hear while typing braille is done the >>>>>> same way you'd set feedback for on-screen or bluetooth keyboards. >>>>>> Unfortunately, there is no setting for braille input only. >>>>>> >>>>>> From VoiceOver's settings screen, choose "Typing Feedback". >>>>>> Under the "Software Keyboards" heading, select the amount of feedback >>>>>> you want. Again, this affects both braille input and on-screen keyboards. >>>>>> Remember that, as discussed in another section, contracted braille does >>>>>> not honor any character echo settings, only words. >>>>>> >>>>>> Usage >>>>>> To use the braille keyboard, you must be on the home screen, on some >>>>>> HTML content (such as a webpage), or editing a text field. If any of >>>>>> these is true, turn your rotor to "braille screen input", which is >>>>>> nearly always just to the right of your current rotor selection. Your >>>>>> device will switch to landscape mode if it is in portrait, and you can >>>>>> begin. >>>>>> >>>>>> you will be told the input mode (see below), the type of braille in use >>>>>> (6 dot, 8 dot, or contracted), and the fact that your device is now in >>>>>> landscape mode. If you have VoiceOver set to speak hints, which is the >>>>>> default setting, you are also told which side your Home button is now on >>>>>> and "to calibrate braille dots, place the first three fingers of first >>>>>> your left hand, then your right, on the screen." This calibration step >>>>>> is not necessary--you can begin brailling straight away. To be honest, I >>>>>> have not yet discovered what calibration does, as there seems to be no >>>>>> difference if I calibrate or go right to typing. I have also found that >>>>>> VoiceOver soon stops speaking this calibration message, but that, by >>>>>> quickly pressing dots 4 5 6, then dots 1 2 3, you can calibrate at any >>>>>> time. Again, though, I haven't worked out just what purpose calibration >>>>>> serves. >>>>>> >>>>>> If the iOS device is relatively flat, such as on a table, it will >>>>>> default to "tabletop mode". On an iPhone 6 or smaller, this means that >>>>>> the dots are laid out in a sort of flattened V shape. For the iPhone 6 >>>>>> Plus, and any iPad, all six dots will be side by side. Anyone who has >>>>>> used a Perkins braille writer will find this arrangement very familiar. >>>>>> Also, I have tried this on an iPhone 6 (not the Plus), and could have my >>>>>> fingers almost side by side with no problem. Your milage may vary, >>>>>> though, depending on the size of your hands. The dot arrangement is a >>>>>> much easier straight line on iPads and the iPhone 6 Plus, making those >>>>>> devices very comfortable to type on. >>>>>> >>>>>> If your device is closer to being on its side, it will be in "screen >>>>>> away mode", with the dots along the two shorter edges of the screen. In >>>>>> this mode, hold your device with your thumbs on top, near the volume >>>>>> buttons, your pinkies on the opposite side, and your hands curved so the >>>>>> other three fingers of each hand rest on the screen, perpendicular to >>>>>> the long edges. It takes some practice, but you will eventually be able >>>>>> to use this mode without muffling the speaker (a definite possibility on >>>>>> the iPhone or iPod Touch) by relying on your fingers to steady your >>>>>> device, not your palms. >>>>>> >>>>>> One problem some people run into is getting Tabletop Mode into the >>>>>> correct orientation. Often, when it is first activated, the dots are >>>>>> flipped around, with dots 3 and 6 closest to you. To fix this, simply >>>>>> angle your device so it enters Away mode, but be sure the screen is >>>>>> facing toward you, not away from you as though you were going to type on >>>>>> it. Once you hear "Away mode" while the screen is facing you, put the >>>>>> device back into Tabletop Mode and you should find the orientation to >>>>>> now be correct. It may sound like a lot to go through, but it's really a >>>>>> quick rotation toward you and then flat again, and you'll hardly think >>>>>> about it after a while. >>>>>> >>>>>> In either mode, your index fingers are dots 1 and 4, your middle fingers >>>>>> are 2 and 5, and your ring fingers are 3 and 6. Some people may want to >>>>>> flip the dots as MBraille allows, so 1 and 4 are on the bottom instead >>>>>> of the top. At this time, though, that is not possible. >>>>>> >>>>>> Here are the gestures you can use while in braille input mode: >>>>>> >>>>>> one-finger swipe right: space >>>>>> one-finger swipe left: delete most recent character (you cannot swipe >>>>>> left and hold to keep deleting) >>>>>> one-finger swipe up/down: access typing suggestions, apps that match >>>>>> what you've typed if on a Home Screen, or move by the HTML element whose >>>>>> first letter you entered (webpages/HTML content only) >>>>>> two-finger swipe left: delete previous word (iOS8.3 or above). Note >>>>>> that, in contracted mode, this erases the last translated word along >>>>>> with anything you've typed but not yet translated; in six dot mode, it >>>>>> erases back to the previous space or new line since there's no >>>>>> translation to worry about. >>>>>> two-finger swipe right: new line >>>>>> two-finger swipe down: immediately translate current word (contracted >>>>>> mode only) >>>>>> two-finger scrub: exit Braille Screen Input mode >>>>>> two-finger rotor left/right: choose another rotor setting, which will >>>>>> exit Braille Screen Input >>>>>> three finger swipe left/right: toggle between contracted and >>>>>> uncontracted (called "six dot") braille (on iPads, eight dot braille is >>>>>> also an option) >>>>>> hold a finger on the screen: enter "explore mode", where you can move a >>>>>> finger around to find the different dots' positions >>>>>> Finding Apps With Braille >>>>>> Similar to the handwriting feature introduced in iOS7, you can use >>>>>> braille to search for apps. On any home screen, rotor to braille and >>>>>> begin typing the name of the app you want. As you type, VoiceOver will >>>>>> announce how many matches it has found. To browse them, flick up or down >>>>>> with a finger, then flick right with two fingers (the "enter" gesture) >>>>>> to open an app once you hear it. >>>>>> >>>>>> Note that the three-finger swipe left or right to change input grade >>>>>> does not work here. As far as I've been able to tell, you are in six-dot >>>>>> entry by default and cannot change that. >>>>>> >>>>>> Edit Fields >>>>>> As mentioned, braille input can be used anywhere an on-screen keyboard >>>>>> is present. However, the braille keyboard does not include any editing >>>>>> or selection commands except deleting by character or word, nor does it >>>>>> offer commands to review what you have written. For both of these >>>>>> functions, use the rotor or a two-finger scrub to exit braille input >>>>>> mode, then the normal VoiceOver gestures to review, select, or edit your >>>>>> text. >>>>>> >>>>>> The suggestions you get as you type are not the same as the suggestions >>>>>> offered by iOS8's new predictive typing feature. Instead, they are >>>>>> based, as far as I can tell, on common braille mistakes and standard >>>>>> misspellings. For instance, if you type "jug", one suggestion might be >>>>>> "dug", since j and d are one dot different; "tets" would offer a >>>>>> suggestion of "test", because you switched the last two characters.. >>>>>> This is both good and bad: it is nice to be able to quickly select the >>>>>> word you meant if you made a mistake instead of deleting the whole >>>>>> thing, but auto-complete would also be handy so you could fill longer >>>>>> words in faster. >>>>>> >>>>>> Remember that braille is only one option. There is nothing stopping you >>>>>> from writing something in braille, then switching back to the on-screen >>>>>> keyboard for a while. This may become essential if you want to access >>>>>> Emoji, or if there is a symbol you cannot figure out how to type in >>>>>> braille. It may also prove useful to take advantage of the afore >>>>>> mentioned auto-complete feature--you might find that faster than braille >>>>>> in some instances. The point is that you can use braille alongside, not >>>>>> instead of, on-screen keyboards if you like. >>>>>> >>>>>> Navigating Web Content >>>>>> If you are on a webpage, you can use braille input to move around. For >>>>>> example, type an h, and then flick down to move to the next heading, or >>>>>> up to move to the previous one. To exit braille and start reading from >>>>>> where you landed, just rotor left or right, or perform a two-finger >>>>>> scrub. In iOS8.3 and above, once you start editing a text field on a >>>>>> webpage, you can type as normal. In iOS8 through iOS8.2, there was a bug >>>>>> where typing in edit fields on webpages would fail; if you are seeing >>>>>> that problem, please update to the latest iOS version. >>>>>> >>>>>> Known Bugs >>>>>> iOS8's braille input is Apple's first try at offering system-wide >>>>>> braille, and it already feels quite solid. It has a few problems and >>>>>> missing features, but I find myself using it all the time despite the >>>>>> hiccups. Here's a list of the bugs I and others have found so far (this >>>>>> list is current as of iOS8.3): >>>>>> >>>>>> Key echo is currently not working if you use contracted braille. When I >>>>>> type in 6 dot, with my key echo set to "characters and words", I hear >>>>>> exactly that - the characters I type, and the words when I enter a white >>>>>> space or punctuation symbol. With contractions, though, only words are >>>>>> echoed. >>>>>> On very rare occasions, two dots may become flipped. For instance, I >>>>>> once had dot 2 appear where dot 1 should e, while dot 1 took dot 2's >>>>>> place. Several calibrations in a row seem to clear this up, and it has >>>>>> not happened to me since a single occurrence in iOS8.1, but it is >>>>>> something to check if you are seeing very odd results as you type. >>>>>> Conclusion >>>>>> This feature works very well overall, aside from the minor issues noted >>>>>> above. Having braille input available anywhere is a truly wonderful >>>>>> addition to iOS; use it for emails, your passcode, passwords, texts, >>>>>> searches… Anywhere you can type text, you can choose to do so in >>>>>> braille. In fact, I find myself able to use more complex passwords, >>>>>> because it is so much faster and easier to braille them than to use the >>>>>> on-screen keyboard. For more, take a look at Apple's official >>>>>> documentation on this topic, >>>>>> <http://help.apple.com/iphone/8/en.lproj/iph10366cc30.html>or my own >>>>>> wishlist for the next update to Braille Screen Input. >>>>>> <http://www.applevis.com/blog/braille-ios-opinion/ways-apple-could-make-ios8s-braille-input-even-better> >>>>>> What do you think of this feature? Are you having problems with it? Are >>>>>> there bugs or features I forgot to cover? Leave a comment, and let's >>>>>> talk about it! >>>>>> >>>>>> Join our WhatsappGroups for Apple users And Android users, >>>>>> We provide assistance from an accessibility point of view. >>>>>> to join our Groups kindly contact me on+61424787863. >>>>>> or MRNitin on +919725661243. >>>>>> >>>>>> sencerely, >>>>>> Sagar. >>>>>> sent using OS X Mail. >>>>>> >>>>>> >>>>>> >>>>>> -------------- next part -------------- >>>>>> An HTML attachment was scrubbed... >>>>>> URL: >>>>>> <http://accessindia.org.in/pipermail/mobile.accessindia_accessindia.org.in/attachments/20150827/25f895df/attachment.html> >>>>>> >>>>>> >>>>>> Search for previous postings at: >>>>>> http://www.mail-archive.com/[email protected] >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Mobile.accessindia mailing list >>>>>> [email protected] >>>>>> http://accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in >>>>>> >>>>>> to post send mail to: [email protected] >>>>>> >>>>>> Disclaimer: >>>>>> 1. Contents of the mails, factual, or otherwise, reflect the thinking of >>>>>> the person sending the mail and AI in no way relates itself to its >>>>>> veracity; >>>>>> >>>>>> 2. AI cannot be held liable for any commission/omission based on the >>>>>> mails sent through this mailing list.. >>>>> >>>>> >>>>> >>>>> >>>>> Search for previous postings at: >>>>> http://www.mail-archive.com/[email protected] >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Mobile.accessindia mailing list >>>>> [email protected] >>>>> http://accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in >>>>> >>>>> to post send mail to: [email protected] >>>>> >>>>> Disclaimer: >>>>> 1. Contents of the mails, factual, or otherwise, reflect the thinking of >>>>> the person sending the mail and AI in no way relates itself to its >>>>> veracity; >>>>> >>>>> 2. AI cannot be held liable for any commission/omission based on the >>>>> mails sent through this mailing list.. >>>> >>>> -------------- next part -------------- >>>> An HTML attachment was scrubbed... >>>> URL: >>>> <http://accessindia.org.in/pipermail/mobile.accessindia_accessindia.org.in/attachments/20150828/32d76cfe/attachment.html> >>>> >>>> >>>> Search for previous postings at: >>>> http://www.mail-archive.com/[email protected] >>>> >>>> >>>> >>>> _______________________________________________ >>>> Mobile.accessindia mailing list >>>> [email protected] >>>> http://accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in >>>> >>>> to post send mail to: [email protected] >>>> >>>> Disclaimer: >>>> 1. Contents of the mails, factual, or otherwise, reflect the thinking of >>>> the person sending the mail and AI in no way relates itself to its >>>> veracity; >>>> >>>> 2. AI cannot be held liable for any commission/omission based on the mails >>>> sent through this mailing list.. >>> >>> >>> >>> >>> Search for previous postings at: >>> http://www.mail-archive.com/[email protected] >>> >>> >>> >>> _______________________________________________ >>> Mobile.accessindia mailing list >>> [email protected] >>> http://accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in >>> >>> to post send mail to: [email protected] >>> >>> Disclaimer: >>> 1. Contents of the mails, factual, or otherwise, reflect the thinking of >>> the person sending the mail and AI in no way relates itself to its veracity; >>> >>> 2. AI cannot be held liable for any commission/omission based on the mails >>> sent through this mailing list.. >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> <http://accessindia.org.in/pipermail/mobile.accessindia_accessindia.org.in/attachments/20150828/bd25c638/attachment.html> >> >> >> Search for previous postings at: >> http://www.mail-archive.com/[email protected] >> >> >> >> _______________________________________________ >> Mobile.accessindia mailing list >> [email protected] >> http://accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in >> >> to post send mail to: [email protected] >> >> Disclaimer: >> 1. Contents of the mails, factual, or otherwise, reflect the thinking of the >> person sending the mail and AI in no way relates itself to its veracity; >> >> 2. AI cannot be held liable for any commission/omission based on the mails >> sent through this mailing list.. > > > > > Search for previous postings at: > http://www.mail-archive.com/[email protected] > > > > _______________________________________________ > Mobile.accessindia mailing list > [email protected] > http://accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in > > to post send mail to: [email protected] > > Disclaimer: > 1. Contents of the mails, factual, or otherwise, reflect the thinking of the > person sending the mail and AI in no way relates itself to its veracity; > > 2. AI cannot be held liable for any commission/omission based on the mails > sent through this mailing list.. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://accessindia.org.in/pipermail/mobile.accessindia_accessindia.org.in/attachments/20150829/90254bc9/attachment.html> Search for previous postings at: http://www.mail-archive.com/[email protected] _______________________________________________ Mobile.accessindia mailing list [email protected] http://accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in to post send mail to: [email protected] Disclaimer: 1. Contents of the mails, factual, or otherwise, reflect the thinking of the person sending the mail and AI in no way relates itself to its veracity; 2. AI cannot be held liable for any commission/omission based on the mails sent through this mailing list..
