Accessibility Agent — automated accessibility compliance for Revit
The Accessibility Agent reads a Revit model and evaluates door widths, ramp gradients, turning circles, sanitary layouts, and stair geometries against UK Approved Document M and the US ADA Standards for Accessible Design. It focuses on ai accessibility compliance for Revit across both Part M volumes and ADA scopes. It is available now as a co-built Labs engagement under MSA + Appendix, on the roadmap for a productised Beta release.
- Element-pinned accessibility-violation report covering doors, ramps, sanitary rooms, stairs, and circulation routes for each Revit model run.
- Suggested remediations cite the source clause from the applicable Approved Document or ADA standard so the designer can review the exact wording in context.
- Same agent runs against either rule pack — UK and US practices configure once per project type and re-run checks on every design iteration.
What the Accessibility Agent does.
-
Door, corridor, and turning-circle checks
Reads Revit room boundaries, door widths, and circulation paths against the accessible-route requirements in the active rule pack. Flags every door narrower than the applicable threshold with the element ID, the measured width, and the rule clause from Part M or ADA. Highlights pinch points in corridors and turning circles in front of doors, lifts, and sanitary rooms so UK Part M accessibility reviews capture every obstruction before issue.
-
Ramp, stair, and handrail geometry
Evaluates ramp gradients, stair riser and tread dimensions, landing depths, and handrail extensions in the Revit model. Compares each element against the applicable standard, classifies hard violations vs. advisory items, and pins findings to specific element IDs for quick navigation. Handles external ramps, internal stair cores, and split-level transitions so the same workflow supports both ADA accessibility audits and UK Part M checks in one pass.
-
Sanitary-accommodation layout
Walks accessible WCs, bathrooms, and changing places against the diagram-based requirements in Part M and ADA. Reports clearance violations such as transfer spaces, manoeuvring spaces, and approach zones with the measured value and the threshold. Cross-references the relevant diagrams from UK Building Regulations Approved Documents so designers can confirm that grab-rail positions, pan offsets, and basin locations align with the illustrated layouts.
-
Per-rule-pack configuration for UK and US
Each Labs deployment selects the applicable rule pack — UK Approved Document M or US ADA Standards for Accessible Design (2010). The configuration step maps Revit parameters, project templates, and view filters to the chosen standard so results align with the studio’s existing detail libraries. The agent flags advisory items separately so the licensed architect of record decides scope and can document any justified departures in the project’s accessibility report.
-
Revit-native integration and Inspector lineage
Runs inside the same VitruAI + Revit integration as the Code Compliance Agent, using shared Revit-API plumbing for element selection, section-box views, and rule-context callouts. Findings appear as Revit-native views, schedules, or external reports that slot into existing QA/QC workflows. In one sentence: this is The Inspector for accessibility, tuned specifically for Part M and ADA rather than general building-code rules.
-
Available now as a Labs engagement
Roadmap status means the Accessibility Agent runs today as a co-built Labs engagement under MSA + Appendix. VitruAI calibrates the rule pack against the customer’s project types — residential, commercial, healthcare, or education — and validates checks on a live project before wider rollout. That same configuration then feeds the roadmap for the productised Beta, so early Labs participants shape how ai accessibility compliance for Revit behaves in day-to-day use.
Accessibility Agent — common questions
-
When will the Accessibility Agent ship as a productised release?
The Accessibility Agent is available now as a Labs engagement under MSA + Appendix, where we co-build the rule-pack configuration against one of your live Revit projects. The productised Beta release sits downstream of this Roadmap and Labs work, informed by those early deployments. If you need automated accessibility checks on a project this quarter, Labs is the right path; the waitlist is for teams that can adopt the standardised Beta later.
-
Which rule packs do you cover today?
Labs engagements cover UK Approved Document M, including both Volume 1 (Dwellings) and Volume 2 (Buildings other than dwellings), and the US ADA Standards for Accessible Design (2010). The agent selects the correct scope per project so a housing scheme uses the dwelling provisions and an office fit-out uses the non-dwelling provisions. Other jurisdictions such as Australia’s AS 1428 or Canada’s CSA B651 can be scoped as additional rule packs within the same ai accessibility compliance for Revit framework.
-
Does it cover residential vs. commercial differently?
Yes — for UK projects, the agent distinguishes between Approved Document M Volume 1 for dwellings and Volume 2 for buildings other than dwellings, based on the project’s Revit template or a per-model setting. For US projects, it respects ADA distinctions between public accommodations, commercial facilities, and mixed-use schemes, and can tag different wings or floors accordingly. This mirrors how practices already split workflows between residential and commercial in their UK Part M accessibility review and ADA accessibility audit processes.
-
How accurate is it on edge cases like phased renovations?
For phased renovations and existing buildings, the agent still checks door widths, ramps, stairs, and sanitary layouts against the chosen standard, but it treats many findings as advisory. Existing-building provisions, “technically infeasible” alterations, and extent-of-renovation triggers always require human judgment by the architect of record. The report marks these items clearly so the designer can decide whether to upgrade, justify an exception, or document the condition in the project’s accessibility narrative.
-
How does this work alongside the Code Compliance Agent?
The Accessibility Agent shares the same Revit-API plumbing and deployment pattern as the Code Compliance Agent, but the rule scope is different. Code Compliance focuses on building-code topics such as setbacks, heights, egress, and fire compartmentation, while Accessibility focuses specifically on Part M and ADA provisions for access and use. Many studios run both agents on the same Revit model so accessibility issues, fire strategy, and zoning constraints are reviewed together before formal submission.
-
What does the workflow look like inside Revit?
Designers run the Accessibility Agent from within the VitruAI + Revit integration, selecting the active rule pack and project type before each check. The run produces a model-linked report with views, element IDs, and rule citations that can be assigned during internal QA or design team reviews. That same output feeds into practice-specific workflows for UK Building Regulations Approved Documents sign-off and pre-submission audits alongside general code checks.