Dashboard Accessibility Statement
Dashboard Accessibility Statement What are we doing? Accessibility features Accessibility barriers Roadmap How are we doing? Contact us PowerBI ArcGIS PowerBI ArcGIS This statement applies to the City of Hamilton’s Dashboards built on PowerBI and ArcGIS. We want everyone who visits the City of Hamilton’s website to feel welcome and find the experience rewarding. The City of Hamilton is committed to the goals set out in the Accessibility for Ontarians with Disabilities Act (AODA), 2005 and its regulations. The Integrated Accessibility Standard Regulation (IASR) calls for all new websites for organizations with more than 50 employees to comply with the Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. These guidelines explain how to make web content more accessible for people with disabilities, and user friendly for everyone. At the City of Hamilton we are striving to design and test to comply with WCAG 2.1 Level AA. Where possible we will align with WCAG 2.2 to ensure forward compatibility. To help us make the City of Hamilton’s dashboards a positive place for everyone and to comply with the AODA/IASR, we’ve been conducting automatic, manual, and end-user testing to help us update our dashboards to ensure WCAG compliance. Our Dashboards make use of industry-standard techniques and best practices to provide the highest possible level of web site accessibility for our users. These dashboards are built on the PowerBI platform: The PowerBI platform provides these accessibility features: These dashboards are built on the ArcGIS platform: The ArcGIS platform provides these accessibility features: Due to conditions beyond our control, there are s ome instances where we are unable to provide information in an accessible format. For example, some HSR maps, RSS feeds, or content we don’t have control over. We will introduce accessible solutions as they become available. We are aware of the accessibility features and barriers identified above. We will continue to work with our vendors to address known accessibility barriers and implement available fixes and enhancements to our data visualization dashboards as they become available. This accessibility statement will be reviewed and updated annually, or more frequently as needed. We’ve worked hard on the City of Hamilton Dashboards and believe, outside of the listed known errors, that we’ve achieved our goal of WCAG 2.0 Level AA. We are continuing to work on the accessibility of our data visualization dashboards and will strive to meet WCAG 2.1 Level AA and WCAG 2.2 where possible. We monitor the Dashboards regularly to maintain accessibility and usability, but if you find any problems, please let us know. We are committed to the ongoing process of making our city, services, and digital environments welcoming and more accessible. Please let us know what you liked about using the City of Hamilton’s Dashboards, or if you had trouble with any part of it. Accessibility Feedback/Compliant Form
Datasets available for download
This dataset has no data
Additional Info
| Field | Value |
|---|---|
| Last Updated | October 7, 2026, 07:20 (UTC) |
| Created | October 7, 2026, 07:20 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
|
|
Title
Title for the Dataset.
|
Dashboard Accessibility Statement |
|
Description
A description of the dataset.
|
Dashboard Accessibility Statement What are we doing? Accessibility features Accessibility barriers Roadmap How are we doing? Contact us PowerBI ArcGIS PowerBI ArcGIS This statement applies to the City of Hamilton’s Dashboards built on PowerBI and ArcGIS. We want everyone who visits the City of Hamilton’s website to feel welcome and find the experience rewarding. The City of Hamilton is committed to the goals set out in the Accessibility for Ontarians with Disabilities Act (AODA), 2005 and its regulations. The Integrated Accessibility Standard Regulation (IASR) calls for all new websites for organizations with more than 50 employees to comply with the Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. These guidelines explain how to make web content more accessible for people with disabilities, and user friendly for everyone. At the City of Hamilton we are striving to design and test to comply with WCAG 2.1 Level AA. Where possible we will align with WCAG 2.2 to ensure forward compatibility. To help us make the City of Hamilton’s dashboards a positive place for everyone and to comply with the AODA/IASR, we’ve been conducting automatic, manual, and end-user testing to help us update our dashboards to ensure WCAG compliance. Our Dashboards make use of industry-standard techniques and best practices to provide the highest possible level of web site accessibility for our users. These dashboards are built on the PowerBI platform: The PowerBI platform provides these accessibility features: These dashboards are built on the ArcGIS platform: The ArcGIS platform provides these accessibility features: Due to conditions beyond our control, there are s ome instances where we are unable to provide information in an accessible format. For example, some HSR maps, RSS feeds, or content we don’t have control over. We will introduce accessible solutions as they become available. We are aware of the accessibility features and barriers identified above. We will continue to work with our vendors to address known accessibility barriers and implement available fixes and enhancements to our data visualization dashboards as they become available. This accessibility statement will be reviewed and updated annually, or more frequently as needed. We’ve worked hard on the City of Hamilton Dashboards and believe, outside of the listed known errors, that we’ve achieved our goal of WCAG 2.0 Level AA. We are continuing to work on the accessibility of our data visualization dashboards and will strive to meet WCAG 2.1 Level AA and WCAG 2.2 where possible. We monitor the Dashboards regularly to maintain accessibility and usability, but if you find any problems, please let us know. We are committed to the ongoing process of making our city, services, and digital environments welcoming and more accessible. Please let us know what you liked about using the City of Hamilton’s Dashboards, or if you had trouble with any part of it. Accessibility Feedback/Compliant Form |
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
24.52 |
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
|
|
Published Date
Published date of the dataset.
|
2026-10-06 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Access category
Type of access granted for the dataset (open, closed, service, etc).
|
public |
|
License
License used to access the dataset.
|
License not specified |
|
Limits on use
Limits on use of data.
|
|
|
Location
Location of the dataset.
|
https://data-SpatialSolutions.opendata.arcgis.com/datasets/SpatialSolutions::dashboard-accessibility-statement |
|
Data Service
Data service for accessing a dataset.
|
|
|
Owner
Owner of the dataset.
|
OpenHamilton |
|
Contact Point
Who to contact regarding access?
|
City of Hamilton |
|
Contact Point Email
The email to contact regarding access?
|
[email protected] |
|
Publisher
Publisher of the dataset.
|
City of Hamilton |
|
Publisher Email
Email of the publisher.
|
|
|
Author
Author of the dataset.
|
OpenHamilton |
|
Author Email
Email of the author.
|
|
|
Accessed At
Date the data and metadata was accessed.
|
2026-10-06 |
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
bf2b9752e8a04bb9b07c9336dc89220b |
|
Language
Language(s) of the dataset
|
English |
|
Link to dataset description
A URL to an external document describing the dataset.
|
https://data-SpatialSolutions.opendata.arcgis.com/datasets/SpatialSolutions::dashboard-accessibility-statement |
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
City of Hamilton |
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
|
|
Number of data columns
If tabular dataset, total number of unique columns.
|
|
|
Number of data cells
If tabular dataset, total number of cells with data.
|
|
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments