Ref. 4602
From أبو يوسف (@Ayoub_atwa) on Telegram:
https://t.me/CodeOnTheGoDiscussions/6632
"2. Project Explorer & File Tree Navigation:
The current tree-view structure is complex to navigate.
Suggestion: It would be much smoother if the navigation functioned like a standard "File Manager" (where opening a folder replaces the current view with its contents).
The Long-Press Bug: There is a critical focus issue. If a folder is "expanded," performing a long-press on it (to create a new file/folder) triggers the action on one of the child files inside it instead. We currently have to "collapse" the folder first just to long-press it. The accessibility focus must remain strictly bound to the parent node."
From the same user, this is the preface post to a series of issues (including this one) designed to increase accessibility for users with low vision or blindness:
https://t.me/CodeOnTheGoDiscussions/6630
"Dear Code on the Go Development Team,
Thank you for your proactive approach to accessibility. As an Android developer who relies on screen readers, I would like to share some insights to help improve the experience for low-vision and blind users.
To understand why certain UI elements fail, it is crucial to understand how screen reader users interact with the screen:
Sequential Swiping: We swipe left or right with one finger to move the accessibility focus sequentially from one UI element to the next (e.g., 1, 2, 3, 4).
Touch Exploration: To navigate faster without swiping dozens of times, we touch the screen directly where we expect a button to be. Once the screen reader announces the element under our finger, we double-tap anywhere on the screen to activate it.
Scrolling & Paging: Scrolling requires a two-finger swipe (up/down/left/right). UI elements that rely on complex internal scrolling or dragging often cause the screen reader focus to get lost or jump erratically.
Long-Press & Drag gestures: A long-press is performed via a "double-tap and hold" gesture (similar to bringing up message options in WhatsApp/Telegram). If we need to drag an element, we hold the second tap and slide our finger. The app must accurately register the accessibility focus during this gesture without misinterpreting the target.
With these mechanics in mind, here are 4 key areas where the app's accessibility can be significantly enhanced:"
Ref. 4602
From أبو يوسف (@Ayoub_atwa) on Telegram:
https://t.me/CodeOnTheGoDiscussions/6632
"2. Project Explorer & File Tree Navigation:
The current tree-view structure is complex to navigate.
Suggestion: It would be much smoother if the navigation functioned like a standard "File Manager" (where opening a folder replaces the current view with its contents).
The Long-Press Bug: There is a critical focus issue. If a folder is "expanded," performing a long-press on it (to create a new file/folder) triggers the action on one of the child files inside it instead. We currently have to "collapse" the folder first just to long-press it. The accessibility focus must remain strictly bound to the parent node."
From the same user, this is the preface post to a series of issues (including this one) designed to increase accessibility for users with low vision or blindness:
https://t.me/CodeOnTheGoDiscussions/6630
"Dear Code on the Go Development Team,
Thank you for your proactive approach to accessibility. As an Android developer who relies on screen readers, I would like to share some insights to help improve the experience for low-vision and blind users.
To understand why certain UI elements fail, it is crucial to understand how screen reader users interact with the screen:
Sequential Swiping: We swipe left or right with one finger to move the accessibility focus sequentially from one UI element to the next (e.g., 1, 2, 3, 4).
Touch Exploration: To navigate faster without swiping dozens of times, we touch the screen directly where we expect a button to be. Once the screen reader announces the element under our finger, we double-tap anywhere on the screen to activate it.
Scrolling & Paging: Scrolling requires a two-finger swipe (up/down/left/right). UI elements that rely on complex internal scrolling or dragging often cause the screen reader focus to get lost or jump erratically.
Long-Press & Drag gestures: A long-press is performed via a "double-tap and hold" gesture (similar to bringing up message options in WhatsApp/Telegram). If we need to drag an element, we hold the second tap and slide our finger. The app must accurately register the accessibility focus during this gesture without misinterpreting the target.
With these mechanics in mind, here are 4 key areas where the app's accessibility can be significantly enhanced:"