DEV Community

Cover image for Migrating to Mobile Accessibility without a Freeze Window
Amit chakraborty
Amit chakraborty

Posted on Originally published at amitchakraborty.dev

Migrating to Mobile Accessibility without a Freeze Window

The Situation

Say you are a mobile app developer tasked with improving the accessibility of your React Native application. You have been using an older approach to accessibility, but you know it's time to migrate to a more modern and robust solution. However, you cannot afford to introduce a freeze window, where development and releases are put on hold while the migration is taking place. Your team is still receiving feature requests and bug fixes, and you need to ensure that the migration does not disrupt the normal functioning of your app.

You start by trying to integrate the new accessibility features into your existing codebase, but you quickly realize that it's not as straightforward as you thought. The new features require significant changes to your app's architecture, and you're not sure how to make the transition without introducing bugs or breaking existing functionality. You've already spent several days trying to make it work, but you're still experiencing issues with screen reader support, high contrast mode, and other accessibility features.

The cost of not migrating to the new accessibility features is clear: your app will not be usable by users with disabilities, and you may even be subject to legal penalties. But the cost of introducing a freeze window is also high: your team will not be able to deliver new features or bug fixes, and your app will fall behind the competition.

Why it Happens

The old approach to accessibility in React Native relied on a set of third-party libraries and workarounds to provide basic accessibility features. However, these libraries are no longer maintained, and the workarounds are not compatible with the latest versions of React Native. The new approach to accessibility in React Native uses a built-in set of APIs and tools to provide robust accessibility features, but it requires significant changes to the app's architecture.

One of the main reasons why migrating to the new accessibility features is challenging is that it requires a deep understanding of the app's architecture and how it interacts with the accessibility APIs. Additionally, the new features require significant testing and validation to ensure that they are working correctly, which can be time-consuming and resource-intensive.

The Fix, Step by Step

To migrate to the new accessibility features without introducing a freeze window, you can follow these steps:

  1. Create a separate branch for the migration: Create a new branch in your version control system to isolate the migration work from the rest of the codebase. This will allow you to work on the migration without affecting the main branch.
  2. Update the app's architecture: Update the app's architecture to use the new accessibility APIs and tools. This may involve significant changes to the app's codebase, including updating components, screens, and navigation.
  3. Implement accessibility features incrementally: Implement the accessibility features incrementally, starting with the most critical ones. For example, you may start by implementing screen reader support, followed by high contrast mode, and then other features.
  4. Test and validate each feature: Test and validate each accessibility feature as you implement it, to ensure that it is working correctly and not introducing bugs or breaking existing functionality.
  5. Merge the migration branch into the main branch: Once you have completed the migration, merge the migration branch into the main branch, and release the updated app to production.

What it Costs, and When Not to Do It

The cost of migrating to the new accessibility features without a freeze window is significant, as it requires a deep understanding of the app's architecture and the accessibility APIs, as well as significant testing and validation. However, the cost of not migrating is also high, as it may result in legal penalties and a loss of users with disabilities.

You should not attempt to migrate to the new accessibility features without a freeze window if you have a very large and complex codebase, or if you have a very short deadline to complete the migration. In these cases, it may be better to introduce a freeze window to ensure that the migration is done correctly and without introducing bugs or breaking existing functionality.

At Your Level

  • Starting out: If you're new to mobile app development, focus on learning the basics of accessibility and how to implement it in your app. Start by reading the official React Native documentation on accessibility and experimenting with the built-in accessibility APIs.
  • Working engineer: If you're an experienced mobile app developer, focus on understanding the new accessibility features and how to implement them in your app. Start by reviewing the app's architecture and identifying areas where the new accessibility features can be implemented.
  • Senior or staff: If you're a senior or staff engineer, focus on leading the migration effort and ensuring that it is done correctly and without introducing bugs or breaking existing functionality. Start by creating a plan for the migration and assigning tasks to team members.
  • Lead or director: If you're a lead or director, focus on prioritizing the migration and allocating resources to ensure its success. Start by reviewing the business case for the migration and identifying the resources needed to complete it.

In the Interview

When interviewing for a mobile app development position, you may be asked about your experience with accessibility and how you would migrate an app to the new accessibility features. A weak answer might be: "I would just update the app to use the new accessibility APIs and tools." A strong answer would be: "I would start by reviewing the app's architecture and identifying areas where the new accessibility features can be implemented. I would then create a plan for the migration, including testing and validation, and assign tasks to team members. I would also ensure that the migration is done incrementally, without introducing a freeze window, to minimize the impact on the app's functionality and user experience."

The follow-up question might be: "How would you handle a situation where the migration is taking longer than expected and the app's functionality is being impacted?" A strong answer would be: "I would prioritize the most critical accessibility features and implement them first, while also ensuring that the app's functionality is not impacted. I would also communicate regularly with the team and stakeholders to ensure that everyone is aware of the progress and any issues that arise."


Amit Chakraborty is a founding engineer and senior architect — React Native, AI/RAG systems and production architecture. Portfolio: www.amitchakraborty.dev · LinkedIn · GitHub. Open to senior and founding engineering roles, remote worldwide.

Top comments (0)