47
edits
Changes
→Publishing Information Online
<div class="mw-collapsible mw-collapsed" style="border: 1px solid #ccc; background-color: #f9f9f9; padding: 1em; width: 90%;">
<div class="mw-collapsible mw-collapsed" style="border: 1px solid #ccc; background-color: #f9f9f9; padding: 1em; width: 90%;">
'''Question'''
'''Q4: Is there guidance on accessible formats?'''
<div class="mw-collapsible-content">
<div class="mw-collapsible-content">
All online government content must meet official language and accessibility standards. As set out in the Standard on Web Accessibility, all government web pages must meet all five [[/www.w3.org/TR/WCAG20/#conformance-reqs|Web Content Accessibility Guidelines (WCAG) 2.0 conformance requirements]].
In particular, section 6.1.1 states that an accessible document needs to be a file type where “Sufficient Techniques specific to each technology (that is relied upon) are used where applicable”. Since WCAG only has Technology Specific Techniques for .pdf, Plain Text, and .HTML, then an accessible document needs to be in one of those file types, and follow the technology specific techniques.
For open information resources there needs to be at least one version of the document that is compliant with the Standard on Web Accessibility, but other non-accessible versions can also be added. For example, it would be acceptable for institutions to publish an accessible .pdf of a document and also add a non-accessible Microsoft Word version.
</div>
</div>
</div>
</div>
<div class="mw-collapsible mw-collapsed" style="border: 1px solid #ccc; background-color: #f9f9f9; padding: 1em; width: 90%;">
<div class="mw-collapsible mw-collapsed" style="border: 1px solid #ccc; background-color: #f9f9f9; padding: 1em; width: 90%;">
'''Question'''
'''Q5: When proactively publishing to the Open Government portal, is the Chief Information Officer (CIO) approval of metadata elements required?'''
<div class="mw-collapsible-content">
<div class="mw-collapsible-content">
Yes. Approval from your Chief Information Officer (CIO), or delegate, is required before publishing your briefing material metadata on [[/open.canada.ca/en/proactive-disclosure|open.canada.ca]]. To support institutions and CIOs in managing the risks related to the release of data and information assets, TBS has developed a ‘Open Government Portal Publication Checklist’ that consolidates common release exceptions. It is the responsibility of CIOs to ensure that an answer of ‘True’ can be given for all criteria before any series of data and information resources are published and thereby released under the [[/open.canada.ca/en/open-government-licence-canada|Open Government Licence]].
</div>
</div>
</div>
</div>
<div class="mw-collapsible mw-collapsed" style="border: 1px solid #ccc; background-color: #f9f9f9; padding: 1em; width: 90%;">
<div class="mw-collapsible mw-collapsed" style="border: 1px solid #ccc; background-color: #f9f9f9; padding: 1em; width: 90%;">
'''Question'''
'''Q6: If an institution has its own approval processes, is CIO approval required when proactively publishing to the Open Government Portal?'''
<div class="mw-collapsible-content">
<div class="mw-collapsible-content">
It depends. CIO approval is required when publishing information to [[/open.canada.ca/en/proactive-disclosure|open.canada.ca]] for which there is no template available as “Open Information” such as a report tabled in Parliament. However, CIO approval is not required when publishing information to open.canada.ca for which there is a template available such as for travel expenses, hospitality expenses, and reclassification of positions. For more information on CIO approvals, please refer to our [[/open.canada.ca/ckan/en/dataset/9eaa6d0e-4b8c-5241-acf7-c6885294b8c1|Open Government Guidebook.]]
</div>
</div>
</div>
</div>