Description
Calculate the angular height of supplied text geometry.
Accessibility records distinguish requested support, recorded barriers, display choices and measured local geometry. Six-dot permutations depend on array orientation, angular text size depends on viewing geometry, and playback speed changes nominal runtime. These operations do not establish accessible communication, consent, legibility or compliance for an individual or environment.
Calculate the angular height of supplied text geometry.
When to use this tool
Use Display Text Measured Angular Size when you already have measuredTextHeight, viewingDistance and need to calculate the angular height of supplied text geometry.
How to use the tool and how it works
- Enter measuredTextHeight, viewingDistance. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read angularHeightRadians. Use the output convention below.
Require measuredTextHeight>=0 and viewingDistance positive/finite; return 2*atan((height/distance)/2) in radians.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| measuredTextHeight | Measured Text Height | Required. Finite number; minimum 0. |
| viewingDistance | Viewing Distance | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| angularHeightRadians | 2*atan((height/distance)/2) under centered frontal geometry; lengths must share units. | Required. Finite number. |
{
"input": {
"measuredTextHeight": 2,
"viewingDistance": 10
},
"output": {
"angularHeightRadians": 0.19933730498232408
}
}Limitations and assumptions
- Height and distance must share units and assume centered frontal geometry. No legibility, visual function, font metric or accessible text size is established.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Review the person's recorded preferences and actual resource or route with the complete accessibility requirements. Test the relevant output and physical arrangement directly; a display token, scalar clearance or nominal playback ratio does not verify suitability or access.
References
Similar or alternative tools
- Access Route Measured Turning Margin
Compare a measured clear diameter with a supplied required diameter.
- Accessible Audio Speed Runtime Ratio
Calculate nominal playback runtime at a supplied speed multiplier.