Accessibility

Urbance Technologies Inc. ("Urbance," "we," "us," "our") is committed to ensuring that our platform — including urbance.ca and all key user flows — is accessible to the widest possible audience, regardless of technology, ability, or circumstance. We believe that digital accessibility is not a feature or an afterthought; it is a fundamental part of building a trustworthy, inclusive marketplace.

Our commitment to accessibility extends across every major surface of the Urbance platform, including:

• The main Urbance website and marketing pages (urbance.ca)
• The Instant Quote and service booking flow
• The Customer Dashboard (bookings, history, account management)
• The Provider Portal and onboarding flow (pros.urbance.ca)
• All legal, policy, and informational pages including this statement
• Account registration, login, and authentication flows
• Communication channels including in-platform support and contact forms

We recognize that accessibility is an ongoing effort and that digital platforms continue to evolve. Urbance is dedicated to continuously improving the accessibility of our platform as technology and standards advance, and we welcome feedback from all users.

Urbance works toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is the internationally recognized standard for web accessibility, and achieving it means ensuring that our platform is perceivable, operable, understandable, and robust for users with a wide range of abilities and assistive technologies.

We acknowledge that full conformance with every WCAG 2.1 AA criterion across all pages and flows is an aspirational and iterative goal. We aim to meet or exceed these criteria and are actively working to identify and remediate areas that fall short. Accessibility improvements are reviewed and prioritized as part of each development cycle.

Target Conformance Summary

Urbance is a technology company operating primarily in British Columbia, Canada. Where applicable, we also consider guidance from the Accessible Canada Act (ACA) and provincial accessibility legislation in markets we serve.

Our product and engineering teams treat accessibility as a first-class consideration during design and development — not a post-launch remediation step. New features are reviewed against WCAG 2.1 AA criteria before release, and we use both automated tools and manual testing to validate conformance.

The following accessibility features are implemented across the Urbance platform. These features are designed to support a broad range of users, including those who use assistive technologies such as screen readers, voice control software, keyboard navigation, and screen magnifiers.

Keyboard & Navigation

Screen Reader & Assistive Technology

Forms & Error Handling

• Visible, associated labels on all form inputs — no floating placeholder-only fields for required information.
• Descriptive error messages that explain what went wrong and how to fix it — not just "invalid input."
• Inline validation with programmatic announcements to screen readers via aria-live regions.
• Required field indicators that are both visually and programmatically communicated.
• Sufficient timeout warnings for time-sensitive interactions such as session expiry.
• No CAPTCHA barriers that rely solely on visual interpretation — where verification is required, accessible alternatives are provided.

Visual Design & Readability

• Color contrast for body text meets or exceeds the WCAG 2.1 AA minimum ratio of 4.5:1.
• Large text contrast (18pt+ or 14pt bold) meets or exceeds the WCAG minimum ratio of 3:1.
• Information is never conveyed by color alone — icons, labels, or patterns are used as additional indicators.
• Minimum body font size of 16px across all primary content areas.
• Text can be resized up to 200% in browser settings without loss of content or functionality.
• Line spacing, letter spacing, and paragraph spacing meet WCAG text spacing criteria.

Responsive & Device Accessibility

• Fully responsive layout for desktop, tablet, and mobile viewports.
• Touch target sizes for all buttons and interactive elements meet a minimum of 44x44 CSS pixels on mobile.
• No content loss or overlap when displayed in portrait or landscape orientation on mobile devices.
• Pages function correctly when OS-level text scaling is applied on iOS and Android.
• The platform is compatible with iOS accessibility features including Dynamic Type and Display Zoom.

Multimedia & Rich Content

• Where video content is used, captions or transcripts are provided or planned.
• Decorative animations and transitions respect the user's operating system-level "Reduce Motion" preference (prefers-reduced-motion).
• No content flashes more than three times per second, in accordance with seizure prevention guidelines.
• Icons used within the interface are always accompanied by a text label or programmatic equivalent, not used in isolation.

Urbance is a growing platform, and we are transparent about the fact that some areas of the platform may not yet fully meet every WCAG 2.1 AA criterion. We believe it is more respectful to users with disabilities to be honest about limitations than to claim conformance we have not yet achieved.

Current Known Limitations

• Some dynamic UI components — including certain modals and multi-step booking flows — may not yet have complete ARIA role and live-region coverage for all screen reader combinations.
• Certain third-party widgets embedded in the platform (such as payment forms via Stripe, or map embeds) are outside our direct control and may present accessibility challenges. See Section 7 for more detail.
• Some older marketing pages created before our current accessibility standards were established may not yet have been fully audited and remediated.
• Complex data tables in the Provider Dashboard are being updated to include proper row and column header associations.
• Some PDF documents or downloadable files linked from the platform may not be fully accessible. We are working to remediate or replace these with accessible HTML alternatives.
• Auto-populated address or service fields that rely on Google Places may have limited screen reader support depending on the user's browser and assistive technology version.

Our Remediation Commitment

We are actively working to address these limitations. Issues are prioritized by the severity of the accessibility barrier they create, with particular emphasis on barriers that prevent core task completion (such as getting a quote, booking a service, or managing an account). Our team targets resolution of high-priority issues within each development sprint.

If you encounter an accessibility issue that is not listed here, please let us know. User reports are one of the most important inputs into our accessibility improvement process.

If you encounter a barrier on the Urbance platform, or if you need information or a service provided in an alternative format, we are here to help. Urbance is committed to providing an accessible experience through alternative means where our digital platform falls short.

