Do Apple and Google Actually Follow WCAG AAA?

The Public Commitments

Both Apple and Google make strong public commitments to accessibility:

Apple has built extensive accessibility features into iOS and macOS — VoiceOver (screen reader), Switch Control, Magnifier, Display Accommodations (color filters for color blindness), and many more. Apple's accessibility page states: "We believe that technology should be accessible to everyone." Apple's developer documentation includes accessibility guidelines, and the Human Interface Guidelines reference WCAG standards.

Google has developed Material Design, its design system for Android and web applications, which includes an accessibility section explicitly referencing WCAG contrast requirements. Google provides the Lighthouse accessibility audit tool, which tests against WCAG criteria. Google's Android platform includes TalkBack (screen reader), BrailleBack, Sound Amplifier, and colour correction features.

Both companies have dedicated accessibility teams, publish accessibility statements, and participate in W3C standards bodies. The stated commitment is genuine and substantial. The question is how it translates to the products themselves.

Apple's Contrast Record

Apple's design aesthetic has historically favoured light grey text, thin fonts, and low-contrast secondary text — an aesthetic that looks elegant but frequently fails WCAG contrast requirements.

iOS Placeholder Text

iOS form field placeholder text has consistently used light grey text that falls below the WCAG 4.5:1 AA threshold for normal text. Measured placeholder text in various iOS versions has recorded contrast ratios as low as 2.3:1 — significantly below the 4.5:1 AA minimum. Apple's rationale appears to be that placeholder text is intentionally de-emphasised to indicate it is not content — but this distinction is invisible to a contrast measuring tool and difficult for low-vision users to make.

macOS Secondary Text

macOS system UI uses secondary text in window titles, menu descriptions, and helper text that frequently fails AA contrast. The macOS sidebar text (inactive items) in dark areas of the interface has been measured below 4.5:1 in multiple macOS versions.

The Apple.com Website

Periodic accessibility audits of apple.com have found contrast failures, particularly in product page marketing copy where light grey text on white backgrounds is used for design aesthetics. Apple's marketing pages — designed to look premium and minimal — regularly sacrifice contrast for visual elegance.

Google's Contrast Record

Google's Material Design system explicitly calls out WCAG contrast requirements. Material Design 3 (the current version) requires a minimum 4.5:1 contrast ratio for text and specifies accessible color roles. This is a more explicit accessibility commitment than Apple's design system documentation.

Google Search

Google's search results page has faced accessibility audits that found contrast issues in secondary text elements — particularly the URL text displayed below search results, which has been measured below 4.5:1 in some iterations. The coloured visited link state also fails contrast requirements in some Google Search designs.

Google Apps

Disabled state indicators in Google applications (grey-out text for unavailable functions) frequently fail WCAG contrast. Disabled states are specifically exempted from WCAG requirements (WCAG 1.4.3 explicitly exempts "inactive user interface components"), but the exemption can be applied too broadly to content that is conceptually disabled but still needs to be readable.

Material Design 3: A Genuine Improvement

Material Design 3 (2021+) represents a genuine improvement in Google's accessibility approach. The color system explicitly defines contrast-safe color roles, and the documentation provides minimum/maximum contrast guidance for each role. Apps built using Material Design 3's color theming system are more likely to produce accessible contrast by default than earlier Material Design versions.

The Industry-Wide Problem

Apple and Google are not outliers in their contrast failures — they are, if anything, better than average. The WebAIM Million, an annual accessibility audit of the top 1 million websites, consistently finds that over 80% have WCAG contrast failures. The figure has improved slowly year over year, but contrast errors remain the most common WCAG failure type by a significant margin.

The scale of the problem reflects several factors:

• Design culture vs. accessibility culture: In most design teams, visual aesthetics are evaluated more rigorously than accessibility compliance. A design that looks great in a presentation to leadership but fails contrast requirements may get approved because the contrast failure is invisible in the decision-making context.
• Tooling gaps: Contrast checking is not built into most design workflows by default. It requires deliberate addition — a plugin, a separate tool, or a design review step specifically for accessibility. Many teams simply do not have this step.
• Brand color constraints: Companies with established brand colors that fail contrast requirements face a genuine dilemma: change the brand color (rarely acceptable) or fail accessibility requirements. This creates pressure to rationalise non-compliance.
• WCAG AAA is aspirational: The 7:1 AAA contrast ratio is explicitly described as aspirational — WCAG says that "it is not possible to satisfy all Level AAA Success Criteria for some content." AAA compliance is genuinely difficult to achieve for all text in complex designs while maintaining visual hierarchy and aesthetics.

What AA Compliance Actually Requires

WCAG 2.1 AA — the standard that most legal frameworks require — mandates:

• 4.5:1 minimum contrast for normal text (smaller than 18pt regular or 14pt bold)
• 3:1 minimum contrast for large text (18pt+ regular or 14pt+ bold)
• 3:1 minimum contrast for non-text content (UI components, icons, charts)
• No contrast requirement for decorative text or inactive components

AA compliance is achievable without sacrificing visual quality. Many well-designed systems achieve AA across all text elements while maintaining typographic hierarchy and aesthetic quality. The constraint is real but manageable — it requires building contrast checking into the design process from the beginning, not adding it as an afterthought.

Check color contrast →