2207 90B St SW #102Edmonton, Alberta, T6X 1V8, Canada
+1 (780) 680-5739info@hbtech.ca
HB Technology
Engineering & Cloud Capabilities

Comprehensive IT & Web Solutions

View All Services →
Web Design & DevelopmentModern, mobile-first websites engineered for speed, accessibility, and Core Web Vitals. Built for performance and long-term maintainability.
Technical SEO & Performance AuditTechnical SEO architecture, Schema.org structured data, and search engine optimization engineered to capture high-intent organic search traffic.
eCommerce DevelopmentHigh-converting online stores on Shopify or WooCommerce with secure Canadian payment processing, inventory systems, and performance optimization.
Custom Web ApplicationsTailored portals, internal tools, and SaaS platforms designed around your exact workflows using React, Node.js, and cloud-native architecture.
Custom WordPress DevelopmentCustom, lightweight WordPress engineering with modular Gutenberg and ACF Pro blocks — zero bloated themes and sub-second load times.
White Label Web DevelopmentSenior-level white-label web development and maintenance partnership for Canadian digital agencies and marketing firms.
Domains & Cloud HostingHigh-availability Canadian cloud hosting, proactive monitoring, security, and ongoing technical support designed for uptime and compliance.
Managed IT & Cloud InfrastructureReliable Canadian hosting, proactive monitoring, security, and ongoing technical support designed for uptime and compliance.
Need managed cloud architecture, custom workflow software, or 24/7 Edmonton IT support?
Schedule Technical Consultation →
Industry-Specific Systems

Tailored Technology by Vertical

Explore All Industries →
Government & Public SectorSecure, accessible, and compliant digital infrastructure for municipalities and public agencies.
Enterprise IT SolutionsScalable cloud architecture, workflow automation, and custom digital platforms for growing enterprises.
Non-Profit OrganizationsCost-effective, high-impact digital platforms to amplify your mission, community reach, and donor engagement.
Small BusinessesAffordable, high-converting digital storefronts, local SEO strategies, and custom web development for growing businesses.
Looking for custom compliance (PIPEDA / FOIP / HIPAA / SOC2) or ERP systems integration?Request Industry Consultation →
About HB Technology Solutions

Company, Credentials & Insights

About UsLearn about our mission, vision, and core values.
Our ServicesExplore our full range of web development and IT solutions.
Domains & HostingRegister domains, manage DNS, and secure cloud hosting.
Blogs & InsightsLatest articles on technology, design, and digital growth.
TestimonialsHear what our clients and partners have to say about working with HB Tech.
Technology

Municipal Website Checklist for Alberta: Privacy & Security

Municipal Website Checklist for Alberta: Privacy & Security
Yujesh K C
By Yujesh K CLead Software Engineer
Published: 2026-11-20T02:11:19.324Z⏱️ 18 min read

A resident visits a municipal website to pay a property tax bill, register a child for a recreation program or find the date of the next council meeting. They expect the information to be easy to locate and the process to work. They also expect their personal information to remain private.

For Alberta municipalities, delivering that experience involves more than choosing a website theme and publishing information. A municipal website may handle service applications, online payments, public notices, meeting documents, contact forms and records requests. Each function introduces responsibilities around accessibility, privacy, information management and cybersecurity.

The regulatory landscape has also changed. Alberta's Access to Information Act (ATIA) and Protection of Privacy Act (POPA) came into force on June 11, 2025, replacing the relevant parts of the former Freedom of Information and Protection of Privacy Act (FOIP). Municipalities need to consider these changes when reviewing their websites, service portals and the systems connected to them.

This checklist explains the areas municipal administrators, IT managers and technology partners should review when building or maintaining a municipal website in Alberta.

Start with the legislation that applies to Alberta municipalities

Before reviewing individual website features, it is worth separating legal obligations from recommended technical standards. They are not interchangeable.

Municipalities are public bodies under Alberta's access and privacy legislation. The Access to Information Act (ATIA) establishes the public's right to request records held by public bodies, subject to specified exceptions. The Protection of Privacy Act (POPA) governs how public bodies collect, use, disclose and protect personal information.

Accessibility has a different legal framework. Alberta does not currently have a province-wide accessibility statute equivalent to Ontario's Accessibility for Ontarians with Disabilities Act. That does not mean municipal websites can ignore accessibility. The Alberta Human Rights Act protects people from disability-based discrimination in services available to the public and requires reasonable accommodation to the point of undue hardship.

Municipal policies, local bylaws, procurement requirements and individual service arrangements may introduce additional expectations. A municipality should establish which requirements apply to its own operations rather than assuming that one technical standard covers everything.

