Segments list accessibility

[Piciok]

I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first

• [X] Check out all the menus and keyboard shortcuts. Maybe the feature already exists?
• [X] Try with the newest version from GitHub
• [X] Read the documentation and FAQ, Known issues, Troubleshooting to see if the feature already exists
• [X] See if someone already suggested this under Issues or Discussions

Description

I would like to suggest an improvement of the segments' list which would make it faster for users of screen readers to work with the segments. This is especially useful when chaptering long podcast episodes and it will make it possible to quickly control which segment we are currently working with.

It is currently possible to navigate through individual segments using arrow keys which is great for both screen reader users and those who do not need them but still prefer operating their computer with a keyboard. This is great, however when using a screen reader it is necessary to switch between two modes: a document mode which is used to navigate through the DOM of a web document and in which regular keyboard keys such as letters and numbers are used to quickly get the users to key controls on a website such as headings, forms, tables etc.; and the focus mode in which users operate keyboard shortcuts, input information into forms etc. in which the keyboard behaves as expected. Currently the navigation by segments is done in the focus mode which makes it impossible for a screen reader user to tell which segment they are currently focused on. I would like to suggest a redesign of the segments' list so that this kind of direct and fast interaction is possible. In order to do that, the following changes are needed:

1. The segments' list needs to become a table with the columns for the segment name (if applicable or blank otherwise), the start time and the end time of a segment.
2. This table should be assigned the "grid" role as per the W3C WAI ARIA specification so that it can be operable with the arrow keys in the focus mode. The following examples are a great demonstration of both how such a table can be interacted with and how it could be coded.
3. Once the enter key is pressed, the focus should be moved to the edit field where the segment name can be included (as far as I know this is already happening);
4. The modal dialog for the new chapter name should be assigned role "dialog" (again, as per ARIA specs) so that the focus mode of the screen reader is retained when the new window appears. again, an example of a modal dialog
5. Once the chapter name has been saved, the focus should be returned to the segment (grid cell) from which the name change was initiated i.e. the segment for which we have just entered a chapter name.

I hope you will be able to introduce the suggested improvements. Lossless Cut seems to be the only tool that is both accessible and offers enough of a low-level entry point so that users who would be doing simple video editing for the first time can quickly learn it so it is a great addition into our toolbox.

Thank you so much in advance for looking into this.

[mifi]

thanks for your suggestion. I'm vey busy atm but definitely something to look into. PRs welcome for trivial changes.