Proposal for adding accessibility in Termux
---
The accessibility issue of Termux for TalkBack is very disappointing.
- I have programmed for Android and can suggest solutions:
1) Use EditText instead of View.
However, this method has a drawback, for example:
private CharSequence getText would need to be changed to public Editable getText.
2) Use AccessibilityEvent#TYPE_ANNOUNCEMENT (https://developer.android.com/reference/android/view/accessibility/AccessibilityEvent#TYPE_ANNOUNCEMENT).
Using this method doesn't require you to be a genius; you just need to handle the KeyEvent.KEYCODE_DEL event (https://developer.android.com/reference/android/view/KeyEvent#KEYCODE_DEL).
- We can simply announce the deleted text or character.
3) Add the ability to select text using the volume keys.
In general, Android screen readers work like this with EditText, but unfortunately, we have View instead 😦
We should also remember to announce the selected character.
4) How about adding descriptions for the states of the Ctrl, Alt, Caps, etc. keys? AccessibilityNodeInfo#setStateDescription (https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo#setStateDescription(java.lang.CharSequence)).
Simply set the state to on and off when pressed and off when the app starts. - I hope at least points 2 and 3 can be implemented by someone; overall, it would be sufficient.
I wish the project to flourish. --- Let me know if you need any further assistance!
- I have programmed for Android and can suggest solutions:
1) Use EditText instead of View.
However, this method has a drawback, for example:
private CharSequence getText would need to be changed to public Editable getText.
2) Use AccessibilityEvent#TYPE_ANNOUNCEMENT (https://developer.android.com/reference/android/view/accessibility/AccessibilityEvent#TYPE_ANNOUNCEMENT).
Using this method doesn't require you to be a genius; you just need to handle the KeyEvent.KEYCODE_DEL event (https://developer.android.com/reference/android/view/KeyEvent#KEYCODE_DEL).
- We can simply announce the deleted text or character.
3) Add the ability to select text using the volume keys.
In general, Android screen readers work like this with EditText, but unfortunately, we have View instead 😦
We should also remember to announce the selected character.
4) How about adding descriptions for the states of the Ctrl, Alt, Caps, etc. keys? AccessibilityNodeInfo#setStateDescription (https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo#setStateDescription(java.lang.CharSequence)).
Simply set the state to on and off when pressed and off when the app starts. - I hope at least points 2 and 3 can be implemented by someone; overall, it would be sufficient.
I wish the project to flourish. --- Let me know if you need any further assistance!
Android Developers
AccessibilityEvent | Android Developers
Android Developers
KeyEvent | Android Developers
Android Developers
AccessibilityNodeInfo | Android Developers
1 Reply
issue in git https://github.com/termux/termux-app/issues/4175
GitHub
Proposal for adding accessibility in Termux · Issue #4175 · termux/...
Feature description this function very supported for talkback users Additional information The accessibility issue of Termux for TalkBack is very disappointing. I have programmed for Android and ca...