Digital Accessibility Requirements
for British Columbia

A practical, plain-language overview of key digital accessibility obligations and expectations in British Columbia—and how they can impact your website, apps, documents, and customer/employee journeys

Who this is for: Organizations operating in British Columbia—including employers, landlords/housing providers, service providers, membership organizations, and public-sector bodies—who publish content, run digital services, or provide digital customer/employee experiences.

Note: This page is informational and not legal advice. Human rights and accessibility obligations are fact-specific and can depend on your organization, the context, and individual needs. For formal guidance, consult qualified legal or compliance professionals.

British Columbia requirements at a glance

Important distinction: Human-rights obligations (like non-discrimination and the duty to accommodate) are legal requirements. WCAG is a technical standard that many organizations use as a measurable way to reduce digital barriers and demonstrate accessibility efforts—but meeting WCAG doesn’t replace the need to respond to individual accommodation needs.

B.C. Human Rights Code: Accessibility barriers (including digital barriers) can create discrimination concerns where they limit equal access to services, employment, housing, or other protected areas, particularly on the ground of disability.

Learn more about BC Human Rights Code

Duty to accommodate: In protected areas like employment and services, organizations are generally expected to take reasonable steps to remove disability-related barriers and provide accommodation, up to undue hardship.

Learn more about Duty to Accommodate

Accessible British Columbia Act (2021) and Regulation (in force Sept 1, 2022): Creates a framework (including accessibility plans, committees, and feedback mechanisms) for prescribed public-sector organizations to identify, remove, and prevent barriers.

Learn more about Accessible British Columbia Act

Common digital benchmark: WCAG Level AA is widely used in B.C. as the practical baseline for accessible websites, apps, and digital journeys (and is required for B.C. government web content under its web standards).

Learn more about WCAG

When accessibility obligations commonly apply

Services: If you provide services to the public (or a defined customer base) in B.C., you are expected to do so without discrimination based on disability. Digital channels that gate access—online applications, booking, account management, support, payments—are commonly in scope.

Employment: If you employ people in B.C., accessibility considerations apply throughout recruitment, hiring, onboarding, training, workplace tools, performance processes, and return-to-work. Digital systems used for these activities (careers sites, applicant tracking systems, HR portals, intranets, e-learning) must not create disability-related barriers.

Housing: Housing providers and landlords must provide access without discrimination. Digital rental applications, tenant portals, and required electronic notices or forms can engage accessibility obligations.

End-to-end journeys matter: Even if your main website looks accessible, barriers can exist in PDFs, embedded third-party tools, authentication flows, and support forms—anywhere a person must interact to get what they need.

What these requirements typically mean in practice (digital accessibility)

1) Preventing disability-related barriers and discrimination

Digital barriers can raise discrimination concerns when they deny equal access or impose disadvantage on people with disabilities (including barriers that arise unintentionally through design choices). Examples include forms that can’t be completed with a keyboard, missing labels for screen readers, critical information conveyed only by color, inaccessible PDFs needed to apply for a job or service, or authentication methods that are not usable for some users.

In many contexts covered by human rights law, organizations are generally expected to accommodate disability-related needs. In digital contexts, that may mean removing barriers in an online journey, providing an alternative accessible method to complete a task, offering content in accessible formats, or enabling assistive-technology compatibility—based on the individual’s needs and the context.

Providing an accessible alternative format for a form or PDF.

Offering assistance to complete an application (for example, by phone or in person) when a digital barrier exists.

Ensuring CAPTCHAs and authentication methods have accessible alternatives.

Extending time limits where feasible.

Providing accessible customer support channels (not voice-only) and an escalation path when accessibility issues are reported.

2) The duty to accommodate (including in digital channels)

In practice, many organizations meet accessibility obligations not only through remediation work, but also through day-to-day processes: making it easy for people to report barriers, responding in a timely way, and providing alternate formats or alternate ways to complete tasks when needed (especially while fixes are in progress).

Maintain a clear feedback channel: Provide a visible way to report accessibility issues (web form, email, phone, and a non-voice option) and route requests to an owner.

Offer alternate formats and alternate methods: Be prepared to provide accessible electronic formats, large print, or other formats as appropriate, and offer an alternate way to complete critical tasks if a barrier blocks access.

Track and triage: Treat accessibility requests like operational work—log them, prioritize by impact, assign owners, and communicate status.

Document outcomes: Keep a simple record of what was reported, how it was addressed, and any interim measures used.

Accessibility feedback and alternate formats (operational expectations)

