A form that calculates an estimate needs a clear place to show its result. HTML provides an element for that job: <output>. It gives the result a semantic home, but it does not perform the calculation simply by appearing on the page.
The MDN reference for output describes a container for a calculation result or the outcome of a user action. Its for attribute can identify contributing controls by their IDs. Application logic still needs to update the displayed value.
Make the result understandable
Imagine a simple fabric-length estimator. A result of “3.2” leaves the visitor guessing. Is that metres, panels or a price? Place a meaningful label and unit beside the value, and explain assumptions such as an allowance included in the estimate.
Our suggested design review uses three states: no usable input yet, a valid result and an input that cannot be calculated. Decide what the visitor sees in each state. Showing yesterday’s valid-looking number after the inputs become invalid can be more confusing than showing no number at all.
Do not confuse display with submission
The HTML standard’s output definition states that its value is not submitted with the form. Giving the element a name does not turn the calculated result into an ordinary submitted field.
For an order or other consequential transaction, the server should validate the inputs and calculate the authoritative result. A value shown in the browser is useful feedback, not a trustworthy replacement for that process.
Test the interaction, not only the markup
Change the inputs with a keyboard and check whether the result remains easy to find. Test the actual screen-reader and browser combinations your service supports, especially when updates occur frequently. Do not assume that a suitable element alone guarantees a comfortable announcement pattern.
A good calculator makes the result, its units and its limits clear. The output element supports that structure; the surrounding labels, error handling and calculation logic make it useful.

