The vendor is required to provide for architecture, design, development, migration, troubleshooting, and hosting for the town’s municipal website.
- Our website should prioritize usability and accessibility.
- The base layout or navigation of a page should not change drastically when switching from a desktop computer to a mobile device.
- Web content editors should not have to understand or account for reflow in order to create and maintain web pages.
- Conforms to the most recently adopted version of web content accessibility guidelines (WCAG 2.2 at time of publication).
- Must communicate all accessibility related updates at least 48 hours before implementation, when possible, and shall not implement said updates without the consent of the town unless said update is necessary to maintain the website’s functionality.
- Our website must be hosted in the states in a physically secure facility with immutable, off-site, air-gapped backup
- Network security and monitoring must meet current best practices for the prevention of intrusion, denial-of-service attacks, and other efforts to corrupt our website or render it unusable.
- The login process must follow current best practices for passwords.
- Operating system and web framework updates must be timely, and be tested before being installed on our website environment.
- Updates must be able to be rolled back if they negatively impact our website.
- The ability to preview and/or edit the mobile layout of a page.
- Web editors should not need to worry about how content will translate from desktop to mobile.
- The website should be able to seamlessly adapt to a mobile layout without formatting or accessibility issues.
- However, web editors should also be able to view and edit mobile layouts separately from the desktop layout.
- Page layouts should be responsive to all screen sizes, not just mobile devices.
- Our current page layout will appear differently when viewed on a smaller computer screen, such as a laptop.
- Buttons, text, containers, images, and general page formatting should be able to adapt to varying screen sizes without compromising formatting or accessibility.
- The ability to limit the style choices presented to web editors based on their level of access to the website (i.e., specific widgets, font size, style, color, etc.)
- Front-end users should be able to customize the appearance and functionality of the website to accommodate any potential disability or other accessibility-related factor, including the ability to increase font size, pause animations and videos, adjust contrast, highlight links, hide images, and customize cursor size (e.g., dyslexia-friendly settings).
- Contract Period/Term: 1 year
- Questions/Inquires Deadline: April 28, 2025