[gentoo-project] gitlab accessibility

[gentoo-project] gitlab accessibility

[William Hubbs]

[-- 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 --]

Re: [gentoo-project] gitlab accessibility

[Michał Górny]

On Thu, 2022-07-14 at 16:21 -0500, William Hubbs wrote:
> 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.

I'm talking of browsers without ECMAScript, particularly text browsers.
On GitHub, things obviously aren't perfect but I can at least find
a file in the repository and view its contents.  On GitLab, the file
list is simply not there.



-- 
Best regards,
Michał Górny

Re: [gentoo-project] gitlab accessibility

[Anna V.]

On 2022-07-15 09:09, Michał Górny wrote:
> On Thu, 2022-07-14 at 16:21 -0500, William Hubbs wrote:
> > 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.
> 
> I'm talking of browsers without ECMAScript, particularly text browsers.
> On GitHub, things obviously aren't perfect but I can at least find
> a file in the repository and view its contents.  On GitLab, the file
> list is simply not there.

You can always `git clone` the repo to view its files. But non-standard
features (like "merge requests" and CI) indeed require using either:

* a browser with bleeding edge JS support (because everyone uses latest
Chrome and Firefox and polyfills/babel are for losers who don't use
experimental features in production)
* OR custom CLI utilies (btw, can you point me on some I can use? like
dev-vcs/hub for GitHub -- I have no desire to interact with their heavy
and slow[0] web application).

[0]: https://forgeperf.org/

Re: [gentoo-project] gitlab accessibility

[William Hubbs]

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

On Fri, Jul 15, 2022 at 01:09:31PM +0500, Anna V. wrote:
> On 2022-07-15 09:09, Michał Górny wrote:
> > On Thu, 2022-07-14 at 16:21 -0500, William Hubbs wrote:
> > > 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.
> > 
> > I'm talking of browsers without ECMAScript, particularly text browsers.
> > On GitHub, things obviously aren't perfect but I can at least find
> > a file in the repository and view its contents.  On GitLab, the file
> > list is simply not there.
> 
> You can always `git clone` the repo to view its files. But non-standard
> features (like "merge requests" and CI) indeed require using either:
> 
> * a browser with bleeding edge JS support (because everyone uses latest
> Chrome and Firefox and polyfills/babel are for losers who don't use
> experimental features in production)

You can do a bit with merge requests and ci/cd using git push options.

https://docs.gitlab.com/ee/user/project/push_options.html

> * OR custom CLI utilies (btw, can you point me on some I can use? like
> dev-vcs/hub for GitHub -- I have no desire to interact with their heavy
> and slow[0] web application).

dev-vcs/python-gitlab is the one I maintain at the moment; there may be
others I don't know about.

William

> 
> [0]: https://forgeperf.org/
> 

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