Skip to main content

Web Content Accessibility Guidelines

Understanding accessibility standards and laws that WCAG measure web content accessibility, primarily for people with disabilities.

Samantha Postlethwaite avatar
Written by Samantha Postlethwaite
Updated yesterday

We're working to ensure the front office meets Americans with Disabilities Act (ADA) requirements. Our goal is to make the front office compatible with WCAG AA 2.1 standards to support all major assistive tools for individuals with visual and motor visibilities, and then begin adapting to the latest WCAG AA 2.2 standards. For SmartRec's administrator portal, we provide supplementary software for our organizations' employees who need visual or motor assistance when using Amilia’s solution.


🌐 About WCAG and the laws driving compliance

​The Web Content Accessibility Guidelines (WCAG) are a series of guidelines published by the World Wide Web Consortium (W3C), aimed at making web content more accessible, primarily for people with disabilities. These guidelines are commonly used as the framework for ADA Compliance and Section 508 of the Rehabilitation Act of 1973.

Key federal and provincial/state laws—including the U.S. ADA (Titles II & III), Colorado HB 21-1110, Canada’s Accessible Canada Act, Ontario AODA, Nova Scotia Accessibility Act, Manitoba AMA, and BC Accessible BC Act—are driving strict WCAG compliance for public and private organizations, while other regional laws provide broader anti-discrimination protections. Click here for more details.

🏢 What we're doing at Amilia

We’re committed to ensuring that users with disabilities who rely on assistive technologies can use SmartRec to its fullest, just like any other user. By following accessibility best practices in our product design, we improve usability for everyone.

Check out our Voluntary Product Accessibility Template (VPAT) to see how we meet WCAG standards, and where we're working to improve. More changes are coming!

SmartRec Accessibility Conformance Report - WCAG Edition (Based on VPAT® Version 2.5)

Some of the changes we're implementing

  • Keyboard navigation through the site

  • Screen reader compatibility for visually impaired users

  • Color contrast that meets accessibility standards

  • Resizable text without layout issues

  • Form labels and error identification for assistive tech

  • Alt text capabilities for non-decorative images

  • Consistent layout and intuitive navigation

  • Regular platform audits and updates

✏️ Your role as a SmartRec admin

While SmartRec gives you the tools and a solid foundation, you are responsible for making sure your store configuration and content meet accessibility requirements.

Your responsibilities include

  • Add alt text to all non-decorative images you upload

  • Use clear and descriptive language for links and buttons

  • Maintain good color contrast if customizing themes

  • Keep content easy to read and logically structured

  • Audit your content regularly to catch and fix issues early

  • Test your store using tools like WAVE or a screen reader such as NVDA

👪 What this means for your participants

By adhering to accessibility best practices, you create a more welcoming and inclusive experience for all members of your community.


This means participants with disabilities can:

  • Independently browse and register for programs

  • Complete transactions without assistance

  • Access information in a way that works for them

  • Have a seamless experience, just like every other user

It’s not just about legal compliance…it’s about building trust and creating equal access for a smoother, more intuitive experience for all participants.


❓ Frequently Asked Questions

1. What is a Voluntary Product Accessibility Template (VPAT)?

A Voluntary Product Accessibility Template (VPAT) can be completed to document and measure a product's conformance with WCAG accessibility standards and guidelines. WCAG versions 2.0, 2.1, (and soon 2.2) are most often referenced in laws about accessibility. Both versions have 3 levels of compliance: A, AA, AAA, with criterion becoming stricter at each level.

2. Which US and Canadian laws require WCAG compliance for websites and digital content?

Below is a summary of key laws in the US and Canada that require WCAG compliance for websites and digital content:

United States

