Investing in Accessibility

January 8, 2018

The Government of Canada is committed to openness and transparency. When we open government, we need to open it to all Canadians, regardless of their accessibility needs.

That’s why I’m thrilled that the Treasury Board Secretariat is making what I hope will be a transformative investment. We’re putting out a contract for an innovative, open source solution to help improve accessibility. We’re making the investment to help make Government and its information truly open by default, for all Canadians.

Buying tech to support accessibility

On January 5th, I was at DigiHub, a business incubator in Shawinigan, Quebec. I was with colleagues to announce that we have put out a contract to enhance accessibility for content on our website, for persons with disabilities.

To address the challenge, we’ll be scaling and iterating the agile procurement process that we launched over the summer. I’m excited to demonstrate that we can and should continue to make our procurement process simpler and faster.

Becoming open by default

Over the summer, we were very happy to complete a competitive procurement process within two months (more info in this blog). We worked with a great team at Public Services and Procurement Canada to award a contract to improve the usability of our Open by Default Pilot portal.

But usability was not our only challenge in making government open by default. The accessibility of the documents on our portal was another concern. The portal provides public access to our draft documents. We discovered that public servants sometimes struggle to make their documents fully accessible to people with a variety of accessibility needs.

The global technological community is investing in the development of new tools to enhance accessibility. Emerging technologies show promise in improving accessibility and support inclusion. We want to tap into that expertise to find solutions for more digital accessibility on our pilot portal.

We’re buying technology differently

Since our procurement pilot over the summer, we’ve been spreading the word that government can buy technology differently. By modernizing and streamlining our procurement processes, we can support digital marketplaces that help us deliver better results for Canadians.

So when we asked partners across government to get involved, there were lots of volunteers! Several departments are contributing funds. The Public Service Commission agreed to identify a second challenge. And Public Services and Procurement Canada again accepted to serve as our contracting authority.

Now we have two amazing opportunities to improve digital accessibility. We’re focused on two government websites, and the Government of Canada recruitment site. I would love to see as many proposals as possible submitted to find the best solution.

Our procurement process

We are looking to work with leading innovators in Canada and abroad to help address accessibility challenges.

If you’re interested in submitting a bid, please take a look at our call for proposals. Bids are due by the end of January. We’re looking to award contracts to improve accessibility relating to:

  1. Documents on the Open by Default Pilot Portal;
  2. Searching and applying for federal government jobs.

We’re using a similar procurement process to what we piloted over the summer. The infographic explains the process. We’ll start by selecting up to three highest ranked bidders for each of the two challenges. After that, we’ll run a Dragon’s Den-style evaluation event to select the top contractor for each of the two challenges.

Figure 1. Infographic of CFP Process
Infographic of CFP Process
Figure 1. Infographic of CFP Process - Text version
  • Step 1: Stage 1 - Bidder Submits Proposal
  • Step 2: Stage 1 - Canada Evaluates and Ranks Bidder Proposals
  • Step 3: Stage 1 - Canada recommends top three Bidders for Contract award
  • Step 4: Stage 2 – Canada awards up to three Contracts
  • Step 5: Stage 2 – Contractors completes Phase 1 of the Work, Prototype Presentation
  • Step 6: Stage 3 – Canada evaluates Prototype Presentations
  • Step 7: Stage 3 – Canada selects one Contractor to proceed to Phases 2 and 3
  • Step 8: Stage 3 – Contractor completes Phases 2 and 3 of the Work, Development and Testing, and Implementation Support for Challenge 1 or Updated Requirements for Challenge

Want to learn more?

You’re invited to a webinar on January 9th, 2018. Registration information is on the tender notice. Officials will be available to answer your questions on the procurement process.

I look forward to seeing what kind of solutions bidders will come up with. This is our chance to improve digital accessibility for all Canadians.

I hope you will take this opportunity to propose brilliant, creative ideas. Government needs to build on external expertise to capitalize on opportunities like improving accessibility. We’re committed to leveraging open innovation to try to make that happen, together!

