Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

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 ✗

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

5 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 5 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

5 <nav> landmark(s) found

1 of 5 <nav> elements are unlabeled

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

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

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

Link & Button Quality

4 issue(s) across 138 links and 26 buttons

REVIEW

4 issue(s) across 138 links and 26 buttons

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /global/en/legal/privacy.onlycontent.html; /global/en/legal/privacy.onlycontent.html

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.primaryheader__stickyButton (#100 on page); button.form__infoIcon (#1004 on page); button.form__infoIcon (#1019 on page); button.form__infoIcon (#1034 on page)

136 link(s) with descriptive text

138 links

0 empty

0 generic text

2 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
/global/en/legal/privacy.onlycontent.htm…	Privacy Statement	new tab	Add '(opens in new tab)' to text
/global/en/legal/privacy.onlycontent.htm…	privacy statement	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

158 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

/global/en/legal/privacy.onlycontent.html; /global/en/legal/privacy.onlycontent.html

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.primaryheader__stickyButton (#100 on page); button.form__infoIcon (#1004 on page); button.form__infoIcon (#1019 on page); button.form__infoIcon (#1034 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 2 pass AA only

a Content Area

3.78:1

#000000

#64696C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Main Navigation

3.58:1

#000000

#636564

needs 4.5:1 (normal text)

16px · top of page (header area)

span Netherlands

3.43:1

#000000

#62625E

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 UBS Netherlands	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Skip Links	6.84:1	3.0:1	#000000	#95938D	Pass
h2 Additional language …	3.48:1	3.0:1	#000000	#63635F	Pass
h2 Main menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Main menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Additional language …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Engineering enduranc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our capabilities	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 About us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer Navigation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Personalize your vis…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Choose your login	6.84:1	3.0:1	#000000	#95938D	Pass
h3 Search Title	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Individual investors	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Corporates & Institu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Legal Information	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Our financial servic…	6.84:1	4.5:1	#000000	#95938D	Pass
a Content Area	3.78:1	4.5:1	#000000	#64696C	Fail
a Main Navigation	3.58:1	4.5:1	#000000	#636564	Fail
span Netherlands	3.43:1	4.5:1	#000000	#62625E	Fail

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.

A+

Heading Hierarchy

64 headings

PASS

64 headings

Single H1 present

H2 Skip Links
H2 Additional language and service options
H3 Choose your login
H4 Individuals
H4 Corporate & Institutions
H2 Main menu
H3 in Luxembourg
H3 in the Netherlands
H3 Funds and prices
H3 UBS ETFs
H3 Capabilities
H3 Insights
H3 About us
H3 Contact us
H3 Investment Banking
H3 Client Portal
H3 Our firm
H3 Investor Relations
H3 Media
H3 Sustainability and Impact
H3 Cyber Security at UBS
H3 Overview
H3 About us
H3 Professional careers
H3 Early careers
H3 Apprentices
H3 Search jobs
H3 Search Title
H2 Main menu
H3 in Luxembourg
H3 in the Netherlands
H3 Funds and prices
H3 UBS ETFs
H3 Capabilities
H3 Insights
H3 About us
H3 Contact us
H3 Investment Banking
H3 Client Portal
H3 Our firm
H3 Investor Relations
H3 Media
H3 Sustainability and Impact
H3 Cyber Security at UBS
H3 Overview
H3 About us
H3 Professional careers
H3 Early careers
H3 Apprentices
H3 Search jobs
H2 Additional language and service options
H1 UBS Netherlands
H2 Engineering endurance
H2 Our capabilities
H3 Individual investors
H3 Corporates & Institutions
H2 About us
H2 Footer Navigation
H3 Capabilities
H3 About us
H3 Careers at UBS
H3 Contact
H3 Legal Information
H2 Personalize your visit with cookies

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

4 decorative image(s) correctly marked

3 image(s) with good alt text

7 images 3 good alt text 4 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#psInput-3-ps-dialog	checkbox	Statistics	for/id
#psInput-2-ps-dialog	checkbox	User preference	for/id
#psInput-4-ps-dialog	checkbox	Marketing	for/id

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 18 passed

PASS

100

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.

○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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[accesskey]` values are unique

●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

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○`<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

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has a `[lang]` attribute

○`<html>` element has a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Document has a main landmark.

○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.

○Elements with visible text labels have matching accessible names.

○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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.