Visual Identity for a Public University Facing Accessibility and Consistency Pressures
A public university is updating its visual identity across 40 departments, a website, printed diplomas, and campus signage. The current identity uses a serif logotype, a green-and-gold palette, and a seal that appears in dozens of unofficial variants. The accessibility office reports that the gold-on-white combination fails contrast in web headers and that department sites have diverged widely. The rectorate wants a single rigid manual enforced centrally. Departmental communications staff argue that rigid rules will not fit diverse events and will be ignored. The university also has a legal obligation to meet accessibility standards on its website, and the diploma printing contract specifies a fixed layout that cannot change for two years.
1. How should the identity system be structured to satisfy central consistency, departmental flexibility, and accessibility?
Read the worked answer
Build a modular system with fixed and flexible layers. Fixed: logotype, seal usage, accessible color pairs, typography families, and minimum contrast rules for web and print. Flexible: layout templates, secondary palette combinations that pass contrast, and event-specific graphic devices drawn from an approved library. Provide tested templates for the most common departmental needs (lectures, conferences, student events) so staff do not improvise. For the web, publish accessible color pairs with measured contrast ratios and component-level guidance rather than a PDF manual alone. This addresses the central authority's need for consistency and the departments' need for flexibility, while making accessibility a non-negotiable constraint embedded in the approved options. The reasoning is that a design system governs the rules and the components, not every artifact.
2. How should the team handle the gold-on-white contrast failure and the diploma layout constraint?
Read the worked answer
For the web, the gold-on-white combination must be replaced for text: use a darker gold or the green for text on white, or white text on green, and reserve metallic gold for non-text accents. Publish the measured contrast ratios and the approved pairs. For diplomas, the layout is fixed for two years, so the team should not promise an immediate change; instead, document the accessibility issue, propose a compliant revision for the next contract cycle, and ensure any digital version of the diploma or accompanying web page is accessible. This separates what can be fixed now from what must be scheduled, which is the honest and defensible position. The reasoning is to treat accessibility as a compliance trajectory with documented milestones rather than an all-or-nothing claim.
3. How should the team respond to departmental staff who say the manual will be ignored?
Read the worked answer
Treat the prediction as a design problem in adoption. Involve departmental staff in testing templates, provide editable source files rather than locked PDFs, and run short training sessions. Reduce the number of rules to the ones that matter (logo clear space, approved color pairs, type hierarchy) and allow documented exceptions for event graphics. Measure adoption after launch and revise. This responds to the real cause of divergence - unusable tools and unclear priorities - rather than adding enforcement. The reasoning is that a visual identity succeeds through usable components and shared ownership, and consistency is maintained by making the compliant path the easiest path.