Does the BFSG apply to our career page?

Not to the application flow. The BFSG covers products and services for consumers (BFSG); a recruitment procedure is not among them. The applicable standards are the AGG and SGB IX. The rest of your website is a different matter: where goods or services are offered to consumers, the BFSG applies to those areas, and the career page usually sits in the same application built from the same components.

What does a discriminatory application flow cost?

Section 15 (2) AGG provides for appropriate monetary compensation. Where the claim concerns a failure to hire, it is capped at three months' salary (AGG) if the person would not have been hired even in a discrimination-free selection. The claim must be asserted in writing within two months (AGG) of receiving the rejection. On top of that come the cost of the proceedings, the public reaction and the position that is still unfilled.

Is an email address enough as an accessible alternative?

As an interim measure it helps, as a permanent state it does not. A separate route that only one group of people has to use is itself unequal treatment. So word the second route openly for all applicants, place it visibly at every stage of the form, and work on the flow itself in parallel.

We use a bought applicant tracking system. Who carries the responsibility?

Towards applicants, the employer does. The employer chose the procedure and answers for it. The work can be shifted to the vendor contractually: a conformity statement against EN 301 549, remediation deadlines, a right to test in your own tenant. Audit the embedded flow like an area of your own, exactly as with any other embedded third-party content.

Which part of the form fails most often in audits?

The file upload and error handling. Hand-built drop zones replace the browser's native field and lose its name, keyboard operability and feedback in the process. Right behind them come labels that exist only as placeholder text: 33.1 percent (WebAIM Million) of form inputs on home pages are not properly labelled, and application forms are considerably longer than home pages.

How long does an audit of the application flow take?

For a flow with job search, account creation, a multi-step form and an upload we plan a few days: one keyboard pass, one screen reader pass, one under time pressure, plus the review of the job advertisements as documents. The result is a prioritised list, separated into what your own team can fix and what has to go to the vendor.

Accessible Job Applications: Career Pages Without Barriers

Career pages rarely make it onto the checklist when a company starts working on digital accessibility. The reason is understandable: the German Accessibility Strengthening Act does not cover them. It governs products and services for consumers (BFSG), and someone applying for a job is not acting as a consumer. The standard is still written into law, just in a different place: the General Equal Treatment Act explicitly prohibits discrimination on the grounds of disability in access to employment (AGG), and Book IX of the Social Code imposes further duties on employers. Both have been in force for years, both are enforceable in court, and neither asks whether the application form was built in house or bought in.

Key takeaways

The BFSG does not cover the application flow: it applies to products and services for consumers (BFSG). The application procedure is governed by the AGG and by SGB IX.
Discrimination during a selection procedure can trigger compensation of up to three months' salary (AGG), even if the person would not have been hired in any case.
33.1 percent (WebAIM Million) of form inputs on home pages are not properly labelled. Application forms are the longest forms a company operates.
7.8 million (Federal Statistical Office) people in Germany have a recognised severe disability; their unemployment rate stood at 12.0 percent (Federal Employment Agency) in 2025.
Buying an applicant tracking system moves the work, not the responsibility. It is handled exactly like any other embedded third-party content.

The BFSG ends where the application begins

The German Accessibility Strengthening Act defines its scope exhaustively. It covers a list of products and a list of services, and both are written for the relationship between a provider and a consumer (BFSG): telecommunications services, elements of passenger transport services, consumer banking services, e-books, services in electronic commerce. A job advertisement is not a service in electronic commerce, and an application is not a contract for goods. Anyone trying to file the career page under the BFSG will find no hook to hang it on.

That produces a false sense of calm. The same company audits its shop, audits its customer portal, and leaves the application flow running exactly as it was built years ago. Yet this is the area with the most immediate commercial damage: someone who gets stuck in the customer portal picks up the phone. Someone who gets stuck uploading a CV does not. The application goes somewhere else, and nobody inside the company hears about it. Internally the failure shows up as an application that failed to arrive, not as a defect in your own software.

Two sentences that make the difference

Section 7 (1) AGG prohibits discrimination against employees on the grounds of disability. Section 6 (1) AGG makes clear that applicants for an employment relationship also count as employees (AGG). An application form that cannot be completed without a mouse is therefore not a convenience issue but a barrier to access within the meaning of the act.

The consequences are equally clear. Under section 15 (2) AGG a person who has been discriminated against may claim appropriate monetary compensation; where the claim concerns a failure to hire, it is capped at three months' salary (AGG) if the person would not have been hired even in a discrimination-free selection. That cap is the detail not to skim over: a claim arises even when the application had no chance on the merits. It must be asserted in writing within two months (AGG) of receiving the rejection.

How many people the application flow affects

At the end of 2025 a good 7.8 million (Federal Statistical Office) people in Germany held an officially recognised severe disability, which equals 9.4 percent (Federal Statistical Office) of the population. The figure does not describe the group most people picture when they hear the word disability: a good 91 percent (Federal Statistical Office) of severe disabilities were caused by illness, only a small share is congenital. These are largely people who developed a visual impairment, hearing loss or a motor impairment in the middle of their working life, and who had filled in every application form without difficulty until then.

