ADA Compliance for Digital Building Directory Signs (2026): Checklist, Design Specs + Procurement Language

Last Updated: 8/14/2026

Quick Summary: This guide explains how ADA rules apply to digital building directory signs, especially where buyers often get confused. Building directories are generally exempt from tactile characters and Braille requirements, but they still need safe physical placement, accessible communication, readable digital interfaces, and clear procurement documentation. For state and local government entities, the DOJ’s Title II rule makes WCAG 2.1 AA especially important for digital services by 2026 or 2027, so buyers should require VPAT/ACR documentation, accessibility testing, remediation SLAs, and onsite acceptance checks before final approval.

Under the ADA Standards for Accessible Design, building directories are generally exempt from tactile (raised) characters and Braille requirements, but a digital directory kiosk still must be installed and designed so people with disabilities can safely approach it, reach it, and access its information through effective communication. With the DOJ’s Title II digital accessibility rule setting WCAG 2.1 Level AA as the technical standard for state and local government services by April 24, 2026, procurement teams and facility managers need directory-specific guidance that connects ADA sign scoping, physical placement safety, and digital interface accessibility into one defensible implementation path.

A digital building directory sign is a lobby-mounted display (touch or non-touch) that publishes tenant, floor, and wayfinding information and is updated electronically rather than reprinted. Most buyers assume directories follow the same ADA rules as permanent room signs. They don’t. This confusion leads to three common mistakes: applying tactile sign rules where they don’t belong, ignoring physical access and safety requirements that do apply, and purchasing interactive touchscreens without requiring WCAG-aligned interface design or vendor accountability.

The stakes are higher than aesthetics. Nearly 20% of Americans have some type of disability, according to Section 508 procurement guidance. If your building’s primary wayfinding tool cannot be safely approached, physically operated, or visually perceived by people with disabilities, you’ve created a barrier at the front door. This guide delivers three things competitors skip: a clear breakdown of what the ADA Standards actually require for directories versus what is required for digital interfaces under the 2026 DOJ rule, installation specifications that prevent protrusion hazards and circulation conflicts, and copy-paste procurement language that forces accessibility into contracts before the kiosk ships.

Use this checklist to separate ADA sign rules, physical access requirements, digital interface accessibility, communication obligations, and procurement documentation.

Digital Directory Accessibility Requirement Areas

Directories may be exempt from tactile-and-Braille sign fabrication rules, but they are not exempt from the obligation to provide accessible communication and safe physical access to the information they present. That nuance is what separates compliant projects from lawsuits. The rest of this guide gives you the implementation checklist, design specifications, and contract templates to get it right the first time. Digital Directory Express provides lobby directory signs designed with these requirements built in, so you don’t have to engineer accessibility from scratch.

What the ADA Standards Say About Signs and Why Directories Confuse Everyone

ADA sign compliance is scoping plus technical requirements. Scoping answers which signs need accessibility features. Technical requirements answer how those features must be designed. Most confusion happens because people skip scoping and jump straight to “Does this need Braille?” The answer depends on what the sign communicates and whether it is permanent or changeable.

Sign scoping means determining which sign types are required to be accessible and which technical requirements apply based on what the sign communicates and how permanent it is. The U.S. Access Board Chapter 7 guide breaks signs into three categories. First, permanent room and space identification signs must have raised (tactile) characters and Grade 2 Braille. Think restroom signs, stairwell labels, and room numbers. Second, directional and informational signs (like “Conference Center →”) must meet visual requirements like character height and contrast but typically do not need tactile elements. Third, certain content is explicitly exempt from tactile requirements: temporary signs, occupant names and logos, and building directories.

Building directories fall into the exempt category because the information changes frequently. Tenants move in and out. Names are updated. Listings get reorganized. Fabricating tactile characters and Braille for every tenant name on every floor is impractical when the directory might change monthly. The Access Board recognized this and carved out the exemption. That’s the good news.

The confusion comes from what the exemption does not mean. It does not mean you can ignore accessibility entirely. It does not mean a digital directory can block a hallway, protrude into a travel path, or display illegible information. It means you’re exempt from one specific fabrication rule (tactile sign production), not from providing equal access to the information the directory conveys.

Why does a lobby directory still matter if it’s exempt? Because in most buildings, the directory is the primary wayfinding touchpoint. If a visitor cannot safely approach the kiosk, read the screen, or use the interface, the building has failed to provide effective communication. Effective communication means providing information in ways that are as understandable and usable for people with disabilities as they are for everyone else. Courts have ruled that relying on inaccessible systems can violate ADA obligations even when the content itself is exempt from specific technical standards. Think of it as a risk management issue.

Use this comparison to clarify which sign types typically require tactile characters, Braille, visual contrast, or only general readability best practices.

ADA Sign Requirements by Sign Type

Here’s a practical decision tree. Ask: Is this a permanent room or space identification sign? If yes, it needs tactile and Braille. Ask: Is this content temporary or changeable (like a tenant list)? If yes, exempt from tactile/Braille. Ask: Does the sign provide directional or informational content that doesn’t identify a permanent space? If yes, visual requirements apply but tactile typically does not.

One common installation combines exempt and non-exempt content. You might mount a digital directory screen next to permanent tactile signs that label “Elevator” or “Restroom.” The directory itself is exempt, but the nearby labels are not. Best practice is to pair your changeable tenant directories with compliant tactile signs at critical decision points like elevator lobbies and main doors. This gives users two access paths: one for quick visual browsing (the screen) and one for tactile confirmation (the permanent signs).

Before you change a kiosk design, first classify the content. Permanent room identification has different ADA sign rules than changeable directory information. Understanding scoping saves you from applying irrelevant requirements and missing the ones that actually matter.

2026 Digital Accessibility Reality: When WCAG and Section 508 Matter for Digital Directories

Does WCAG apply to my directory? Start here: Are you a state or local government entity? If yes, the DOJ Title II final rule requires WCAG 2.1 Level AA compliance for covered digital services, including web content and mobile applications. For larger entities (populations over 50,000), the compliance date is April 24, 2026. Smaller entities and special district governments have until April 26, 2027.

If your lobby directory includes an interactive touchscreen interface with search, filtering, or wayfinding features, treating it as a digital service covered by the rule is the safest approach. The DOJ rule establishes technical requirements to provide concrete standards to public entities on how to fulfill their obligations under Title II to provide equal access to all of their services, programs, and activities that are provided via the web and mobile apps. A touchscreen directory that serves as the primary information access point in a city hall, county building, or transit station falls squarely into that category.

For state and local government entities, the DOJ’s Title II digital accessibility rule sets WCAG 2.1 Level AA as the technical standard for covered web and mobile services, with a compliance date of April 24, 2026 for larger public entities. This is not optional. It’s a federal regulation with enforcement mechanisms. Massachusetts Title II guidance confirms WCAG 2.1 AA as the standard and emphasizes the April 24, 2026 date for municipalities over 50,000 residents.

What if you’re not a government entity? Private commercial buildings, healthcare facilities, and educational institutions are not directly covered by the Title II rule. But WCAG-aligned design is still recommended as best practice for reducing complaints and improving usability. Courts have used WCAG as a benchmark in Title III cases (public accommodations). Procurement teams at private institutions often require WCAG compliance in RFPs because it provides a clear, testable standard and reduces legal risk. The practical reality is that WCAG has become the de facto accessibility standard for interactive digital interfaces across both public and private sectors.

Section 508 is a related but separate requirement. Section 508 of the Rehabilitation Act requires federal agencies to make their electronic and information technology accessible to people with disabilities. If your project involves federal procurement, federal funding, or federal facilities, Section 508 compliance is mandatory. The Section 508 standards incorporate WCAG 2.0 Level AA as the baseline technical requirement. Many state and local governments also adopt Section 508 language in their procurement policies even when not strictly required.

A VPAT is a Voluntary Product Accessibility Template used to produce an Accessibility Conformance Report (ACR) that documents how well a product supports accessibility standards such as WCAG and Section 508. When you’re buying a digital directory kiosk, asking for a current VPAT/ACR is the simplest way to understand what you’re getting. A vendor that cannot produce an ACR or provides one with major nonconformance issues is telling you they haven’t tested their product for accessibility. That’s a red flag.

Minnesota IT procurement guidance requires agencies to request ACRs based on VPATs early in the procurement process. Colorado’s vendor accessibility checklist similarly mandates evaluation of WCAG 2.1 Level A and AA conformance and requires vendors to complete an ACR using the ITI VPAT template. These aren’t unique policies. States across the country are embedding accessibility documentation requirements into standard IT procurement workflows.

Accessibility Procurement Requirements by Owner Type

If a city, county, or other public entity is buying a touchscreen directory as part of its public-facing services, requiring WCAG 2.1 AA evidence in the contract is the simplest way to reduce 2026 compliance risk. Don’t wait until after installation to discover the interface fails basic keyboard navigation, has insufficient contrast, or times out without warning. Write the requirement into the RFP. Require testing evidence before acceptance. Make remediation a condition of final payment.

Digital Directory Express offers turnkey digital directory solutions that integrate hardware selection, WCAG-aligned interface design, and documentation into a single delivery. This eliminates the coordination problem where one vendor builds the enclosure, another codes the UI, and nobody takes responsibility for accessibility testing or ACR production. Turnkey delivery means one partner owns the entire accessibility outcome.

Physical Installation Specs for ADA-Friendly Digital Directory Kiosks

Don’t design the UI until you know where the kiosk can legally and safely go. Physical placement is the first accessibility decision. Get it wrong and the best-designed touchscreen in the world won’t matter because users cannot safely approach it.