1. Make accessibility part of the website's design

A resident should not need to use a mouse, see every colour accurately or understand complicated technical language to access essential municipal information.

Consider someone using a screen reader to check a garbage collection schedule, a keyboard-only visitor trying to complete a recreation registration form, or a resident with low vision attempting to read a public notice. If the website creates unnecessary barriers for these visitors, its services are not reaching everyone equally.

The Web Content Accessibility Guidelines (WCAG) provide an established technical framework for identifying and reducing these barriers. WCAG 2.2 Level AA is a sensible target for new municipal website development and accessibility improvements. It should be treated as a technical benchmark and procurement requirement where adopted, not as a blanket statutory WCAG mandate for every Alberta municipality.

Accessibility items to review

  • Keyboard navigation: Visitors should be able to move through menus, forms, buttons, links and interactive elements using a keyboard. Focus indicators must remain visible.

  • Screen reader compatibility: Use meaningful headings, semantic HTML, descriptive links, properly labelled form fields and appropriate alternative text for informative images.

  • Colour contrast: Text, buttons and important interface elements should have sufficient contrast. Do not communicate important information through colour alone.

  • Readable content: Use plain language, descriptive headings, short instructions and consistent navigation. Explain municipal terminology where necessary.

  • Accessible documents: Council agendas, meeting minutes, application forms and public reports should be available in accessible formats. Scanned PDFs without selectable text can create significant barriers.

  • Captions and transcripts: Recorded council meetings and public information videos should include appropriate captions or alternative text-based access.

  • Responsive layouts: Pages and forms should remain usable on mobile devices, including when visitors zoom in or increase text size.

  • Accessible forms: Identify required fields, explain validation errors and provide instructions that assistive technologies can interpret.

Automated accessibility scanners can identify missing labels, contrast problems and certain structural issues. They cannot reliably evaluate every experience. Manual keyboard testing and testing with screen readers are necessary parts of a meaningful review.

Municipalities can also examine how their existing accessibility policies translate into digital services. The City of Edmonton, for example, has adopted accessibility guidance that references WCAG for its internet website and web content. Local government policies can provide useful examples for other Alberta communities.

For a more detailed technical explanation, see our guide to website accessibility and WCAG 2.2 in Canada.

2. Review privacy under Alberta's POPA

A municipal website can collect more personal information than its public-facing design suggests. A simple recreation registration form may request a resident's name, address, contact details and information about a child. A service request may contain photographs of private property, complaints about neighbours or details about an individual's circumstances.

Each collection needs a clear purpose and appropriate safeguards.

Under POPA, municipalities must have a lawful basis for collecting personal information and must follow the applicable rules for its use, disclosure, protection and retention. Website developers should work with the municipality's privacy officer or legal team to ensure that forms and connected systems support these obligations.

Privacy checklist for municipal websites

  • Explain data collection: Each form should identify what information is being collected, why it is required and how it will be used. Provide the appropriate privacy notice.

  • Collect only necessary information: Avoid asking residents for details that are not needed to deliver the requested service.

  • Review third-party services: Examine analytics platforms, embedded maps, payment gateways, email marketing systems and external registration tools to understand what information they receive.

  • Control access: Restrict access to resident submissions, account information and administrative records to authorized personnel.

  • Protect submitted information: Use encrypted connections, secure storage and appropriate transmission controls.

  • Establish retention rules: Website submissions, uploaded documents and system logs should follow approved municipal retention and disposition schedules.

  • Document responsibilities: Establish who manages privacy notices, reviews collection practices, approves changes and responds to incidents.

One important change deserves particular attention. POPA requires public bodies to establish and implement a Privacy Management Program. The implementation deadline was June 11, 2026. As of November 2026, municipalities should already have this program in place, with documented policies and procedures supporting privacy compliance.

Privacy impact assessments also deserve attention. POPA establishes requirements for assessments in prescribed circumstances, including relevant new programs, projects, services and substantial changes to existing arrangements involving personal information. Municipalities should determine when an assessment is required before introducing a new online service or changing an existing one.

These requirements are not limited to the website's visible pages. A registration form connected to a third-party database, for example, must be considered as part of the wider information-handling process.

Official guidance is available through the Government of Alberta's privacy management resources and the Office of the Information and Privacy Commissioner of Alberta.

3. Keep online services secure

A municipal website is a public-facing entry point into a much larger technology environment. It may connect to payment providers, email systems, document repositories, content management systems and internal administrative applications.

A vulnerability in one of those connections can expose information or interrupt essential services. Security reviews should therefore cover the website and its connected infrastructure, not just the homepage.

