Budget Planning
Resources
How to Use OIT's Enterprise Agreement Accessibility Vendors (Doc)
Position Descriptions and job postings for accessibility-related roles (Sheets)
Guidance for hiring accessibility specialists (Coming Soon)
Archived resources:
FY23-24 Accessibility Budget Planning and Spending
Accessibility budget dollars will be arriving to your agency budget offices starting July 1, 2023. Agencies should work with their own budget offices to start Fiscal year budgeting for testing, remediation, staff, and other accessibility needs (like training and accessibility software).
There will be a single line item in your budget for accessibility.
Agency staff should reach out to their budget directors with questions about funding.
Agencies should use their IT Accessibility Adoption Plans to help with budget requests.
Any additional funding needed should be requested in future budget sessions.
In your request, indicate the full amount of funding needed to be compliant with HB21-1110 and include the additional 10% to be set aside for future replacement costs (per OSPB Budget Guidance).
While OIT will provide guidance on the request, specific questions related to finances should go to OSPB through your budget team (similar to other budget requests).
Previous Draft Language To Consider For Future Budget Requests
OIT's FY 2023-24 Decision Item - Accessibility Testing and Remediation - IT Capital
OIT's Budget Amendment FY23: Technology Accessibility Program
Governor’s Budget Submission: Summary of OIT’s Technology Accessibility Program Request
Staff Hiring Using the Accessibility Budget
The budget for staff is not called out specifically in the budget so agencies will want to plan for those positions within the total budget dollars they receive.
Staff hiring for agencies should be non-technical roles as technical roles are required to stay within OIT. Non-technical positions include roles such as project and program managers, communications roles, web content editors, and accessibility coordinators. Technical roles that should go through OIT are developers and testers.
Focus on your total funding amount and rethink as an agency how you want to spend those dollars. This should be a collaborative discussion with your working group and include your budget office. The agencies are able to spend the funds at their discretion and they aren’t beholden to the line item amounts indicated in their original budget request. (e.g., FTEs, testing, remediation, etc.).
If before the end of FY25-26, agencies want more funds they will need to submit a Decision Item during the normal budget process.
For help with hiring accessibility positions and defining those roles check out the Position Descriptions and job postings for accessibility-related roles (Sheets).
Estimating For Testing and Remediation
Manual Testing Estimation Guidance for Websites
Use the following criteria to help determine the estimated hours needed to manually test websites:
Priority (Low, Medium, High):
It is recommended that all high and medium-priority sites are manually tested regardless of complexity.
Low priority, "Simple" websites may not need to be included in your manual testing budget for websites. These sites will require the site owner to manually test using the tools that are available to the state.
The complexity of the site will determine the size of the testing effort:
Simple / S / 20 hours: informational content with simple images (e.g. logos, icons), simple search, no video or audio, very few PDFs if any, no live updated content embeds (e.g. Twitter, Facebook), no e-commerce or custom forms
E.g., This website, IT Accessibility Planning Guide
Moderate/ M / 40 hours: more complex than a simple site with media (video, audio, images, PDFs) e-commerce and more complex forms, simple search, media and limited live updated content embeds (e.g. data studio, calendar, Twitter, Facebook).
Complex / L / 80 hours: Large sites with dynamic content like maps, complex forms, e-commerce transactions, and other embedded applications (APIs), advanced search functionality
View OIT's Accessibility Plan list of websites for an example on how the number of hours and cost for website testing were calculated.
Remediation Guidance for Websites:
Website platform issues will need to be fixed by the vendors. OIT is working with SIPA/Tyler Technologies (colorado.gov platform provider) to remediate colorado.gov platform issues.
Please share your colorado.gov manual testing reports with the TAP office team: oit_accessibility@state.co.us
Agency needs for website remediation will vary. Agencies should consider the following when deciding if additional resources are needed for website remediation:
The capacity of your communications team
How complex the remediation is
The volume of the work
The skill set of the team that will be doing the website remediation
Agencies may decide to use existing staff to remediate website content.
Manual Testing Guidance for Applications
To determine the estimated hours needed to manually test applications
Use the Apps tab on your IT Accessibility Adoption Plan to estimate the manual testing hours needed.
One way to categorize the applications is to use a scale for the size of the application (such as XS, S, M, L). You can then use the following testing hour estimates (which are in general about half of the hours needed to remediate):
XS = 20 hours
S = 40 hours
M= 80 hours
L = 100 hours
If needed, you can use 80 hours of manual testing time per website or application as a general default.
To calculate the funding needs, take the total manual testing hours needed and multiply by an average $125/hr.
Remediation Guidance for Applications:
To determine the estimated hours needed to remediate applications, use the Apps tab on your IT Accessibility Adoption Plan to estimate remediation hours needed.
You will want to categorize the applications to better estimate (such as XS, S, M, L). Then use the following remediation hour estimates:
XS = 40 hours
S = 80 hours
M= 160 hours
L = 320 hours
To calculate the funding needs for remediation, take the total remediation hours needed and multiply by an average $125/hr.
Learn How to Use OIT's Enterprise Agreement Accessibility Vendors.
Accessibility, Tech Debt and Technology Planning Workbooks (TPWs)
How do the Technology Planning Workbooks inform the IT Accessibility Adoption Plans and vise versa?
Agencies will have information in their TPWs regarding applications and IT systems that will be helpful when creating plans for remediation. One example may be that an application has an "F" rating in the TPW and there are plans and budget to completely update that system next year. In this case, an agency may decide NOT to invest time/energy into testing and remediating the old system as they know it will be replaced.
If not replaced by July 1, 2024, agencies will need to put reasonable accommodations in place for the IT system and may need to include those in the budget request. See below, "What is an accessibility accommodation?"
Remediating accessibility issues at the end of the design cycle or after launch is expensive, inefficient and oftentimes results in the need to create a parallel version to accommodate specific disabilities.
Resources for remediation should include training and tools for teaching teams to remediate digital content on their own and more importantly, to create content with accessibility in mind from the very beginning.
What is an accessibility accommodation?
To put it plainly, accessibility is a proactive solution to provide equal access to all. Accessibility is the goal that the state of Colorado is earnestly working toward.
Accommodations are a reactive and many times costly response to addressing special cases. Accommodations may mean that information has to be maintained in multiple places and formats, or that an in-person service can’t be closed because an online service cannot be accessed by all those that need it.
“Accessibility is the baseline of equal service, and accommodation is the second step to take when accessibility alone isn't enough.” - Disability Thinking
What Applications Will OIT Be Responsible For?
Enterprise Applications (see list below) – OIT and agencies are partners in accessibility accountability. Use this decision tree to understand how agencies will partner with OIT and when agencies are fully responsible.
Was the application built using an Enterprise Application platform?
No: The agency is responsible for testing, remediation and project management costs
Yes: Continue to the next question
Was the application built by OIT?
No
The agency is responsible for testing costs
The agency is responsible for the cost of agency development remediation (any issues that are caused by agency development and not the vendor's platform)
The agency will provide testing results related to Enterprise platform failures to OIT and OIT will work with the platform vendor to ensure they remediate issues related to the platform
The agency is responsible for project management costs regarding testing and remediating this application
Yes
OIT is responsible for testing and remediation costs
OIT is responsible for project management costs regarding testing and remediating this application
Enterprise Applications
Salesforce
ECS (Hyland Enterprise CMS / On Base)
Google Workspace & GCP
Service Hub (Service Now)
AWS (Infrastructure as a Service)
Tableau (Data Visualization)
Azure DevOps
Socrata/CIM (Colorado.data.gov)
ArcGIS
Mulesoft
Kronos
Active Directory (Microsoft)
Colorado Business Express (MyBiz)
Electronic Document Warehouse
PingID
One Identity
Radiant Login Virtual Directory