Zum Inhalt springen
BFSG compliance since 2025

Accessibility for Banks and Insurance: BFSG Compliance for Financial Portals

Banks, savings banks and insurance companies are among the most heavily obligated BFSG entities: online banking platforms, digital application portals, contract completion flows and advisory calculators must meet WCAG 2.2 AA since 28 June 2025. We audit, remediate and support ongoing compliance for financial service providers.

BFSG mandatory from 28.06.2025 Online banking & portals WCAG 2.2 AA financial sector

50+

accessible projects

7.8M

severely disabled in DE

WCAG2.2

conformance level AA

100/100

Lighthouse accessibility

The financial sector faces particular scrutiny under the Accessibility Strengthening Act: online banking platforms, insurance portals, digital application forms and contract completion flows fall directly within the BFSG scope. For people with visual impairments, motor limitations or cognitive disabilities, accessible financial services are not a convenience feature but a prerequisite for equal participation in economic life. We bring experience from over 50 accessible projects (project experience) to the auditing and remediation of financial portals and know the sector's particular technical requirements: multi-factor authentication, document upload, contract steppers and complex calculation tools.

Why financial service providers are particularly affected

The BFSG applies to all companies that provide services or products to consumers — and few sectors are as intensely digital as financial services. Online banking, securities accounts, loan applications, insurance comparisons and digital claims reporting: almost every interaction between a financial institution and a private customer now takes place via a digital interface. According to the 2024 Digital Report of the Banking Association, 76 percent (Bundesverband deutscher Banken, 2024) of the German population regularly uses online banking. For older and impaired customer groups who particularly depend on accessible financial services, a non-accessible platform means exclusion from basic financial services.

There is also particular liability relevance in the financial sector: a contract completion that is impossible for a blind user due to an inaccessible multi-step form not only constitutes a BFSG violation but can also trigger discrimination claims under the General Equal Treatment Act (AGG). The financial regulator BaFin monitors BFSG implementation in the regulated sector. Early and systematic accessibility protects financial institutions from fines and reputational damage. We therefore recommend treating the WCAG audit not as a one-time compliance exercise but as a continuous quality process.

The biggest accessibility challenges in the financial sector

Multi-factor authentication

TAN entry, SMS OTP, push notifications and TOTP apps must be accessible to screen readers and fully operable by keyboard. Time limits for TAN entry must be adjustable or extendable (WCAG 2.2.1).

Digital application forms

Loan applications, account openings and insurance applications often span 10–20 form steps. Each step must be correctly labelled, error-tolerant and equipped with clear correction instructions (WCAG 3.3.1–3.3.4).

Financial calculators and simulators

Credit, pension and insurance calculators with sliders, dropdown menus and dynamic results must be fully operable by keyboard and their outputs must be comprehensible to screen readers.

Payments and bank transfers

IBAN input fields, amount entries with currency format, confirmation steps and digital signatures must be correctly labelled, error-tolerant and handle time-critical transactions safely.

Document upload and identification

Identity document upload, payslip import and video identification procedures present complex accessibility requirements. Clear status feedback, accessible file inputs and alternative identification paths are mandatory.

Contract documents and notifications

Terms and conditions, product information sheets and contract documents as PDF must be tagged according to PDF/UA. Push notifications, email alerts and in-app messages must be accessible to all assistive technologies.

Online banking: technical accessibility requirements

Online banking platforms are among the most technically complex web applications in existence. Single-page architectures with dynamic account overviews, interactive charts and real-time data place particular demands on ARIA markup and focus management. When a transfer is completed and a success message appears as a toast notification, that message must be announced by screen readers via an ARIA live region without disrupting the user's focus. When a bank statement is displayed as a table, column headers must be correctly associated with data cells so that a screen reader can read out every transaction entry in full.

Particular challenges arise with session management: online banking sessions time out after brief inactivity for security reasons. WCAG 2.2.1 requires that users are warned before a time limit expires and can extend it. We implement accessible session timeout dialogs that are screen-reader compatible, keyboard operable and clearly visible even with limited vision. We also test the screen reader compatibility of all critical banking functions with NVDA on Windows and VoiceOver on iOS and macOS.

Making online banking accessible

Transfers, statements and portfolio views made accessible

Every transaction in online banking must be completable for users with assistive technologies. We test every step of the transfer process with a screen reader and keyboard and systematically resolve barriers.

  • IBAN fields with correct label and formatting guidance
  • Transaction confirmation screens fully readable by screen reader
  • Statement tables with correctly associated column headers
  • Session timeout warning accessible and extendable by keyboard
  • Push TAN and SMS OTP entry accessible without time pressure
banking.mybank.com/transferNew transferRecipient IBAN *GB29 NWBK 6016 1331 9268 19Amount *250.00 GBPReferenceContinueFocus visible (2.4.7)Screen reader outputRecipient IBAN, required,edit text field, emptyAmount in GBP, required,two hundred fifty poundsLive region: transferis being processed …WCAG 1.3.1 / 2.1.1 / 3.3.2 / 4.1.3

Insurance portals: application forms and claims reporting