A protruding object is an item that extends into a circulation path at a height where it may not be detected by a cane, creating a collision hazard for people with low vision. The U.S. Access Board sign guide explains protrusion limits: objects with leading edges between 27 inches and 80 inches above the floor cannot project more than 4 inches into circulation paths when wall-mounted, or more than 12 inches when post-mounted (if the object is detectable below 27 inches by cane).

For wall-mounted directory enclosures, the common interpretation is a 4-inch maximum protrusion from the wall. This is why many lobby directories are recessed into the wall or mounted in alcoves rather than projecting into main corridors. If you’re mounting a slim-profile touchscreen flat against a wall, verify that the total depth (screen + enclosure + mounting bracket) stays within 4 inches. If your design exceeds that, you need to either recess the installation or ensure the leading edge is detectable by cane below 27 inches (which usually means adding a base or plinth that extends to the floor).

For freestanding pedestal kiosks, the 12-inch protrusion rule applies if the base is cane-detectable (extends to the floor and is detectable within the 27-inch height zone). Many pedestal designs inherently meet this because the base creates a detectable object at floor level. If you’re considering a narrow pedestal with a small footprint, confirm with your accessibility consultant or local authority having jurisdiction that the installation meets protrusion safety requirements.

Clear floor space means providing unobstructed space for a wheelchair user to approach and use the directory. Think of this as equivalent to the “beyond door swing” logic used for tactile sign placement in the Access Board guide. You wouldn’t place a required sign where a door swing would block access to it. Same principle applies to interactive kiosks. Don’t place the directory where a door swing, furniture arrangement, or other obstruction prevents someone in a wheelchair from getting close enough to use it.

Typical clear floor space guidance calls for a 30 by 48 inch minimum space positioned for either forward or parallel approach. For a touchscreen directory, forward approach is most common. Position the kiosk so a user can roll up to the screen without encountering planters, benches, or other barriers. Avoid placing interactive kiosks in door-swing conflict zones. This is basic circulation planning but gets missed in retrofit projects where lobbies are already crowded.

Reach to interactive elements is less about strict numeric requirements (which vary by context) and more about practical usability. Keep key actions like “Search,” “Directory A–Z,” “Floor selector,” and “Send to phone” within comfortable reach for seated users. Avoid placing critical buttons in the extreme top corners of a 55-inch display. Test your layout by sitting in a chair and confirming you can access all functions without straining. Digital Directory Express designs place primary navigation controls in the center third of the screen and avoid relying on extreme edge taps for essential tasks.

Non-glare finish and lighting matter more for digital screens than for printed signs. A printed sign might have a non-glare matte surface. A digital screen has a glass surface that can reflect overhead lighting, windows, and lobby chandeliers. Use anti-glare or anti-reflective glass. Adjust screen brightness to remain legible under your actual lobby lighting conditions (test at different times of day). Angle the screen slightly downward if it’s mounted high, to reduce ceiling light reflections. These are practical commissioning steps that get skipped when teams treat kiosks like furniture instead of functional information systems.

Touch versus non-touch affects reach and operable-part constraints. A non-touch “contactless” directory that uses proximity sensors, QR codes, or a companion mobile app reduces the need for precise reach ranges and fine motor control. Users don’t have to physically tap the screen. They can scan a QR code and complete the task on their own device, which they’ve already customized for their accessibility needs. Non-touch doesn’t eliminate placement requirements (the kiosk still can’t be a protruding hazard), but it does reduce operational barriers for people with limited dexterity or reach.

The fastest way to fail an accessibility review is to mount a directory where users cannot safely approach it or where the enclosure becomes a protruding object in the path of travel. Avoid this by conducting a site survey before ordering hardware. Measure door swings. Identify circulation paths. Confirm mounting surface capabilities. Choose purpose-built enclosures like the upright pedestal kiosk that are engineered with protrusion and stability in mind, rather than improvising a mount for a commercial TV.

Use this onsite checklist to confirm that the installed digital directory is reachable, stable, readable, and safe in the building’s circulation path.

Onsite Digital Directory Accessibility and Safety Checklist

On-Screen Design Specs for Directory UI

If your directory is interactive, assume people will use it with low vision, limited dexterity, or no audio. Design for those scenarios from day one rather than retrofitting accessibility after complaints arrive. The specs below are anchored to WCAG 2.1 Level AA because that’s the standard public entities must meet by 2026, and it’s become the benchmark for private procurement as well.

Contrast targets start with WCAG ratio requirements. Normal text (under 18-point or under 14-point bold) needs a contrast ratio of at least 4.5:1 against its background. Large text (18-point and larger, or 14-point bold and larger) needs at least 3:1. For UI components and graphical objects, the requirement is 3:1 minimum contrast against adjacent colors. TouchSource’s ADA compliance guide summarizes these thresholds and explains why they matter: sufficient contrast ensures legibility for users with low vision or color vision deficiencies.

Use a contrast checker tool during design. Test your tenant names, floor labels, and search results against the background color. If you fail the ratio test, increase the contrast (darken text or lighten background). Avoid light gray text on white backgrounds or dark blue on black. These combinations look modern but fail accessibility testing. Stick to high-contrast pairings like black on white, white on dark blue, or dark gray on light backgrounds.