For recruiting, the working-age share of that group is what matters. Around 3.1 million (Federal Employment Agency) severely disabled people are of working age according to the most recently evaluated disability statistics. Their employment rate stood at 50.9 percent (Federal Employment Agency) in 2024, well below the rate for the population as a whole. Employers with 20 or more workplaces employed around 1.14 million (Federal Employment Agency) severely disabled people in 2024.

Indicator	Value	Source
People with a recognised severe disability, end of 2025	7.8 million	Federal Statistical Office
Share of the population	9.4 percent	Federal Statistical Office
Employment rate 2024	50.9 percent	Federal Employment Agency
Unemployment rate 2025	12.0 percent	Federal Employment Agency
Registered unemployed for a year or longer, 2025	45 versus 34 percent	Federal Employment Agency
Monthly exit rate into employment, 2025	2.8 versus 6.2 percent	Federal Employment Agency

The gap opens up less when holding a job than when finding a new one. The unemployment rate among severely disabled people was 12.0 percent (Federal Employment Agency) in 2025. On annual average in 2025, around 45 percent (Federal Employment Agency) of unemployed severely disabled people had been registered for a year or longer, compared with 34 percent among people without a severe disability. The monthly rate of exit into employment on the primary labour market was 2.8 percent (Federal Employment Agency) against 6.2 percent for people without a severe disability. Every additional barrier in the application process extends exactly that duration.

The employment quota turns this into arithmetic

Alongside the prohibition of discrimination sits a second, far more concrete duty. Under section 154 (1) SGB IX, private and public employers with a monthly annual average of at least 20 workplaces must fill at least 5 percent (SGB IX) of those workplaces with severely disabled people. Employers who miss the quota pay a monthly compensatory levy for each unfilled mandatory workplace. Section 164 (1) SGB IX additionally requires employers to examine whether vacant positions can be filled with severely disabled people (SGB IX).

Public employers face a third duty with direct consequences for the design of the application flow: under section 165 SGB IX, severely disabled people who apply for an advertised position are invited to an interview; the invitation may only be omitted where professional suitability is obviously lacking (SGB IX). The duty presupposes that the application arrives at all and that the declaration of a disability can actually be recorded. A select field that cannot be operated by keyboard effectively disables the duty to invite. The same point is examined from the buying side in public procurement.

In practice the quota is not met. According to the most recent figures available, from 2023, 180,359 companies (Inklusionsbarometer Arbeit) fell under the employment obligation, and the economy-wide employment rate fell from 4.44 to 4.41 percent (Inklusionsbarometer Arbeit). Almost 47,000 companies (Inklusionsbarometer Arbeit) employ not a single person with a disability although they are obliged to. Among small companies with 20 to 39 staff the employment rate is a mere 2.9 percent (Inklusionsbarometer Arbeit).

The calculation your board will understand

The compensatory levy falls due every month for each unfilled mandatory workplace. An application flow that screens out severely disabled applicants before they even reach the inbox prevents precisely the hires that would reduce that levy. This is the rare case where accessibility does not appear as a cost item but as an offset.

Five stages where applications break off

An application flow is not a form, it is a chain. Every link has its own reason for abandonment, and every abandonment stays invisible to the company because it happens before the inbox. The following six points cover the majority of the cases we see in audits.

Job search and filters

Filter fields without labels, result lists that swap themselves out without announcement, and job ads published as untagged PDFs with no heading structure.

Account and sign-in

A mandatory account before applying, an image puzzle without an alternative, a code from a second app. The ways around this are in the article on authentication.

Required fields

Labels that exist only as placeholder text, asterisks with no explanation, date fields that enforce a particular notation without naming it.

File upload

A drop zone that responds only to drag and drop, with no reachable button and no feedback on whether the file arrived.

Error messages

A red outline with no text, an error list at the top of the page with no jump target, feedback that is purely visual. See the article on error and status messages.

Session and time limit

The session ends after fifteen minutes, the entries are gone, and there was no warning. Whoever types more slowly loses first.

These defects are not the exception, they are the norm on the web. The annual automated evaluation of one million home pages found detectable WCAG failures on 95.9 percent (WebAIM Million) of pages. Home pages contained an average of 6.9 form inputs (WebAIM Million), a 36 percent increase within three years, and 33.1 percent (WebAIM Million) of those inputs were not properly labelled. On 51 percent (WebAIM Million) of all home pages evaluated, form input labels were missing.

Applying those numbers to an application flow means tightening the standard: a home page has seven fields, an application form has thirty to eighty. On top of that come controls that already stand out on home pages. 46.3 percent (WebAIM Million) of the pages evaluated had empty links and 30.6 percent (WebAIM Million) empty buttons. An empty submit button in an application form is the end of the process, not a cosmetic flaw.

The upload is where it goes wrong most often

In modern application flows the file upload is nearly without exception a bespoke component, and nearly without exception a hand-built one. The browser's native field is keyboard operable, carries an accessible name and reports the selection to assistive technology. The moment it is replaced by a styled drop zone, every one of those properties becomes a deliberate decision by the development team, and every one of them can be missing.

