Images & Graphics

0%
All meaningful images have descriptive "alt text" that explains what the image shows
Decorative images (backgrounds, dividers) are hidden from screen readers with empty alt text
Charts, graphs, and rate graphics have text descriptions explaining the data
Images of text are avoided (use real text instead, so it can scale and be read aloud)
Logos and icons that convey meaning have text alternatives

Text & Readability

0%
Text has enough contrast against its background (at least 4.5:1 for normal text, 3:1 for large text)
Text can zoom to 200% without breaking the layout or cutting off content
Headings are used in order (H1, then H2, then H3) with no skipped levels
Each page has one main heading (H1) that describes the page content
Line spacing and paragraph spacing are adequate for easy reading
Content is written in plain language members can understand (rates, fees, and terms especially)

Navigation & Menus

0%
All pages can be navigated using only a keyboard (Tab, Enter, arrow keys)
When tabbing, a visible outline clearly shows which element is focused
The focused element is never hidden behind a sticky header, chat bubble, or cookie bannerWCAG 2.2
A "Skip to main content" link is available at the top of each page
Navigation menus are consistent across all pages
Help options (phone, chat, contact, branch finder) appear in the same place on every pageWCAG 2.2
Dropdown menus can be opened and closed with the keyboard
Links are clearly visible and look different from regular text
Link text describes where it goes (avoid "click here" or "read more")
Breadcrumbs or other aids help members know where they are

Buttons & Click Targets

0%
Buttons and links are large enough to tap (at least 24x24 CSS pixels; 44x44 recommended for mobile)WCAG 2.2
There's enough space between clickable items to prevent accidental taps
Buttons clearly look clickable and are coded as real buttons or links
Any drag-and-drop action also has a simple tap or click alternativeWCAG 2.2

Forms & Logins

0%
All form fields have visible labels (not just placeholder text inside the field)
Required fields are clearly marked and explained
Error messages clearly explain what went wrong and how to fix it
Errors are announced to screen readers (not shown by color alone)
Login doesn't rely on memory or puzzles — password managers, passkeys, and copy/paste all workWCAG 2.2
Forms allow browser autofill and password managers to work
CAPTCHAs have accessible alternatives (audio option, or avoid CAPTCHAs entirely)
Members don't have to re-enter information they already provided in the same processWCAG 2.2
Help text and instructions are available while filling out forms

Videos & Audio

0%
All videos have captions (subtitles) that can be turned on
Videos have audio descriptions for important visual content
Audio content (like podcasts) has a written transcript available
Videos and audio don't play automatically — members click to start
Media players can be controlled with a keyboard (play, pause, volume)

Time & Motion

0%
Members get a warning and a way to extend before being logged out
Carousels and sliders have pause/stop buttons
Animations can be paused or reduced, respecting the "reduce motion" setting
No content flashes more than three times per second (seizure risk)
Time-limited actions (like completing an application) allow enough time

Documents & PDFs

0%
PDFs are "tagged" for accessibility (not just scanned images)
Important documents are also available in HTML format when possible
Document links indicate the file type and size (e.g., "Rate Sheet (PDF, 250KB)")
Rate sheets and disclosures use proper table formatting with header cells
eStatements and account documents are accessible

Online Banking Features

0%
Login works with screen readers and keyboard navigation
Two-factor authentication offers accessible options (not image-only)
Account balances and transaction history are readable by screen readers
Money transfers show a confirmation screen before completing
Bill pay interface is keyboard accessible
Mobile check deposit instructions are clear and accessible
Loan and account application forms are fully accessible

Calculators & Tools

0%
Loan and savings calculators work with the keyboard only
Calculator results are announced to screen readers when they update
Rate comparison tables use proper header cells
Branch/ATM locator maps have a text-based alternative list

Chat & Support

0%
Live chat widget is keyboard accessible
Chat messages are announced to screen readers as they arrive
Alternative contact methods are available (phone, email, TTY/711 relay)
Chatbots provide accessible responses and a path to a human

Technical Foundation

0%
Page sections use proper landmark roles (header, nav, main, footer)
Page language is set (e.g., lang="en" for English)
Each page has a unique, descriptive title
Core content stays available if JavaScript fails to load
Third-party widgets (chat, digital banking, ads) don't break accessibility
Website tested with at least one screen reader (NVDA, JAWS, or VoiceOver)