Text size and legibility depend on viewing distance. A lobby directory is typically viewed from 3 to 6 feet away. For stand-off distances in that range, aim for a minimum equivalent font size of 18 to 24 points for body text (tenant names, floor numbers) and 28 to 36 points for headings (section labels like “Floor 3” or “Directory A–Z”). These are practical minimums, not code mandates. The Access Board sign guide provides character height formulas for permanent signs based on viewing distance, and while those formulas don’t directly apply to screens, the underlying legibility principle does: farther viewing distance requires larger characters.

Use sans-serif fonts. Arial, Helvetica, Open Sans, and similar typefaces are more legible on screens than serif fonts or decorative scripts. Avoid all-caps for body text (it’s harder to read). Use sentence case or title case. If your brand guidelines require a specific font, test it for on-screen legibility at your target sizes and distances before committing to it across the entire directory interface.

Motion and flash must be carefully controlled. WCAG Success Criterion 2.3.1 (Three Flashes or Below Threshold) prohibits content that flashes more than three times per second because it can trigger seizures in people with photosensitive epilepsy. For a building directory, this is straightforward: don’t use rapidly flashing animations, strobe effects, or flickering transitions. Smooth, slow transitions are fine. Rapid blinks are not. Most directory UIs don’t need motion at all. A static list of tenants with smooth scroll is fully functional and carries zero seizure risk.

Timeouts and session resets are a major usability issue on public kiosks. Users with mobility or cognitive disabilities may need more time to read, search, or make a selection. If your directory automatically resets after 30 seconds of inactivity, you’re penalizing slower users. Best practice is to provide a visible countdown timer (“This session will reset in 15 seconds”) and an easily accessible “Extend time” button. WCAG 2.2.1 (Timing Adjustable) requires that users can turn off, adjust, or extend time limits unless the time limit is essential to the activity. For a directory, the time limit is not essential. You can extend it or disable it. Digital Directory Express kiosks default to 60-second idle timeouts with a 10-second warning and a large “Need more time?” button that resets the clock.

Touch target sizing prevents accidental taps and accommodates users with tremors or limited fine motor control. A common internal standard is 44 by 44 CSS pixels (equivalent) for primary touch targets, with adequate spacing between adjacent targets to prevent mis-taps. This aligns with WCAG 2.5.5 (Target Size, Level AAA) guidance, though that criterion is Level AAA (not AA). Even so, it’s a reasonable design standard for public kiosks where precision tapping is difficult. Make your “Search” button, tenant name links, and floor selectors large enough to tap comfortably. Avoid tiny tap zones in screen corners or densely packed grids where a shaky hand might select the wrong item.

Alternative access paths solve the “I can’t use the touchscreen” problem. QR codes are the simplest alternative. Display a QR code on the kiosk screen (or printed nearby) that links to a mobile-friendly directory page. Users who cannot operate the touch interface can scan the code and complete the task on their own phone, which they’ve configured with screen readers, voice control, or other assistive technology. The QR must not be the only access method (some users don’t have smartphones), but it’s a powerful supplement. Pair it with a short URL printed below the QR so users can type it manually if needed. Ensure the mobile experience is also WCAG 2.1 AA compliant. An inaccessible mobile fallback defeats the purpose.

Audio and captions matter if your directory uses video for instructions or wayfinding. If you include a “How to use this directory” video, provide synchronized captions. Don’t rely on audio alone to convey critical information. Users may be Deaf or hard of hearing, or they may be in a noisy lobby where audio is unintelligible. Captions make video content accessible to everyone. If audio announcements are used (like “Your directions have been sent to your phone”), provide a visual equivalent on screen.

Digital Directory UI Accessibility Guidelines

Treat a touchscreen directory like a public-facing digital service: high contrast, readable type, minimal motion, and no critical task that requires hearing or precise fine-motor control. These specs are not theoretical. They’re testable, enforceable, and aligned with the WCAG 2.1 AA standard that public entities must meet by April 2026. If you’re procuring a directory today, write these requirements into your RFP. If you already have a directory installed, audit it against these criteria and fix gaps before they become complaints.

The interactive touch screen directory from Digital Directory Express ships with templates that meet these contrast and sizing targets out of the box. You’re not starting from a blank design canvas. You’re customizing a proven accessible foundation.

ADA Compliance Checklist for Digital Building Directories

Use this checklist in three phases: pre-bid (to write accessibility requirements into your RFP), pre-install (to verify vendor submissions and site readiness), and commissioning (to confirm the installed system meets acceptance criteria). A kiosk isn’t “ADA compliant” because it looks modern. It’s compliant when its location, hardware, interface, and documentation can all be verified against written accessibility criteria.

Use this checklist to document accessibility requirements from procurement through vendor submission, installation, commissioning, and long-term governance.

