There is no fixed amount for making a login environment accessible, and any vendor who quotes one without questions is guessing. What can be said is this: the costs are determined by three factors you can check yourself before requesting a quote. The number of unique screens behind the login, the extent to which those screens are built from standard components or custom-made, and whether the company resolves the problems it finds itself or has them resolved.
The invoice starts with the number of unique templates, not the number of pages. A dashboard with ten tabs that all use the same table, filter, and form structure is often cheaper in assessment work than a login environment with five completely different screens. What counts is variation in interaction: a login form, a password reset flow, a dashboard with filters, an upload function, and a settings page are five different things to assess, even though they sit behind the same login.
Why a login environment often requires more work than the rest of the site
A login environment has problems that a public website usually does not. Sessions that expire after a fixed time violate the requirement around time limits. Error messages for an incorrect password must be traceable for a screen reader to the field where the error occurs. Dynamic elements such as a dropdown menu, a notification bar, or a live-updated counter require focus management: where does the cursor jump to when something changes without the user refreshing the page. These are all points that an automated scan partially detects, but does not fully assess — that is also stated in every report we deliver.
A second cost factor is the origin of the components. If the environment uses a standard library from a well-known framework, accessibility problems are often known and can be resolved with documented adjustments. If the dashboard is mostly custom-built, created by a developer who did not think about accessibility, then each component must be reviewed and adapted separately. You won't notice that difference in the report, but you will in the time restoration takes.
Testing and repair are two separate line items
The cost of mapping the problems and the cost of solving them are two different things, and it is wise to budget for them separately. Axessia tests, prioritises the findings in plain language, and documents what has been checked — that is the part you need to demonstrate that an assessment has been conducted. Actually rewriting a form label, adjusting a colour contrast, or rebuilding an upload component is repair work, and we deliberately do not do that ourselves: that choice is yours to make with your own developer or agency, using the action list as a guide.
That distinction also explains why two companies with a similar login environment can receive very different quotes. One company has an internal development team that works through the action list itself at an hourly rate, the other must hire an external agency for each part. The assessment itself is of comparable scope in both cases; the repair work is not.
What you can establish in advance
Before you expect a figure, it is useful to determine yourself how many unique screen types your account environment has and which of them exhibit dynamic behaviour such as notifications, filters, or live updates. Those two pieces of information largely determine the scope of the assessment work. You can get an indication of where your own environment stands by taking the free quick-scan; which covers a handful of core pages without requiring you to create an account. To access the full scan that also includes the login flow and checkout process, and to see a detailed overview of what is involved, you can view the prices and packages.
Whether your specific situation falls under the law and what that means for your account environment is described in the exemption rules and the scope of the directive; we break that down for your situation in the knowledge base with explanations on each topic. If you are unsure where the figures and testing criteria we use come from, we explain that on the page on how the information is compiled.
Do you want to know where your own login environment currently stands, at no cost? The quick scan provides an initial indication within a few minutes, and the knowledge base shows which areas deserve attention afterwards.