When Contacting Us About an Accessibility Issue

To help us assist you as quickly and effectively as possible, please include the following information when reaching out:

1. The page or feature — Describe which page, section, or feature you were trying to use (e.g., "the Instant Quote form" or "the booking confirmation page").
2. What happened — Briefly describe the issue or barrier you encountered (e.g., "the dropdown could not be selected with keyboard" or "the error message was not announced by my screen reader").
3. Your device and browser — Include the device type (desktop, phone, tablet), operating system, browser, and any assistive technology you are using (e.g., "iPhone 15, iOS 17, Safari, VoiceOver").
4. Your preferred contact method — Let us know whether you prefer email, a callback, or another method of response.

Contact Options

User feedback is one of the most valuable tools we have for identifying and resolving accessibility barriers. We actively encourage all users — including those with and without disabilities — to report issues they encounter on the Urbance platform.

There is no issue too small to report. Whether you have found a broken focus indicator, an unlabelled button, a contrast issue, or a more significant barrier that prevents you from completing a task, we want to know about it. Every report is reviewed by our team and contributes to our ongoing accessibility improvement roadmap.

What Happens After You Report

• We will acknowledge your report within 1 business day.
• Your report will be reviewed and assessed against WCAG 2.1 criteria by our team.
• If the issue is confirmed, it will be logged in our accessibility backlog and prioritized by severity and impact.
• We will notify you when a fix is deployed, where you have provided contact information and opted in to follow-up.
• If a fix cannot be made quickly, we will offer an immediate workaround or alternative means of accessing the affected content or service.

The Urbance platform integrates with and embeds content or functionality from third-party providers. While we carefully evaluate the accessibility of these integrations and choose partners who prioritize inclusive design, we do not control the underlying code, interfaces, or update cycles of third-party services.

Third-Party Integrations on Urbance

• Payment Processing (Stripe). All payment forms are hosted and rendered by Stripe, Inc. Stripe has its own accessibility program and works toward WCAG 2.1 AA compliance. If you experience a barrier in the Stripe payment form, you may contact Stripe's support directly. Urbance is not able to modify Stripe's payment UI directly.
• Mapping and Location Services. Address autocomplete and mapping functionality may rely on Google Maps or similar providers. The accessibility of these tools is governed by the respective third-party. We work to provide accessible alternatives (e.g., manual address entry) where possible.
• Live Chat and Support Widgets. Our in-platform support chat may use a third-party chat widget. We select providers who offer keyboard-accessible and screen-reader-compatible chat experiences, and we review accessibility as part of our vendor evaluation process.
• Analytics and Tracking Scripts. Third-party analytics tools operate invisibly in the background and do not create accessibility barriers for users. They do not render visible content that would require accessibility compliance.
• Embedded Social or Video Content. Where videos or social media embeds are used on the platform, we provide equivalent text descriptions or accessible links to the source content where the embedded version is not fully accessible.

Urbance is committed to selecting and working with third-party service providers who share our commitment to accessibility. Where a third-party component presents an accessibility barrier that cannot be resolved, we will work to provide an equally effective accessible alternative means of accomplishing the same task.

If you encounter a barrier that appears to be related to a third-party component, please still report it to us. We will investigate whether a mitigation or alternative can be provided, and we will raise the issue with the relevant third-party vendor.

Urbance uses a combination of automated tools, manual expert testing, and real-user feedback to evaluate and improve the accessibility of our platform on an ongoing basis. We believe that accessibility testing must be both systematic and human-centered to be effective.

Automated Testing

• Automated accessibility scans are conducted using industry-standard tools including Axe and Lighthouse during development and as part of our build process.
• Automated tests are run on core user flows (homepage, quote flow, booking confirmation, account pages) after each significant release.
• Results are reviewed by our engineering team and failing checks are triaged by severity.

Manual Testing

• Key pages and flows are manually audited against WCAG 2.1 AA criteria on a periodic basis.
• Manual testing includes keyboard-only navigation, testing with VoiceOver on macOS and iOS, NVDA on Windows, and TalkBack on Android.
• Testing includes verification of heading hierarchy, landmark structure, color contrast, focus management, form error handling, and modal/dialog accessibility.
• New features and design changes are reviewed for accessibility concerns before they are released to production.

User Feedback Loop

• Reports submitted through our accessibility reporting channel are reviewed within 1 business day and fed into our development roadmap.
• We maintain an internal accessibility backlog that is reviewed as part of each development sprint.
• Where feasible, users who report issues are notified when a fix has been deployed.

Release-Based Improvements

Accessibility improvements are shipped as part of regular Urbance platform releases. We do not treat accessibility as a standalone project with a discrete end date — it is an integral part of every development cycle. Our goal is to reduce the number of known accessibility issues with each release and to prevent the introduction of new barriers through proactive design review.

Urbance may update this Accessibility Statement from time to time to reflect changes to our platform, our accessibility practices, applicable standards, or the results of ongoing audits. We will update the "Last updated" date at the top of this page whenever a material change is made.

We encourage users to review this statement periodically. If we make a significant change to our accessibility status or practices, we will note the nature of the change below the "Last updated" date for a period of 90 days following the change.

This statement does not constitute a legal warranty of conformance. It represents our good-faith effort to communicate our current accessibility status and our commitment to ongoing improvement. Questions about this statement should be directed to support@urbance.ca.

This Accessibility Statement was last reviewed and updated on February 25, 2026. Urbance Technologies Inc., British Columbia, Canada.