Digital Directory Accessibility Procurement and Acceptance Checklist

Accessibility acceptance criteria are the pass/fail requirements a product must meet before the owner accepts it, such as documented WCAG testing results and verified fixes for critical issues. Use this checklist as your acceptance criteria. Don’t sign off on a directory installation until every item in the commissioning section passes. Don’t release final payment until documentation and training are complete.

Only 25% of federal respondents indicated they include appropriate accessibility language in ICT solicitations, according to Section 508 assessment recommendations. That procurement gap is why accessibility failures happen downstream. Use this checklist to close the gap. Make accessibility a contract requirement, not a hope. For additional implementation support and answers to common rollout questions, see the directory FAQs on the Digital Directory Express site.

Procurement Language You Can Copy and Paste

Accessibility must be purchased, not hoped for. The cleanest way to get an accessible digital directory is to write enforceable requirements into your RFP, tie acceptance criteria to accessibility verification, and make remediation a contractual obligation. Most procurement failures stem from vague language like “directory should be accessible” without defining what that means or how it will be tested. The templates below remove that ambiguity.

Minimum Submittals Required from Vendors:

All proposals must include the following accessibility documentation:

• Accessibility Conformance Report (ACR): A current ACR based on the ITI VPAT template (version 2.4 or later), documenting conformance to WCAG 2.1 Level AA. The ACR must be dated within the last 12 months and must cover the directory software interface, content management system (if applicable), and any companion mobile/web applications. Minnesota IT procurement guidance requires ACRs as a standard submittal for IT products, and this requirement aligns with that best practice.
• Known Issues List: A detailed list of any known accessibility nonconformance issues, including severity (critical, high, medium, low), affected user groups, and workarounds (if any). If the product is fully conformant, vendor must state “No known accessibility issues” in writing.
• Accessibility Roadmap: For any known issues identified, vendor must provide a remediation plan with target fix dates. Critical issues must be resolved before final acceptance. High-priority issues must have a resolution timeline not exceeding 90 days post-installation.
• Testing Evidence: Documentation of accessibility testing performed, including tools used (e.g., axe DevTools, WAVE, manual keyboard testing), test dates, and summary of findings. Vendor must identify whether testing was performed in-house or by a third-party accessibility auditor. Massachusetts procurement guidance recommends identifying an accessibility subject matter expert and requiring testing as part of vendor evaluation.

Conformance Target Language (for RFP Scope of Work):

“The digital building directory system, including all user-facing interfaces (touchscreen UI, web-based admin panel, and any mobile companion applications), must conform to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as published by the World Wide Web Consortium (W3C). Conformance to WCAG 2.1 Level AA is required to meet the Department of Justice’s Title II digital accessibility rule for state and local government entities, with compliance required by April 24, 2026 for larger entities and April 26, 2027 for smaller entities and special district governments (Federal Register, April 24, 2024). Vendor must provide objective evidence of conformance through an Accessibility Conformance Report and pre-delivery testing documentation.”

For federal procurement or projects subject to Section 508, substitute or supplement the above with: “The system must conform to Section 508 standards (36 CFR Part 1194, incorporating WCAG 2.0 Level AA as the baseline technical requirement).” Cite Section 508 blog guidance on building accessibility into procurement as the rationale.

Testing and Acceptance Criteria (for RFP or Contract Deliverables Section):

“Prior to final delivery, Vendor must provide a pre-delivery accessibility test report documenting WCAG 2.1 Level AA conformance for the directory interface. The report must include:

• Test methodology (automated tools used, manual test procedures, assistive technology used)
• Test date and tester credentials (name, role, accessibility certification if applicable)
• Findings summary with pass/fail determination for each applicable WCAG 2.1 Level AA Success Criterion
• Screenshots or video evidence for critical user flows (search, directory browsing, wayfinding, session timeout handling)
• Remediation status for any nonconformance issues discovered

Owner reserves the right to conduct onsite acceptance testing after installation. Acceptance testing will include:

• Physical installation verification (protrusion limits, clear floor space, glare assessment)
• UI accessibility spot-checks (contrast measurement, text legibility, touch target sizing, timeout behavior)
• Functional testing of alternative access paths (QR code functionality, mobile experience usability)

Any critical accessibility issues discovered during acceptance testing must be remediated at no additional cost to Owner within 30 calendar days. High-priority issues must be remediated within 60 days. Medium and low-priority issues must be scheduled for resolution within 90 days. Final payment will be withheld until all critical and high-priority issues are closed and verified.”

This language is adapted from procurement best practices documented by Colorado OIT and Massachusetts Executive Office of Technology Services and Security. Both sources emphasize tying acceptance and payment to verified accessibility outcomes.

Training and Governance (for Contract Deliverables or Statement of Work):

“Vendor must provide training for Owner’s designated content editors and administrators on maintaining accessibility throughout the directory lifecycle. Training must cover:

