Aiforseniorslife
+1 416 572 3180
Support materials and a quiet workspace for program delivery

Operations

Delivery and accessibility model

The interface, the support line and the facilitation pattern are designed for people aged 55 and over, including those who will never complete a consumer onboarding flow unaided. Large type on this public site is part of the same brief, not a separate marketing choice.

Interface

Platform

A participant sees one entry point. After the coordinator supplies the list, we send a sign-in link by email or issue a short code that a host can read aloud in the room. There is no requirement to invent and remember a new password. If an email address is not available, the coordinator can request a code-based path at scoping.

Controls are large, captions are on by default for facilitated video, and there is no autoplaying promotional media. A missed live session can be watched as a recording for 90 days. The recording carries the same captions and transcript as the live hour.

The learning environment does not contain advertising, third-party retargeting, or suggested “next products.” Navigation stays inside the current program. If a person reaches a dead end, the support number is visible in the same view as the session list.

Staff coordinators have a separate view: cohort roster, attendance, and which practical tasks are marked complete. That view uses a staff password that meets the rules in the security section below.

Standards

Standards we build to

The learning interface is specified against WCAG 2.2 Level AA. Text and interface contrast is targeted at 4.5:1 or greater for standard text. Body type in the learning environment is not set below the 18-pixel floor used on this site. Focus states are visible. Keyboard users can reach every control required to join a session and complete a task.

Media does not autoplay. Motion can be switched off; the same reduced-motion preference honoured on this public site is honoured in the program interface. Captions and transcripts are supplied for facilitated sessions. We do not rely on colour alone to mark attendance or task state.

These are design targets and operating practices. They are described in the accessibility statement issued to procurement teams. They are not a substitute for an organization’s own AODA obligations, and they are not a claim of certification by a named auditor on this page.

Support

Learner support line

The line is open Monday to Saturday, 09:00–19:00 Eastern Time, in English and French. It is staffed for onboarding, device friction, and “I cannot see the join button” problems. It is not a medical, legal or banking advice line, and callers are told so if the question turns that way.

Typical contacts are a lost email link, a tablet that will not wake the microphone, a caption language that needs switching, and a request to join by phone audio. Where the issue is a local room setup, we escalate to the client coordinator rather than improvising a site visit.

Repeat failures to join are logged against the intake so the weekly summary is not a surprise. Coordinators receive a digest of open issues, not a transcript of every call. After hours, a recorded message points to the next opening time and to the coordinator’s published channel.

Rooms

Facilitated model

Aiforseniorslife provides the lead facilitator for each live session. The client provides a host when the intake is tied to a building, a branch or a library room. The host greets, helps with seating and devices, and keeps the social contract of the room. The facilitator leads the task.

Group size is agreed at scoping. Very large intakes are split so that a person can be seen and heard, not parked on a silent grid. If attendance drops, we do not cancel the remaining weeks by default. We discuss with the coordinator whether to merge groups, keep the calendar, or adjust the host pattern. Low attendance is reported; it is not hidden.

Facilitators follow the scripted boundaries: no diagnosis, no product lock-in, no collecting credentials. If a participant discloses harm or a possible crime, the facilitator follows the escalation path written for that licence rather than inventing a response in the moment.

Calendar

Onboarding timeline

Week 1 — Scope

Population, languages, devices, reporting recipients and privacy addendum are confirmed. You receive a scoping note and a draft calendar.

Week 2 — Coordinator briefing

The named coordinator receives the toolkit, the room or device checklist, and the support-line script staff may quote.

Week 3 — Roster

The participant list is loaded. Preferred access method — email link or code — is set per person where needed.

Week 4 — Access test

A short join test is offered. Support-line hours are published to participants. Print packs are shipped or downloaded.

Week 5 — First live session

Session one runs. Attendance and join issues are logged the same day. The weekly coordinator summary begins.

Week 6 — Steady state

The remaining calendar is treated as fixed unless the coordinator requests a change. Recordings accumulate under the 90-day rule.

Records

Data, security and hosting

Learner records for licensed programs are stored in Canada. Enquiry records submitted through this website are treated as described in the Privacy notice. We do not sell either class of data and we do not pass it to third parties for their own marketing.

Access to learner records is limited to the program team operating the intake and to the client coordinator for that licence. Staff passwords follow a length and rotation rule issued in the security note; where two-factor authentication is issued, it is required. Learner access by link or code is treated as a session token, not as a standing password.

Retention follows the licence: reports are issued at the agreed cadence; learner-level records are deleted on the contract schedule, or earlier on written request where the addendum allows. A closing export can be provided in a tabular file before deletion. Hosting subcontractors, if used, remain bound to Canadian storage for program records.

Devices

Device and connection requirements

The program is tested on tablets that are about a decade old and on laptops that would not be issued as “current” staff machines. A 9-inch screen is the practical floor. A browser on its current or previous major version is enough. Headphones help in a shared room; a microphone is optional because a host can speak for the group.

The connection must hold a 45-minute facilitated session. If it cannot, the print pack and the recording window are the fallback, plus the telephone line. We do not require a particular operating system or a app-store install as a condition of joining.