We reviewed 11 of the 88 linked pages, at 1280 px and 390 px. Everything we say below comes from these captures, and each statement has the measurement it comes from underneath it.
First screen at 1280×800 and at 390×844, as it looked when we read it.Where the first screen ends depends on the window size. Open them at full size to see it.
First screen at 1280×800 and at 390×844, as it looked when we read it. Where the first screen ends depends on the window size. Open them at full size to see it.
We ran 6 checks. Complete: 2. Partial: 4. Not measured: 0. With that, we flag 2 changes for you.
2
Decide
What you can decide
Each one is a change you can make, with the measurement it comes from and how to check that it is done. In stage 3 we tell you in what order we would make them.
They are not ordered by urgency. Which one you work on first is a decision this report does not make.
Found in the review, with no demonstrated relation to what you asked for.
Act
Mark which of these fields are required
Why we say this —On these pages we found at least one form that asks for details and does not mark which are required in a way we can read. It appears on all 11 pages we reviewed.
Nobody knows what they can leave blank. Neither does the browser, so it cannot warn before sending: the warning comes late or not at all.
You will know it is done whenthe required fields are declared as required.
One form asks for a single detail, and we found nothing that says whether it is required.
It appears on 1 of the 11 pages we reviewed. · The same value appears in 2 places.
Where: /
The measurement: We counted what the form asked for when it opened; it may ask for more as you go.
Confirm it by looking at the form: the required fields stand out at a glance, and in the code they have required
What we do not know about this check: Complete across the pages we read.
Make one of these actions stand out from the others
Why we say this —On the first screen of these pages there are actions that share the same background, text color and font size. It appears on 11 of the 11 pages we reviewed.
Whoever arrives has to read them all to decide. When everything carries the same weight, nothing guides.
You will know it is done whenthose actions no longer share all three at once.
2 changes, in the order we would make them. If you are only going to change one thing, change the first one.
Where this order comes from: three things we measured — how much it overlaps with what you asked us for, whether we could check it fully or only partly, and on how many of the 11 reviewed pages it appears. What we checked fully goes before what we checked partly. We do not measure how much each change costs, so if the first is expensive and the third is one line, start with the third.
Mark which details in this form are required
How to check it: Confirm it by looking at the form: the required fields stand out at a glance, and in the code they have required
We looked at this in full and found nothing to fix.
Metadata and shareability
Other things we observed, none of which point to a problem.
There are 14 facts.
We counted 101 images on the pages we reviewed. 29 of them are declared as decorative.
The main heading of / says: “The future of building happens together”.
The main heading of /login says: “Sign in to GitHub”.
The main heading of /features/ai/github-app says: “From issue to merge, in one app”.
And 8 more.
11 of the 11 pages we reviewed have a title, a description and sharing data.
Metadata and shareability
We looked at it on every page we read and found nothing to flag.
What its forms ask for
A form without a title inside the form itself. If there is a heading just above it but outside it, we do not count it.
A form without a title of its own asks for 1 detail; we found no mark we can read that says whether it is required. It is on /.
A form without a title of its own asks for 3 details. 2 of them are required. It is on /login.
A form without a title of its own asks for 1 detail; we found no mark we can read that says whether it is required. It is on /login.
A form without a title of its own asks for 1 detail; we found no mark we can read that says whether it is required. It is on /login.
Why it matters: Every detail asked for before getting an answer is one more decision for whoever fills it in.
We counted what the form asked for when it opened; it may ask for more as you go. We only see the forms the page declares as forms.
What we checked and what was left out
This report looks at this site at 390 pixels wide, with the same checks we run on desktop. There are three things specific to mobile that we do not check yet: the size of what has to be tapped, whether the phone zooms in on the page when a field is tapped, and what text size is left afterwards. That we do not name them does not mean they are fine: it means we have not looked at them.
We read 11 pages on desktop, and all of them could also be read on mobile.
Consent notice: we could not determine whether there was one on 10 of the 11 pages of this review. On those pages, what we describe is what loaded before we responded to anything; if the notice exists, content that only appears afterwards may be missing.
We read 11 of the 88 pages we found linked from the one you gave us. We start with the pages in the main navigation; footer links go last. Besides the page you gave us, we read up to 10 more pages per diagnostic. Here we reached that limit.
What we did and on what
We read 11 pages on October 11, 2026. We have 5 findings, in 3 groups.
How we chose which pages to read. We followed the links on github.com and found 143 anchors. 42 were repeated and 14 pointed outside the site.
We ran 6 checks. Complete: 2. Partial: 4. Not measured: 0.
We ran 6 checks. Complete: 2. Partial: 4. Not measured: 0.
With that, we flag 2 changes. In no case do we hold back.
Where we did not look
Each abstention with its cause and its scope. Absence of observation is not absence of the problem.
Links whose destination we could not determine · on 11 pages we read
We cannot tell which are links that lead nowhere and which are buttons that work — tabs and dropdowns are written the same way. We do not claim that any of them is broken.
Computed accessibility
Partial. Visible focus does not show in a still capture, so we did not check it.
Navigation and links
Partial. We checked links with no declared destination, but we did not follow any, so we do not detect a link that leads to a page that does not exist.
First screen and calls to action
Partial. We stopped before finishing: of the visible links and buttons on this page, we stored 76 of 78.
Third parties and consent
Partial. This check only covers the domains the page called while loading. We do not judge whether what the page does with those domains is lawful.
Comparison with a reference population
We do not yet compare this site with any reference corpus.
LIMITS OF THIS REVIEW
These observations are limited to the reviewed pages listed above.
The pages we did not read are not in these observations: nothing this report says refers to them.
What we count as a link or button: links, buttons, controls that submit a form, and anything that declares a link or button role. If something acts as a control without declaring itself one, we do not see it.
We measure contrast against the reference the check itself comes with: 4.5 to 1 for normal text and 3 to 1 for large text. It is not a threshold of our own. We do not measure text placed over an image or a gradient: the check cannot determine the background color, and those cases do not reach these observations.
This review looked at the site in its light version. If the site changes its appearance when the computer or phone is in dark mode, that version has not been looked at, and what we say here about contrast does not apply to it.
This review was done from the Netherlands, within the European Union. A visitor from outside the European Union may not see the same thing: some sites change depending on where they are requested from.
Fixed layers are measured in each of the windows used in this review. At another window size, the part of the first screen that is covered changes, and a layer that covers nothing in one window may cover something in another.
We do not count images declared as decorative: an image is declared decorative with alt="", and that is a choice made by whoever put it there. We trust that declaration; we do not check whether the image really is decorative.
When we review the declared type of a field, we go by its name and its label. We do not check what is typed into it, so a field whose name does not announce what it expects can go by without us flagging it.
You wrote “A general review” as your goal. We could not relate what you wrote to what we know how to check, so we ordered the report without taking it into account. That is a limit on our side.
This review abstains on 6 points. Each one, with its cause and its scope, is under “Where we did not look”.
The measurements, one by one
On all 11 pages we reviewed, the first screen has links and buttons that share the same background, text color and font size.
F4 · First screen and calls to action
Their appearance does not separate one action from another: someone arriving has no visual cue to choose by.
It appears on 11 of the 11 pages we reviewed. Among them: /, /login, /features/ai/github-app. Plus 8 more.
About this check: Partial. We stopped before finishing: of the visible links and buttons on this page, we stored 76 of 78.
If you decide to change it: Change the style of whichever one should be the main action. We have not tested the change, so we do not know what else is affected.
One form asks for a single detail, and we found nothing that says whether it is required.
F3 · Observed forms
Why it matters: Whoever fills it in does not know what they can leave blank until they try to send it.
It is on /.
We counted what the form asked for when it opened; it may ask for more as you go.
One form asks for a single detail, and we found nothing that says whether it is required.
One form asks for a single detail, and we found nothing that says whether it is required.
Where it is
Sign up for GitHub§email:user_email
If you decide to change it: Mark each required field in its label, and declare it on the field itself with the required attribute. We have not tested the change, so we do not know what else is affected.
On all 11 pages we reviewed, there are external domains that load before anyone touches anything. On the page with the most, there are 2.
F6 · Third parties and consent
They showed up in the first load. We could not determine whether this page shows a consent notice, so we do not know whether any of this would have changed after answering it. If that matters for what you are going to decide, check it by hand before acting.
They are: github.githubassets.com, images.ctfassets.net, i.ytimg.com.
It appears on 11 of the 11 pages we reviewed. Among them: /, /login, /features/ai/github-app. Plus 8 more.
About this check: Partial. This check only covers the domains the page called while loading. We do not judge whether what the page does with those domains is lawful.
No fix proposed: this is a decision worth consulting on.
censo-de-formularios.v1 · we do not count: hidden, submit, button, reset, image and the anti-spam tokens · the fields marked aria-hidden · the search fields: they do not ask for details about the person; they are a navigation control · the fields that appear while typing or in later steps: they are not guessed
Selection rule
not recorded
These versions identify the instrument, not the exact wording: the same version can cover later wording corrections.
Requested address
https://github.com
Final address
https://github.com/
Reading
Read on October 11, 2026. Sites change.
Examples made on public home pages. They imply no commercial relationship, engagement, validation or approval on the part of the brands analyzed.
If you own one of these sites and do not want its report here, write to us and we will take it down the same day. You do not have to explain why.
