search

rkkr / simple-keyboard

Apache License 2.0
1.13k stars 224 forks source link

Request for improved accessibility #324

Open bmivzkrp opened 2 years ago

bmivzkrp commented 2 years ago

Dear developers, could you improve the accessibility so that blind users can use this keyboard? The settings interface is very accessible, I managed to configure it. But I failed to use it for printing. I will be very grateful for your attention to this problem.

rkkr commented 2 years ago

What is

use it for printing.

?

bmivzkrp commented 2 years ago

Sorry, I don t know English well. I m trying to type using this keyboard. But the screen reader doesn t tell me anything.

bmivzkrp commented 2 years ago

I use Jieshuo Screen Reader, but when using Android Accessibility Suite (Talkback), the same thing will happen.

rkkr commented 2 years ago

I have never tested Talkback. But I doubt that fixing the issue (whatever it is) will help as this keyboard has no spell checker. This keyboard doesn't know anything about words, it's just separate letters, so you would only get separate letters being read out to you. And as it doesn't make any corrections, whatever you mistyped, will be typed.

There should be better tools for your porpoise.

bmivzkrp commented 2 years ago

The concept of typing by blind users looks something like this:

  1. You focus on the editing field;

  2. Touch it twice;

  3. The screen reader will inform you that the edit field is active, as well as what type of keyboard is active (numeric keypad, keyboard for entering passwords, etc.);

  4. You point your finger at the keyboard. Screen reader announces which letter your finger is on. When you find the right letter - just raise your finger, and it is entered (the screen reader also informs about it). If a blind user knows the keyboard very well, he can type almost as much as the person who sees. Could you check the interaction of this keyboard with TalkBack? You can use the keyboard from Google as a standard.

Personally, I would like to abandon the keyboard provided by Google, especially since the manufacturer of my smartphone has provided the ability to disable absolutely all Google services. I also created an issue in the context of another keyboard, but I was not answered:

https://github.com/AnySoftKeyboard/AnySoftKeyboard/issues/3098

I would be very grateful if you would try to make your wonderful little keyboard completely accessible to blind users. )

omentic commented 2 years ago

I'm a little confused - what do you mean by "print"? Is that the same thing as typing?

But I see the issue after trying out TalkBack. No letters are read out and there seem to be input bugs, which makes it almost completely inaccessible.

triallax commented 2 years ago

Note that this issue seems to have been reported before: https://github.com/rkkr/simple-keyboard/issues/204

Erifxof commented 2 years ago

Amélioré. Accessibilité

Erifxof commented 2 years ago

Crach clavier simple

Erifxof commented 2 years ago

Améliorer accessibilité.

pvagner commented 2 years ago

I see this is an AOSP keyboard fork and it appears as some AOSP keyboard features were not ported over. e.g. spell checker is not included and accessibility is not included too. I guess this is result of trying to make the keyboard as lightweight and as simple as it could be. https://android.googlesource.com/platform/packages/inputmethods/LatinIME/+/refs/heads/master/java/src/com/android/inputmethod/accessibility?autodive=0%2F%2F/

bmivzkrp commented 2 years ago

@rkkr The problem still exists.

bmivzkrp commented 2 years ago

So I found a keyboard accessible for screen readers. This is OpenBoard, which is based on the AOS keyboard. For now, this is an acceptable option for me, but this keyboard has many features that I rarely use. Therefore, I consider this Issue still relevant.

ObjectInSpace commented 2 years ago

Do you have any plans to support blind people, or should we all just use OpenBoard since it actually works?