How it works
Using GlirOS with the keyboard or a screen reader
Moving around without a mouse, what a screen reader should get, and what isn't covered yet. The same in the web version and the desktop app.
GlirOS can be used with the keyboard alone on its main screens: the chat, the model menu, Settings, Media Studio's main controls and the welcome steps, from GlirOS 0.1.81 (desktop app and web version).
Moving around with the keyboard
- Tab moves forward and Shift+Tab back. Every stop shows a focus ring.
- The first Tab in a new window shows Skip to the message box at the top left. Press Enter, and you can type straight away.
- The chat list and projects: a chat's title opens it, and a project's name opens or closes the project. The ⋯ button beside each one appears when you reach the row with Tab.
- The model menu: the arrow keys move up and down, Home and End go to the first and last model, and Enter chooses. Tab closes the menu and goes on from its button.
- The ⋯ menus: Tab closes them too.
- Settings and every dialog: while one is open, Tab stays inside it and goes round. Esc closes it, and you are back where you were.
- Media Studio's timeline: choose a clip, then Ctrl+← or Ctrl+→ moves it one place earlier or later. You can also use Earlier and Later in its part. Ctrl+Z takes a move back.
- Choices that look like a row of buttons (in Settings, and the welcome's language choice): each row is one Tab stop, and the arrow keys, Home and End choose.
With a screen reader
- An answer should be read once it is written, not word by word while GlirOS is still writing it.
- The parts of the screen have names: the chat list, the conversation and the page's sections. The open chat and the open Settings section are marked as the current one.
- Places and steps should be said: after a move on the timeline, the clip's place ("Clip 2 of 3"), and in the welcome, each step ("Step 2 of 4: …").
How it was checked
The chat, the model menu, every Settings section, Media Studio, the welcome steps and the dialogs went through an automated accessibility check (the WCAG 2.1 A and AA rules, colour contrast included), with nothing left to fix, and then a walk through them with the keyboard. That is a check, not a certificate. GlirOS hasn't been tried with a screen reader by a person yet.
Not covered yet
The tools' own panels (for example a map or a calendar) haven't been checked yet.
Tell us what doesn't work
If something can't be reached with the keyboard, or a screen reader reads it wrongly, write to us from the Contact page and say: which screen (for example Settings > Memory, or the model menu), the keys you pressed, which screen reader and GlirOS's version (Settings > About). We'd like to fix it.