Essential website security controls

  • HTTPS and valid SSL certificates: Encrypt communication between residents and the website. Monitor certificate expiry and renewal.

  • Multi-factor authentication: Require additional authentication for administrators and users with access to sensitive systems.

  • Role-based permissions: Give staff access according to their responsibilities. Someone responsible for publishing news should not automatically have unrestricted access to all system settings and resident records.

  • Software updates: Keep the CMS, plugins, themes, frameworks, server software and dependencies updated. Remove unused components.

  • Web application protection: Apply appropriate input validation, output encoding, rate limiting and protection against common web application attacks.

  • Secure backups: Maintain protected backups and test restoration procedures. A backup that cannot be restored is not a reliable recovery plan.

  • Monitoring and logging: Monitor suspicious login attempts, unexpected changes, unusual traffic and potential data exposure.

  • Administrative protection: Use strong credentials, restrict administrative access where practical and remove former employees' accounts promptly.

  • Incident response: Establish procedures for identifying, containing, investigating and recovering from security incidents.

Security should also extend to the hosting environment. Municipalities should understand where their website and associated data are hosted, who administers the infrastructure, how backups are protected and what support is available during an outage.

A hosting provider's marketing claims are not a substitute for documented security controls. Review service agreements, access responsibilities, backup arrangements, incident notification procedures and recovery expectations.

Our article on cybersecurity practices for Canadian organizations provides additional background on practical protection measures. Municipalities should adapt those measures to their own risk profiles and public-sector responsibilities.

4. Treat public records as part of the website architecture

Municipal websites publish information that residents may need to locate years after its original publication. Council minutes, bylaws, public notices, development applications and procurement documents can all have administrative, legal or historical value.

Publishing a document online does not remove the municipality's responsibility for managing the underlying record.

Under Alberta's Municipal Government Act, municipalities have specific recordkeeping responsibilities, including requirements relating to original bylaws and council minutes. Section 214 also addresses the authority to destroy certain municipal records and the retention of personal information used to make decisions affecting individuals.

A municipality should maintain approved records retention and disposition schedules that cover electronic records as well as paper documents. The website and its content management system should support those arrangements.

Questions to ask during a records review

  • Are council minutes, bylaws and public notices stored in a managed document repository?

  • Can staff identify the original publication date and the latest version of a document?

  • Are outdated documents archived according to approved retention schedules?

  • Can authorized staff retrieve records when responding to an ATIA request?

  • Are public documents separated from confidential or restricted records?

  • Are website backups and document archives protected against unauthorized changes or deletion?

Search functionality matters too. A resident looking for a particular bylaw or council decision should not have to browse through dozens of unrelated pages. A well-organized document library, descriptive filenames, meaningful categories and reliable search can make public information substantially easier to access.

Municipalities developing more advanced document libraries or internal administrative systems may benefit from custom web application development rather than trying to force every workflow into a basic content management system.

5. Check forms, payments and third-party integrations

Some of the highest-risk areas of a municipal website are not ordinary content pages. They are the interactive services residents use to complete transactions.

Consider an online property tax payment service. The website may display a payment form, but the actual transaction could be handled by an external payment provider. The municipality still needs to understand how the connection works, what information is transferred and which organization is responsible for each part of the process.

Apply the same scrutiny to recreation registration, building permit applications, public consultation surveys, library systems and online complaint forms.

Before approving an integration, review the following:

  • What personal information does the service collect?

  • Where is that information stored and processed?

  • Does the provider use the information for any additional purpose?

  • Are security responsibilities clearly documented in the agreement?

  • Can the service meet the municipality's accessibility expectations?

  • What happens if the provider experiences a data breach or service outage?

  • Can the municipality retrieve its information or transition to another provider?

  • Are privacy and accessibility requirements considered during procurement and testing?

Payment processing deserves particular care. Use established payment providers and avoid storing cardholder information directly in the municipal website unless there is a properly justified and independently reviewed requirement. Review the provider's applicable payment security obligations and the division of responsibilities.

For municipalities with complex registration, permitting or service-request workflows, a properly designed custom web application can provide more control over permissions, validation, integrations and reporting.

6. Build a website that residents can actually use

Compliance is not the only measure of a successful municipal website. Residents should be able to find information without understanding the municipality's internal department structure.

For example, a person searching for a building permit should not need to know whether the municipality places that service under planning, development services or community infrastructure.

Organize the website around common resident tasks. Useful sections often include:

  • Residents: Property taxes, waste collection, utilities, recreation and community services.

  • Business and development: Business licensing, zoning, building permits, inspections and economic development.

  • Municipal government: Council information, agendas, minutes, bylaws, budgets and public consultations.

  • News and notices: Emergency announcements, road closures, service interruptions and community updates.

  • Contact and support: Department contacts, office hours, service-request forms and emergency information.

