Accessibility planning starts with the information someone needs to read, identify, or follow. A visual communications brief can name those tasks alongside the intended medium, rather than treating accessibility as a single finishing check. The useful starting question is which published reference addresses each deliverable.
Why Accessibility Belongs in the Brief
A logo, a room label, and a government web page may belong to one visual system, but the sources describe different requirements for them. Begin with an inventory that separates branding, information, direction, and digital interaction. For each item, record where it appears, what it communicates, and which reference will guide review. That makes the specification more precise than a general instruction to make everything accessible. Keep the inventory attached to the brief through approvals. It can show which decisions are settled, which source supports each requirement, and which items still need a specific review.
WebAIM's 2026 Million report found low-contrast text on 83.9% of the one million home pages analyzed in February 2026, compared with 79.1% in 2025. Across the sample, 95.9% had detected WCAG 2 failures, averaging 56.1 detected errors per page. These are automated findings: WebAIM explains that some failures cannot be detected automatically and that a page without detected errors is not necessarily accessible or conformant.
Colour Contrast by the Numbers
For digital text, WebAIM's contrast explanation describes a minimum ratio of 4.5:1 under WCAG Level AA, with 3:1 for large text. It defines large text as at least 18pt, or at least 14pt when bold. Text rendered within a graphic is also covered. Record the foreground and background together: a color name alone does not describe the pairing being evaluated.
The explanation warns against rounding a result up to pass. Its example of #777777 gray has a 4.47:1 contrast ratio and fails the 4.5:1 threshold. A specification can record the measured ratio beside each proposed pairing, with separate examples for body copy, large headings, and text placed in graphics.
Text that forms part of a logo or brand name is exempt from that contrast requirement. Keep that exception attached to the logotype itself when documenting the palette. Ordinary text elsewhere in the design needs its own assessment. WebAIM also explains WCAG 2.1's 3:1 non-text contrast requirement for visual information needed to identify interface components and states, and for graphical parts needed to understand content, subject to the exceptions it describes.
Accessible Signage in Physical Spaces
The U.S. Access Board's signs guide distinguishes identification of permanent rooms and spaces from directional and informational signs. Where permanent-room labels are provided, visual and tactile requirements apply; examples include room numbers, restrooms, and conference rooms. Exterior permanent-room signs away from the doorway need visual treatment but do not have to be tactile.
For tactile signs, the guide specifies raised characters repeated in Grade 2 braille, with braille below the raised characters, and a reading-height range of 48–60 inches. It describes non-glare finishes and light-on-dark or dark-on-light contrast for the relevant characters and background, while stating that no minimum contrast ratio is specified. The digital text ratios above should therefore not be transferred to physical signs.
Directional and informational signs need visual requirements but are not required to be tactile. Exempt categories include directories, menus, company names and logos, and temporary signs posted for seven days or less. A sign schedule should identify the function and location of each item before assigning requirements, rather than assuming that all signs in a building need the same treatment.
Roadway devices require a separate reference. FHWA describes the MUTCD as governing traffic control devices, including those on site roadways open to public travel. Its edition page identifies the 11th Edition with Revision 1, dated December 2025; FHWA's overview states that Revision 1 took effect March 5, 2026. These traffic control standards apply separately from storefront, fascia, or monument identity signs.
Digital Deliverables for Public-Sector Clients
The Department of Justice Title II fact sheet identifies WCAG 2.1 Level AA as the technical standard for state and local government web content and mobile apps. It includes content supplied through arrangements with contractors. Its example of a PDF application still used by the public explains that being posted earlier does not, by itself, bring that application within the exception discussed there.
The fact sheet reports that the Interim Final Rule published April 20, 2026 extended compliance dates to April 26, 2027 for entities with populations of 50,000 or more, and April 26, 2028 for smaller entities and special district governments. Those dates and that scope belong to the government rule. WebAIM's automated survey used WCAG 2.2 A/AA checks; it should not be treated as a statement of the DOJ rule's version.
For a project brief, list the web pages, apps, and PDFs under consideration and identify the responsible reviewer for each. Refer questions about the rule's application and exceptions back to the government source. A design checklist can organize the review without deciding those questions.
Building Accessibility Checks into the Project Plan
Turn the inventory into review tasks with a named owner and a place to record the result. For a digital palette, ask for the text size, foreground and background values, measured contrast ratio, and proposed use. For a room label, record whether it identifies a permanent space, where it will be positioned, and which visual or tactile provisions the sign specification addresses.
Keep a separate entry for roadway traffic devices so their reference is clear. At approval, compare the specified requirement with the actual deliverable rather than relying on an overall impression of the presentation. If a color pairing, label, or format changes, return that item to review.
For handover, keep the approved examples with the recorded checks. A future revision can then be compared with a named requirement and an actual result, rather than an unexplained approval mark. Open questions should remain visible in the project record, with the next action and responsible reviewer identified before the item is signed off.