Detectable warning surface dome geometry

Client-side port:the logic and table in this page are a TypeScript port of the harness function, checked against values exported from the Python tests. Not a live API call. Domain maturity, quoted from the harness README: “No domain expert (ADA/accessibility consultant or city ADA coordinator) has reviewed this code yet.” It is a v1 draft, not compliance guidance. The harness treats 0.2 in as an exact match with zero tolerance, which its own validation sheet flags as an open question given real manufacturing variance, so a 0.21 in dome fails here. Base-to-base spacing is derived as center-to-center minus base diameter. The amber “tight” band is a display choice, not a PROWAG tolerance (and the height has none). Contrast, surface width and placement are fixed illustrative values (parallel curb ramp, 0 in offset); switching them off omits them so the check reports not enough input.Real function this maps to:check_detectable_warning.Not modeled: alterations and technical-infeasibility exceptions (this function does not cover them), platforms, rail boarding areas and driveways (R305.2.6 to R305.2.8), dome cut-edge and expansion-joint allowances, the concrete-border allowance (not wired into the code), and any numeric contrast ratio (PROWAG states none). Location is fixed to the parallel curb ramp rule here; the function also covers perpendicular, blended, refuge-island and rail-crossing placement. The dome grid is an illustrative square layout, not a manufacturer pattern.See also:Detectable warning surface, auto sweep · Curb ramp, interactive