• Proper use of accessible templates (locked contrast and typography settings)
• How to add/edit tenant listings without breaking WCAG conformance (e.g., avoiding color-only status indicators, maintaining text contrast, proper heading structure)
• Accessibility governance rules (mandatory accessibility checks after major content updates)
• Escalation process for accessibility questions or issues

Training must be delivered within 30 days of system go-live and must include written documentation (user guide or video tutorials) that can be referenced by future staff. Vendor must designate an accessibility point of contact who will be available for ongoing accessibility questions during the warranty period.”

The Section 508 assessment identifies training as a key operational control for sustaining accessibility. Writing it into the contract ensures it happens.

Use this remediation SLA schedule in the contract service level agreement so accessibility issues are prioritized, acknowledged, and resolved within defined timelines.

Accessibility Remediation SLA Schedule

Remediation means fixing accessibility barriers (design, code, content, or hardware configuration) so the product meets the agreed accessibility standard. SLA timelines should be tied to payment milestones. For example: “Owner will release [X]% of final payment upon closure of all critical issues and [Y]% upon closure of all high-priority issues.”

Accessibility Point of Contact (for Contract Management Section):

“Vendor must designate an Accessibility Lead who will serve as the primary point of contact for all accessibility-related questions, issues, and remediation coordination. Vendor must provide Accessibility Lead contact information (name, title, email, phone) within 5 business days of contract execution. Vendor must also provide an escalation path (manager or executive contact) for unresolved accessibility issues. Owner will designate an internal Accessibility Coordinator who will interface with Vendor’s Accessibility Lead and coordinate acceptance testing and ongoing governance.”

A defensible RFP for a digital building directory should require a current VPAT/Accessibility Conformance Report (ACR), documented WCAG 2.1 AA testing results, and a contractually binding remediation timeline as a condition of acceptance. Use the templates above to create that defensible RFP. Customize the timelines and severity definitions to match your project’s risk tolerance and schedule, but don’t remove the core accountability mechanisms: evidence before award, testing before acceptance, remediation before final payment.

Digital Directory Express can provide procurement-ready specifications, sample RFP language, and a complete documentation package including ACRs and test reports. Contact the team to request a spec pack tailored to your project’s procurement requirements and timeline.

Common Pitfalls and How Digital Directory Express Helps You Avoid Rework

Most compliance failures are preventable and usually happen at handoff points: designer to fabricator, fabricator to installer, installer to content editor. Each handoff is an opportunity for accessibility requirements to get dropped, misunderstood, or deprioritized. The pitfalls below represent the most common failure modes Digital Directory Express has observed across hundreds of lobby directory projects. Each one is fixable, and most are preventable if you address them in procurement.

Pitfall: Installing in the wrong location. The kiosk becomes a protruding object or blocks circulation. Symptom: accessibility auditor flags the installation as a cane-detection hazard or wheelchair users report they cannot approach the screen without backing into furniture. Fix: conduct a site survey before ordering hardware. Measure door swings, circulation paths, and wall depths. Select an enclosure that fits the space safely. Prevent in procurement: require the vendor to conduct a pre-installation site visit and provide a placement plan as part of the proposal. Include installation location approval as a contract milestone.

Pitfall: Accessibility “dies” after launch. Tenant updates break contrast or typography. Symptom: six months post-install, the directory screen shows light gray text on white backgrounds because a new office manager uploaded tenant names using an unapproved template. Fix: implement content governance rules. Lock templates so contrast and font settings cannot be changed. Train editors on what they can edit (names, floor numbers, logos within size limits) and what they cannot (colors, fonts, layout structure). Prevent in procurement: require the vendor to deliver locked accessible templates and provide editor training as a contractual deliverable. Include a clause requiring accessibility checks after major content updates.

Pitfall: No documentation. The owner cannot prove due diligence when a complaint arrives. Symptom: a user files an ADA complaint or a journalist asks “How do you ensure your lobby directory is accessible?” and the facilities team has no ACR, no test report, no as-built drawings showing compliant placement. Fix: create a procurement submittals binder (physical or digital) that includes the ACR, accessibility test report, site photos showing compliant installation, content governance policy, training records, and remediation log. Store it where your legal team can find it. Prevent in procurement: require all accessibility documentation as a contract deliverable before final payment. Make the binder a line item in your acceptance checklist.

Pitfall: Over-relying on exemption. “Directories are exempt” becomes “we can ignore accessibility.” Symptom: procurement team assumes the directory exemption means no accessibility requirements apply and orders the cheapest touchscreen kiosk without verifying placement safety, UI accessibility, or vendor accountability. The installed system fails effective communication because the interface is unusable by people with disabilities. Fix: establish a “minimum accessibility experience” standard for public-facing information. Even if tactile/Braille fabrication is exempt, commit to WCAG-aligned UI, safe placement, and alternative access paths. Prevent in procurement: include a policy statement in your RFP that clarifies the exemption applies to sign fabrication rules but does not eliminate the obligation to provide accessible communication. Require WCAG 2.1 AA for all interactive interfaces regardless of ADA sign scoping.

