What Does It Take to Get There?

Decoupling is not just a technical detail – it’s a strategic choice that affects the entire development model. A well-designed base software, combined with clearly defined interfaces and a thoughtful component architecture, enables high code reuse across different models and generations.

This requires:

• A clear software architecture that defines responsibility, dependencies, and isolation between functions
• CI/CD pipelines that support both vehicle-specific verification requirements and continuous integration
• Cross-functional teams capable of owning entire functions – from development to in-field operations

Middleware plays a key role here. It acts as a hub between hardware and application, abstracting the complexity of diverse hardware platforms. By managing resources, providing standardized APIs, and enabling virtualization, middleware forms a technical backbone for portability and reuse at a scale previously hard to achieve.

With increased connectivity, OTA updates, and external APIs comes increased responsibility. Cybersecurity and data protection can no longer be added at the end of development – they must be embedded in the architecture from the start.

Safety-critical functions must be isolated, updates signed and validated, and all data handling must comply with strict regulations – including GDPR and industry-specific standards such as UNECE R155 and ISO/SAE 21434. The ability to secure systems over time is key to building both trust and technical resilience.

Organizational Transformation in Practice

Technical transformation must be supported by organizational structures. OEMs that break down function-based silos and create teams with end-to-end responsibility – from idea to OTA update – report improved development speed and product quality.

At the same time, the relationship with suppliers is changing. Instead of linear chains, platform-based collaborations are emerging, where OEMs, Tier 1s, and tech companies co-develop around shared APIs, data models, and lifecycle strategies. This demands new levels of technical leadership and openness across the ecosystem.

The Car of the Future Is Always Current

The strategic business benefits are clear: faster time-to-market, shorter update cycles, and better scalability of innovation across product lines. At the same time, new revenue models emerge through service-based offerings, subscription features, and extended vehicle lifespans.

But with longer vehicle lifespans come new demands. Managing the full software lifecycle – from initial development to support, updates, and decommissioning – becomes a new challenge for the industry.

OEMs need strategies for maintaining compatibility with legacy hardware, handling component obsolescence, and ensuring that even vehicles on the road for ten to fifteen years can still receive critical updates and security patches.

In the end, the value of tomorrow’s vehicle won’t just lie in what’s built into it – but in its ability to continuously improve after delivery.
Data becomes an asset. APIs become business interfaces. The product becomes a platform.

Key Requirements – What Must You Do?

To ensure compliance, businesses and organizations should do the following steps:

Conduct a comprehensive accessibility audit to identify gaps in existing digital solutions. Automated tools such as axe DevTools, WAVE, and Lighthouse are useful for detecting technical issues, but they do not capture everything. Complement them with manual reviews and user testing to ensure real accessibility.

Implement measures based on WCAG 2.1 AA – The POUR principles should be followed:

• Perceivable: Information must be accessible to everyone, regardless of sensory limitations. Example: Alternative text, clear contrast, customizable fonts.
• Operable: Navigation and interaction must work with assistive technologies. Example: Keyboard navigation, predictable interactions.
• Understandable: Information must be easy to read and use. Example: Plain language, consistent design
• Robust: Content must be compatible with different technical solutions, including screen readers and AI-based assistants.

Train employees in digital accessibility. This means to ensure that designers, developers, and content creators have the necessary knowledge to create accessible content.

Ensure that subcontractors comply with the rules. When procuring services, accessibility requirements must be included in contracts.

Don’t skip to document and report. Organizations must establish routines to meet the requirements and conduct regular audits. Accessibility statements should be published on websites and updated regularly.

Common Pitfalls and How to Avoid Them

Implementing digital accessibility can be challenging, and many organizations encounter similar obstacles. Here are the most common pitfalls and how to avoid them.

Understanding the Exact Requirements

Many businesses underestimate the complexity of accessibility requirements and assume that meeting basic WCAG levels is enough. The issue is that guidelines are not always easy to interpret and implement. The solution is to train your team and consult experts. Automated tools provide a good overview, but manual testing with real users is essential to identify practical barriers.

Implementing Changes on Time

One of the biggest mistakes is postponing accessibility work until the deadline approaches, leading to costly last-minute fixes. Plan actions early and prioritize key changes that have the greatest impact on usability. Integrating accessibility into the regular development process reduces the risk of late and expensive adjustments.

Testing with Real Users

Even if a website technically meets WCAG requirements, it does not necessarily mean it functions well for people with disabilities. User testing with individuals who have different needs is crucial for identifying real problems. Without this, you risk creating solutions that look good on paper but are difficult to use in reality.

Training the Entire Organization

Accessibility is not a one-time task for developers – it requires a long-term strategy where everyone in the organization, from designers and content creators to management and support staff, understands its importance. Regular training and clear internal guidelines ensure that knowledge remains up to date and applied at all levels.

Overcoming Internal Resistance and Resource Constraints

A common misconception is that accessibility work is time-consuming and expensive. In reality, inaccessible solutions often become more costly in the long run due to legal risks, customer losses, and negative publicity. Highlight the business benefits and ensure that management views accessibility as an investment rather than a cost.

Getting Started – A Practical Checklist

To succeed with digital accessibility, having a structured plan is crucial. Here is a practical checklist to ensure your organization is ready:

1. Conduct an accessibility audit: Identify gaps in digital solutions using automated tools and manual testing.
2. Train developers, designers, and content creators: Ensure they understand WCAG 2.1 AA and best practices for accessibility.
3. Update websites and digital services: Implement improvements to meet accessibility requirements. Prioritize changes with the most significant impact.
4. Test with real users: Involve people with different disabilities to ensure practical usability.
5. Train staff and management: Educate everyone involved, from developers to decision-makers, to secure internal support.
6. Ensure subcontractors comply: If you use external systems or services, confirm they meet accessibility standards.
7. Document and report: Establish a long-term accessibility plan and publish an accessibility statement.