https://fdic.gov
Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
73
GRADE
C
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
137 PASS 2 REVIEW 4 FIX
DFavicon & BrandingAction3 icon(s) detectedFIX
Favicon & Branding
Action3 icon(s) detected
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
DWeb ManifestActionNot foundFIX
Web Manifest
ActionNot found
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.
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
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.
BLink & Button Quality30 issue(s) across 143 links and 42 buttonsREVIEW
Link & Button Quality
30 issue(s) across 143 links and 42 buttons
30 issue(s) across 143 links and 42 buttons
Critical::
30 button(s) with no accessible text
Icon-only buttons need an aria-label so screen readers can announce them.
Got: button.tbm-button (#103 on page); button.glider-dot (#201 on page); button.glider-dot (#202 on page); button.glider-dot (#203 on page); button.glider-dot (#204 on page); button.glider-dot (#300 on page); button.glider-dot (#301 on page); button.glider-dot (#302 on page); button.glider-dot (#303 on page); button.glider-dot (#384 on page) (+20 more)
Info::
143 link(s) with descriptive text
143 links
0 empty
0 generic text
0 new tab
30 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| <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 |
| <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 |
| <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 |
| <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 |
| <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 |
| <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 |
| <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 |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
155 links and buttons have descriptive text
Icon-only buttons need an aria-label so screen readers can announce them.
button.tbm-button (#103 on page); button.glider-dot (#201 on page); button.glider-dot (#202 on page); button.glider-dot (#203 on page); button.glider-dot (#204 on page); button.glider-dot (#300 on page); button.glider-dot (#301 on page); button.glider-dot (#302 on page); button.glider-dot (#303 on page); button.glider-dot (#384 on page) (+20 more)
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
BLighthouse Accessibility AuditsScore 82/100 — 5 failing, 27 passedREVIEW
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 27 passed
82
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
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.field__item > div.paragraph > div.tabs-container > input#consumers div.field__item > div.paragraph > div.tabs-container > input#consumers |
div.field__item > div.paragraph > div.tabs-container > input#bankers div.field__item > div.paragraph > div.tabs-container > input#bankers |
div.field__item > div.paragraph > div.tabs-container > input#analysts div.field__item > div.paragraph > div.tabs-container > input#analysts |
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.
Names and labels
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.region > div#block-fdic-theme-mainnavigation > nav#tbm-main > button.tbm-button div.region > div#block-fdic-theme-mainnavigation > nav#tbm-main > button.tbm-button |
div > div.glider > div.glider-dots > button.glider-dot div > div.glider > div.glider-dots > button.glider-dot |
div > div.glider > div.glider-dots > button.glider-dot div > div.glider > div.glider-dots > button.glider-dot |
div > div.glider > div.glider-dots > button.glider-dot div > div.glider > div.glider-dots > button.glider-dot |
div > div.glider > div.glider-dots > button.glider-dot div > div.glider > div.glider-dots > button.glider-dot |
div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot |
div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot |
div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot |
div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot |
div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot div#block-fdic-theme-dataandinsight > div#data-and-insights-glider > div.glider-dots > button.glider-dot |
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div > div > div.scrollable > iframe div > div > div.scrollable > iframe |
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.
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 |
|---|
BOARD MEETING div.paragraph > div.mosaic-text-wrapper > div.field > div.field__item |
PRESS RELEASE div.paragraph > div.mosaic-text-wrapper > div.field > div.field__item |
These are opportunities to improve the legibility of your content.
Navigation
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Skip to main content body.acquia-cms-toolbar > a.skipheader |
Here’s how you know div.usa-banner__inner > div.usa-banner__header > div > button#fdic_how_you_know |
These are opportunities to improve keyboard navigation in your application.
○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-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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●`[accesskey]` values are unique
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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"]`
○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.
○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+Landmark Structure11 landmarksPASS
Landmark Structure
11 landmarks
11 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
A+Heading Hierarchy22 headingsPASS
Heading Hierarchy
22 headings
22 headings
Info::
Single H1 present
- H2 About
- H2 Resources
- H2 Analysis
- H2 News
- H2 Alert - Impersonation Scams
- H1 About the FDIC
- H2 Consumers
- H2 Consumers
- H3 Consumer Resources
- H2 Bankers
- H2 Bankers
- H3 Banker Resources
- H2 Analysts
- H2 Analysts
- H3 Analyst Resources
- H2 Data & Insights
- H3 Quarterly ROA
- H3 Number of Insured Banks
- H3 DIF Balance
- H3 DIF Reserve Ratio
- H3 Domestic Deposit Growth
- H2 Footer Secondary Menu
AAlt Text QualityAll 38 images OKPASS
Alt Text Quality
All 38 images OK
All 38 images OK
Info::
5 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
31 image(s) with good alt text
38 images 31 good alt text 2 decorative
| Issue | Count |
|---|---|
| too long | 5 image(s) |
AForm Accessibility1 of 9 controls have issuesPASS
Form Accessibility
1 of 9 controls have issues
1 of 9 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="op" id="who-what-go">
Info::
8 control(s) properly labeled
9 controls
8 labeled
0 placeholder only
1 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| #query1 | search | Search FDIC.gov | for/id |
| #query2 | search | Search FDIC.gov | for/id |
| #consumers | radio | Consumers | for/id |
| #bankers | radio | Bankers | for/id |
| #analysts | radio | Analysts | for/id |
| Enter your email address | for/id | ||
| #who-am-choices | select | About you | for/id |
| #who-path-choices | select | Your request | for/id |
| #who-what-go | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" name="op" id="who-what-go">
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
A404 Error PageHTTP 404, custom pagePASS
404 Error Page
HTTP 404, custom page
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Follow the FDIC on X ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+Print StylesheetPrint styles detectedPASS
Print Stylesheet
Print styles detected
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_GiIcNgZ7385q2iyRAaTRPhiEDH3JEwPPE9umUOIAVN4.css?delta=4&language=en&theme=fdic_theme&include=eJxlTtmOwzAI_CE2_qQIG5LQ4EMGb5u_7xlVq30ZNJeYVFWxmUStaQ-pdoYnBOqjoU54wRtwcfFj5hyZQsLmUgvwzVXKfgY_FBaSNKdhXnMgdPyRYrJu_sdYpFB-fJGy1LfhG2cOw65knxCsKsQ9vA9kJsFHUZ37dG5o2HHt2DY7Z3yVaZQ2ooptTGCHOecQ0Rg8zplXzFzGf8H8UDb4Fb5aeOGUKw3lO_r1c40
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/default/files/css/css_GiIcNgZ7385q2iyRAaTRPhiEDH3JEwPPE9umUOIAVN4.css?delta=4&language=en&theme=fdic_theme&include=eJxlTtmOwzAI_CE2_qQIG5LQ4EMGb5u_7xlVq30ZNJeYVFWxmUStaQ-pdoYnBOqjoU54wRtwcfFj5hyZQsLmUgvwzVXKfgY_FBaSNKdhXnMgdPyRYrJu_sdYpFB-fJGy1LfhG2cOw65knxCsKsQ9vA9kJsFHUZ37dG5o2HHt2DY7Z3yVaZQ2ooptTGCHOecQ0Rg8zplXzFzGf8H8UDb4Fb5aeOGUKw3lO_r1c40 ✓Inline @media print Not detected ✗
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
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)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 About the FDIC | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 About | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Resources | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Analysis | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 News | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Alert - Impersonatio… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Consumers | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Consumers | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Bankers | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Bankers | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Analysts | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Analysts | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Data & Insights | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Footer Secondary Men… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Consumer Resources | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Banker Resources | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Analyst Resources | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Quarterly ROA | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Number of Insured Ba… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 DIF Balance | 21.00:1 | 3.0: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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.