Repair the missing quotation note before replacing the whole tool
An incomplete customer view can look like a limitation of the underlying application. Before replacing a working tool, compare the stored information, the supported presentation options and the actual task the customer cannot finish.
This fictional case concerns an HTML quotation draft. The line data and totals are correct, but an important condition is hidden by a shortened display. It is a presentation problem with a consequence for interpretation, not a reason to assume that every part of the quoting system is unsuitable.
Locate the missing meaning
Line L-4 in draft Q-88 contains the approved note: “Include the slotted bracket only after the customer confirms drawing D-12.” The staff record holds the full sentence. The customer-facing draft displays only “Include the slotted bracket…” and exposes the rest in a hover tooltip.
A reviewer using a narrow touch screen cannot reliably reveal the condition. A keyboard review also finds no usable way to open the tooltip. The visible fragment can therefore suggest an unconditional inclusion when the underlying note is conditional.
The team compares the source record, the generated HTML and the presentation rules. The full note is present in the page data. A line-clamping rule and the hover-only presentation hide it. The supported template configuration permits the note area to wrap and remain visible beneath its line.
Compare the real alternatives
Replacing the quoting platform would involve migrating products, templates, permissions and existing drafts. It could still recreate the same abbreviated-note design if the requirement were left unchanged. That is a substantial transition with no demonstrated need from this finding alone.
Keeping the tooltip and telling staff to write shorter notes is also inadequate. The condition is necessary to the approved meaning. Moving it to a general footer would weaken its association with L-4 and make it harder to tell which product it qualifies.
The selected repair uses the supported template capability to display the complete note with the relevant line. Notes wrap naturally and do not depend on hover to become available. If the layout cannot accommodate the content, the design must provide an explicit accessible expansion with an understandable control; it cannot silently remove the condition.
In this worked case, always-visible wrapping meets the requirement without a new interactive component.
Demonstrate the reader's result
The revised draft shows the entire L-4 sentence on a narrow screen. A keyboard reviewer can reach and read the line and its note in the intended order without opening a hover-only element. The condition remains attached to L-4 rather than being repeated under every product.
The comparison confirms that quantities, unit prices and the draft total are unchanged. Another line with a short note remains readable, and a line without a note does not acquire a misleading placeholder condition. A longer approved note is checked to ensure that the repair did not merely move the truncation limit.
These are fictional results of the selected correction. They support the limited decision to repair this presentation; they do not establish that all accessibility or commercial checks for the application are complete.
Keep the replacement question open to better evidence
The review also records what would change the recommendation. If the provider did not permit a supported template change, if the application dropped the source note, or if a necessary access rule could not be enforced, the comparison would be different. Those are capabilities to inspect, not reasons to assume failure in advance.
Maintenance matters too. The chosen configuration and its purpose should be recorded so that a later visual redesign does not restore the ellipsis. The acceptance example should include the full conditional sentence because a short note would not expose the original problem.
A repair-versus-replacement decision is strongest when it names the observed limitation, the inspected capability, the chosen change and its remaining limits. It should not defend the existing platform at all costs, but it should avoid moving unrelated systems merely to solve a local, supported problem.
The website-renewal service can assess wider constraints. Internal workflow development can address the staff decision behind a quotation when that, rather than presentation, is the actual gap.