Use this table to prevent the most common accessibility mistakes before the directory is purchased, installed, or accepted.

Common Digital Directory Accessibility Pitfalls and Fixes

Accessibility governance is the policy and workflow that keeps content and UI updates accessible over time, not just on install day. Without governance, even a perfect launch will drift into noncompliance within months. The lowest-cost accessibility fix is the one you write into the RFP before you buy the directory. Fixing problems after installation is expensive (physical rework, software redevelopment, content re-entry) and disruptive (taking the directory offline for repairs). Preventing problems during procurement is cheap (adding contract language costs nothing; requiring documentation is a checkbox in the submittal form).

Digital Directory Express eliminates handoff risk by owning the entire delivery: site survey, enclosure selection, WCAG-compliant UI design, installation coordination, documentation, and training. You don’t coordinate three vendors and hope they all understand accessibility. You work with one partner accountable for the outcome. When you build your directory with Digital Directory Express, accessibility is engineered in from site planning through long-term content governance.

Frequently Asked Questions

Are building directory signs required to have Braille?

Under the ADA Standards’ sign guidance, building directories are generally exempt from tactile characters and Braille requirements, but nearby permanent room and space identification signs may still require tactile and Braille. The U.S. Access Board Chapter 7 guide explains that the exemption applies to changeable content like tenant names and company logos. Permanent room signs (like “Conference Room 301” or “Restroom”) that identify spaces do require tactile characters and Grade 2 Braille when provided. Treat the directory as part of the overall wayfinding system. Pair your digital directory with compliant tactile signs at critical decision points like elevators and main doors so users have both visual and tactile access to essential information.

Does a touchscreen directory kiosk have to meet WCAG?

WCAG is the clearest testable standard for digital interfaces, and it becomes especially important for state and local government services under the DOJ’s Title II rule that sets WCAG 2.1 AA with major compliance dates in 2026 and 2027. If you are a state or local government entity, the DOJ’s final rule requires WCAG 2.1 Level AA compliance for covered web and mobile digital services by April 24, 2026 (larger entities) or April 26, 2027 (smaller entities and special districts). Interactive touchscreen directories used for public wayfinding fall into that coverage. Even for private buildings, requiring WCAG-aligned design is a practical way to reduce complaints and improve usability. WCAG provides objective success criteria that can be tested, verified, and written into contracts. It’s become the de facto accessibility benchmark for public-facing digital systems regardless of legal mandate.

What is the 2026 ADA digital accessibility deadline?

For larger state and local government entities, the DOJ’s Title II digital accessibility rule sets April 24, 2026 as the compliance date for WCAG 2.1 Level AA for covered web and mobile services. Smaller state and local government entities (populations under 50,000) and special district governments have until April 26, 2027. These dates apply to digital content and services provided by public entities, including interactive kiosks and touchscreen directories used for public information and wayfinding. Massachusetts Title II guidance confirms these timelines and emphasizes that WCAG 2.1 Level AA is the technical standard entities must meet. If you’re a public entity procuring or upgrading a digital directory in 2024 or 2025, build the WCAG requirement into your RFP now so the delivered system is compliant on day one.

What should we require from vendors to prove accessibility?

At minimum, require a current VPAT/Accessibility Conformance Report (ACR), documented test results against WCAG 2.1 AA, and a written remediation plan with dates. The ACR should be completed using the ITI VPAT template (version 2.4 or later) and dated within the last 12 months. It should document conformance for the directory UI, any web-based admin interface, and mobile companion applications. The test report should include methodology (tools used, manual testing procedures, assistive technology testing), test dates, findings summary, and evidence (screenshots or video) for critical user flows. The remediation plan should list any known issues, assign severity levels, and provide target fix dates. Minnesota procurement guidance and Colorado’s vendor checklist both require ACR submission as standard practice. Tie payment milestones to remediation closure. Withhold a portion of final payment until all critical and high-priority accessibility issues are verified fixed.

Are tenant names and logos required to be tactile?

Occupant names, company names, and logos are generally treated as exempt content in ADA sign scoping, even when included on signs that also contain required room identification information. The Access Board sign guide clarifies that changeable content like tenant lists and logos do not require tactile fabrication. This exemption recognizes the impracticality of producing tactile characters and Braille for information that changes frequently. If the same installation combines a permanent room label (like “Suite 200”) with a changeable tenant nameplate, the permanent room ID component still requires tactile and Braille, but the tenant name itself does not. Design mixed-content signs carefully. Confirm which elements are permanent (and therefore subject to tactile/Braille rules) and which are changeable (and therefore exempt).

What’s the biggest ADA risk with digital lobby directories?

