That is an expensive omission. Modernization rebuilds the very things that determine accessibility: page templates, components, forms, navigation, and workflows. Fixing accessibility during a rebuild costs a fraction of retrofitting it later. And legal expectations have risen. The European Accessibility Act has applied since June 2025, and accessibility lawsuits and complaints continue in many other jurisdictions.

The state of the web shows how much work remains. WebAIM's 2026 analysis found detectable accessibility failures on almost every major home page it tested. An application modernization company should treat accessibility as part of the rebuild, not a later project.

The Regulatory Picture

The European Accessibility Act covers products and services that the Commission considers most important for persons with disabilities, including computers and operating systems, smartphones, banking services, e-commerce, e-books, and electronic communications. The harmonized standard EN 301 549 references WCAG 2.1 Level AA for web content, which has become the practical benchmark for conformance.

Elsewhere, accessibility obligations continue to apply through disability discrimination laws, public sector requirements, and procurement rules. Organizations that sell internationally face a patchwork of requirements that point toward the same technical standard.

How Inaccessible the Web Still Is

The WebAIM Million 2026 report tested the home pages of the top one million websites. It found detectable WCAG 2 failures on 95.9% of home pages, up from 94.8% in 2025, reversing several years of small improvements. Across the million pages, it detected more than 56 million distinct errors, an average of 56.1 per page, up 10.1% from the previous year. Low contrast text appeared on 83.9% of home pages and missing alternative text for images on 53.1%.

Automated tools detect only some accessibility issues, so full conformance rates are lower still. Business applications, with complex forms, tables, and workflows, often fare worse than marketing home pages.

The Rebuild Is Where an Application Modernization Company Adds Accessibility

Modernization offers unique advantages for accessibility:

Components are being rebuilt: Accessible buttons, forms, menus, dialogs, and tables can be designed once in a component library and reused everywhere.

Design systems are being created: Color palettes, typography, and spacing can meet contrast and readability requirements from the start.

Workflows are being redesigned: Complex processes can be simplified, which helps all users, including those using assistive technologies.

Testing is being set up: Automated accessibility checks can be built into new pipelines from the beginning.

Content is being migrated: Alternative text, headings, and document structure can be corrected during migration.

Retrofitting accessibility after launch means revisiting components, templates, and content that were just built. Teams pay twice.

What App Modernization Services Should Include

App modernization services should include accessibility across the delivery lifecycle:

Requirements: WCAG 2.1 AA conformance as a non-functional requirement, with any additional standards required by the client's markets.

Baseline audit: An assessment of the legacy application's accessibility, so known issues are not carried forward.

Accessible design system: Components built and documented to meet accessibility requirements, with keyboard support, focus management, labels, and roles.

Development practices: Semantic markup, correct use of ARIA where needed, and accessible patterns for dynamic content.

Automated testing: Accessibility checks in continuous integration, failing builds on serious issues.

Manual testing: Keyboard-only navigation, screen reader testing, and zoom testing on key journeys.

User testing: Sessions with people with disabilities on critical workflows.

Documentation: An accessibility conformance report or statement describing conformance and known limitations.

Each element should appear in the statement of work, with acceptance criteria.

Application Modernization Consulting: Assessing the Legacy Estate

Application modernization consulting should include accessibility in portfolio assessments. For each application, assess current accessibility, the user groups affected, legal exposure by market, and the cost of fixing issues during modernization compared with fixing them separately. This information helps prioritize which applications to modernize first and justifies the accessibility effort within each program.

Applications used by customers in EU markets covered by the European Accessibility Act, and applications used by employees with disabilities, often deserve higher priority.

A Representative Program

Consider a regional bank modernizing its online banking and loan application portal. The original scope covers a move to a modern front-end framework, new APIs, and cloud hosting. Accessibility is listed as a phase two item.

An accessibility baseline audit finds that the legacy portal has hundreds of issues: unlabeled form fields, keyboard traps in date pickers, low contrast text, and error messages that screen readers do not announce. The bank serves customers across several EU countries, so the European Accessibility Act applies to its consumer banking services.

