Individual 64848's submission
CAN-ASC-2.4 – Wayfinding and Signage
Feedback items
Item id
1772135192513_943
Heading id
s0
What kind of suggestion are you making?
General comments on the overall standard or a section such as things that are missing
What should we change?
larity of Audience
The section speaks broadly to:
• Federal public sector
• Private sector
• NGOs
• Indigenous communities
• Society at large
Concern
It does not clearly distinguish between federally regulated entities and other jurisdictions. Rural municipalities may assume mandatory application when it is not yet regulatory.
Recommendation
Add a clear statement early in the section outlining:
• Who the standard applies to immediately
• Who may adopt voluntarily
• How provincial or municipal governments fit within the framework
Equity-Based vs Minimum Requirements
The section states that standards are designed to achieve “the highest levels of accessibility” rather than minimum technical requirements.
Concern
While this is commendable, it creates uncertainty for municipalities and small entities that typically design to minimum code compliance. There is no explanation of how entities should balance aspirational standards with financial constraints.
What should we change it to?
Recommendation
Clarify:
• Whether these standards are intended to exceed current building codes
• How jurisdictions should reconcile conflicts between this standard and existing provincial codes
Why should we change it?
For municipalities and rural entities, the strong equity framing can create uncertainty because:
• It emphasizes highest accessibility levels rather than minimum compliance
• It does not yet explain how cost, scalability, or phased implementation are addressed
• It does not clarify regulatory status for non-federal bodies
Heading text
1. Accessibility Standards Canada: About us
Heading number portion
1.
Item id
1772135337838_50
Heading id
s5
What kind of suggestion are you making?
General comments on the overall standard or a section such as things that are missing
What should we change?
Clarity of Purpose
Strength
The Introduction clearly states that everyone has the right to navigate indoor and outdoor environments effectively, safely, and efficiently. It recognizes that signage is often inaccessible and that consultation with persons with disabilities is essential.
What should we change it to?
The Introduction does not clearly differentiate between:
• New construction
• Major renovations
• Existing buildings
Why should we change it?
Because the Introduction shapes how the entire standard is understood, applied, and funded across different communities.
Heading text
6. Introduction
Heading number portion
6.
Item id
1772135458345_629
Heading id
s6.2
What kind of suggestion are you making?
General comments on the overall standard or a section such as things that are missing
What should we change?
Clarify in the Guiding Principles how affordability and scalability are evaluated in practice, particularly for rural and small municipalities with limited technical and financial capacity.
What should we change it to?
Specify how affordability and scalability will be applied in real-world implementation, especially for smaller and rural communities.
Why should we change it?
Because without explaining how affordability and scalability are applied, smaller and rural communities may struggle to interpret and implement the principles consistently.
Heading text
6.2 Guiding principles
Heading number portion
6.2
Item id
1772135565296_544
Heading id
s6
What kind of suggestion are you making?
General comments on the overall standard or a section such as things that are missing
What should we change?
Clarify in the Scope section how the standard applies to new construction versus existing facilities and include scalable compliance pathways for small and rural environments to reduce retrofit uncertainty.
What should we change it to?
Because without clear distinctions and scalable pathways, smaller and rural communities may face uncertainty, disproportionate retrofit costs, and inconsistent application of the standard.
Why should we change it?
Because unclear scope increases legal, financial, and operational risk for smaller jurisdictions trying to determine what is mandatory versus aspirational.
Heading text
7. Scope
Heading number portion
7.
Item id
1772135648586_510
Heading id
s7.2
What kind of suggestion are you making?
General comments on the overall standard or a section such as things that are missing
What should we change?
Clarify within the Inclusions section which elements are mandatory minimum requirements versus recommended best practices to reduce implementation ambiguity.
What should we change it to?
Clearly distinguish in the Inclusions section between mandatory “shall” requirements and advisory “should” best practices to improve implementation clarity.
Why should we change it?
Because without a clear distinction, municipalities may over-interpret advisory guidance as mandatory, increasing cost, liability risk, and implementation confusion.
Heading text
7.2 Inclusions
Heading number portion
7.2
Item id
1772135753249_85
Heading id
s7.3
What kind of suggestion are you making?
General comments on the overall standard or a section such as things that are missing
What should we change?
Revise the Exclusions section to clearly state whether excluded topics such as tactile maps and acoustics will be addressed in future mandatory standards, are covered under separate standards, or remain permanently outside scope, and explain how practitioners should manage these gaps in the interim.
What should we change it to?
Expand the Exclusions section to clearly explain whether excluded topics such as tactile maps, acoustics, and assistive listening systems will be addressed in future standards, are governed by existing standards, or are intentionally outside the scope, and provide practical interim guidance so practitioners understand how to manage these elements during planning and procurement.
Why should we change it?
Because when excluded items are not clearly addressed, municipalities and designers are left uncertain about whether those elements are deferred, optional, regulated elsewhere, or unintentionally omitted, which increases the risk of inconsistent application, procurement delays, redesign costs, and potential accessibility gaps or liability exposure.
Heading text
7.3 Exclusions
Heading number portion
7.3
Item id
1772135843543_358
Heading id
s9
What kind of suggestion are you making?
General comments on the overall standard or a section such as things that are missing
What should we change?
Add practical implementation guidance in the General Requirements for Lighting and Contrast that explains acceptable verification methods, realistic retrofit expectations, and scalable application for smaller and existing facilities.
What should we change it to?
Clarify in the General Requirements for Lighting and Contrast how compliance is to be measured in practice, provide simplified field verification methods, and distinguish expectations for new construction versus existing facilities to reduce implementation and retrofit uncertainty.
Why should we change it?
Because the General Requirements for Lighting and Contrast introduce highly technical thresholds and measurement methods that may exceed the practical capacity of smaller and rural municipalities, and without clearer implementation guidance they create uncertainty around compliance verification, retrofit obligations, lifecycle maintenance costs, and alignment with existing provincial building codes.
Heading text
10. General requirements for lighting and contrast
Heading number portion
10.
Item id
1772135928661_524
Heading id
s10.1
What kind of suggestion are you making?
General comments on the overall standard or a section such as things that are missing
What should we change?
Clarify the lighting requirements to include practical guidance on measurement methods, retrofit expectations, phased compliance, and scalable application for smaller or rural facilities, while aligning thresholds with existing building codes to reduce cost, technical burden, and compliance uncertainty.
What should we change it to?
Revise the lighting section to clearly outline acceptable measurement methods, define how requirements apply to new construction versus existing facilities, allow phased or risk-based compliance for retrofits, align thresholds with existing building codes where possible, and provide scalable options that reflect the financial and technical capacity of smaller and rural municipalities.
Why should we change it?
Because without clear measurement methods, phased retrofit guidance, and scalable application aligned with existing codes, smaller and rural municipalities may face disproportionate capital costs, technical verification challenges, inconsistent enforcement interpretations, and increased legal and operational risk when attempting to implement the lighting requirements.
Heading text
10.1 Lighting
Heading number portion
10.1
Item id
1772136025489_917
Heading id
s10.1.1
What kind of suggestion are you making?
General comments on the overall standard or a section such as things that are missing
What should we change?
Revise the Application subsection to clearly define how lighting requirements apply across different building types, distinguish between new construction and existing facilities, clarify expectations for outdoor versus indoor environments, and provide proportional compliance options for low-traffic, small, or rural settings.
What should we change it to?
Revise the Application subsection to specify to what types of facilities, projects, and environments the lighting requirements apply, including distinctions between federally regulated buildings, new construction, major renovations, existing facilities, and low-complexity or rural settings.
Why should we change it?
Because without clear and proportional application guidance, municipalities may misinterpret uniform lighting thresholds as universally mandatory, leading to unnecessary retrofits, budget strain, inconsistent enforcement, and avoidable delays in delivering practical accessibility improvements.
Failsafe check: Passed
Heading text
10.1.1 Application
Heading number portion
10.1.1
Submission ID
64848
Submitted by