Accessibility Audit Report

mail.google.com

Completed27 Jun 2026, 13:00viewport 756 × 413

Accessibility score

D56 / 100

Poor

Weighted by issue severity and affected elements.

Affected elements by severity

Critical1

Serious0

Moderate6

Minor0

Rule violations

Affected elements

Passed checks

Manual review

Executive summary

accounts.google.com/v3/signin/identifier?continue=... scored 56/100 — a poor grade driven by issues that create barriers for people with disabilities.

Across the page, automated checks flagged 2 distinct rule violations affecting 7 elements: 1 critical and 6 moderate. The critical failures — select element must have an accessible name — prevent screen-reader and keyboard users from completing key tasks.

A further 1 check could not be evaluated automatically and require manual review, while 33 checks passed. Remediating the one critical rule will clear the highest-impact barriers first.

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 2 accessibility issues 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

2 rule violations, grouped by severity.

Critical1 rule · 1 element

Moderate1 rule · 6 elements

Critical

1 rule · 1 element

Criticalselect-name

element

Select element must have an accessible name

Ensure select element has an accessible name

WCAG 2.0 AWCAG 4.1.2

Why it matters

Blocks people with disabilities from using core functionality. Fix as a top priority.

How to fix

→Element does not have an implicit (wrapped) <label>
→Element does not have an explicit <label>
→aria-label attribute does not exist or is empty
→aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
→Element has no title attribute
→Element's default semantics were not overridden with role="none" or role="presentation"

Where — sample elements

select

<select name="hl" class="N158t" data-language-selector-select="" jsname="rfCUpd">

Learn more ↗

Moderate

1 rule · 6 elements

Moderateregion

elements

All page content should be contained by landmarks

Ensure all page content is contained by landmarks

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

→Some page content is not contained by landmarks

Where — sample elements

.gEc4r

<div class="gEc4r"><img src="//ssl.gstatic.com/images/branding/googlelogo/2x/googlelogo_color_74x24dp.png" class="TrZEUc" alt="Google" width="74" height="24"></div>

div[jsname="paFcre"]

<div jsname="paFcre"><div class="aMfydd" jsname="tJHJj"><h1 class="Tn0LBd" jsname="r4nke">Sign in</h1><p class="a2CQh" jsname="VdSJob">with your Google Account to continue to Gmail. This account will be available to other Google apps in the browser.</p></div></div>

.Flfooc

<div class="Flfooc">

+ 3 more affected elements

Learn more ↗

Needs manual review

1 check could not be decided automatically and should be verified by a person.

color-contrast2

Elements must meet minimum color contrast ratio thresholds

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

Passed checks33

Automated checks that returned no violations on this page.

aria-allowed-attr
aria-conditional-attr
aria-hidden-body
aria-hidden-focus
aria-prohibited-attr
aria-valid-attr-value
aria-valid-attr
autocomplete-valid
button-name
bypass
color-contrast
document-title
empty-heading
form-field-multiple-labels
heading-order
html-has-lang

+ 17 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