In this article

This article treats agency work for municipalities as nonpartisan public service communication. A hypothetical cultural event or service-point announcement should explain where, when and how residents can use it. The goal is to help everyone reach the same accurate information. Identity, posters, web notices and wayfinding should identify a consistent institutional source. Define content accuracy, accessibility review and update authority as separate responsibilities in the brief, making ongoing information management part of the project alongside its initial design.

Quick answer

An agency brief for a municipality should focus on clear, accessible and nonpartisan public service information. State the service, location, date, participation or application steps and the current information source. Provide the poster's essential details as real text online too. The institution approves accuracy while responsible teams assess design and accessibility requirements through defined checks.

Structure the notice around service users' questions

For a sample cultural event, list residents' needs before the institution's long introduction. What is happening, where, when, and what must someone do to participate? Obtain service conditions from approved institutional content. A clear hierarchy between heading and detail can support reading at a distance on a poster and quick reading online. Institutional presentation should not overshadow service information. Trying the content with people who have different reading habits can reveal expressions that seem obvious internally but remain unclear to the public.

Do not leave information inside an image alone

Place essential information in real text alongside the digital poster. W3C's image alternative decision tree explains how meaningful images need context-appropriate descriptions and how complex information should also appear elsewhere on the page. Instead of forcing every detail into a short image description, provide a readable content section. Choose the alternative text according to the image's function. In the event notice, dates and application steps should be explicit on the page. This does not by itself complete every accessibility requirement.

Use measurable checks for colour and text

Using institutional colours does not make every text-background combination readable. W3C's WCAG 2.2 explanation specifies a minimum contrast ratio of 4.5:1 for relevant normal text and 3:1 for large text, with stated exceptions. Identify which digital content will be checked against that criterion instead of relying on visual preference. Avoiding colour alone to convey important service distinctions is also a useful design objective. Contrast testing does not establish accessibility of the whole product; define the wider review and specialist responsibilities separately.

Keep posters, web pages and signs consistent

When the service point changes address or hours, updating one social graphic may be insufficient. Printed notices, web pages and entrance signs may also be affected. Establish one current information source for the agency's versions. Assign verification owners for any additional languages or explanation formats. Assess wayfinding through the steps users follow, alongside its appearance. Obtain physical production conditions from relevant suppliers rather than assuming that one screen mockup authorises every application in different environments.

Manage changes and removal after publication

A public service notice continues to need attention after its first release. Remove expired events and update changed information across affected channels. Identify an institutional content owner and publication approver, and record how the agency receives corrections. Keep editable templates, approved wording and publication files distinct. Trial an actual information update as part of acceptance to expose missing responsibilities. This work concerns neutral communication explaining public services, assessed through access to accurate information and understandable instructions.

  • Has the institution approved service, place, date and application details?
  • Is essential content available as real text outside the image?
  • Are contrast review, information updates and removal responsibilities assigned?

Key takeaways

  • Write the brief through service users' questions before institutional introductions.
  • Support visual notices with accessible text and defined review procedures.
  • Include information updates and expired-notice removal in the project.

Frequently asked questions

What is the main communication objective here?

Explain the location, timing and steps for using public services in a nonpartisan way. Connect design decisions to accuracy, clarity and accessibility, using the institution's approved content as the basis.

Is posting a poster on social media enough?

Provide essential details in readable text beyond the image. Plan a context-appropriate image alternative and ensure the current official page carries the same accurate information.

Does a contrast test verify all accessibility?

No. Contrast is one important check. Content structure, image alternatives and other usage needs require separate review. Define the assessment with competent teams rather than drawing a general compliance conclusion from one test.

Sources and further reading