Website Provider Services

Website Provider Services to serve as the main face of District online platforming which may be provided on an ad hoc, periodic, or as-needed basis.
- The proposer must be able to offer an integrated, end-to-end solution encompassing CMS/platform configuration and any required development, information architecture, responsive design, content migration, accessibility, security, hosting, training, and ongoing support.
- CMS Operations and Content Governance
• Provide an accessible CMS that non-technical District staff can use to create, preview, review, approve, schedule, publish, update, archive, and restore content through governed workflows and reusable templates. Proprietary, software-as-a-service, and managed open-source solutions are eligible. A separated or headless architecture is not required;
• Provide desktop/mobile preview, reusable components, protected layouts, shared content and media, and structured metadata. Include configurable role-based approvals, governed navigation changes, named content owners, scheduled publication and expiration with notifications, version history and restoration, and an auditable publishing history;
- Accessibility and Sustainability:
• Full keyboard operability with visible focus and no keyboard traps;
• Skip links, landmark regions, and a logical heading structure enforced by the authoring tool;
• Enforced alternative-text entry or explicit decorative-image designation, as appropriate, and programmatically associated form labels at authoring time;
• Applicable WCAG contrast requirements, including at least 4.5:1 for normal text, 3:1 for large text, and 3:1 for relevant non-text interface components and graphical objects;
• Remediation of high-traffic and transaction-critical PDFs/documents to WCAG 2.1 AA, or converting them to accessible web pages based on a prioritized inventory assessment;
• Manage accessible document archiving, expiration, and redirects to preserve link integrity;
• Enforced accessibility checks and required metadata at upload;
• A pre-publication gate that prevents publication with unresolved critical issues detectable by the configured authoring checks, together with a staff-facing dashboard or equivalent report showing post-launch findings and remediation status; and
• A maintained public accessibility statement with an issue-reporting mechanism.