Accessibility & privacy

Designed for access

The HTML website uses semantic headings, keyboard-operable links, forms and disclosures, visible focus indicators, large controls, responsive layouts and reduced-motion support. The public proposal can be read without JavaScript. The budget calculator and participant hub use JavaScript; the calculator’s default scenario and formulas are written out in the feasibility brief.

The HTML proposal is the primary accessible reading version. The designed PDF is a companion and has not been certified as an accessible PDF. Neither the website nor the proposed physical environment has received an independent accessibility audit.

Participant accounts and project records

The project hub is designed to authenticate through WorkOS AuthKit using a Google account. When configured, it processes the identity and email needed to manage access and uses an encrypted session in an HttpOnly cookie. WorkOS and Google handle their own authentication services. Sign-in alone does not grant access to private project material; project approval is a separate step.

Participants can record their own offers, commitments and next actions. Approved participants can view the project timeline and appropriately shared document links. Project administrators manage membership, milestones and document access; operational administration should use only the information needed for coordination.

Do not submit medical records, benefit award letters, government identifiers, banking information or resident housing-eligibility documents to this general collaboration hub. It is not a housing application, donation processor or benefits case-management system.

The example view contains clearly illustrative contributions. It does not sign anyone in or create actual donor commitments. If WorkOS is not configured, real sign-in is unavailable and private API access remains closed.

Documents in Google Drive

Project documents are stored in Google Drive. The hub holds links and coordination metadata; Drive retains the files and separately checks its own sharing permissions. A Google login to the hub does not automatically grant Drive access. An administrator must share a file with the intended Google accounts and assign the appropriate hub visibility.

The project’s initial Drive folder is private to its owner. No public-link sharing or invitations to other people have been performed. Document retention and participant-account deletion procedures must be established before live use; the current local prototype is not a substitute for an adopted privacy policy.

Hosting and local development

The site is currently a local review prototype, with a Cloud Run-ready application. Local development can persist project records in a private local JSON file. Production is designed to use Google Firestore with a dedicated runtime identity; production startup refuses local-file storage. No public cloud service has been deployed in this update.

No tracking analytics, advertising pixels or third-party embedded widgets are included. External source and document links open services governed by their own practices. Hosting providers may process routine request logs. The public budget calculator stays in the visitor’s browser.

Images and the proposed environment

The aerial, courtyard, porch, home-interior and maker-lab images are generated concept illustrations with fictional people. Their architectural cues draw from current Champion American Freedom 2848PC and Clayton Buckeye Desert Sky references. Step-free foundations, entries, paths, shade and interior adaptations are proposed design work. The maker lab is a proposed common facility.

The 14-home diagram carries the intended count and four-court arrangement. The generated aerial supplies atmosphere and may differ from that exact count. Neither establishes a parcel, code compliance, wheelchair clearances, summer shade, drainage, buildability or manufacturer approval. Detailed design needs residents and qualified professionals.

Original manufacturer photographs and plans are linked to their sources; they are not republished as public product assets. The concepts imply no partnership or endorsement.

Project status

Future Reach Collective is the chosen project name. The proposed Florida legal name is Future Reach Collective, Inc.; formation and federal charitable recognition have not been completed. Future Reach Communities is the envisioned network. No site acquisition, partnership, grant award or construction commitment is represented.

Location and finance research is dated October 13, 2026; manufacturer/community references were first checked October 9. Program availability and eligibility require confirmation. No charitable gifts or housing applications are being accepted.