The bank moves accessibility into the main scope. The team builds an accessible component library, adds automated accessibility tests to the pipeline, and runs screen reader testing on account opening, loan application, and payments. The added effort is modest compared with the overall program, and far smaller than a separate remediation project would have been. The bank launches with a conformance report and a plan for ongoing testing.

Mobile and Native Applications

Modernization often includes new mobile apps or the rebuild of existing ones. Mobile accessibility relies on platform features such as screen readers built into iOS and Android, dynamic text sizing, and switch control. Components must expose correct labels, roles, and states to these features, and layouts must adapt when users enlarge text. The same principles from WCAG apply, and EN 301 549 includes requirements for non-web software. Test on real devices with assistive technologies enabled, since emulators do not reproduce every behavior.

Budgeting for Accessibility

Buyers often ask how much accessibility adds to a modernization budget. When included from the start, the additional effort is usually a modest share of the program, concentrated in design system work, testing, and training. The cost rises sharply when accessibility is deferred, because teams must reopen components, retest workflows, and sometimes redesign features that cannot be made accessible without structural change.

A useful approach is to estimate both paths during planning: accessibility in scope from the start, and accessibility as a later remediation project. The comparison almost always favors early inclusion, and it gives sponsors a clear reason to approve the effort. Include legal and reputational exposure in the comparison where the application serves markets with active enforcement.

Training Teams Along the Way

Accessible delivery depends on people as much as tools. Designers need to understand contrast, focus states, and accessible patterns. Developers need to know semantic markup and how assistive technologies interpret code. Testers need practice with screen readers and keyboard navigation. Content authors need guidance on headings, link text, and alternative text. A modernization program is a good opportunity to build these skills in the client's own teams, so accessibility survives after the provider hands over.

Common Pitfalls

Modernization programs that include accessibility still make avoidable mistakes:

Relying only on automated tools: Many issues, such as logical reading order and meaningful labels, need manual testing.

Using overlay widgets: Third-party overlays that claim to fix accessibility automatically rarely achieve conformance and can interfere with assistive technologies.

Ignoring documents: PDFs and generated documents often remain inaccessible even when web pages are fixed.

Forgetting third-party components: Embedded payment, chat, and map components must also be accessible.

Treating launch as the end: New features and content can reintroduce issues without ongoing testing.

Choosing an App Modernization Development Firm

When evaluating an app modernization development firm or application modernization agency, ask:

How do you include accessibility in modernization requirements and design?

Do you build accessible design systems and component libraries?

What automated and manual accessibility testing do you perform?

Do you test with people with disabilities?

Can you produce an accessibility conformance report at launch?

How do you handle accessibility of third-party components and documents?

Firms offering application modernization consulting services that answer with specific practices and examples will deliver accessible results. Firms that treat accessibility as an optional extra will leave it for later. Ask to see an accessible component library from a previous project and a sample conformance report, since these show practice rather than intent.

Keeping Applications Accessible After Launch

Accessibility degrades without maintenance. New features, content updates, and third-party changes can introduce barriers within weeks of launch. Keep automated checks in the release pipeline, include accessibility in definition-of-done criteria, schedule periodic manual audits of key journeys, and provide a channel for users to report barriers. Track open accessibility issues alongside other defects, with agreed response times for serious ones. Update the conformance report or accessibility statement when significant changes ship. Assign a named owner for accessibility so these tasks do not fall between teams.

Accessibility Benefits Everyone

Accessible applications are usually easier for everyone to use. Clear labels, logical navigation, good contrast, and simple workflows reduce errors and support calls. Captions help users in noisy environments. Keyboard support helps power users. Investments made for accessibility often improve conversion and customer satisfaction across the whole user base. Older customers, people with temporary injuries, and users on small screens or slow connections all gain from the same design choices, which widens the return on the effort well beyond compliance.

Accessibility is now both a legal requirement in major markets and a widespread failure across the web. Modernization rebuilds the components, templates, and workflows that determine accessibility, which makes it the cheapest and most effective time to get it right. An application modernization company should put WCAG 2.1 AA conformance into requirements, design systems, development, and acceptance testing. Avail app modernization services with accessibility built into design, development, and testing. Rebuilding an application is the best opportunity to make it work for every user.