Repair visit selection without replacing the job tool
A job application can be useful overall while one component blocks ordinary work. The decision is whether the demonstrated limitation belongs to that component or to the system’s underlying records and rules.
This fictional review concerns a timeline used to select a visit. Mouse users can open the visit, but a keyboard user cannot reach the interactive markers. The organization initially asks for a replacement application.
Establish what still works
The reviewer inspects a safe copy of the tool. Job J-58 has three separate visits with stable identifiers. The standard list view exposes their dates, status and links. An authorized keyboard user can reach and open each list item.
The timeline uses the same data but renders its markers without a usable keyboard interaction. Its source is available, but the old component has no supported way to supply the required interaction behavior through its documented configuration.
The records and permission rules are not the demonstrated cause. Rebuilding them would expand the project before resolving the actual boundary.
Compare the available changes
The review considers three options.
First, retain the timeline and add a permanent accessible list beside it. This can provide a complete alternative if both views stay synchronized and the timeline does not trap interaction.
Second, replace only the timeline with a component whose interactions can be implemented and reviewed appropriately. This requires integration and visual review, but can preserve the application’s data and routes.
Third, replace the whole application. That would require migration, permission reconstruction, retraining and broad acceptance. The current evidence does not establish a need for those additional changes.
The organization chooses the first option for the initial repair. Staff primarily need to select a visit; the timeline’s visual overview remains supplementary.
Define the result rather than merely adding a list
The repaired screen presents the visit list as an ordinary part of the page, with meaningful link text and visible focus. Selecting V-58B opens that visit’s existing detail route. The timeline does not intercept keyboard movement or hide the list on a narrow screen.
The source record remains the same. There is no second manually maintained list that could drift from the timeline.
In the fictional acceptance exercise, the keyboard reviewer opens all three visits, returns to the list and identifies the currently selected one. A mouse user can still use the timeline. A read-only account retains its original limits, and another job J-59 shows only its own visits.
Inspect the limits of the chosen repair
The list resolves the demonstrated visit-selection task. It does not establish that every other part of the application meets all accessibility requirements. The review record identifies the journeys and methods tested, plus any broader assessment still required.
The timeline remains a maintenance dependency. If a future change requires editing schedules directly within it, the current alternative may no longer satisfy the task. That is the concrete trigger to assess component replacement.
The team avoids calling the whole system “fixed” when the evidence concerns one interaction.
Make the decision reusable
The proposal and handover retain the option comparison, selected scope and controls. A later maintainer can see why the list exists and why it must remain connected to the same visit data.
For your own system, identify a successful route to the same underlying record. Comparing that route with the failing component can help locate the limitation. Software repair begins with that evidence and explains the smallest supported change before recommending a broader replacement.