Alex Benay

Alex Benay
Chief Information Officer, Government of Canada

Alex Benay currently serves as the Chief Information Officer of the Government of Canada. Prior to this appointment, Alex was the President and Chief Executive Officer of the Canada Science and Technology Museums Corporation since July 2014.

From 2011 to 2014, he was Vice-President of Government Affairs and Business Development at OpenText. He has played a leadership role in Canada's digital industry, as well as in promoting the global shift to digital in organizations such as the G20, the Commonwealth Secretariat and the Olympics. Before joining OpenText, Alex managed various teams and programs at the Canadian International Development Agency, Foreign Affairs and International Trade Canada, Natural Resources Canada, and Library and Archives Canada.

Add new comment

Rules of Engagement

We look forward to hearing from you. Your ideas and feedback are central to the development of both the Open Government portal and the Government of Canada’s approach to Open Government.

While comments are moderated, the portal will not censor any comments except in a few specific cases, listed below. Accounts acting contrary to these rules may be temporarily or permanently disabled.

Comments and Interaction

Our team will read comments and participate in discussions when appropriate. Your comments and contributions must be relevant and respectful.

Our team will not engage in partisan or political issues or respond to questions that violate these Terms and Conditions.

Our team reserves the right to remove comments and contributions, and to block users based on the following criteria:

The comments or contributions:

  • include personal, protected or classified information of the Government of Canada or infringes upon intellectual property or proprietary rights
  • are contrary to the principles of the Canadian Charter of Rights and Freedoms, Constitution Act, 1982
  • are racist, hateful, sexist, homophobic or defamatory, or contain or refer to any obscenity or pornography
  • are threatening, violent, intimidating or harassing
  • are contrary to any federal, provincial or territorial laws of Canada
  • constitute impersonation, advertising or spam
  • encourage or incite any criminal activity
  • are written in a language other than English or French
  • otherwise violate this notice

Our team cannot commit to replying to every message or comment, but we look forward to continuing the conversation whenever possible. Please note that responses will be provided in the same language that was used in the original comment.

Our team will reply to comments in the official language in which they are posted. If we determine the response is a question of general public interest, we will respond in both official languages.


Submitted by Anonymous on February 15, 2018 - 2:44 PM

There is a lot that could be done to actually promote innovation in accessibility. I don't think that the focus of this was useful, nor was the process. I’d suggest the following could be done to both CKAN & Drupal 8: could be reviewed against: - WCAG 2.1 AA - ARIA 1.1 - ATAG 2.0 AA These are relatively new & there is more work needed to address this within WET, Drupal 8 & CKAN. That requires a focus not on the documents, but on the system. • Building accessible drag/drop pattern & applying it to Drupal 8 would be useful. An accessible pattern to manage complicated Drag/Drop functionality just doesn’t exist on the internet. Someone needs to build that pattern. It fits into a challenge with Block Layouts in Drupal 8 that may or may not be part of the site in the future. • Building automated testing framework using Deque’s open-source aXe-core library There is some room to do this, but the aXe-core library isn’t geared at evaluating documents. It would be useful to have a consistent framework for evaluating accessibility that could be added to a continuous integration framework. This library could also be expanded to better evaluate how well sites meet WCAG 2.1, ARIA 1.1 & ATAG 2.0. • Integrating Deque’s open-source aXe library into CKEditor to replace existing CKEditor Accessibility Plugin The current plugin provided by CKEditor is using a library that is depreciated. This needs to be updated so that content editors can get immediate updates when they add or update a page using the WYSIWYG. • Evaluate CKAN & Drupal 8 for voice navigation with: - Dragon Naturally Speaking - Amazon’s Alexa There are far more people who use voice control tools like Dragon Naturally Speaking than who use screen reader. Unfortunately, there has been very little testing of how to use voice controls. may be inaccessible for people who use these now. It is unclear how a service like this would be useful to someone using Amazon’s Alexa, but it also isn’t clear if any thought has gone into how it might be useful. There is a lot more that could be done. These are just some initial ideas.