glitchsoc - Link to source
TapType v2.0 is out!
TapType is a keyboard for blind users — no visible keys, just tap where QWERTY keys would be and it predicts your words. Fully accessible with TalkBack.
What's new in v2.0:
Multi-language support — English (US/UK), Deutsch, Espanol. All speech, announcements, and punctuation fully translated. Switch languages right from the keyboard.
Reorganised settings into clean categories with per-language user dictionaries and punctuation.
TTS engine fixes — language switching and engine changes now work reliably.
Download the APK:
github.com/aaron-gh/taptype-re…
If you find TapType useful, consider supporting its development:
paypal.me/aaronhewitt
github.com/sponsors/aaron-gh
liberapay.com/fireborn/
#TapType #Accessibility #A11y #Blind #Android #TalkBack #Keyboard #AssistiveTech

Release TapType 2.0 · aaron-gh/taptype-releases

Multi-language support TapType now supports multiple languages with full translations for all keyboard speech, announcements, and UI. Languages English (US) — QWERTY layout English (UK) — QWERTY l...
GitHub
#a11y #Accessibility #android #blind #talkback #keyboard #assistivetech #taptype

reshared this

in reply to aaron

mastodon - Link to source

Woochancho

The word prediction is really good, I like it a lot.
Ere are some issues that i found:
*Sometimes punctuation is spoken in English.
*Ñ doesn't appear in the layout, just next to L.
*When you write a vowel and you choose its accented variation with right, a space is introduced. I'm not sure how to deal with character variants without long presses. Introducing the "´" symbol next to P, like in Latin American Spanish qwerty distribution, would be a good workaround.
in reply to aaron

mastodon - Link to source

Woochancho

the categories and symbols when you swipe right at the end of the list are spoken in Spanish, but the basic symbols with swipes up and down are spoken in english.
Regarding the Ñ bug, I was referring to the physical layout. The last letter on the right side of the screen is L like in English, but in Spanish L is followed by ñ.
You can't write or predict words like año (year) or mañana (morning) because Ñ doesn't appear in the keyboard.
in reply to Woochancho

glitchsoc - Link to source

aaron

@muchanchoasado I see what's happening with the accented fouls. They are in the dictionary as words, and shouldn't be. they are committing a space because they are being considered a completed word. If you start typing a word that contains an accented character, the word should be suggested even without typing the accent, so just don't.
@Woochancho
in reply to Woochancho

glitchsoc - Link to source

aaron

@muchanchoasado I fixed so if you type an exact match to a word, and the variant of the word with an accent is actually more common, that variant will be suggested first. Obviously this will change as the keyboard learns how you type, but there was an issue where the exact match was always being suggested higher than the variant even when the variant should be more common, so thanks for helping me track that one down!
@Woochancho
in reply to Woochancho

glitchsoc - Link to source

aaron

@muchanchoasado It was designed so that prediction is the primary input method, and the fallback only exists for those times when prediction is failing or you need to type a word that is not, in fact, a word, like obscure acronyms and such. As a result, it doesn't include a lot of characters on the keyboard face like gboard and others do, so for passwords etc just use another inputmethod.
@Woochancho
in reply to Woochancho

mastodon - Link to source

Woochancho

Sometimes I need to disable talkback because single-finger gestures stop working, but I'm totally sure this is Talkback's fault. Same happens with Advanced Braille and other keyboards that require direct touch. Last year I've discovered Jieshuo Extension, I don't know why they called it like that if its an individual app, that makes GBoard extremely responsive with talkback, but it only works well for a few minutes.
If you manage to finish your screen reader and the payd features are unlocked through Google Play, I'll subscrive or buy it for sure.
in reply to Woochancho

glitchsoc - Link to source

aaron

@muchanchoasado This is unfortunately a talkback issue. You turned on pass through in the settings? the trick is to tap once on the keyboard when you open the text field. it should say TapType keyboard. Then your gestures should work, so long as you swipe in the keyboard area. If you have trouble with this, making the keyboard full screen in settings might help.
@Woochancho
in reply to aaron

friendica (DFRN) - Link to source

Peter Vágner

@aaron All other keyboards are so complicated because they provide its own text editing functionality. This one is designed in a way that due to predictions the correct words are typed right after first attempt.
I just wanted to say I like it and it's awesome.

I'm looking how difficult it might be to add more languages, for me and other friends I'll add slovak and czech if it turns out to be doable.

@aaron
in reply to aaron

friendica (DFRN) - Link to source

Peter Vágner

@aaron I know you do have loads of comments and feature requests and the like.

If you will eventually be considering accepting localization contributions such as translation of string resources, finding and cleaning up localized word frequency lists, adding data for different locale specific keyboard layouts and similar, count me in please. I like the project, find it usefull and if there will ever be a chance for being helpfull I'd be happy to become part of it.

@aaron
in reply to aaron

glitchsoc - Link to source

Quanchi

send help. I am trying to install the app, only for play Protect to end up not liking it. It says : "This app can request access to sensitive data. This can increase the risk of identity theft or financial fraud." It refused to install the app and told me app not installed. Do I need to turn off play protect entirely to install this or there is a way to somehow make an exception?
in reply to aaron

glitchsoc - Link to source

Quanchi

I turned it off. It didn't provide me with an option to install anyways or else I would have kept it on. I have tried the keyboard and here are my thoughts: 1. I think the keyboard sounds are loud and on the aggressive side to my liking personally. They're in stereo as well which isn't the best for something like this in this situation. I'm thinking more along some soft click sounds instead. 2. I don't know if it's the algorithm or the fact the bottom row is on where the space bar and other buttons should be on normal keyboards, but it feels like I have to try multiple times to either write a word correctly or get it in the suggestions list. If I had to guess, I think it's probably the keyboard placement but I could be wrong. Keep up the great work. I really like it so far and like how easy it is to access all the functions in an easy way
in reply to Quanchi

glitchsoc - Link to source

aaron

@quanchi Thanks for the feedback. I will look into providing other sound options. I included the current ones because each one is slightly different, which allows me to type with TapType almost exclusively using the sounds, only having tts announcements for navigating the suggestions list, which I do not often need to do.

As for the predictions issue, yes, it is most likely due to the placement. you could also try making the keyboard shorter or taller to suit. Omitting that last row for numbers, space and return was an intention design choice I don't intend to change.

@Quanchi
⇧