public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed

From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: mgorny@gentoo.org, cyber+gentoo@sysrq.in
Subject: [gentoo-project] gitlab accessibility
Date: Thu, 14 Jul 2022 16:21:14 -0500	[thread overview]
Message-ID: <YtCIyloDJDRRopAY@linux1.home> (raw)

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

Hey all,

I was on vacation when the issues were brought up, but I want to start a
new thread about this.

I will quote the sections from the messages on the previous thread I am
referring to.

mgorny:
> I would really prefer if someone worked on the GitLab accessibility
> issues before someone tried to do that.  Like, made GitLab something
> more than a blank site on less-than-state-of-art web browsers.

I don't know which browsers you are talking about. I personally use
chrome and it isn't a blank page. I'm sure it probably works on firefox
as well. I have briefly checked Edge and it is fine there.
I think you need to be more specific about the browsers you are talking
about. Also, if you are a web developer, you might want to open MR's for
gitlab to get this fixed if you can.

Anna:
What specific accessibility issues do you see in gitlab? I see some
unlabeled buttons in places, and it is challenging to follow
conversations on MR's, but this is no different than github; it has
these types of issues as well. One thing I do is to use the api through
tools like python-gitlab or for github github-cli to get around issues
like these.

Also, I'm going to start another thread about github shortly that I'll
add you to.

Thanks,

William


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

next             reply	other threads:[~2022-07-14 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 21:21 William Hubbs [this message]
2022-07-15  7:09 ` [gentoo-project] gitlab accessibility Michał Górny
2022-07-15  8:09   ` Anna V.
2022-07-15 19:46     ` William Hubbs

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YtCIyloDJDRRopAY@linux1.home \
    --to=williamh@gentoo.org \
    --cc=cyber+gentoo@sysrq.in \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox