Skip to content
https://goldmansachs.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
8
REVIEW
2
PASS
3
INFO
0
Checks
13
3 PASS 2 REVIEW 8 FIX
D
Landmark Structure
Action
23 landmarks
FIX
23 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
17 <nav> landmark(s) found
Warning::
13 of 17 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
17 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 17 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

14 pass 6 fail WCAG AA 4 pass AA only
span What We Do
2.89:1
#000000
on
#3F5974
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Insights
1.76:1
#000000
on
#263947
needs 4.5:1 (normal text)
16px · top of page (header area)
span Our Firm
2.15:1
#000000
on
#344655
needs 4.5:1 (normal text)
16px · top of page (header area)
span Careers
2.59:1
#000000
on
#405260
needs 4.5:1 (normal text)
16px · above the fold
span Investor Relations
3.29:1
#000000
on
#4E626C
needs 4.5:1 (normal text)
16px · above the fold
span Investor Relations
4.11:1
#000000
on
#637077
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Navigating Energy Su…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Navigating Energy Su…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CAREERS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 RESOURCES21.00:13.0:1
#000000
#FFFFFF
Pass
h2 OUR BUSINESSES21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CONNECT21.00:13.0:1
#000000
#FFFFFF
Pass
title Home | Goldman Sachs6.95:14.5:1
#000000
#7297C5
Pass
span What We Do2.89:14.5:1
#000000
#3F5974
Fail
span Insights1.76:14.5:1
#000000
#263947
Fail
span Our Firm2.15:14.5:1
#000000
#344655
Fail
span Careers2.59:14.5:1
#000000
#405260
Fail
span Investor Relations3.29:14.5:1
#000000
#4E626C
Fail
span Investor Relations4.11:14.5:1
#000000
#637077
Fail
span Pressroom5.10:14.5:1
#000000
#757F80
Pass
span Pressroom5.98:14.5:1
#000000
#868A83
Pass
span Worldwide6.95:14.5:1
#000000
#969587
Pass
span Worldwide8.14:14.5:1
#000000
#ABA08C
Pass
span Alumni21.00:14.5:1
#000000
#FFFFFF
Pass
span Alumni21.00:14.5:1
#000000
#FFFFFF
Pass
span Client Login21.00:14.5:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 89/100 — 5 failing, 24 passed
REVIEW
89

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.gs-footer__social-row > ul.gs-uitk-c-gj0gbd--col-root > li > a.gs-link div.gs-footer__social-row > ul.gs-uitk-c-gj0gbd--col-root > li > a.gs-link

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CAREERS div.gs-footer__column > nav.gs-uitk-c-19t1gcf--navigation-root > div.gs-uitk-c-yeppji--navigation-menu-list-root > ul.gs-uitk-c-1gl7rjn--navigation-menu-list-list
RESOURCES div.gs-footer__column > nav.gs-uitk-c-19t1gcf--navigation-root > div.gs-uitk-c-yeppji--navigation-menu-list-root > ul.gs-uitk-c-1gl7rjn--navigation-menu-list-list
OUR BUSINESSES div.gs-footer__column > nav.gs-uitk-c-19t1gcf--navigation-root > div.gs-uitk-c-yeppji--navigation-menu-list-root > ul.gs-uitk-c-1gl7rjn--navigation-menu-list-list
Privacy and Cookies Cookie Preferences Terms & Conditions Security & Fraud Awar… div.gs-uitk-c-esq4q6--footer-legal-links-root > nav.gs-uitk-c-19t1gcf--navigation-root > div.gs-uitk-c-yeppji--navigation-menu-list-root > ul.gs-uitk-c-1gl7rjn--navigation-menu-list-list

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Discover Our Purpose and Values div.gs-card-content > div.gs-uitk-c-ba4ye1--card-footer-root > div.gs-uitk-c-1kna1v0--button-root > a.gs-link
Why Invest in Goldman Sachs div.gs-card-content > div.gs-uitk-c-ba4ye1--card-footer-root > div.gs-uitk-c-1kna1v0--button-root > a.gs-link
Review Our Initiatives div.gs-card-content > div.gs-uitk-c-ba4ye1--card-footer-root > div.gs-uitk-c-1kna1v0--button-root > a.gs-link

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CAREERS ul.gs-uitk-c-1gl7rjn--navigation-menu-list-list > div.gs-uitk-c-40hzrl--navigation-collapse-menu-root > nav.gs-footer__column-collapse-menu-heading > a.gs-navigation-menu-item__link
RESOURCES ul.gs-uitk-c-1gl7rjn--navigation-menu-list-list > div.gs-uitk-c-40hzrl--navigation-collapse-menu-root > nav.gs-footer__column-collapse-menu-heading > a.gs-navigation-menu-item__link
OUR BUSINESSES ul.gs-uitk-c-1gl7rjn--navigation-menu-list-list > div.gs-uitk-c-40hzrl--navigation-collapse-menu-root > nav.gs-footer__column-collapse-menu-heading > a.gs-navigation-menu-item__link
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Heading Hierarchy
6 headings
PASS
6 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Navigating Energy Supply Disruptions and Global Market Responses
  • H1 Navigating Energy Supply Disruptions and Global Market Responses duplicate H1
  • H2 CAREERS
  • H2 RESOURCES
  • H2 OUR BUSINESSES
  • H2 CONNECT

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Alt Text Quality
All 18 images OK
PASS
All 18 images OK
Info::
18 decorative image(s) correctly marked
18 images 18 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback