Skip to content

Main content

Access Route Measured Turning Margin

Compare an explicit turning diameter with a supplied requirement without certifying an accessible route or selecting standards.

Loading tool…

Description

Compare a measured clear diameter with a supplied required diameter.

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.

Compare a measured clear diameter with a supplied required diameter.

When to use this tool

Use Access Route Measured Turning Margin when you already have measuredClearDiameter, suppliedRequiredDiameter and need to compare a measured clear diameter with a supplied required diameter.

How to use the tool and how it works

  1. Enter measuredClearDiameter, suppliedRequiredDiameter. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read turningMargin, meetsSuppliedDiameter. Inspect meetsSuppliedDiameter before interpreting the associated values.

Require both diameters>=0; margin=measured-required, meets=measured>=required.1

Input fieldMeaning and unitsAccepted input
measuredClearDiameterMeasured Clear DiameterRequired. Finite number; minimum 0.
suppliedRequiredDiameterSupplied Required DiameterRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
turningMarginTurning MarginRequired. Finite number.
meetsSuppliedDiameterMeasured diameter>=supplied required diameter, including equality; no accessibility standard is selected.Required. Boolean.
json
{
  "input": {
    "measuredClearDiameter": 160,
    "suppliedRequiredDiameter": 150
  },
  "output": {
    "turningMargin": 10,
    "meetsSuppliedDiameter": true
  }
}

Limitations and assumptions

  • Equality meets the supplied scalar requirement. No actual turning path, clearance, mobility device, accessibility code or safe route is validated.
  • 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

  1. Calculation and input contract: disability-studies/access-route-measured-turning-margin — tool.io

Similar or alternative tools