Creating Accessible Local Government: The Process
Vivienne Conway, Keith Fitzpatrick · 2017 · Proceedings of the 14th International Web for All Conference (W4A) · doi:10.1145/3058555.3058572
Summary
This short paper documents the end-to-end process the City of Cockburn, a local government authority in Western Australia, followed to develop an accessible replacement website. The paper provides a practical 9-step roadmap: (1) embed accessibility in official planning documents, (2) identify issues with the current website via user feedback and technical audit, (3) initiate formal procurement, (4) choose a developer who understands accessibility, (5) provide accessibility training for developers and content providers, (6) develop a project plan with accessibility checkpoints, (7) identify issues and find solutions, (8) determine the success of the project, and (9) plan next steps. The City's existing website (built 2007) had never received explicit accessibility complaints, but customer service data revealed complaints about finding information and navigation — which are accessibility issues by another name. A baseline audit against WCAG 2.0 showed only 28% of pages passed Level A criteria, 32% passed Level AA, and 28% passed Level AAA, with 52% failing Level A. The target for the new website was WCAG 2.0 Level AA for all components under the City's control. User testing by the Digital Accessibility Centre (DAC) with professional testers with disabilities confirmed the technical audit findings.
Key findings
Several practical lessons emerged from the project. Including an accessibility expert on the procurement panel proved crucial: none of the three shortlisted developers had produced websites that fully met WCAG 2.0 AA, and without specialist knowledge on the panel, providers with limited accessibility experience could have been selected based on plausible-sounding responses. The selected developer initially underestimated the time required for accessibility evaluation, and confusion arose between WCAG 2.0 AA compliance requirements versus best-practice features, requiring negotiation and in-house training. Lack of understanding about mobile accessibility impact required dedicated demonstration sessions with assistive technology users. Executive buy-in was a challenge, addressed through "Learn at Lunchtime" education sessions and toolbox talks. The project plan used three phases: wireframes in InVision for collaboration, design format with simultaneous desktop/mobile development, and an interactive slice environment enabling rigorous accessibility evaluation. The paper emphasizes that long-term success depends on a content management structure built on education and accountability rather than a "protectionist" gateway approach, and that staff training and regular re-testing are essential to prevent accessibility degradation as new content is added.
Relevance
This paper offers a rare, detailed practitioner account of implementing web accessibility within a real government organization, making it highly valuable for accessibility professionals working with public sector clients. The practical lessons are broadly applicable: the importance of accessibility expertise in procurement panels (to challenge vendor claims), the need for training before and during development (not just handing developers a standard), the challenge of distinguishing compliance requirements from best practices, and the critical role of executive education. The finding that none of the shortlisted Australian developers could demonstrate full WCAG 2.0 AA compliance highlights a persistent skills gap in the web development industry. The paper's emphasis on sustainability — ongoing training, regular auditing, content management accountability, and focus groups — addresses the common failure mode where accessible websites degrade over time as untrained staff add non-conforming content. Future considerations around document remediation (PDF accessibility), translation services for culturally diverse communities, and library integration show mature accessibility thinking. The paper is limited by being written during the project rather than after completion, so outcome data is not yet available.
Tags: government accessibility · WCAG compliance · procurement · organizational accessibility · case study · Australia · accessibility audit · user testing · accessibility training · project management · web development · content management · policy · mobile accessibility
Standards referenced: WCAG 2.0 · EN 301 549