The duty to accommodate is not unlimited. Accommodation may be limited where it would cause undue hardship (a high threshold that is context-specific and typically requires evidence—not assumptions). In practice, organizations often address urgent barriers through remediation and/or an interim alternative channel while longer-term fixes are delivered.

3) Limits: undue hardship

What this means for your website and digital channels

The standard you’ll hear about (WCAG)

Common benchmark: WCAG Level AA is widely used as the practical baseline for accessible websites and digital journeys in Canada.

B.C. government web content (who this applies to): This applies when you build, manage, or publish digital content for the Province of B.C. (e.g., ministries/agencies or vendors publishing on their behalf). Provincial web standards require meeting the most current version of WCAG at Level AA (alongside additional content standards such as plain language).

Accessibility must be maintained: New content, new features, and vendor updates can introduce barriers if accessibility isn’t built into design, development, QA, and publishing workflows.

Shared components matter: Navigation, authentication, search, templates, and forms can create organization-wide issues if they are not accessible.

What content is typically in scope

Core public journeys: eligibility checks, applications, bookings, sign-up/sign-in, payments, account management, and cancellations.
Customer support and issue resolution: contact flows, complaint paths, chat, web forms, and knowledge-base content.
Documents and downloads: PDFs and forms people must read, understand, sign, or submit (including policies, notices, and contracts).
Employment-related digital systems: careers sites, online assessments, applicant tracking systems, onboarding portals, timekeeping, HR self-serve, and required training.
Third-party tools and embedded services: identity providers, chat widgets, scheduling tools, maps, payment providers, and any vendor platform you rely on. Using a third party doesn’t remove the need to ensure people with disabilities can access your service end-to-end.

Core accessibility themes to watch for

Perceivable: Provide text alternatives for non-text content; ensure sufficient color contrast; don’t convey meaning by color alone.
Operable: Everything works with a keyboard; focus is visible; users can pause/stop/move content where applicable.
Understandable: Clear labels and instructions; consistent navigation; helpful, specific error messages.
Robust: Use semantic structure so assistive technologies can interpret content reliably; ensure accessible name/role/value for interactive controls.

A practical way to get started

Identify high-impact journeys: List the pages, workflows, and documents people rely on to access your services, employment opportunities, or housing.
Assess current accessibility: Combine automated testing with manual checks (keyboard-only and screen reader testing) across key templates, forms, PDFs, and vendor tools.
Prioritize by human impact: Address navigation, forms, errors, contrast, document accessibility, and authentication barriers first—these often block access entirely.
Fix and validate: Remediate issues, then re-test and document outcomes so teams can ship changes with confidence.
Prevent regressions: Embed accessibility into procurement, design reviews, content publishing, development standards, and release QA.

Evidence you should keep (to show diligence and support procurement)

Accessibility audit results (and the scope/standard used).
Issue log with severity/impact and decision notes.
Remediation plan with priorities, owners, and target dates.
Re-test evidence showing fixes were validated.
Vendor accessibility documentation for third-party tools (e.g., accessibility statements or conformance reporting).
Records of accessibility feedback, alternate-format requests, and how they were addressed.

How 4Point can help

If you’re working to reduce digital accessibility barriers and strengthen alignment with British Columbia accessibility expectations, a practical first step is understanding where you stand. 4Point can run an accessibility audit to establish a baseline, identify the highest-risk barriers, and provide prioritized recommendations you can use to plan remediation.

Scoping session: Confirm what’s in scope (e.g., specific forms, templates, pages, or key user journeys in B.C. operations), the volume to be reviewed, and the accessibility standard(s) to assess against (commonly WCAG 2.1 Level AA).

Accessibility audit: Review an agreed set of forms/pages and document accessibility gaps that could create barriers for people with disabilities across end-to-end digital journeys (including documents and embedded third-party tools where applicable).

Conformance report and prioritization: provide conformance findings, severity ratings, and a recommended fix order.

Conformance report and prioritization: Provide findings with severity ratings and a recommended fix order, mapped to relevant WCAG success criteria and practical impact.

Recommendations and remediation plan: Share next-step recommendations and a remediation plan, including an optional statement of work for remediation of the audited items (remediation delivery is not included in the audit engagement).

Next step: Request an audit by sharing your digital scope (properties, platforms, documents, and key journeys used in British Columbia), your target standard (e.g., WCAG 2.1 AA), and any key dates. We’ll confirm the audit approach and sample size (templates/journeys) and deliver a prioritized findings summary with recommended fixes.

Contact 4Point: Request an accessibility audit.

Anchor 2

Digital Accessibility Requirements for British Columbia