Detectable warning surface extent — auto

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 applies the 24 in extent minimum in every application context, with no tolerance, and the amber “tight” band (within 2 in of the minimum) is a display choice, not a PROWAG tolerance. The dome dimensions are held at values inside the ranges, and contrast, surface width and placement are fixed illustrative values (parallel curb ramp, 0 in offset).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, dome cut-edge and expansion-joint allowances, the concrete-border allowance (not wired into the code), any numeric contrast ratio, and placement scenarios other than the parallel curb ramp rule. The dome grid is an illustrative square layout, not a manufacturer pattern.See also:Detectable warning surface, interactive · Curb ramp, auto sweep