The biggest risk is using an inaccessible directory as the primary wayfinding tool because if users can’t physically approach it or perceive the information, the building’s wayfinding system can fail the “effective communication” expectation even if the directory is exempt from tactile sign fabrication rules. Effective communication is a core ADA obligation. If your lobby directory is the only practical way for visitors to find tenants and floors, and the interface is not usable by people with disabilities, you’ve created a barrier at the entry point. Mitigate this risk with a three-part strategy: safe physical placement (clear approach, no protrusion hazards), WCAG-aligned UI design (contrast, legibility, keyboard access, timeouts), and alternative access paths (QR codes linking to a mobile-friendly directory, companion tactile signage at elevators). Don’t rely solely on the directory exemption. Build a defensible wayfinding system that serves all users.

How do we keep directories accessible after go-live?

Sustained accessibility requires content governance: locked templates for contrast and typography, trained editors, and periodic accessibility checks after every major content update. Start by delivering the directory with accessible design templates where color schemes, font choices, and contrast ratios are locked and cannot be changed by content editors. Train the people who will add and edit tenant listings on what they can modify (names, suite numbers, logos within size constraints) and what they must not touch (fonts, background colors, layout structure). Document governance rules in a written policy: “All tenant updates must use the approved template. Major content changes (new floor sections, UI redesigns) require an accessibility review before publishing.” Assign an internal accessibility coordinator who periodically audits the live directory and escalates issues. Section 508 recommendations emphasize training and operational controls as key to maintaining compliance over time. Make governance a contract deliverable. Require the vendor to provide editor training and a governance playbook as part of the project closeout.

Can Digital Directory Express help with ADA/WCAG procurement and specs?

Yes, Digital Directory Express can provide procurement-ready specifications, installation guidance, and directory design templates that align with ADA sign scoping and WCAG-oriented digital accessibility goals. The team delivers turnkey solutions that combine code-compliant enclosures, WCAG 2.1 AA-aligned UI design, ACR documentation, accessibility test reports, and editor training into a single accountable package. This eliminates the coordination problem where hardware vendors, software developers, and content teams all point fingers when accessibility issues arise. When you work with Digital Directory Express, one partner owns the accessibility outcome from site survey through long-term content governance. Request the ADA + WCAG Procurement Spec Pack to receive copy-paste RFP language, installation checklists, and sample accessible UI templates. Schedule a lobby placement review to confirm your proposed kiosk location meets protrusion and circulation requirements before hardware is ordered. Start the conversation at the contact page.

Conclusion

Building directories occupy a unique position in accessibility compliance. They are exempt from ADA tactile sign fabrication rules yet still subject to obligations around safe physical access, effective communication, and (for public entities) WCAG 2.1 AA digital interface standards by April 2026. This creates confusion. Most buyers either over-apply tactile requirements where they don’t belong or under-apply accessibility requirements that do matter. The result is procurement delays, costly rework, and accessibility barriers at the building’s front door.

The path forward is clear. Understand sign scoping so you know which rules apply to your directory and which do not. Engineer physical installation for safe approach and protrusion compliance. Design the UI to meet WCAG 2.1 Level AA standards (especially if you are a public entity facing the 2026 compliance deadline). Write enforceable accessibility requirements into your RFP including ACR submission, testing evidence, and remediation SLAs. Maintain accessibility post-launch through governance, training, and periodic audits.

Digital Directory Express specializes in directory-specific accessibility implementation. The team handles site surveys, enclosure engineering, WCAG-compliant UI design, ACR production, testing, installation coordination, and training as a single integrated delivery. You don’t manage multiple vendors and hope they all understand accessibility. You work with one accountable partner who has engineered hundreds of compliant lobby directories for government, commercial, healthcare, and education clients.

Request the Digital Directory Express ADA + WCAG Procurement Spec Pack today. You’ll receive copy-paste RFP language, installation specification checklists, sample accessible UI templates, and a remediation SLA framework you can insert directly into your solicitation documents. Schedule a lobby placement review to confirm your proposed kiosk location meets circulation and protrusion requirements before you order hardware. Start the process at digitaldirectoryexpress.com/contact or explore turnkey options at digitaldirectoryexpress.com/directories.

The 2026 deadline is not theoretical. It’s federal regulation with enforcement mechanisms. Don’t wait for a complaint to discover your directory fails basic accessibility requirements. Build compliance into procurement, installation, and content governance from the start. The lowest-cost fix is the one you write into the RFP before the kiosk ships.

References

1. Federal Register: Nondiscrimination on the Basis of Disability, Accessibility of Web Information and Services of State and Local Government Entities
2. Mass.gov: ADA Title II Digital Accessibility Information
3. U.S. Access Board: Chapter 7, Signs
4. Section508.gov: Accessibility in Procurement Guide
5. Section508.gov: Section 508 Assessment 2023 Recommendations
6. Minnesota MNIT: Procurement for Accessible IT Products and Services
7. Colorado OIT: Vendor Accessibility Checklist
8. Mass.gov: Planning for Accessibility During the Procurement of Digital Products and Services
9. Section508.gov: Building Accessibility into Your Procurement Process
10. TouchSource: ADA and Digital Signage Compliance Guide