The drop zone has a reachable button with its own accessible name, not just a hint about dragging and dropping.
The button meets the minimum size of 24 by 24 (W3C) CSS pixels required by success criterion 2.5.8 of WCAG 2.2.
After selection the file name appears as text on the page and is announced through a status message under success criterion 4.1.3.
Upload progress is not only drawn as a bar but also written out as text.
Permitted file types and the size limit are stated before the field, not only in the error message.
An uploaded file can be removed again by keyboard, and the removal is confirmed.
Keyboard-only operation is tested end to end, not just the focus order on the first page.

The second trap is the application assistant that parses a CV and pre-fills the fields. It saves time as long as it works. If it misreads a PDF without structure, the result is an application with scrambled entries that the person has to correct without being able to tell which field is currently in focus. An assistant like that belongs in a screen reader test before it is rolled out; how that works is set out in the article on screen reader optimisation.

Required fields, error messages and the time limit

WCAG 2.2 added two criteria for forms that bite particularly hard in a recruiting context. Success criterion 3.3.7 requires that information already entered in the same process must not have to be entered again, unless re-entering it is essential (W3C). Success criterion 3.3.8 requires that an authentication step must not depend on a cognitive function test for which no alternative exists (W3C). Both are described in detail in the overview of WCAG 2.2.

Situation in the application form	What goes wrong	Criterion
The address is requested again after the CV	Duplicate entry across several steps	3.3.7 Redundant Entry
The label exists only as placeholder text	The label disappears as soon as typing starts	3.3.2 Labels or Instructions
An error is shown only by a red outline	Not perceivable without colour perception	3.3.3 Error Suggestion
An image puzzle before submitting	No alternative route through authentication	3.3.8 Accessible Authentication
Saving a draft produces no perceivable feedback	Assistive technology does not report the success	4.1.3 Status Messages
No autocomplete for name and address	Every field has to be typed out by hand	1.3.5 Identify Input Purpose

The time limit deserves separate attention. Application forms have session limits because they hold personal data, and rightly so. What is wrong is the silent variant: the session ends, the submit button leads to the sign-in page, the entries are gone. People working with voice control or eye tracking need a multiple of the time for the same input; the article on voice operation shows how far the time budgets diverge. A draft saved at every step and an option to extend before the session expires defuse the problem.

Validation itself also decides whether people abandon. A check that fires when the field is left and pulls the focus back makes keyboard completion impossible. Rebuilding the page on submit on top of that loses the position in the form. The rules for this are in the article on form validation.

A bought applicant tracking system stays your responsibility

Most application flows do not run on your own domain. The path ends on the career page and continues into an applicant tracking system, embedded as a frame or hosted under its own address. Legally that changes nothing: the person is discriminated against by the procedure the employer chose. Pointing at the vendor is not a defence in proceedings under the AGG.

Request a conformity statement against EN 301 549, with a date, the scope of testing and the method used. A self-declaration without a test report is not reliable information.
Ask to see the application flow in a customer instance, not the sales demo. What matters is the tenant with your fields, your required entries and your layout.
Put into the contract how quickly reported barriers are fixed and what happens when the deadline passes.
Insist on a fallback: an address to which an application can be sent informally, visible at every stage of the form.
Audit embedded third-party content inside your own pages instead of treating it as foreign territory.

The fallback is the single most effective step and takes an hour to implement. It does not replace an accessible flow, because a separate route for one group of people is itself a disadvantage. But it prevents an application from ending at an image puzzle while the tracking system waits for a vendor update. The wording matters: not a special address for people with disabilities, but an open second route for all applicants.

Audit before the position goes live

An application flow cannot sensibly be audited page by page. The object of the audit is the process: from the job list to the confirmation screen, with real data and a real file. In our audits three passes run side by side, and each one finds different defects.

Step 1

Keyboard pass

No mouse, from the job list to the confirmation page. Visible focus, sensible order, every control reachable, no keyboard trap in the select field or the date picker.

The fourth pass is the most important one and the one least often carried out: people who use assistive technology every day fill in the form and talk while they do it. Automated tools find missing labels; they do not find that a required field asks for information a person does not want to disclose, or that a select field for the degree of disability offers levels that do not exist. A screen reader test with real users does not replace a technical audit, and the technical audit does not replace it either.

Anyone running career pages in several countries also audits against the rules that apply there; which duties go beyond German law is set out in the article on accessibility abroad. For the German framework, the overview of BFSG requirements provides the delimitation, and a WCAG audit provides the test report that procurement wants to see.

An application that ends at a form field appears in no report. To the company it looks like an application that failed to arrive, not like a defect in its own software.

Working principle from auditing application flows

Sources and Studies

This article draws on data from the Federal Statistical Office, the Federal Employment Agency, Inklusionsbarometer Arbeit and the WebAIM Million, and on the texts of the AGG, SGB IX, the BFSG and WCAG 2.2. The figures cited refer to the state of the respective publication.