Skip to content
https://blackrock.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
Form Accessibility
Action
7 of 9 controls have issues
FIX
7 of 9 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="searchText" id="searchText">; <input type="submit" id="submit">; <input type="text" name="emailcode" id="emailcode">; <input type="text" name="master_product" id="field0">; <input type="text" name="master_market" id="field1">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="searchText" id="searchTextOpt">; <input type="email" name="emailAddress" id="field2">
Info::
2 control(s) properly labeled
9 controls
2 labeled
2 placeholder only
5 unlabeled
ControlTypeLabelMethod
#marketmgscheckboxnone
#productmgscheckboxnone
#searchTextOpttext(基金名稱或基金代號)placeholder only
#field2email( 電子郵件地址*)placeholder only
#field0text(none)none
#field1text(none)none
#submitsubmit(none)none
#searchTexttext(none)none
#emailcodetext(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="searchText" id="searchText">; <input type="submit" id="submit">; <input type="text" name="emailcode" id="emailcode">; <input type="text" name="master_product" id="field0">; <input type="text" name="master_market" id="field1">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="searchText" id="searchTextOpt">; <input type="email" name="emailAddress" id="field2">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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.
D
Lighthouse Accessibility Audits
Action
Score 59/100 — 2 failing, 3 passed
FIX
59

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.

ARIA

Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn how `aria-hidden` affects the document body.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
body#tw-one body#tw-one

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
本基金上市日前(不含當日)，經理公司不接受本基金受益權單位數之買回。 p > b > span > b
內文提及之「好的投資 人人有得」並非指稱投資該ETF基金之績效或獲利，為說明透過貝萊德iShares ETF的服務方案，有機會做為投資人準備不同的理財目標的途… p > b > span > b
股票入息基金所稱之「入息」係指基金會使用符合其投資目標之衍生性工具，以產生額外之收入。為獲取較一致性之配息收入，除股票投資之資本利得及股息收益外，賣出短期選擇… p > b > span > b
非投資等級債券基金主要係投資於較高風險之債券，適合能適當承受高風險之非保守型投資人，投資人投資以非投資等級債券為訴求之基金不宜占其投資組合過高之比重。由於非投… p > b > span > b
申購境內基金N 類型受益權單位（即遞延手續費類型之受益權單位）之受益人，其手續費之收取將於受益人申請買回時支付，且該費用將依持有期間有所不同。其餘費用之計收與… p > b > span > b
申購手續費屬後收型C級別之境外基金，手續費雖可遞延收取，惟每年仍須支付1.25％的分銷費，可能造成實際負擔費用增加。申購手續費屬後收型B級別之境外基金，手續費… p > b > span > b

These are opportunities to improve the legibility of your content.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Links are distinguishable without relying on color.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○Heading elements appear in a sequentially-descending order
○`<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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Touch targets have sufficient size and spacing.
○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.
B
Heading Hierarchy
25 headings
REVIEW
25 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
4 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 好債智級選 收益更到位
  • H1 好債智級選 收益更到位 duplicate H1
  • H2 超強重大趨勢：人工智慧
  • H2 基礎建設與專業技術人員發展機會
  • H2 查詢貝萊德月配息基金配息紀錄
  • H2 搜尋基金
  • H2 焦點基金
  • H3 貝萊德環球資產配置基金(基金之配息來源可能為本金)
  • H3 貝萊德全球智慧數據股票入息基金 (基金之配息來源可能為本金且並無保證收益及配息）
  • H3 貝萊德環球動態趨勢多元資產組合基金（基金之配息來源可能為本金）
  • H2 好的投資 人人有得
  • H2 (empty)
  • H2 想要更聰明地長期投資？
  • H2 (empty)
  • H2 什麼是永續投資？
  • H2 (empty)
  • H3 A、Ｂ級別簡介
  • H3 了解更多
  • H2 成為貝萊德LINE好友
  • H2 (empty)
  • H3 貝萊德在台灣
  • H3 了解更多
  • H2 了解更多
  • H3 貝萊德全球網頁
  • H3 法規專區

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page or Resource Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
A+
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
8 image(s) with good alt text
9 images 8 good alt text
IssueCount
too long1 image(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 好債智級選 收…20.29:13.0:1
#000000
#FBFBFB
Pass
h1 好債智級選 收…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 超強重大趨勢…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 基礎建設與專…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 查詢貝萊德月…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 搜尋基金20.29:13.0:1
#000000
#FBFBFB
Pass
h2 焦點基金20.29:13.0:1
#000000
#FBFBFB
Pass
h2 好的投資 人人…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 想要更聰明地…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 什麼是永續投…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 成為貝萊德LINE…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 了解更多20.29:13.0:1
#000000
#FBFBFB
Pass
h3 貝萊德環球資…20.29:13.0:1
#000000
#FBFBFB
Pass
h3 貝萊德全球智…20.29:13.0:1
#000000
#FBFBFB
Pass
h3 貝萊德環球動…20.29:13.0:1
#000000
#FBFBFB
Pass
h3 A、Ｂ級別簡介20.29:13.0:1
#000000
#FBFBFB
Pass
h3 了解更多20.29:13.0:1
#000000
#FBFBFB
Pass
h3 貝萊德在台灣20.29:13.0:1
#000000
#FBFBFB
Pass
h3 了解更多20.29:13.0:1
#000000
#FBFBFB
Pass
h3 貝萊德全球網…20.29:13.0:1
#000000
#FBFBFB
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.

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

Send Feedback