Specifications include, but are not limited to: TN-TIMES Design. a. Functional and Technical Requirements. TN-TIMES shall meet the requirements defined in Attachment C, “TN-TIMES Functional and Technical Requirements,” in addition to all other requirements specified in this Contract. b. Accessibility. TN-TIMES shall be compliant with section 508 ADA standards for web applications. c. Web Design Requirements. All web pages designed as part of TN-TIMES shall comply with the following: (1) adhere to HTML5 guidelines, (2) development using responsive website techniques (e.g., Bootstrap), (3) use of only State approved logos, (4) development for multiple browsing platforms and versions, (5) use of approved Cascading Style Sheets for consistent look, and (6) do not include the use of Java, Active X, Flash or other browser plug-ins. d. Web Browser Compatibility. TN-TIMES shall be compatible and fully functional in the following web browsers: (1) Microsoft IE 11 and higher, (2) Firefox build 55 and higher, (3) Google Chrome build 60 and higher, (4) Safari 10.0 and higher, and (5) all versions of Edge. TN-TIMES shall support responsive mobile views for all web interfaces including the following mobile Operating Systems and higher: (1) Apple iOS 10.0 (Safari Mobile); and (2) Android 4.4 (Chrome Mobile). TN-TIMES shall notify a user if TN-TIMES does not support the user’s web browser, and shall provide steps to download/install a supported browser. e. Data Exchange Formats. TN-TIMES shall support open data exchange formats including XML, WFS, ESRI Feature Service, and GeoJSON via web services. f. API Endpoints. TN-TIMES shall have HTTP-based web Application Program Interface (“API”) endpoints to provide the capability to programmatically query, create, update and delete user account and other Data, both individually and in bulk. API endpoints shall be accessible only by users authorized by the State. The Contractor shall maintain current updated documentation for API endpoints, and shall provide this documentation to the State on the Effective Date, and throughout the Term when there are changes or updates associated with API endpoints. g. TN-TIMES Interfaces. The Contractor shall be responsible for acquiring any necessary rights or permissions with respect to the implementation of TN-TIMES. The authentication/authorization method used to secure any interface(s) required by the Contractor shall be subject to approval by the State. h. TN-TIMES Version Control. The Contractor shall provide a clearly defined version control process including test and production environments, and full “roll back” to previous version capabilities. i. Online Help. TN-TIMES shall provide up-to-date online help, including context-sensitive on-line help. The online help shall be specific to a user’s role(s). j. Required Fields & Error Checking. TN-TIMES shall clearly identify missing or invalid required elements upon data entry. Certain data entry fields within TN-TIMES shall have error-checking routines to provide the user with feedback in the cases of incorrect or mis-keyed information. Examples of fields that would be appropriate for error-checking include dates, numeric values (e.g., quantities), user account phone numbers, and user account address information. k. Dropdown Lists. Dropdown lists for data entry fields shall be inserted as designated by the State. l. Navigation. TN-TIMES shall provide the capability for any user to access other screens and modules without backing out of menus or menu paths.