Insurance portals particularly depend on multi-step form processes: tariff configuration, application capture, health questions and contract signing follow in sequence and must function as a cohesive, accessible user journey. For a health insurance application with 40 form fields and three steps, it is not enough to test each step in isolation — the transfer of data between steps, the step indicator with ARIA attributes and error handling when returning to an earlier step must all be tested together for accessibility.

Claims reporting forms are frequently operated in an emotionally stressful situation: an older customer files a claim after a burglary or accident and depends on accessible forms. Clear error messages, logical step sequences without time pressure and the ability to save a started application and continue later are not just accessibility requirements here but quality features for all users. We review these processes holistically and deliver concrete implementation recommendations for accessible web development in a financial context.

Tip: Check time limits in financial forms

Many insurance and banking portals reset form sessions after 15–30 minutes for security reasons. WCAG 2.2.1 requires that users are warned before expiry and can extend the time — except for security-critical processes where an exception applies. Correctly implementing this exception with the required notice is a frequent audit point in our WCAG audits.

Our approach for financial service providers

Technical solutions for sector-specific challenges

Accessible MFA components

TAN input fields with correct label, automatic focus and comprehensible countdown. SMS OTP and push TAN with alternative input paths for users without a smartphone. TOTP apps with accessible setup instructions.

Accessible stepper forms

Multi-step application forms with correct aria-current marking of the active step, persistent error handling and the ability to return to previous steps without losing entered data.

Accessible financial charts

Price and performance charts with text alternative, data table and keyboard accessibility. Portfolio overviews as accessible tables with correct scope attributes and sortable columns by keyboard.

PDF/UA for contract documents

Terms and conditions, product information sheets and contract documents as accessible PDF/UA documents with correct tag structure, reading order and accessible form fields for digital signatures.

Accessible CMS integration

Accessibility-compliant content production for financial websites based on TYPO3, WordPress or other CMS platforms. Editorial training for accessible content, texts and images.

Inclusive UX consulting

Embedding accessibility early in the UX design process: accessible design systems, contrast checking in the mockup phase and user testing with people with disabilities for realistic findings.

Business opportunities through accessible financial services

Accessibility in the financial sector is far more than a legal obligation — it opens up a purchasing-power-rich and loyal customer group. Around 7.8 million (Federal Statistical Office, 2023) severely disabled people live in Germany; added to this are far more people with temporary limitations, older customers with age-related impairments and users in situations that restrict their perception (spectacle wearers, bright environments, limited motor skills while driving). All benefit from accessible financial portals.

Older customers are particularly relevant in the financial sector: the group of over-60s holds more than 60 percent (DIW Berlin, 2023) of private net wealth in Germany, according to data from the German Institute for Economic Research. This customer group switches financial products less frequently and has a high willingness to remain loyal to institutions that give them a good digital experience. An accessible online banking platform that is fully operable with enlarged text and without a mouse creates a measurable competitive advantage over rivals.

Accessible websites rank better in search engines: semantic HTML, correct heading structures and descriptive alt texts improve crawlability and contribute to better organic positions. For financial service providers competing in heavily contested keyword segments such as 'apply for a loan', 'open an account' or 'compare car insurance', this is a relevant side effect of thorough accessibility implementation. Our services therefore combine accessibility with search engine optimisation and performance.

Platforms and technologies in the financial sector

React and Angular banking frontends

Modern online banking platforms are frequently built in React or Angular as single-page applications. We audit and optimise ARIA markup for dynamic content, route change announcements and focus management in modal dialogs and overlays.

TYPO3 and enterprise CMS

Many banks and insurance companies operate their information sites on TYPO3 or other enterprise CMS systems. We audit templates, content elements and plugins for WCAG conformance and train editorial teams.

API-driven portals and headless

Insurance portals with API integration, headless architectures and embedded calculators are audited at component level. Accessible state management patterns and ARIA notifications for asynchronous calculation results.

PDF/UA and document management

Terms and conditions, product information sheets, account statements and contract documents: we convert existing PDF documents to PDF/UA and train your editorial team in creating accessible documents from Word and InDesign.

Sustainable BFSG compliance for financial institutions

Financial portals are continuously evolving: new product features, regulatory updates, redesigns and new sales channels. Accessibility must therefore be embedded as a permanent quality process rather than a one-time certification exercise. We help financial institutions integrate accessibility into their development processes: automated Axe checks in the CI/CD pipeline, accessibility checklists for developers and designers, and regular re-audits for new features and releases.

For financial institutions that need to document their accessibility on an ongoing basis and demonstrate it to regulators, we offer structured BFSG monitoring services: regular spot audits, documentation of conformance status and support in updating the accessibility statement. We also support the development and delivery of training programmes for developers, designers and content owners. This makes accessibility a permanent part of quality assurance at your organisation.

  • BFSG initial audit with prioritisation by transaction relevance
  • WCAG 2.2 AA testing of all critical customer paths (account, loan, insurance application)
  • MFA accessibility: TAN, SMS OTP, push TAN and time limit management
  • Accessible stepper forms and error handling per WCAG 3.3.1–3.3.4
  • PDF/UA conversion for terms, product information sheets and contract documents
  • Accessibility statement per BFSG with conformance status and feedback channel
  • BFSG monitoring and ongoing quality assurance for new features
  • Developer and editorial training on WCAG and accessible development

Frequently asked questions about accessibility in the financial sector

Related industries and regions