NIST's Campus Conduct Rule: What Federal Accessibility Law Actually Requires

In July 1990, when President Bush signed the Americans with Disabilities Act, federal agencies were simultaneously bound by a parallel legal framework that predated it: Section 504 of the Rehabilitation Act of 1973, which prohibits disability discrimination in any program receiving federal financial assistance — including the programs federal agencies run themselves. The ADA and Section 504 have operated in tandem ever since, creating layered obligations for federal campuses, facilities, and the rules that govern access to them.

On August 21, 2026, the National Institute of Standards and Technology published a final rule updating 15 CFR Part 265 (opens in new window) — the regulations governing traffic and conduct on NIST grounds (Docket No. 260804-0183, 91 FR 54214). Three pages. Effective immediately. No public comment period noted in the available document metadata. On the surface, this looks like routine administrative housekeeping. The accessibility and legal community should look closer.

What the Rule Actually Governs

NIST operates major research campuses in Gaithersburg, Maryland and Boulder, Colorado. These are not closed military installations — they host visiting researchers, contractors, industry partners, and members of the public participating in standards development processes. The conduct and traffic regulations that govern access to these campuses directly shape who can physically reach federal programs, and under what conditions.

Campus conduct rules typically address vehicle access, pedestrian pathways, parking, and behavioral expectations on federal property. Each of those categories carries Title II (opens in new window) analog obligations under Section 504 and the Architectural Barriers Act: accessible parking ratios, accessible pedestrian routes, drop-off zones, and equitable enforcement of conduct standards that don't discriminate on the basis of disability.

The three-page rule published this week doesn't reveal its full text in the Federal Register preview available, but the regulatory framework it amends — 15 CFR Part 265 — is the operative document. Any revision to campus access rules at a federal facility triggers a straightforward legal question: does the updated rule maintain or improve physical and programmatic access for people with disabilities, or does it create new barriers?

The CORS Lens: Four Questions That Matter

The CORS framework — Community input, Operational capacity, Risk/legal priority, and Strategic alignment — offers a structured way to evaluate what this rule means beyond its bureaucratic surface.

Community: Who actually uses NIST campuses? Visiting researchers with mobility disabilities, deaf scientists attending standards meetings, blind technologists participating in NIST's extensive standards development work. NIST's mission places it at the center of technical standards that affect assistive technology — the irony of inaccessible campus access rules would not be lost on the disability community. The Centers for Independent Living in the Maryland and Colorado regions are the right community partners to consult on whether current campus access conditions reflect disabled people's actual experience.

Operational: Federal agencies have internal Section 504 coordinators and, under 28 CFR Part 39 (opens in new window), obligations to conduct self-evaluations and maintain transition plans. The question is whether NIST's revision process included disability access review or whether this was purely a traffic management update drafted without that lens.

Risk/Legal: This is where the analysis sharpens. Federal facilities are governed by the Architectural Barriers Act of 1968 (opens in new window), enforced by the U.S. Access Board, and by Section 504. The Access Board's ABA Standards apply to any construction or alteration of federal facilities. If the conduct rule revision touches parking configurations, pedestrian route designations, or drop-off procedures, those changes must comply with ABA Standards — not as an aspirational goal, but as a legal requirement.

Strategic: NIST is the agency that literally writes technical standards. Its credibility in the standards development community depends partly on modeling the practices it promulgates. An accessible campus is not just a legal obligation — it's a demonstration of institutional integrity.

The Physical Access Baseline

For any federal campus, the legal floor is clear. 28 CFR Part 39 (opens in new window) requires federal agencies to ensure their programs are accessible to people with disabilities. The ABA Standards — specifically the 2004 ABA Accessibility Standards (opens in new window) — govern the built environment. Any conduct rule that affects how people move through, park at, or access federal grounds must be evaluated against these standards.

The specific elements that any campus conduct rule revision should address include:

| Element | Governing Standard | Primary Citation | Compliance Obligation | |---|---|---|---| | Accessible parking spaces | ABA Standards §F208 | 36 CFR Part 1191, App. B (opens in new window) | Minimum ratios by total spaces; van-accessible spaces required | | Accessible pedestrian routes | ABA Standards §F402 | 36 CFR Part 1191, App. D (opens in new window) | Continuous, unobstructed path from parking to facility entrance | | Drop-off/passenger loading zones | ABA Standards §F209 | 36 CFR Part 1191, App. B (opens in new window) | Accessible loading zones where provided | | Programmatic access | Section 504, Rehab Act | 29 U.S.C. § 794 (opens in new window) | Programs accessible to people with disabilities regardless of facility limitations | | Conduct enforcement | ADA Title II principles | 28 CFR Part 35 (opens in new window) | Enforcement must not discriminate on basis of disability |

The Digital Layer Cannot Be Ignored

Campus conduct rules in 2026 are not purely physical documents. They govern how visitors request access, how parking permits are obtained, how security clearances are processed, and how campus maps and navigation resources are provided. Every digital touchpoint in that chain carries Section 508 (opens in new window) obligations for federal agencies.

This is where the compliance picture becomes genuinely complex. As our research on the compliance framework paradox documents, federal agencies face overlapping obligations across Section 508, WCAG 2.1, and ABA Standards — each with different requirements, different enforcement mechanisms, and different timelines. A campus visitor portal that's inaccessible to screen reader users isn't just a technical failure; it's a Section 508 violation that prevents a blind researcher from completing the same pre-visit process a sighted colleague handles in minutes.

The language access dimension compounds this further. NIST's standards development work is explicitly international — visiting researchers and industry partners arrive from countries where English is not the primary language. Title VI of the Civil Rights Act and Executive Order 13166 (opens in new window) require federally funded programs to provide meaningful access for people with limited English proficiency. A campus conduct rule published only in English, with a visitor portal that doesn't support multilingual navigation, creates access barriers that run parallel to disability access failures.

Idioma.chat (opens in new window) represents the kind of infrastructure that addresses this gap correctly — translating not just visible page text but the full accessibility layer: ARIA labels, alt text, form validation messages, and dynamically loaded content. For a federal agency hosting international visitors, accessibility without language access is, functionally, incomplete accessibility. A blind researcher who uses a screen reader and whose primary language is Korean faces compounded barriers that neither disability access nor language access alone can resolve.

What NIST Should Demonstrate

The settlement trap research from this publication documents a consistent pattern: organizations treat compliance as a discrete event rather than an ongoing obligation. A conduct rule revision is an opportunity to audit the full access picture — physical, digital, and linguistic — not just update traffic flow language.

For practitioners reviewing this rule, the immediate questions are:

• Does the revised 15 CFR Part 265 include any changes to parking designations, pedestrian routes, or drop-off procedures? If so, were those changes reviewed against ABA Standards?
• Does NIST's campus visitor portal comply with Section 508 and WCAG 2.1 AA? Has it been tested with real assistive technology users, not just automated tools? (Automated tools catch at most 37% of actual barriers.)
• Does NIST maintain a current Section 504 self-evaluation and transition plan as required by 28 CFR Part 39.105 (opens in new window)?

NIST's mission is to advance measurement science and standards. Its campus conduct rules should model what compliant federal facility governance looks like — not as a symbolic gesture, but as a demonstration that the agency governing technical standards applies those standards to its own operations.

The full text of the rule, available via the official PDF on govinfo.gov (opens in new window), will determine whether this is routine maintenance or a missed opportunity. Either way, the legal framework governing what NIST owes its campus visitors — disabled, multilingual, or both — hasn't changed.