Accessibility Statement

1. Our commitment

TagsForHope^® Inc. wants every partner (including people who use assistive technology) to be able to apply, sign in, browse the catalog, and place orders on this portal without barriers. We view accessibility as an ongoing effort rather than a one-time project, and we work on it as part of normal development, not as an afterthought.

2. The standards we work to

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and we track the newer WCAG 2.2 success criteria as we build. As an Ontario company we work in the spirit of the Accessibility for Ontarians with Disabilities Act (AODA), and we recognize the Americans with Disabilities Act (ADA) for our partners in the United States.

3. What we do

• Semantic HTML with proper landmarks, headings, and labels, so screen readers can navigate the portal's pages and forms.
• Keyboard operability and visible focus states for interactive controls.
• A color palette designed against WCAG contrast requirements, managed centrally so fixes apply everywhere.
• Text that scales: the portal uses relative units and remains usable when zoomed.
• Accessibility review as part of building and changing portal features.

4. Known limitations

We'd rather be honest about the edges we know about:

• PDF invoices are not yet fully tagged for screen readers. If you need an invoice in an accessible format, email us and we'll provide one.
• Data-dense tables (catalog configuration and order breakdowns) scroll horizontally on small screens and are easiest to use on a larger display.
• Third-party components (for example, embedded payment fields from providers we may use) are outside our direct control and may not fully conform.

5. Feedback and support

If anything on this portal is in your way, tell us: [email protected]. Accessibility reports get priority (we aim to respond within one business day, ahead of general support questions), and we'll work with you to complete whatever you were trying to do, including taking an application or an order by email while we fix the barrier. Feedback like this goes straight into our development queue.

6. Compatibility

The portal is built for current versions of Chrome, Firefox, Safari, and Edge, on desktop and mobile, and is designed to work with common screen readers. Older browsers may work but aren't actively supported.

7. Review

We review this statement, and the portal's conformance, as the portal evolves and at least annually.