Canada

  • Federal - Americans with Disabilities Act (ADA) Title II

    • Applies to state & local governments and funded projects.

    • Requires all websites, mobile apps, SaaS, and digital documents to meet WCAG 2.1 A/AA.

    • Compliance deadlines: 2026 (50K+ people) and 2027 (<50K).

    • Enforcement: government oversight; lawsuits generally settled with legal fees.

  • Federal - Accessible Canada Act (ACA)

    • Applies to federally regulated organizations.

    • Mandates WCAG 2.0/2.1 AA compliance for all digital content.

    • Enforcement: audits, complaints, fines up to $250,000.

  • Colorado - HB 21-1110

    • Mandates WCAG 2.1 AA compliance for public-facing state and local government digital services by 2025.

    • Enforcement via state oversight; strong alignment with federal ADA.

  • Ontario - Accessibility for Ontarians with Disabilities Act (AODA)

    • Applies to public & private organizations (especially large employers).

    • Requires WCAG 2.0 AA compliance for websites and digital content.

  • Other U.S. laws (mainly discrimination-focused, with indirect impact on accessibility):

    • California Unruh Act

    • New York Human Rights Law & Civil Rights Law

  • Manitoba – Accessibility for Manitobans Act (AMA)

    • Applies to public and private organizations.

    • Requires WCAG 2.1 AA compliance for digital content.

  • British Columbia – Accessible BC Act

    • Currently applies only to government entities, expected to expand into private/nonprofit sector

    • Mandates WCAG 2.1 AA compliance, with phased standards.

  • Nova Scotia Accessibility Act

    • Mandates development of standards for digital and communication accessibility, aligning with WCAG.

    • Focus: public & private organizations, compliance roadmap to 2030.

3. Is SmartRec fully accessible now?

We're committed to achieving WCAG 2.1 AA compliance across core customer journeys and user paths, ensuring screen reader compatibility and maintaining a clean VPAT assessment for customer-facing features.

While the platform already supports accessible user experiences, accessibility is never “one and done.” We are continually improving, testing, and expanding our support, based on user feedback and evolving standards.

We're committed to achieving WCAG 2.1 AA compliance across core customer journeys and user paths, ensuring screen reader compatibility and maintaining a clean VPAT assessment for customer-facing features including the store, "My Account" and mobile app.


4. What about the exceptions listed in your VPAT?

A VPAT provides a clear, honest view of what’s fully supported, what’s in progress, and where improvements are planned. Exceptions are typically small technical items that don’t impact real users (e.g., background code improvements). No platform is perfect, and transparency is key.

5. Am I at risk because of exceptions listed in the VPAT?

Our prioritization ensures critical and serious barriers don’t exist. Most legal complaints arise when users cannot complete tasks at all, not when minor enhancements are pending. We focus on real-world usability to help protect you and your users.

6. How often do you update accessibility features?

We release improvements regularly. Critical and serious accessibility issues are addressed as soon as they’re identified. Minor and moderate improvements are rolled out in scheduled updates.

7. Can Amilia audit my store or content?

While we’re here to guide and support, we do not perform store-level accessibility audits or fix customer-created content. If you need expert help, we recommend working with a certified accessibility consultant.

8. Do I need to add alternative text to all images?

No, not to every image. Our platform distinguishes between three types of images:

  • Images that need alt text: Images that convey important information solely via the image (e.g., multiple facility booking images) require alt text. Our admin tools provide specific fields for adding alt text to these images.

  • Decorative images: Most images on stores are considered decorative (i.e., shown where there is equivalent text information and the image does not add any important additional information) and don't need descriptive alt text. Our platform automatically handles these with empty alt text (alt="") to ensure compatibility with screen readers without extra work from you.

  • Rich Text Editor images: If you're inserting images into store item descriptions using our rich text editor, you must add meaningful alt text if the image conveys information.

When uploading images, our system will prompt you for alt text only when it's required for accessibility compliance.

9. What if I see a platform-related issue or need technical support?

Please notify our team at support@amilia.com or start a chat with us!

* Last updated in August 2025

Did this answer your question?