From: Maxime Devos <maximedevos@telenet.be>
To: Roman Riabenko <roman@riabenko.com>, 55625@debbugs.gnu.org
Subject: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 17:11:38 +0200 [thread overview]
Message-ID: <a5c175d27ae2a24205b7116456ac08fc796fadb2.camel@telenet.be> (raw)
In-Reply-To: <2e715e0492a32632b4392e2fffeae8ff1a33437a.camel@riabenko.com>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Roman Riabenko schreef op wo 25-05-2022 om 09:03 [+0300]:
> When viewing a video in totem, totem controls in the botton are not
> accessible with the mouse. It is possible to control the playback with
> keyboard.
What kind of accessibility are you looking for? Supporting only the
mouse is usually considered to be inaccessible and additionally
supporting keyboard control is usually considered good for
accessibility, so I assume you're referring to a different kind of
accessibility (*) here.
(*) <https://developer.gnome.org/documentation/guidelines/accessibility.html>
and other sources have some information on what is usually meant by accessibility.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-28 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 6:03 bug#55625: GNOME: totem controls not accessible Roman Riabenko
2022-05-28 15:11 ` Maxime Devos [this message]
2022-05-28 15:35 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-05-28 16:29 ` Maxime Devos
2022-05-28 16:34 ` Maxime Devos
2022-05-28 19:15 ` Roman Riabenko
2022-05-28 19:28 ` Maxime Devos
2022-05-28 19:31 ` Maxime Devos
2022-05-30 18:45 ` Roman Riabenko
2022-05-28 15:20 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a5c175d27ae2a24205b7116456ac08fc796fadb2.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55625@debbugs.gnu.org \
--cc=roman@riabenko.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).