NFR gate: WCAG 2.2 AA + performance + infra alignment (meta)

Problem / Motivation

PRD constraints: WCAG 2.2 AA compliance, urgency to replace Drupal 6, and infrastructure modernization (Kubernetes-ready).

Proposed resolution

  • Define accessibility acceptance gates for key flows (directory, group page, join/leave, create/edit).
  • Establish performance targets for directory queries at scale.
  • Confirm hosting/deploy alignment with current drupal.org infra (Kubernetes, etc.).

Acceptance criteria

  • Accessibility checks documented and passed for MVP flows.
  • A performance test plan exists for directory filtering and group-page loads.

Pipeline

Meta / epic-level gate — not a single implementable feature. The pipeline's Spec Auditor (S) enforces WCAG per feature; this issue tracks the cross-cutting NFR acceptance.

Source: DA-New Groups — MVP PRD (Google Doc). Target Drupal core version per the project's core-version decision (see #3578750).

Part of the MVP epic #3578778.

Proposed approach (reference — not yet decided)

A proposed approach for this exists in the D11 Migration docs (imported via !28 (merged)), reflecting an Open Social → standard Drupal conversion built on the contrib drupal/group module. Treat it as a reference proposal, not a decision — whether this project adopts that schema is still open (see the data-model decision in #3578779). See: Testing Strategy.

Edited by André Angelantoni