Mobile usability deserves equal attention. Residents may visit the website while travelling, standing at a municipal facility or trying to access an urgent service from a phone. Navigation, contact information and essential service pages should remain easy to use on smaller screens.

Performance also matters. Compress images, minimize unnecessary scripts, use caching appropriately and choose hosting that can handle traffic spikes. A municipal website should remain usable when residents are checking an emergency notice or trying to access information during a major community event.

Municipalities planning a redesign can explore website design and development focused on accessibility and performance. Where an existing WordPress installation needs more control over content structures and administrative workflows, custom WordPress development may be an appropriate option.

7. Establish a maintenance and accountability process

A website can pass an accessibility audit on launch day and become less accessible six months later. A new plugin can introduce a vulnerability. A staff member can accidentally publish a confidential attachment. A payment integration can change its terms or technical requirements.

These are ongoing operational issues, not problems that a one-time redesign can solve.

Municipalities should assign clear responsibility for maintaining the website and its connected services. This includes content ownership, technical updates, privacy reviews, security monitoring and incident management.

A practical maintenance schedule should cover:

  • Monthly: Review software updates, backup status, administrator accounts, security alerts and broken links.

  • Quarterly: Review accessibility issues, important page content, form functionality, user permissions and third-party integrations.

  • Annually: Conduct a broader security assessment, review disaster recovery arrangements, evaluate hosting performance and update website governance documentation.

  • Whenever services change: Assess privacy implications, accessibility, security and records management before introducing new functionality.

These intervals are suggested operational practices, not statutory deadlines. A municipality should adjust the schedule to the sensitivity of its data, service criticality and risk exposure.

Working with an experienced managed IT and infrastructure support provider can help municipalities establish consistent monitoring, maintenance and technical support arrangements. Hosting arrangements should also be reviewed through appropriate domain and cloud hosting services that account for uptime, backups, security and recovery.

A practical Alberta municipal website review checklist

The following checklist can help municipal administrators and technology teams organize their next website assessment.

  • Confirm which provincial laws, local bylaws and municipal policies apply.

  • Review website accessibility against WCAG 2.2 Level AA as an adopted technical target.

  • Test keyboard navigation, screen reader compatibility, colour contrast and accessible documents.

  • Review all forms and identify what personal information each one collects.

  • Ensure privacy notices and collection practices reflect POPA requirements.

  • Confirm that the municipality has implemented its required Privacy Management Program.

  • Determine whether new or substantially changed services require privacy impact assessments.

  • Review third-party vendors, hosting providers and payment integrations.

  • Enforce multi-factor authentication and appropriate administrative permissions.

  • Verify software updates, secure backups, monitoring and incident response procedures.

  • Confirm that electronic records follow approved retention and disposition schedules.

  • Test online services on mobile devices and with assistive technologies.

  • Assign responsibility for ongoing content, privacy, accessibility and security reviews.

Choosing the right technology partner for a municipal website

Municipal website projects involve more than visual design. The development team needs to understand how public information is organized, how residents interact with online services and how technical decisions affect accessibility, privacy and security.

For a smaller municipality, the priority may be a maintainable content management system with accessible templates, a reliable document library and straightforward content editing. A larger municipality may need custom applications, multiple departmental workflows, secure integrations and more advanced information management.

The right approach depends on the municipality's existing infrastructure, service requirements, internal resources and risk profile. A technology partner should be able to explain those trade-offs clearly rather than recommending unnecessary complexity.

At HB Technology Solutions, we work on government and public-sector digital solutions with an emphasis on accessible websites, maintainable development and reliable infrastructure. Our team can help assess an existing municipal website, identify technical gaps and plan improvements that support long-term operations.

If your municipality is preparing for a redesign or reviewing its current digital services, request a free project proposal from HB Technology Solutions. A structured review can help establish priorities for accessibility, privacy, security and website performance before development begins.

Frequently asked questions

Are Alberta municipalities legally required to follow WCAG 2.2 Level AA?

Alberta does not currently have a province-wide accessibility statute imposing a universal WCAG 2.2 Level AA requirement on every municipal website. However, municipalities have obligations under the Alberta Human Rights Act, including duties relating to disability discrimination and reasonable accommodation in public services. Local policies, procurement requirements and other applicable rules may establish additional technical expectations. WCAG 2.2 Level AA is a recommended benchmark for municipal website development.

Does FOIP still apply to Alberta municipalities?

