Accessibility Audit Report

github.com

Completed27 Jun 2026, 17:26viewport 756 × 413

Results from cache — scanned less than 24 hours ago

Accessibility score

A90 / 100

Excellent

Weighted by issue severity and affected elements.

Affected elements by severity

Critical0

Serious0

Moderate1

Minor0

Rule violations

Affected elements

Passed checks

Manual review

Executive summary

github.com scored 90/100 — an excellent grade driven by issues that create barriers for people with disabilities.

Across the page, automated checks flagged 1 distinct rule violation affecting 1 element: 1 moderate.

A further 2 checks could not be evaluated automatically and require manual review, while 48 checks passed.

Methodology

Scanned against WCAG 2.0 / 2.1 success criteria at a 756 × 413 viewport, with the results mapped to practical EN 301 549 and European Accessibility Act readiness. Automated testing detects only part of WCAG risk; pair it with manual keyboard and assistive-technology testing for full coverage.

Legal compliance risk

Digital Accessibility Act readiness

Since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to covered digital services across the EU market. Many organizations refer to this as the Digital Accessibility Act in procurement and compliance work. In practice, websites, apps, e-commerce, banking, transport, media and support journeys should align with EN 301 549 and WCAG AA expectations.

Non-compliance can trigger formal complaints, corrective orders, national authority investigations, financial penalties in EUR, reputational harm, contract loss, and restrictions on placing or keeping a non-conforming service in the market. This audit found 1 accessibility issue that may expose your organization to this risk and should be remediated promptly.

Priority implication: treat critical checkout, booking, account, payment and support barriers as commercial and compliance risks, not only technical defects. Remediation evidence can help demonstrate due diligence if customers, public buyers or regulators request proof of accessibility work.

Findings

1 rule violation, grouped by severity.

Moderate1 rule · 1 element

Moderate

1 rule · 1 element

Moderatelandmark-unique

element

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination

Ensure landmarks are unique

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

→The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable

Where — sample elements

.lp-IntroHero > .CtaForm > form[aria-label="Sign up for GitHub"][action="/signup"][method="get"]

<form accept-charset="UTF-8" aria-label="Sign up for GitHub" action="/signup" method="get">

Learn more ↗

Needs manual review

2 checks could not be decided automatically and should be verified by a person.

color-contrast20

Elements must meet minimum color contrast ratio thresholds

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

video-caption2

<video> elements must have captions

Ensure <video> elements have captions

Passed checks48

Automated checks that returned no violations on this page.

aria-allowed-attr
aria-allowed-role
aria-conditional-attr
aria-deprecated-role
aria-hidden-body
aria-hidden-focus
aria-prohibited-attr
aria-required-attr
aria-required-children
aria-required-parent
aria-roles
aria-valid-attr-value
aria-valid-attr
autocomplete-valid
avoid-inline-spacing
button-name

+ 32 more passed checks

Choose Your Path to Compliance

Select the option that works best for you

AI-Powered Fix Instructions

Get detailed, step-by-step instructions with AI assistance to fix issues yourself

✓Code examples and solutions
✓Priority-based guidance
✓Instant access

Full Manual Audit by Expert

Order a comprehensive manual audit from accessibility specialists

✓Expert human review
✓Detailed remediation report
✓Priority support