Manual Testing

OIT has provided the guidance set forth below regarding manual testing:

Manual testing should be done against the WCAG guidelines. This includes screen reader testing but is not exclusive to screen readers so other testing should be done for these four main areas: Visual, Audial, Physical and Cognitive. That means testing for things like color contrast and color dependency that are not related to screen reader users.

Here are the current technical standards for meeting accessibility:

1.    All Information Technology must comply with:
   1.    For all web content and software - W3C WCAG 2.1 level A and AA or higher guidelines.  
2.    Note that technology may also need to meet:
   1.    The technical standards contained in US Section 508 of the rehabilitation act of 1973 Chapter 3: Functional Performance Criteria
   2.    The technical standards contained in US Section 508 of the rehabilitation act of 1973 Chapter 4: Hardware  
   3.    The technical standards contained in US Section 508 of the rehabilitation act of 1973 Chapter 6: Support Documentation and Services

Additionally, our state standards for testing are:

1.    Windows 11 with the latest version of Jaws
2.    Latest version of Chrome browser
3.    Keyboard navigation with Chrome
4.    Mobile to Desktop responsiveness

So, to the extent you are conducting manual testing on a Colorado.gov site, please ensure that testing conforms with those standards. You may submit manual test results to: partnersupport@www.colorado.gov

When you submit those results, you must include the following information:

•    Which specific web page or section of the page were you testing?  
•    What type of error did you find?  
•    What specific error did you find?  
•    How can we replicate the issue?
•    What manual testing tools did you use?
•    What browser version were you on?
•    What operating system version were you on?
•    Provide a citation to the specific WCAG guideline you were testing against that produced the issue
•    Provide the WCAG 2.1 AA Success Criterion.
•    Provide the number of occurrences for this issue.  

If you do not include all of this information, your testing results will be returned to you and not acted on until this information is returned to Tyler.

Once we receive the results and the corresponding information outlined above, including any follow-up information we require, a Tyler team will review the findings and one of the following responses will follow:

•    The issue is already known – Tyler will inform the submitter that the issue is already known and being tracked.  
•    The issue can be mitigated by the content editor – Tyler will inform the submitter that the issue can be mitigated by the submitter’s content editor, and should be pursued with that content editor instead of Tyler.  
•    The issue is related to third-party content – Tyler will inform the submitter that the issue is related to third-party content or integration, and should be pursued with that source instead of Tyler.  
•    The issue cannot be recreated/false positive - Tyler will inform the submitter that Tyler is unable to recreate or confirm the issue, and no further steps will be taken by Tyler until such time as the submitter submits a finding that can be recreated.  
•    The item is new, and will be added to the accessibility tracker – Any items on, or added to, the accessibility tracker will be sized according to the chart below.

Our review will be completed within a commercially reasonably timeframe upon receipt of a complete submission, including any follow-up information we require. Once our review is complete and we have sized the issues (as defined below), we expect to be able to address the issue within the timeframes set forth below. 

Note: D10 base functionality scan on cms.colorado.gov will be complete before each site launch, site findings that differ from D10 base functionality may require agency to mitigate content to reach compliance.