The former Freedom of Information and Protection of Privacy Act was repealed on June 11, 2025, when Alberta's Access to Information Act and Protection of Privacy Act came into force. Certain older requests and transitional matters may still be handled under the former legislation. Municipalities should use the current ATIA and POPA framework for applicable new matters.

What is POPA's Privacy Management Program requirement?

POPA requires Alberta public bodies, including municipalities, to establish and implement a documented Privacy Management Program. The implementation deadline was June 11, 2026. The program supports privacy compliance through policies, procedures and organizational practices.

Should a municipal website use Canadian hosting?

Canadian hosting can help municipalities assess data location, contractual responsibilities and operational control, but choosing a Canadian data centre does not automatically establish legal compliance. Municipalities should review applicable privacy requirements, hosting agreements, vendor access, security safeguards and any cross-border data processing.

How often should a municipal website undergo a security review?

Security monitoring and software maintenance should be ongoing. A broader risk-based security assessment should be scheduled regularly, with additional reviews after major system changes, new integrations, security incidents or changes to the information being collected. The appropriate frequency depends on the municipality's risk profile and service requirements.

Who is responsible for website accessibility and privacy?

Responsibility is shared across municipal leadership, IT teams, communications staff, privacy officers and external technology vendors according to their respective roles. The municipality remains responsible for its applicable public-sector obligations, even when website development, hosting or online services are outsourced.

Disclaimer: This article provides general technical and regulatory information, not legal advice. Municipalities should consult qualified legal and privacy professionals to determine how Alberta legislation, local bylaws and specific contractual obligations apply to their operations. Legislation and official guidance should be checked before making compliance decisions.

🏷️ Tags:#municipal-websites#alberta#website-accessibility#privacy-compliance#cybersecurity#government-technology#WCAG#public-sector
Engineering & Digital Solutions

Build Fast, Scalable Software with Canadian Engineers

Whether you are modernizing existing web infrastructure, designing a custom web application, or expanding local search authority, our Edmonton engineering team builds turnkey solutions backed by strict SLA guarantees.

Request Project Estimate →View All Services
HB Technology Solutions Ecosystem

Explore Our Engineering Services & Industry Solutions

Explore our full suite of web design, custom software engineering, e-commerce, managed IT, and sector-specific architectures.

Service

Web Design & Development

Modern, mobile-first websites engineered for speed, accessibility, and Core Web Vitals. Built for performance and long-term maintainability.

Learn more →
Service

Technical SEO & Performance Audit

Technical SEO architecture, Schema.org structured data, and search engine optimization engineered to capture high-intent organic search traffic.

Learn more →
Service

eCommerce Development

High-converting online stores on Shopify or WooCommerce with secure Canadian payment processing, inventory systems, and performance optimization.

Learn more →
Service

Custom Web Applications

Tailored portals, internal tools, and SaaS platforms designed around your exact workflows using React, Node.js, and cloud-native architecture.

Learn more →
Service

Custom WordPress Development

Custom, lightweight WordPress engineering with modular Gutenberg and ACF Pro blocks — zero bloated themes and sub-second load times.

Learn more →
Service

White Label Web Development

Senior-level white-label web development and maintenance partnership for Canadian digital agencies and marketing firms.

Learn more →
Industry Solution

Government & Public Sector

Secure, accessible, and compliant digital infrastructure for municipalities and public agencies.

Explore solution →
Industry Solution

Enterprise IT Solutions

Scalable cloud architecture, workflow automation, and custom digital platforms for growing enterprises.

Explore solution →
Industry Solution

Non-Profit Organizations

Cost-effective, high-impact digital platforms to amplify your mission, community reach, and donor engagement.

Explore solution →
Industry Solution

Small Businesses

Affordable, high-converting digital storefronts, local SEO strategies, and custom web development for growing businesses.

Explore solution →
Knowledge Base

Related Articles & Engineering Insights

View All Articles →
How Much Does Custom Web App Development Cost in Canada?
2026-11-20T02:18:15.561Z

How Much Does Custom Web App Development Cost in Canada?

Custom web application costs in Canada vary with features, integrations and complexity. Explore 2026 pricing, development timelines and budgeting considerations.

Website Maintenance Costs in Edmonton: What's Included
2026-11-05T04:15:39.006Z

Website Maintenance Costs in Edmonton: What's Included

Wondering what website maintenance costs in Edmonton? Explore monthly pricing, essential services, hidden fees and how to choose the right care plan.

Schema Markup for Canadian Businesses: A Practical Guide
2026-11-05T04:00:17.364Z

Schema Markup for Canadian Businesses: A Practical Guide

Schema markup helps search engines understand your business, services and location. Learn which structured data Canadian businesses need and how to implement it correctly.