• Skip to main content
  • Skip to "About government"

Language switcher

  • Françaisfr
Government of Canada / Government of Canada

Search Accessbility Standards Canada


Use the Left and Right arrow keys to navigate between the top level menu items. Press the ENTER key or double tap the SPACEBAR to select a menu item. To navigate through a sub menu, Press the SPACEBAR or the Down arrow key. Use the Up and Down arrow keys to navigate through submenu items. Press the Enter or SPACEBAR to select a submenu item. Press the ESCAPE key to close the submenu and return to the top level.

Main navigation

  • Home
    • About us
    • Accessibility Plan 2025
    • Get involved
    • Reports and publications
    • Transparency
    • Consultations
    • Organizational structure
  • Standards and technical guides
    • Standards and technical guides database
    • Standards under public review
    • Technical committees
    • Work program
  • Research and funding
    • Funded research project database
    • Advancing Accessibility Standards Research
  • Centre of Expertise
  • Contact us
  • Login

Mobile Menu

  • Home
    • About us
    • Accessibility Plan 2025
    • Get involved
    • Reports and publications
    • Transparency
    • Consultations
    • Organizational structure
  • Standards and technical guides
    • Standards and technical guides database
    • Standards under public review
    • Technical committees
    • Work program
  • Research and funding
    • Funded research project database
    • Advancing Accessibility Standards Research
  • Centre of Expertise
  • Contact us
  • Login

You are here

  1. Canada.ca
  2. Accessibility Standards Canada
  3. Search results

Search results


Displaying 651 - 660 of 808

Individual 65654's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782144092041_213
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?
Mandatory and advisory wording is sometimes unclear or mixed. The draft defines “shall” as mandatory and “should” as advisory, but some clauses combine mandatory and advisory ideas in ways that make the level of compliance required uncertain. Examples include: Clause 11.4.5.2 says virtual engagement organizers “shall” identify accommodation requirements and use compliant web platforms, but Clause 11.4.5.3 says the organizer “should” complete a run-through and user testing to determine whether accessibility needs have been met. Clause 13.5 says the remaining bid period “should” be adjusted after a significant change, but then says an amendment “must” be issued. Clause 15.3.2 says people with disabilities “should” be included as key training delivery members and “shall” be compensated, leaving unclear whether inclusion is optional but compensation is mandatory only if they are included.
What should we change it to?
Separate mandatory requirements from recommendations. Use “shall” only for required compliance items. Use “should” for recommendations. If a recommended practice becomes necessary for accessibility or procurement fairness in certain circumstances, define those circumstances and use “shall.”
Why should we change it?
This makes the standard easier to audit and avoids disagreement about whether a clause is required or recommended.
Heading text
1. Accessibility Standards Canada: About us
Heading number portion
1.
Item id
1782144134504_990
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?
Several clauses require involvement of people with disabilities but do not consistently mention consent, compensation, and confidentiality. Examples include: Clause 12.4.3 includes people with disabilities or lived experience on evaluation panels; Clause 14.2 refers to inspection for barriers by persons with disabilities before delivery; and Clause 15.3.1 requires consultation with people with disabilities in training development. These are important requirements, but they should include guidelines around recruitment, compensation, confidentiality etc.
What should we change it to?
Add a general principle, near the introduction or general requirements, stating that involvement of people with disabilities must be meaningful, accessible, voluntary, appropriately compensated where they provide expertise, and managed with federal and/or provincial/territorial privacy legislation compliance guidelines.
Why should we change it?
This strengthens the “nothing without us” approach while preventing tokenism, privacy breaches, or procurement fairness concerns.
Heading text
1. Accessibility Standards Canada: About us
Heading number portion
1.
Item id
1782144167671_788
Heading id
s0
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 8: “American Sign language (ASL)” and page 9: “indigenous communities / indigenous peoples.”
What should we change it to?
Change to “American Sign Language (ASL)” and “Indigenous communities / Indigenous Peoples.”
Why should we change it?
These are proper names and should be capitalized consistently according to https://our-languages.canada.ca/en/writing-tips-plus/capitalization-indigenous-person-people.
Heading text
1. Accessibility Standards Canada: About us
Heading number portion
1.
Item id
1782144197883_226
Heading id
s0
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 10: “Standard Council of Canada’s Requirements and Guidance for Standards Development Organizations.”
What should we change it to?
Change to “Standards Council of Canada’s Requirements and Guidance for Standards Development Organizations.”
Why should we change it?
The organization name is “Standards Council of Canada.”
Heading text
1. Accessibility Standards Canada: About us
Heading number portion
1.
Item id
1782144234319_757
Heading id
s0
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 10: “These voluntary standards are intended for any organization or person seeking advice apply to federally regulated entities...”.
What should we change it to?
Change to: “These voluntary standards are intended for any organization or person seeking guidance. They apply to federally regulated entities and can be recommended to the Minister responsible for the Accessible Canada Act for adoption into regulation.”
Why should we change it?
The current sentence is grammatically unclear.
Heading text
1. Accessibility Standards Canada: About us
Heading number portion
1.
Item id
1782144272538_738
Heading id
3.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 14: “his majesty the king in right of Canada...” and “accessibility standards Canada...”
What should we change it to?
Change to “His Majesty the King in right of Canada...” and “Accessibility Standards Canada...”
Why should we change it?
Proper names should be capitalized consistently in a legal notice.
Heading text
3.3 Disclaimer and exclusion of liability
Heading number portion
3.3
Item id
1782144317019_736
Heading id
3.6
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?
Page 16: license-to-comments clause is lengthy and difficult to understand.
What should we change it to?
Add a plain-language note immediately after the clause, such as: “In plain language: by submitting comments, you allow Accessibility Standards Canada and the Government of Canada to use and adapt your comments for the standard and related non-commercial purposes.”
Why should we change it?
The legal wording may need to stay in place, but a plain language explanation improves accessibility and aligns with the standard’s plain language goals.
Heading text
3.6 Licence to comments
Heading number portion
3.6
Item id
1782144345201_906
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?
Pages 20-21: the user groups are helpful, but the role of people with disabilities is mostly listed as “end users.”
What should we change it to?
Add a sentence after the user-group list: “People with disabilities may participate as end users, business owners, bidders, evaluators, subject matter experts, employees, and members of supplier teams.”
Why should we change it?
This avoids narrowing people with disabilities to the role of end user and better reflects the principle that people with disabilities are involved throughout procurement.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782144374636_51
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?
Page 22: “Above all and in the spirit of this Standard, people with disabilities are involved in procurement.”
What should we change it to?
Change to: “Above all, and in the spirit of this Standard, people with disabilities must be meaningfully involved throughout the procurement life cycle, in ways that are accessible, respectful, voluntary, and appropriately supported.”
Why should we change it?
The current wording is vague. The revised wording is more actionable and aligns with the rest of the standard.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782144414486_203
Heading id
9.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 27: “Person” uses “his or her capacity.”
What should we change it to?
Change to “their capacity.”
Why should we change it?
Gender-neutral language is more inclusive and consistent with accessibility and equity principles.
Heading text
9.1 Definitions
Heading number portion
9.1
Item id
1782144447436_968
Heading id
9.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 28: “Procurement professional — ... anyone responsible for facilitating the procurement function within an organization and has the responsibility to enter into a contract...”
What should we change it to?
Change to: “Procurement professional — a person responsible for facilitating procurement within an organization, including a person with authority to enter into a contract or contractual agreement to purchase goods, services, facilities, or construction on behalf of a business owner.”
Why should we change it?
The current sentence is awkward and unclear. The suggested wording is clearer and more reflective of the individual’s role and capacity.
Heading text
9.1 Definitions
Heading number portion
9.1
Item id
1782144474948_190
Heading id
10.1.3.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 32: “integrate accessibility requirements into a procurement instead of excluding it.”
What should we change it to?
Change to: “integrate accessibility requirements into a procurement process instead of excluding them.”
Why should we change it?
The pronoun should refer to “requirements.”
Heading text
10.1.3.1 General
Heading number portion
10.1.3.1
Item id
1782144502577_896
Heading id
11.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 36: “CAN-ASC-EN 301 549:20204.”
What should we change it to?
Change to “CAN/ASC - EN 301 549:2024.”
Why should we change it?
The year has an extra digit.
Heading text
11.3 Websites and digital applications
Heading number portion
11.3
Item id
1782144545313_486
Heading id
11.4.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?
Page 37: Note 2 says a hybrid protocol “will be offered” when a person cannot attend in person. Note 2 says a hybrid protocol “will be offered.” Because notes are generally explanatory, “will” may look like a requirement even though it appears in a note. Move this requirement into the body of the clause and use “shall,” or revise the note to advisory language using “should.”
What should we change it to?
Move this out of a note and make it a requirement: “Where an in-person engagement creates a barrier for a participant, organizers shall offer an accessible virtual or hybrid option, or an equivalent accessible method of participation.”
Why should we change it?
Notes are not normally requirements. This accommodation pathway is important enough to be in the full text.
Heading text
11.4.1 General
Heading number portion
11.4.1
Item id
1782144575504_771
Heading id
11.4.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 39: “All required documents are provided at least two (2) business days before the engagement begins.”
What should we change it to?
Change to: “All required documents shall be provided in accessible formats as early as possible, and at least five (5) business days before the engagement begins unless a participant requests otherwise or a shorter timeline is unavoidable.”
Why should we change it?
Two business days may be insufficient for some participants and for arranging alternate formats, interpreters, or assistive-technology preparation.
Heading text
11.4.3 Identifying accommodation needs
Heading number portion
11.4.3
Item id
1782144659738_984
Heading id
11.4.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Page 40: Note 2 suggests accommodation feedback should be shared with all participants. Note 2 says feedback should be shared “with all participants.” If the feedback concerns an accommodation that could identify a participant, sharing it broadly may compromise privacy. Suggested wording should clarify that only aggregated or anonymized findings are shared.
What should we change it to?
Change to: “Feedback on accommodation effectiveness should be reviewed in aggregate and anonymized form and used for continuous improvement. It should not identify participants or disclose accommodation details without consent.”
Why should we change it?
Sharing accommodation feedback with all participants could unintentionally disclose disability-related or medical information.
Heading text
11.4.3 Identifying accommodation needs
Heading number portion
11.4.3
Item id
1782144693427_156
Heading id
11.4.4.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Page 41: Clause 11.4.4.3 lists “Exterior circulation” and “Vehicular access” only.
What should we change it to?
Add “accessible routes from public transit, passenger drop-off, parking, and building entrances” if these are covered by the intended built-environment standard.
Why should we change it?
Access to an in-person event often begins before the building entrance; the route from transit, parking, or drop-off can create barriers.
Heading text
11.4.4.3 Access to facilities
Heading number portion
11.4.4.3
Item id
1782144738109_854
Heading id
11.4.4.6
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Page 42: emergency egress clause requires a list of participants with evacuation needs be provided to the facility manager. Clause 11.4.4.6 requires a list of participants with individual evacuation needs to be provided to the facility manager. This may be necessary for safety, but the clause should say the information must be limited to what is necessary, shared only with those who need it for emergency planning, and handled confidentially.
What should we change it to?
Change to: “With consent, organizers shall identify participants who request evacuation assistance and share only the minimum necessary information with designated emergency personnel or the facility manager.”
Why should we change it?
The current wording creates privacy and consent concerns. Emergency planning should protect confidentiality while still supporting safety.
Heading text
11.4.4.6 Facility emergency egress
Heading number portion
11.4.4.6
Item id
1782144780956_388
Heading id
12.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Page 45: Clause 12.1.1 says “standard competitive procurement rules may be set aside” for individual accommodation procurement. Clause 12.1.1 says standard competitive procurement rules “may be set aside” for individual accommodation procurement. The intent is important, but the phrase could be interpreted too broadly. It should be tied to applicable legal, policy, and delegated-authority requirements and limited to what is necessary to provide timely, effective accommodation.
What should we change it to?
Change to: “Where procurement is conducted to meet the specific accommodation needs of a person with a disability, non-competitive or expedited procurement may be considered where permitted by applicable laws, policies, trade agreements, and delegated authorities, and where the rationale is documented.”
Why should we change it?
The current wording could be read as a broad authority to bypass procurement rules. The revised wording preserves flexibility while recognizing legal and policy limits.
Heading text
12.1.1 Exception - Individual accommodation procurement
Heading number portion
12.1.1
Item id
1782144831974_577
Heading id
12.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Page 46: third-party testing clause says clients shall “include subcontracting requirements for this testing.”
What should we change it to?
Change to: “state in solicitation documents who is responsible for arranging and paying for third-party accessibility testing, the arms- length parameters of the testing agency or individual tester (avoiding perceived or real conflict of interest) , and how testing results will be used in evaluation or acceptance.”
Why should we change it?
Third-party testing may be arranged by the client or supplier. The key issue is objectivity, responsibility, cost, and how results affect evaluation.
Heading text
12.2 Identifying requirements for testing
Heading number portion
12.2
Item id
1782144874188_326
Heading id
13.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 49: solicitation timing mentions the time required to obtain accessible formats, prepare a bid, and submit a response.
What should we change it to?
Add: “The solicitation period should also account for time required to arrange communication supports, attend accessible site visits or bidders conferences, and review accessibility-related amendments.”
Why should we change it?
This better reflects the practical time needed by bidders with disabilities or bidders preparing accessible responses.
Heading text
13.1 Determining the solicitation period
Heading number portion
13.1
Item id
1782144931748_434
Heading id
13.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Pages 49-50: Clause 13.1.1 requires bidders to itemize costs to accommodate themselves or employees during contract performance and excludes these costs from financial evaluation. Bidders are asked to itemize costs expected to accommodate themselves or employees; those costs are to be separated from the financial proposal; the costs are excluded from financial evaluation; and they are validated before award. This could unintentionally require disclosure of disability-related or employee-specific information unless the clause clearly limits what information is collected and how it is assessed.
What should we change it to?
Recommend legal/procurement policy review. Suggested rewrite: “Solicitation documents shall state how accessibility-related costs will be treated. Costs required to meet accessibility deliverables shall be included in the evaluated bid price. Accommodation costs required for bidder participation in the procurement process shall be addressed by the procuring organization where applicable. Any separate treatment of contractor workforce accommodation costs must be permitted by applicable law, policy, and trade obligations and must be clearly described in the solicitation.” Perhaps these costs should be omitted and only provided if the bid is accepted, to ensure that they truly are not used as grounds for accepting or dismissing a particular bid.
Why should we change it?
The current wording has good equity intent but may create pricing, privacy, fairness, and trade-agreement issues if bidders are asked to disclose employee accommodation costs.
Heading text
13.1.1 Accessibility cost treatment in bidding
Heading number portion
13.1.1
Item id
1782144981094_900
Heading id
13.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Page 50: site visits require the organization to “work to provide accessible solutions.”
What should we change it to?
Change to: “When a required site visit is not accessible, clients and procurement professionals shall provide accommodations or an equivalent accessible method of obtaining the same information, without disadvantage to the bidder.”
Why should we change it?
“Work to provide” is too weak for a mandatory accessibility standard. Bidders should not be disadvantaged because a site visit is inaccessible.
Heading text
13.3 Requiring site visits
Heading number portion
13.3
Item id
1782145037034_591
Heading id
14.4
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Page 54: outcome measurement says only that organizations shall identify a process. Examples of measures could include: percentage of procurements with accessibility criteria; percentage with approved justifications for excluding accessibility; number and type of accessibility barriers reported during contract performance; resolution time for reported barriers; number of staff trained; and bidder or end-user feedback on procurement accessibility.
What should we change it to?
Add examples of minimum measures: percentage of procurements with accessibility criteria; percentage with approved justifications for excluding accessibility; number and type of accessibility issues found during delivery; time to remediate; end-user feedback; training completion; and contract outcomes against accessibility requirements.
Why should we change it?
The current clause is too broad. Minimum reporting elements would make the requirement measurable and useful for continuous improvement.
Heading text
14.4 Measuring procurement outcomes
Heading number portion
14.4
Item id
1782145066502_402
Heading id
15.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 56: “communicate with people with various disabilities.”
What should we change it to?
Change to: “communicate with people with different disabilities, communication preferences, and access needs.”
Why should we change it?
This wording is more person-centred and recognizes that access needs vary.
Heading text
15.2 Contents of training
Heading number portion
15.2
Item id
1782145090470_417
Heading id
15.3.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Page 56: “Training shall be developed in consultation with people with disabilities and they shall be appropriately compensated...”
What should we change it to?
Change to: “Training shall be developed in consultation with people with disabilities, who shall be appropriately compensated for their time and expertise.”
Why should we change it?
This improves grammar.
Heading text
15.3.1 Development
Heading number portion
15.3.1
Item id
1782145136684_948
Heading id
15.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Page 56: Clause 15.3.2 says “People with disabilities should be included as key members of the team delivering the training and shall be appropriately compensated...” If inclusion on the training team is optional, the compensation requirement only activates when people with disabilities are included. If the standard intends “nothing without us” to apply to training delivery, inclusion should be a “shall” requirement.
What should we change it to?
Change to either: “People with disabilities shall be included as key members of the team delivering the training and shall be appropriately compensated for their time and expertise,” or “Where people with disabilities are included as key members of the team delivering the training, they shall be appropriately compensated for their time and expertise.”
Why should we change it?
The current sentence mixes a recommendation with a requirement. The standard should clarify whether inclusion is mandatory or recommended, while compensation should remain mandatory whenever people with disabilities are asked to contribute expertise.
Heading text
15.3.2 Delivery method
Heading number portion
15.3.2
Item id
1782145166429_653
Heading id
15.3.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Page 57: training timing requires training at least every 2 years and whenever complaints or standards updates occur.
What should we change it to?
Add: “Organizations shall keep training records and evaluate whether training improves procurement practice.”
Why should we change it?
Without record-keeping and effectiveness checks, training completion may not translate into better accessibility outcomes.
Heading text
15.3.3 Timing
Heading number portion
15.3.3
Item id
1782145400922_417
Heading id
s15
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?
Page 59: include practical Government of Canada procurement resources as online resources.
What should we change it to?
Add references to the Government of Canada accessibility criteria justification form and accessible procurement guidance/checklists (https://www.canada.ca/content/dam/pspc-spac/documents/services/temporary-help/justification-eng.docx), where permitted by ASC bibliography style.
Why should we change it?
These resources directly support implementation of the standard, especially the mandatory justification and planning requirements.
Heading text
16. Annex A: Bibliography (Informative)
Heading number portion
16.
Submission ID
65654
Submitted by
Romy@horizoned.ca
Submitted on
Mon, 06/22/2026 - 12:23
Consent to contact
Yes

Individual 65655's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782144160162_577
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?
DWCC recommends strengthening this section to clarify that Accessibility Standards Canada’s commitment to “nothing without us” must include meaningful decision-making authority for people with disabilities, not only participation, consultation, or review. The section should also more clearly recognize communication access as a core accessibility issue for Deaf, DeafBlind, and Hard-of-Hearing people. For DDBHH people, accessibility includes ASL, LSQ, Indigenous Sign Languages, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible customer support.
What should we change it to?
Add language confirming that “nothing without us” includes disability-led and Deaf-led participation in the design, development, implementation, evaluation, and revision of accessibility standards. Add language recognizing that communication access is a core accessibility requirement. This should include ASL, LSQ, Indigenous Sign Languages, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, and accessible emergency communication. Add language confirming that technical committees and standards-development processes should include relevant lived experience and subject-matter expertise for the barriers being addressed. General disability representation is important, but it is not a substitute for DDBHH, ASL, LSQ, DeafBlind, telecom, digital accessibility, and emergency communication expertise where those issues are affected.
Why should we change it?
This change is needed because “nothing without us” must lead to real influence over accessibility outcomes. Participation alone is not enough if people with disabilities are not involved in decisions that define requirements, evaluate solutions, and prevent barriers before they are built into systems, services, and procurement processes. For Deaf, DeafBlind, and Hard-of-Hearing people, many barriers are communication barriers. If communication access is not recognized from the beginning, public systems may continue to purchase or design inaccessible services, meetings, websites, emergency communications, customer support systems, and digital platforms. This change would better align the section with the Accessible Canada Act’s purpose of identifying, removing, and preventing barriers, and with ASC’s stated goal of achieving the highest level of accessibility.
Heading text
1. Accessibility Standards Canada: About us
Heading number portion
1.
Item id
1782144316679_186
Heading id
s1
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?
Section 2 is currently reserved for publication. DWCC recommends that the final Standards Council of Canada Statement include language confirming that accessibility standards must support the Accessible Canada Act’s purpose of identifying, removing, and preventing barriers, and that standards-development processes must meaningfully include persons with disabilities and relevant lived experience.
What should we change it to?
DWCC recommends that the final statement confirm that standards should be developed, reviewed, published, and implemented in accessible ways. This should include accessible digital formats, plain language, ASL and LSQ summaries where applicable, and communication access for Deaf, DeafBlind, and Hard-of-Hearing people. The statement should also recognize that relevant lived experience and subject-matter expertise are essential to credible accessibility standards, especially where standards affect communication access, digital services, procurement, emergency communication, and public-facing services.
Why should we change it?
Because this section will become part of the final standard, it should reinforce the same accessibility principles that guide the Accessible Canada Act and Accessibility Standards Canada. A standards statement should not be only administrative. It should help ensure that the final standard is understood as a barrier-prevention tool. For DDBHH people, accessible publication and communication access are necessary for meaningful participation in standards development, review, implementation, and future revision.
Heading text
2. Standards Council of Canada Statement
Heading number portion
2.
Item id
1782144489764_932
Heading id
s2
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?
DWCC recommends clarifying that the legal notice should not be interpreted in a way that limits accessibility, accessible formats, communication access, or meaningful participation by persons with disabilities during the public review, standards-development, implementation, or revision process.
What should we change it to?
Add language confirming that nothing in the legal notice limits Accessibility Standards Canada’s commitment to accessible public review, accessible formats, plain language, ASL and LSQ access where applicable, communication supports, and meaningful participation by persons with disabilities. DWCC also recommends that any instructions about authorized use, comments, intellectual property, or public review be provided in accessible formats and plain language, so that Deaf, DeafBlind, Hard-of-Hearing, and other disabled participants can understand their rights and responsibilities when submitting feedback.
Why should we change it?
Legal notices can be difficult to understand and may discourage participation if they are not clear and accessible. Because this draft standard is intended to support accessibility and public participation, the legal notice should be understandable to people with disabilities and should not create confusion about whether they can review, quote, comment on, or submit feedback about the draft. This change would support meaningful participation, especially for DDBHH people who may rely on plain language, ASL, LSQ, captioning, relay-compatible communication, or other communication supports to participate in standards review.
Heading text
3. Accessibility Standards Canada legal notice for standards
Heading number portion
3.
Item id
1782144673294_778
Heading id
3.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?
DWCC recommends strengthening this section to clarify that a consensus-based standards-development process should include meaningful participation by persons with disabilities with relevant lived experience and subject-matter expertise. Where Accessibility Standards Canada does not independently test, evaluate, or verify the content of standards, the process should include stronger safeguards to ensure that accessibility requirements are validated by affected users.
What should we change it to?
Add language confirming that consensus should not replace accessibility validation by people directly affected by the barriers addressed in the standard. Add language stating that, where a standard affects Deaf, DeafBlind, and Hard-of-Hearing people, the standards-development and review process should include relevant DDBHH users, ASL users, LSQ users, DeafBlind users, and accessibility subject-matter experts. Add language confirming that draft standards should be reviewed for practical usability, not only technical wording, so that requirements can prevent real-world accessibility barriers in procurement, digital services, communication access, emergency communication, and public-facing services.
Why should we change it?
Consensus-based standards are important, but consensus alone does not guarantee accessibility. If affected users are not meaningfully involved in testing, reviewing, and validating requirements, standards may unintentionally preserve barriers or overlook communication-access needs. For DDBHH people, accessibility barriers often appear in practical use: meetings without effective interpretation, websites without accessible video or captioning, customer support that relies on phone calls, emergency information without visual or sign-language access, and digital platforms that do not support relay-compatible communication. This change would strengthen the fairness and credibility of the standards-development process and better support the Accessible Canada Act’s purpose of identifying, removing, and preventing barriers.
Heading text
3.1 General
Heading number portion
3.1
Item id
1782144809573_728
Heading id
3.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?
DWCC recommends strengthening this section so that users are clearly informed when revisions, updated drafts, alternate formats, ASL summaries, LSQ summaries, plain language versions, or other accessible versions are available.
What should we change it to?
Add language stating that Accessibility Standards Canada should provide clear version control information for draft standards, including the date of the draft, the date of any revision, and a plain language explanation of significant changes. Add language stating that when revisions are issued, revised accessible formats should also be made available, including accessible digital formats, plain language summaries, and ASL and LSQ summaries where applicable.
Why should we change it?
People with disabilities need to know whether they are reviewing the current version of a draft standard. This is especially important where multiple formats are used. If the standard is revised but accessible versions are not updated at the same time, Deaf, DeafBlind, Hard-of-Hearing, blind, low-vision, and other disabled reviewers may not have equal access to the same information. Clear version control and accessible revision notices support meaningful participation in public review and reduce the risk that people comment on outdated or incomplete versions of the draft.
Heading text
3.2 Understanding this edition of the draft standard
Heading number portion
3.2
Item id
1782144955332_170
Heading id
3.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?
DWCC recommends clarifying that the disclaimer and exclusion of liability do not reduce the purpose, importance, or expected use of the standard as a barrier-prevention tool. The section should also clarify that organizations using the standard remain responsible for complying with applicable accessibility, human rights, procurement, and anti-discrimination obligations.
What should we change it to?
Add language stating that nothing in this disclaimer should be interpreted as reducing the importance of accessible procurement, communication access, or the prevention of accessibility barriers. Add language confirming that users of the standard remain responsible for meeting applicable legal obligations, including obligations related to accessibility, human rights, procurement, employment, service delivery, and the duty to accommodate. Add language encouraging organizations to use the standard proactively to identify, remove, and prevent barriers, even though the standard itself is voluntary unless adopted into regulation or incorporated into another legal, policy, or contractual requirement.
Why should we change it?
The disclaimer is important, but it should not create confusion about the role of the standard. Accessible procurement is a barrier-prevention mechanism. If organizations read the disclaimer as weakening the standard or making accessibility optional, they may continue to purchase inaccessible goods, services, platforms, customer support systems, emergency communication tools, and digital infrastructure. For Deaf, DeafBlind, and Hard-of-Hearing people, inaccessible procurement can create serious communication barriers. This includes barriers to ASL, LSQ, captioning, relay-compatible communication, accessible video communication, emergency alerts, and accessible customer service. Clarifying the disclaimer would help organizations understand that the standard may be voluntary as a standards document, but accessibility obligations may still exist under applicable laws, policies, contracts, and human rights requirements.
Heading text
3.3 Disclaimer and exclusion of liability
Heading number portion
3.3
Item id
1782150659939_891
Heading id
3.4
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?
DWCC recommends clarifying that intellectual property and ownership restrictions should not prevent people with disabilities, disability organizations, Deaf-led organizations, or accessibility reviewers from accessing, reviewing, discussing, citing, or commenting on the draft standard during the public review process.
What should we change it to?
Add language confirming that Accessibility Standards Canada’s intellectual property rights do not limit authorized accessibility-related uses during public review, including use of alternate formats, assistive technologies, plain language, ASL and LSQ summaries, captioned video summaries, screen readers, braille, large print, or other accessible review formats. Add language confirming that disability organizations may quote limited portions of the draft standard for the purpose of submitting comments, explaining accessibility concerns, consulting with members, and preparing public review feedback, subject to ASC’s authorized-use rules.
Why should we change it?
People with disabilities and disability organizations need to be able to review and discuss draft standards in accessible ways. If intellectual property language is too restrictive or unclear, it may discourage community review, especially when organizations need to explain draft language to members, interpreters, captioners, advisors, or accessibility experts. For Deaf, DeafBlind, and Hard-of-Hearing communities, meaningful review may require ASL, LSQ, captioning, relay-compatible communication, plain language, and discussion with people who have lived experience and subject-matter expertise. Clear language would protect ASC’s intellectual property while supporting meaningful participation in the standards-development process.
Heading text
3.4 Intellectual property and ownership
Heading number portion
3.4
Item id
1782150777898_884
Heading id
3.5
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?
DWCC recommends clarifying that patent rights or pending patent applications should not be used in a way that limits accessible procurement, creates vendor lock-in, or prevents organizations from selecting accessible alternatives that meet the needs of persons with disabilities.
What should we change it to?
Add language encouraging users of the standard to consider whether patented or proprietary technologies may affect accessibility, interoperability, affordability, competition, or long-term access. Add language stating that, where a procurement involves accessibility-related technology, organizations should avoid unnecessary dependence on proprietary solutions if that dependence would reduce accessibility, prevent accessible alternatives, limit relay-compatible communication, restrict captioning or sign-language access, or make remediation difficult.
Why should we change it?
Accessible procurement should not create new barriers through vendor lock-in or proprietary systems that cannot be adapted, tested, remediated, or replaced. For Deaf, DeafBlind, and Hard-of-Hearing users, this is especially important for technologies involving captioning, relay-compatible communication, video communication, sign-language video, emergency communication, customer support, and AI-enabled accessibility tools. This change would help organizations consider patent and proprietary technology risks as part of accessibility planning and long-term barrier prevention.
Heading text
3.5 Patent rights
Heading number portion
3.5
Item id
1782150885832_293
Heading id
3.6
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?
DWCC recommends clarifying the licence-to-comments section so that people with disabilities and disability organizations can easily understand what rights they are granting when they submit comments, including written comments, oral comments, ASL comments, LSQ comments, video comments, translated comments, and comments prepared with communication supports.
What should we change it to?
Add a plain language explanation of the licence-to-comments clause. The explanation should clarify that comments may be used by Accessibility Standards Canada and the Government of Canada to revise the draft standard or for related non-commercial purposes. Add language confirming how this licence applies to comments submitted in ASL, LSQ, captioned video, audio, plain language, or other accessible formats. Add language clarifying how ASC will handle attribution, organizational submissions, comments prepared with interpreters or translators, and comments that include lived-experience information from Deaf, DeafBlind, Hard-of-Hearing, or other disabled participants.
Why should we change it?
This clause is legally important but difficult to understand. If people with disabilities or disability organizations are unsure what rights they are giving up, they may be less willing to participate in public review. For DDBHH participants, comments may be submitted or developed through ASL, LSQ, interpretation, captioning, translation, relay-compatible communication, or video formats. The licence should clearly explain how those formats are treated and how contributors’ rights, privacy, attribution, and third-party intellectual property will be handled. A clear plain language explanation would improve accessibility, transparency, and trust in the public review process.
Heading text
3.6 Licence to comments
Heading number portion
3.6
Item id
1782151032411_741
Heading id
3.7
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?
DWCC recommends clarifying the authorized uses section so that people with disabilities, Deaf-led organizations, disability organizations, interpreters, translators, captioners, accessibility advisors, and subject-matter experts can participate meaningfully in reviewing the draft standard. The current language allows users to load, search, browse, and print the document, but it does not clearly explain whether users may share limited excerpts or accessible-format materials for the purpose of preparing public review comments.
What should we change it to?
Add language confirming that authorized non-commercial review uses include using assistive technology, creating or using accessible formats, discussing limited excerpts with accessibility advisors or community members, and sharing limited portions with interpreters, translators, captioners, or support persons for the purpose of preparing public review comments. Add language confirming that these authorized review uses must not alter the official draft standard, remove the legal notice, sell the document, or mislead users about the content or status of the draft standard.
Why should we change it?
Meaningful public review often requires people with disabilities and disability organizations to discuss draft language with others. For Deaf, DeafBlind, and Hard-of-Hearing reviewers, this may require ASL interpretation, LSQ interpretation, DeafBlind communication supports, captioning, plain language explanation, relay-compatible communication, or consultation with Deaf-led and disability-led experts. Clear authorized-use language would protect Accessibility Standards Canada’s document rights while also supporting accessible participation in the review process. Without this clarification, some reviewers may avoid seeking the communication supports or expert advice they need to provide meaningful feedback.
Heading text
3.7 Authorized uses of this document
Heading number portion
3.7
Item id
1782151204679_233
Heading id
s3
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?
DWCC recommends that the final standard publish the Technical Committee membership information in a way that confirms whether the committee included relevant Deaf, DeafBlind, Hard-of-Hearing, ASL, LSQ, DeafBlind communication access, telecom, digital accessibility, emergency communication, and accessible procurement expertise. Because this section is currently reserved for publication, DWCC cannot assess whether the Technical Committee had sufficient DDBHH representation and subject-matter expertise.
What should we change it to?
Add the Technical Committee member list and include enough information to show the range of lived experience, disability expertise, sector expertise, and stakeholder perspectives represented. DWCC also recommends adding a short statement confirming whether Deaf, DeafBlind, Hard-of-Hearing, ASL, LSQ, DeafBlind communication access, telecom, digital accessibility, emergency communication, and accessible procurement expertise were included in the Technical Committee process. If those areas were not represented, ASC should identify how this gap will be addressed before final publication or in the next revision cycle.
Why should we change it?
Technical Committee composition is directly relevant to the credibility and completeness of an accessibility standard. General disability representation is important, but it is not a substitute for relevant lived experience and subject-matter expertise where the standard affects specific communities and barriers. For DDBHH people, procurement decisions can affect ASL, LSQ, Indigenous Sign Languages, DeafBlind communication supports, captioning, relay-compatible communication, video communication, customer support, emergency communication, AI tools, and digital public services. The principle of “nothing without us” requires more than consultation. It requires meaningful involvement of people with relevant lived experience and expertise in the development of the standard.
Heading text
4. Technical Committee members
Heading number portion
4.
Item id
1782151310421_889
Heading id
s4
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?
DWCC recommends that the Preface explain that accessible procurement is a barrier-prevention mechanism. The Preface should make clear that procurement decisions can either prevent barriers before they are purchased or embed barriers into public services, digital systems, customer support, emergency communication, and infrastructure.
What should we change it to?
Add Preface language stating that accessible procurement must be applied from the beginning of the procurement life cycle and must include communication access, digital access, service access, physical access, and safety communication. The Preface should also recognize that accessibility must be defined with relevant lived experience and subject-matter expertise, including Deaf, DeafBlind, Hard-of-Hearing, ASL, LSQ, Indigenous Sign Languages, captioning, relay-compatible communication, accessible video communication, and DeafBlind communication access where those issues are affected.
Why should we change it?
A clear Preface would help readers understand that this standard is not only about procurement administration. It is about preventing accessibility barriers before public money is spent. For DDBHH people, inaccessible procurement can create long-term communication barriers in websites, digital applications, telecom services, meetings, customer support, emergency alerts, education platforms, employment systems, and AI-enabled tools. The Preface should frame accessible procurement as a proactive duty to prevent these barriers from being built into goods and services.
Heading text
5. Preface
Heading number portion
5.
Item id
1782151712760_204
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?
DWCC recommends strengthening the Introduction to explicitly recognize communication access as a core part of accessible procurement. The Introduction should identify Deaf, DeafBlind, Hard-of-Hearing, and sign-language users as intended beneficiaries of the standard. The Introduction should also clarify that people with disabilities must not only be consulted. They must be meaningfully involved in defining requirements, evaluating accessibility, testing solutions, monitoring implementation, and confirming whether procured goods or services actually remove barriers.
What should we change it to?
Add language stating that accessible procurement must include communication access, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital platforms. Add language stating that procurement requirements should be developed with relevant lived experience and subject-matter expertise. Where a procurement affects DDBHH people, this should include Deaf, DeafBlind, Hard-of-Hearing, ASL, LSQ, DeafBlind communication access, telecom, digital accessibility, emergency communication, and accessible procurement expertise. Add language stating that accessible procurement is a barrier-prevention mechanism. Procurement decisions can either prevent barriers before public money is spent or purchase barriers into systems, services, platforms, contracts, and infrastructure.
Why should we change it?
This change is needed because communication access is often overlooked when accessibility is treated mainly as physical access, document access, or general digital access. For Deaf, DeafBlind, and Hard-of-Hearing people, many barriers arise from audio-only systems, phone-based customer support, inaccessible meetings, missing captioning, lack of ASL or LSQ access, inaccessible emergency communication, and digital platforms that do not support video or relay-compatible communication. Accessible procurement must prevent these barriers from being purchased in the first place. If accessibility is added only after a contract is awarded, organizations may be locked into inaccessible systems that are expensive or difficult to fix. This change would better align the Introduction with the standard’s goal of achieving the highest level of accessibility and with the principle that people with disabilities should be involved in procurement in a meaningful and decision-influencing way.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782155275809_805
Heading id
s6
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
DWCC recommends strengthening the Scope to explicitly include communication access, accessible digital and telecommunications services, emergency communication, customer support, AI-enabled systems, and contract management as part of accessible procurement. The current scope is strong, but it should more clearly state that accessibility in procurement includes communication access and not only physical, document, website, or general service accessibility.
What should we change it to?
Add language stating that the standard applies to the procurement of goods, services, systems, platforms, applications, communication tools, emergency communication tools, customer support systems, AI-enabled tools, and digital or telecommunications services where accessibility barriers may arise. Add language stating that accessibility requirements include communication access for Deaf, DeafBlind, and Hard-of-Hearing people, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible customer support. Add language confirming that the standard applies throughout the full procurement life cycle, including planning, solicitation, evaluation, contract award, implementation, monitoring, remediation, renewal, and closeout.
Why should we change it?
The scope determines how organizations understand and apply the standard. If communication access, digital services, telecommunications, AI-enabled systems, and emergency communication are not clearly included, organizations may overlook major barriers affecting Deaf, DeafBlind, and Hard-of-Hearing people. Procurement decisions can lock in barriers for many years. For DDBHH users, this can include phone-only customer service, inaccessible video platforms, missing captions, no ASL or LSQ access, emergency alerts without accessible communication, AI transcription or captioning tools that are not tested with affected users, and digital platforms that do not support relay-compatible communication. Clarifying the scope would help organizations apply the standard consistently and prevent barriers before they are purchased.
Heading text
7. Scope
Heading number portion
7.
Item id
1782157968006_565
Heading id
7.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?
DWCC recommends expanding the intended audience to explicitly include disability organizations, Deaf-led organizations, accessibility subject-matter experts, end users, evaluators, and organizations that support Deaf, DeafBlind, and Hard-of-Hearing people. The standard should also clarify that it is relevant not only to federally regulated entities, but also to organizations purchasing goods, services, digital platforms, communication tools, emergency systems, customer support systems, and AI-enabled accessibility tools that may affect people with disabilities.
What should we change it to?
Add language stating that the intended audience includes procurement professionals, clients, project authorities, technical authorities, senior management, bidders, suppliers, accessibility evaluators, disability organizations, Deaf-led organizations, and end users with disabilities. Add language stating that the standard is relevant to organizations whose procurement decisions affect communication access, digital access, public services, emergency communication, customer support, education, employment, health, transportation, telecommunications, broadcasting, and AI-enabled services.
Why should we change it?
Procurement decisions affect more than the purchasing organization. They affect the people who must use the goods, services, platforms, and systems after they are purchased. For Deaf, DeafBlind, and Hard-of-Hearing people, procurement can determine whether communication access is available through ASL, LSQ, Indigenous Sign Languages, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible customer service, and accessible emergency communication. Including disability organizations, Deaf-led organizations, accessibility evaluators, and end users in the intended audience would make clear that accessible procurement requires relevant lived experience and subject-matter expertise throughout the process.
Heading text
7.1 Intended audience
Heading number portion
7.1
Item id
1782224469938_398
Heading id
7.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
DWCC recommends clarifying that federal procurement requirements, trade agreements, internal procurement policies, standing offers, supply arrangements, budget rules, or administrative procedures should not be interpreted in a way that weakens accessibility, communication access, or the duty to accommodate. The section should state that accessibility must be considered a core procurement requirement, not an optional feature that can be removed because of process convenience, cost pressure, or existing procurement templates.
What should we change it to?
Add language stating that, when adapting this standard to federal, provincial, territorial, municipal, private, or non-profit procurement contexts, organizations should ensure that procurement rules are applied consistently with accessibility, human rights, and duty-to-accommodate obligations. Add language confirming that procurement methods, standing offers, supply arrangements, trade agreement obligations, timelines, or internal procedures should not prevent the inclusion of accessibility requirements, including communication access for Deaf, DeafBlind, and Hard-of-Hearing people. Add language stating that where a procurement process appears to limit accessibility, organizations should use available flexibility, exemptions, accessibility review, or justification processes to prevent barriers from being purchased.
Why should we change it?
Procurement rules can unintentionally become barriers when they are applied without an accessibility lens. Organizations may rely on existing templates, mandatory supply arrangements, short timelines, cost evaluation rules, or rigid procurement procedures that do not account for ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, or accessible customer support. This change would help ensure that procurement restrictions do not override the purpose of accessible procurement. It would also support the Accessible Canada Act’s objective of identifying, removing, and preventing barriers before goods, services, systems, platforms, or contracts are purchased.
Heading text
7.2 Other relevant restrictions or considerations
Heading number portion
7.2
Item id
1782224576417_833
Heading id
7.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
DWCC recommends clarifying that core accessibility requirements, including communication access requirements, should use “shall” where failure to include them would create barriers for people with disabilities. The terms “should” and “may” should not be used for essential accessibility requirements that are necessary for Deaf, DeafBlind, and Hard-of-Hearing people to participate in procurement processes or use procured goods and services.
What should we change it to?
Add language explaining that “shall” should be used for mandatory accessibility requirements that are necessary to prevent barriers. Add language stating that communication access requirements should be mandatory where they are necessary for equal participation or service access. This includes ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible customer support. Add language encouraging users of the standard to avoid treating essential accessibility features as optional through the use of “should” or “may.”
Why should we change it?
Terminology determines whether accessibility is treated as a requirement, recommendation, or option. For DDBHH people, communication access cannot be optional when it is necessary to participate in procurement activities, access public services, receive emergency information, use digital platforms, communicate with customer support, or evaluate procured systems. If essential access requirements are written as “should” or “may,” organizations may treat them as discretionary and purchase inaccessible goods or services. Using “shall” for essential communication-access requirements would strengthen barrier prevention and better support the purpose of accessible procurement.
Heading text
7.3 Terminology
Heading number portion
7.3
Item id
1782224705231_637
Heading id
s7
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends expanding the References section to include or cross-reference resources that address Deaf, DeafBlind, and Hard-of-Hearing communication access, including ASL, LSQ, Indigenous Sign Languages, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible telecommunications services. The current references are useful, but they do not fully address communication access for DDBHH people in procurement contexts.
What should we change it to?
What should we change it to? Add references or cross-references to guidance, standards, or research that address DDBHH communication access in procurement, including: * sign-language access, including ASL and LSQ; * DeafBlind communication supports; * captioning and transcripts; * relay-compatible communication; * accessible video communication; * accessible emergency communication; * accessible customer support; * accessible telecommunications and digital services; * accessibility testing with affected users; * AI-enabled accessibility tools, including transcription, captioning, sign-language technologies, avatars, and automated customer support. DWCC also recommends adding relevant Deaf-led and disability-led research to the bibliography where appropriate.
Why should we change it?
Why should we change it? References guide how organizations interpret and apply the standard. If the reference list does not include DDBHH communication-access materials, organizations may rely mainly on general digital, plain language, service delivery, or built-environment references and miss barriers specific to Deaf, DeafBlind, and Hard-of-Hearing people. For DDBHH users, accessibility requires more than accessible documents or websites. It may require ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible customer service. Adding stronger DDBHH communication-access references would help organizations define better procurement requirements and prevent barriers before goods, services, systems, or contracts are purchased.
Heading text
8. References
Heading number portion
8.
Item id
1782224838556_113
Heading id
s8
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends adding definitions or clarifying existing definitions to ensure that communication access for Deaf, DeafBlind, and Hard-of-Hearing people is fully recognized throughout the standard. The definitions section should include or clarify terms related to ASL, LSQ, Indigenous Sign Languages, DeafBlind communication supports, communication access, accessible video communication, relay-compatible communication, captioning, sign-language translation, Deaf-led expertise, and accessibility testing with affected users.
What should we change it to?
What should we change it to? Add or clarify definitions for the following terms: Communication access: Access to information, interaction, services, meetings, emergency communication, digital platforms, and customer support through effective communication methods, including sign language, captioning, text-based communication, relay-compatible communication, accessible video communication, and DeafBlind communication supports. Deaf, DeafBlind, and Hard-of-Hearing users: People whose access needs may include ASL, LSQ, Indigenous Sign Languages, captioning, relay services, DeafBlind communication supports, visual communication, tactile communication, text-based communication, accessible video communication, and accessible emergency communication. American Sign Language and langue des signes québécoise: Distinct natural languages used by Deaf communities in Canada, not merely alternate formats or accommodations. DeafBlind communication supports: Communication supports that may include tactile sign language, intervenor services, close-vision signing, protactile communication, braille, large print, accessible digital formats, and other individualized communication methods. Relay-compatible communication: Communication systems, platforms, or services that are usable with video relay service, text relay, IP relay, captioned telephone where applicable, and other relay or intermediary communication services. Deaf-led expertise: Lived experience and subject-matter expertise from Deaf, DeafBlind, and Hard-of-Hearing people and organizations that is relevant to defining, testing, evaluating, and monitoring accessibility requirements.
Why should we change it?
Why should we change it? Definitions shape how organizations apply the entire standard. If communication access and DDBHH-related terms are not clearly defined, organizations may treat them as optional accommodations instead of core accessibility requirements. For Deaf, DeafBlind, and Hard-of-Hearing people, accessibility barriers often arise when procurement assumes hearing, speech, phone access, audio alerts, spoken meetings, or English/French text-only communication. These barriers affect public services, emergency communication, customer support, telecom services, digital platforms, education, employment, health, transportation, and AI-enabled tools. Clear definitions would help procurement professionals, clients, bidders, evaluators, and contract managers understand that DDBHH communication access must be built into procurement requirements from the start.
Heading text
9. Definitions
Heading number portion
9.
Item id
1782225048361_254
Heading id
9.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 9.1 by adding and clarifying definitions that are necessary for Deaf, DeafBlind, and Hard-of-Hearing accessibility in procurement. The current definitions of “accessible format” and “communication supports” are useful, but they should be expanded so that communication access is not treated only as an accommodation. The definitions should recognize that communication access can be a core functional requirement of a procured good, service, platform, application, meeting, emergency system, customer support system, or digital service.
What should we change it to?
What should we change it to? DWCC recommends adding or clarifying the following definitions: Communication access: Access to information, interaction, services, meetings, emergency communication, digital platforms, customer support, and procurement processes through effective communication methods. This may include ASL, LSQ, Indigenous Sign Languages, DeafBlind communication supports, captioning, transcripts, text-based communication, relay-compatible communication, accessible video communication, and visual or tactile alerts. American Sign Language and langue des signes québécoise: Distinct natural languages used by Deaf communities in Canada. ASL and LSQ should not be treated merely as alternate formats or optional accommodations. DeafBlind communication supports: Communication supports that may include tactile sign language, close-vision signing, protactile communication, intervenor services, braille, large print, accessible digital formats, visual-tactile alerts, and other individualized communication methods. Relay-compatible communication: Communication systems, platforms, or services that can be used effectively with video relay service, text relay, IP relay, captioned communication where applicable, and other relay or intermediary communication services. Accessible video communication: Video communication that supports visual language and communication access, including sufficient video quality, stable connection, interpreter visibility, screen layout control, captioning where applicable, chat or text functions, and compatibility with relay or interpreting services. Deaf-led expertise: Relevant lived experience and subject-matter expertise from Deaf, DeafBlind, and Hard-of-Hearing people and organizations that can inform accessibility requirements, user testing, evaluation, implementation, contract monitoring, and remediation. Accessibility evaluator: A person with relevant lived experience, technical knowledge, or subject-matter expertise who evaluates whether a good, service, system, platform, or procurement process meets accessibility requirements. Where a procurement affects DDBHH users, evaluators should include Deaf, DeafBlind, or Hard-of-Hearing people with relevant communication-access expertise.
Why should we change it?
Why should we change it? Definitions shape how the entire standard is applied. If DDBHH communication-access terms are not clearly defined, procurement professionals, clients, bidders, evaluators, and contract managers may misunderstand or minimize accessibility requirements. For Deaf, DeafBlind, and Hard-of-Hearing people, barriers often arise when systems assume hearing, speech, phone access, audio alerts, spoken meetings, or text-only communication. These barriers can affect procurement meetings, public-facing services, emergency communication, telecom services, customer support, health systems, education platforms, employment systems, transportation systems, and AI-enabled tools. Adding these definitions would help organizations understand that DDBHH communication access must be built into procurement requirements from the beginning, tested with affected users, and monitored as part of contract performance.
Heading text
9.1 Definitions
Heading number portion
9.1
Item id
1782225206762_365
Heading id
s9
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Section 10 to state that accessibility requirements must include communication access requirements where a procurement affects Deaf, DeafBlind, or Hard-of-Hearing people. The general requirements should also clarify that accessibility must be included from the beginning of procurement, not added after requirements, budgets, timelines, evaluation criteria, or contract terms have already been set.
What should we change it to?
What should we change it to? Add language stating that procurement policies and procedures shall require accessibility to be considered as a core functional requirement throughout the procurement life cycle. Add language stating that communication access must be included where applicable, including ASL, LSQ, Indigenous Sign Languages, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible customer support. Add language stating that clients and procurement professionals shall consult relevant lived experience and subject-matter expertise before excluding, reducing, or deferring accessibility requirements. Add language stating that accessibility requirements should be linked to evaluation criteria, testing, contract deliverables, remediation obligations, and outcome measurement.
Why should we change it?
Why should we change it? General requirements set the baseline for the whole standard. If communication access is not clearly included at this level, it may be overlooked later in planning, engagement, evaluation, bidding, contract management, and training. For Deaf, DeafBlind, and Hard-of-Hearing people, accessibility often depends on whether communication access is built into the procurement from the start. This includes meetings, websites, digital applications, customer support, emergency communication, relay compatibility, captioning, ASL, LSQ, accessible video communication, and AI-enabled tools. This change would help prevent organizations from purchasing barriers and then trying to fix them afterward. Accessibility should be a planned, evaluated, contracted, and monitored requirement.
Heading text
10. General requirements
Heading number portion
10.
Item id
1782225364796_325
Heading id
10.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 10.1 to clarify that accessibility requirements include communication access requirements and that these requirements must be considered regardless of dollar value. The clause should also clarify that “flexible and person-centred” includes flexibility for Deaf, DeafBlind, and Hard-of-Hearing communication access needs.
What should we change it to?
What should we change it to? Add language stating that procurement policies and procedures shall consider communication access throughout a procurement regardless of dollar value. Add language stating that flexible and person-centred procurement includes ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible procurement meetings. Add language stating that low-dollar procurements, pilots, software subscriptions, renewals, emergency purchases, and non-competitive procurements should not be used to bypass accessibility or communication-access requirements.
Why should we change it?
Why should we change it? Accessibility barriers can be created even in low-dollar procurements. A small software purchase, meeting platform, customer support tool, emergency communication tool, AI transcription service, video platform, or renewal contract can create major communication barriers for Deaf, DeafBlind, and Hard-of-Hearing users. If communication access is not considered in policies and procedures from the start, organizations may purchase inaccessible systems and then rely on individual accommodations after barriers have already been built in. This change would strengthen the standard’s existing requirement that accessibility be considered throughout procurement regardless of dollar value.
Heading text
10.1 Policies and procedures
Heading number portion
10.1
Item id
1782225471088_964
Heading id
10.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 10.1.1 to explicitly state that accessibility requirements include communication access requirements. Communication access should be incorporated throughout all phases of procurement, including planning, bidding, contract award, contract management, closeout, evaluation criteria, testing requirements, solicitation documents, contract documents, and industry engagement activities.
What should we change it to?
What should we change it to? Add language stating that accessibility requirements shall include communication access requirements where a procurement affects Deaf, DeafBlind, or Hard-of-Hearing people. Add language stating that communication access requirements may include ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, accessible meetings, and accessible digital platforms. Add language stating that communication access shall be included in specifications, evaluation criteria, testing requirements, solicitation documents, contract documents, industry engagement activities, implementation requirements, and contract monitoring where applicable. Add language stating that communication access shall not be deferred to individual accommodation after procurement decisions have already been made.
Why should we change it?
Why should we change it? Communication access barriers are often created when accessibility is not built into procurement from the beginning. For Deaf, DeafBlind, and Hard-of-Hearing people, barriers can arise in video platforms, customer support systems, emergency communication tools, AI transcription or captioning tools, public-facing websites, digital applications, meetings, bidder conferences, and contract deliverables. If communication access is not included in specifications, evaluation criteria, testing, and contract terms, organizations may purchase inaccessible goods or services and then try to fix them later through individual accommodation. That approach is inefficient, inequitable, and inconsistent with barrier prevention. This change would ensure that communication access is treated as a core procurement requirement throughout the full procurement life cycle.
Heading text
10.1.1 Incorporating accessibility
Heading number portion
10.1.1
Item id
1782225580363_826
Heading id
10.1.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 10.1.2 to clarify that clients and procurement professionals are responsible for identifying and involving relevant accessibility subject-matter experts and affected end users when defining requirements, developing evaluation criteria, verifying deliverables, or deciding whether accessibility requirements are not included. The roles and responsibilities should explicitly include communication-access expertise where a procurement may affect Deaf, DeafBlind, or Hard-of-Hearing people.
What should we change it to?
What should we change it to? Add language stating that the client is responsible for identifying whether the procurement may affect communication access for Deaf, DeafBlind, or Hard-of-Hearing people and, where applicable, including communication-access requirements in specifications, evaluation criteria, testing, and contract deliverables. Add language stating that the procurement professional’s challenge function shall include questioning the exclusion or weakening of communication-access requirements, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible customer support. Add language stating that procurement professionals shall assist clients in identifying relevant lived-experience experts, including Deaf, DeafBlind, and Hard-of-Hearing accessibility evaluators and Deaf-led organizations, when the procurement affects DDBHH users. Add language stating that accessibility deliverables should be verified by people with relevant lived experience or subject-matter expertise where appropriate.
Why should we change it?
Why should we change it? Roles and responsibilities determine who is accountable for preventing accessibility barriers. If communication access is not assigned clearly to clients, procurement professionals, evaluators, and contract managers, it may be missed or treated as an afterthought. For DDBHH people, inaccessible procurement can result in phone-only customer support, missing captions, no ASL or LSQ access, inaccessible emergency communication, video platforms that do not support visual language, and AI tools that are not tested with affected users. The procurement professional’s challenge function is especially important. It should require procurement professionals to question missing accessibility requirements before contracts are awarded, not after barriers are discovered by end users. This change would strengthen accountability and help ensure that accessibility is defined, evaluated, verified, and delivered.
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782225669881_422
Heading id
10.1.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 10.1.3 to state that accessibility requirements must be defined with relevant lived experience, user testing, and subject-matter expertise before procurement requirements are finalized. The clause should also clarify that flexibility in procurement must be used to include and strengthen accessibility requirements, not to defer, weaken, or exclude them.
What should we change it to?
What should we change it to? Add language stating that, when defining requirements, clients shall identify whether the good, service, system, platform, application, or contract may affect communication access for Deaf, DeafBlind, or Hard-of-Hearing users. Add language stating that, where DDBHH users may be affected, requirements shall consider ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital interaction. Add language stating that requirements should be defined with input from affected users and relevant accessibility subject-matter experts before solicitation documents are finalized. Add language stating that flexible procurement approaches should include clear accessibility roadmaps, timelines, interim remediation measures, user testing, and contract monitoring.
Why should we change it?
Why should we change it? Accessibility requirements are often lost when they are not defined early enough. Once a procurement has already defined its business requirements, technical requirements, budget, timeline, evaluation criteria, and contract structure, it becomes much harder to add communication access later. For Deaf, DeafBlind, and Hard-of-Hearing people, missing requirements can lead to inaccessible meetings, digital platforms, customer support, emergency alerts, video services, AI tools, and telecom services. These barriers are preventable if communication access is defined at the beginning. This change would help ensure that flexibility is used to prevent barriers, not to justify purchasing inaccessible goods or services with a promise to fix them later.
Heading text
10.1.3 Defining requirements
Heading number portion
10.1.3
Item id
1782225810752_547
Heading id
10.1.3.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC supports this clause and recommends strengthening it to clarify that flexibility in the procurement strategy must be used to integrate accessibility requirements, including communication access requirements, instead of excluding or delaying them. The clause should also clarify that flexibility must not become a reason to accept inaccessible goods or services without clear remediation obligations, timelines, and interim access measures.What should we change it to? Add language stating that flexible procurement strategies shall be used to include accessibility requirements wherever possible, including communication access requirements for Deaf, DeafBlind, and Hard-of-Hearing users. Add language stating that where full accessibility is not available at solicitation closing or contract award, the procurement strategy shall include a documented accessibility roadmap, interim communication-access measures, user testing, monitoring, and enforceable remediation timelines. Add language stating that interim measures may include ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible customer support, and accessible emergency communication where applicable.
What should we change it to?
What should we change it to? Add language stating that flexible procurement strategies shall be used to include accessibility requirements wherever possible, including communication access requirements for Deaf, DeafBlind, and Hard-of-Hearing users. Add language stating that where full accessibility is not available at solicitation closing or contract award, the procurement strategy shall include a documented accessibility roadmap, interim communication-access measures, user testing, monitoring, and enforceable remediation timelines. Add language stating that interim measures may include ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible customer support, and accessible emergency communication where applicable.
Why should we change it?
Why should we change it? DWCC supports the principle that flexibility should help integrate accessibility instead of excluding it. However, flexibility must be tied to accountability. For Deaf, DeafBlind, and Hard-of-Hearing people, a flexible procurement approach without interim access can still create real barriers. A system that promises future accessibility but launches without captioning, relay compatibility, ASL or LSQ access, accessible video communication, or accessible emergency communication may exclude users during the remediation period. This change would ensure that flexibility supports barrier prevention and does not become a pathway for purchasing inaccessible goods or services.
Heading text
10.1.3.1 General
Heading number portion
10.1.3.1
Item id
1782226036240_278
Heading id
10.1.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC supports the use of flexible procurement requirements where full conformance is not possible at solicitation closing or contract award. However, Clause 10.1.3.2 should be strengthened to ensure that flexibility does not become a pathway for purchasing inaccessible goods or services without enforceable accessibility obligations. The clause should require that accessibility roadmaps include specific remediation timelines, interim access measures, user testing with affected users, reporting obligations, and consequences if accessibility milestones are not met.
What should we change it to?
What should we change it to? Add language stating that a contractor’s accessibility roadmap shall include: * the accessibility barriers identified; * the applicable accessibility standards or requirements; * the remediation steps required; * specific milestones and deadlines; * interim access measures for affected users; * testing with people with relevant lived experience; * reporting obligations to the client; * a process for end users to report barriers during the remediation period; * consequences or contract remedies if remediation milestones are not met. Add language stating that, where a procurement affects Deaf, DeafBlind, or Hard-of-Hearing users, interim access measures shall include communication access where applicable, such as ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible customer support, and accessible emergency communication. Add language stating that remediation shall be agreed upon by the client, contractor, and affected end users or relevant accessibility subject-matter experts where appropriate.
Why should we change it?
Why should we change it? A flexible procurement approach can be useful, but only if it includes accountability. Without clear milestones, interim access, user testing, and consequences, organizations may purchase inaccessible systems and leave users excluded during the remediation period. For Deaf, DeafBlind, and Hard-of-Hearing people, this could mean using a public service, meeting platform, customer support tool, emergency communication system, video platform, AI transcription tool, or digital application that does not provide effective communication access. Accessibility cannot be only a future promise. If a non-conforming solution is procured, affected users need interim access now, and the contractor must have enforceable obligations to remediate within the contract period.
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Item id
1782226213542_617
Heading id
10.1.4
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC strongly supports requiring a mandatory written justification when accessibility requirements are excluded. DWCC recommends strengthening Clause 10.1.4 to make clear that communication access requirements cannot be excluded without specific written justification. The justification should explain whether the procurement may affect Deaf, DeafBlind, or Hard-of-Hearing users, whether ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, or accessible customer support were considered, and why any of those requirements were excluded.
What should we change it to?
What should we change it to? Add language stating that, where accessibility requirements are excluded, the mandatory written justification shall identify which accessibility requirements were considered, which were excluded, and why. Add language stating that, where the procurement may affect DDBHH users, the justification shall specifically address communication access, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible customer support. Add language stating that a justification shall not be accepted unless the client has consulted relevant accessibility subject-matter experts or affected users where appropriate. Add language stating that the justification shall include a risk assessment of the accessibility barriers that may result from exclusion, including communication, safety, emergency, service-delivery, digital-access, and human-rights risks. Add language stating that mandatory justifications should be retained, reviewed, and used for accountability, audit, and continuous improvement.
Why should we change it?
Why should we change it? A mandatory written justification is only effective if it requires enough detail to prevent accessibility from being excluded through vague statements such as “not applicable,” “not required,” “too costly,” or “outside scope.” For Deaf, DeafBlind, and Hard-of-Hearing people, excluding communication access can create serious barriers. These may include inability to use a public service, participate in a procurement meeting, receive emergency information, contact customer support, use a digital platform, access captioning, use relay services, or communicate in ASL or LSQ. This change would make the justification requirement stronger, more transparent, and more useful for preventing barriers before goods or services are purchased.
Heading text
10.1.4 Mandatory justification for excluding accessibility
Heading number portion
10.1.4
Item id
1782226357272_540
Heading id
10.1.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC strongly supports Clause 10.1.4.1 and recommends strengthening it to require specific justification when communication access requirements are excluded. The clause should require clients to identify whether the procurement may affect Deaf, DeafBlind, or Hard-of-Hearing users and whether communication access requirements were considered before exclusion.
What should we change it to?
What should we change it to? Add language stating that a mandatory written justification shall identify the specific accessibility requirements that were considered and the specific accessibility requirements that were excluded. Add language stating that, where the procurement may affect Deaf, DeafBlind, or Hard-of-Hearing users, the justification shall specifically address communication access, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital interaction. Add language stating that the justification shall identify whether affected end users, people with disabilities, Deaf-led organizations, DeafBlind users, Hard-of-Hearing users, or relevant accessibility subject-matter experts were consulted. Add language stating that the risk assessment shall include communication-access risks, safety risks, emergency communication risks, service-delivery risks, digital-access risks, and human-rights risks. Add language stating that the signed justification should be available for internal accessibility audit, procurement review, and continuous improvement.
Why should we change it?
Why should we change it? A mandatory justification is only effective if it requires enough detail to prevent accessibility from being excluded through vague or unsupported reasoning. For Deaf, DeafBlind, and Hard-of-Hearing people, excluding communication access can create serious barriers in public services, emergency communication, customer support, meetings, digital platforms, telecom services, video communication, and AI-enabled tools. This change would make the justification process more accountable. It would require clients to show that they considered DDBHH communication access before excluding it, consulted relevant expertise where appropriate, and assessed the risks of purchasing a good or service without accessibility requirements.
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782226510802_954
Heading id
10.1.4.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 10.1.4.2 so that procurement professionals do more than confirm that a written justification exists. They should confirm that the justification is complete, specific, evidence-based, and addresses the accessibility risks created by excluding requirements.
What should we change it to?
What should we change it to? Add language stating that procurement professionals shall confirm that the written justification: * identifies the specific accessibility requirements excluded; * explains why each excluded requirement was not included; * identifies whether affected end users or relevant accessibility subject-matter experts were consulted; * includes a risk assessment; * identifies any flexible procurement options considered; * includes any interim or alternative accessibility measures; * is signed by the client with delegated authority; * is retained on the procurement file. Add language stating that, where the procurement may affect Deaf, DeafBlind, or Hard-of-Hearing users, the procurement professional shall confirm that the justification specifically addresses communication access, including ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible customer support.
Why should we change it?
Why should we change it? If procurement professionals only confirm that a justification exists, accessibility may still be excluded through incomplete or vague reasoning. The challenge function must include quality control. For Deaf, DeafBlind, and Hard-of-Hearing people, missing communication access can create serious barriers in public services, emergency systems, customer support, digital platforms, meetings, video communication, telecom services, and AI-enabled tools. This change would make the confirmation process more meaningful and would help ensure that accessibility is not excluded without proper analysis, consultation, and accountability.
Heading text
10.1.4.2 Confirmation of justification
Heading number portion
10.1.4.2
Item id
1782226591131_1
Heading id
s10
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Section 11 to explicitly include communication access for Deaf, DeafBlind, and Hard-of-Hearing people in procurement information, websites, applications, forms, notices, help desk support, engagement activities, and digital services. Accessible procurement information must not rely only on written text, audio, phone-based support, or general website accessibility. It must also include accessible communication options for DDBHH users.
What should we change it to?
What should we change it to? Add language stating that procurement information, websites, and applications shall support communication access where applicable, including ASL, LSQ, Indigenous Sign Languages, DeafBlind communication supports, captioning, transcripts, relay-compatible communication, accessible video communication, text-based communication, and accessible customer support. Add language stating that procurement websites and applications should not require phone-only communication, audio-only instructions, inaccessible video, or inaccessible customer support as the only way to participate. Add language stating that help desk, FAQ, tutorial, alert, and support information should be available in accessible formats and communication methods, including plain language, captioned video, ASL or LSQ video where appropriate, text-based support, and relay-compatible contact options.
Why should we change it?
Why should we change it? Procurement information and digital applications are gateways to participation. If these systems are inaccessible, Deaf, DeafBlind, and Hard-of-Hearing people may be excluded before they can even review a solicitation, attend an engagement event, ask questions, submit a bid, request a debrief, or report an accessibility barrier. For DDBHH people, accessibility requires more than readable documents or technically accessible websites. It may require ASL, LSQ, captioning, relay-compatible communication, accessible video communication, text-based support, and accessible customer service. This change would help ensure that procurement information, websites, and applications are accessible in practice, not only in format.
Heading text
11. Procurement information, websites, and applications
Heading number portion
11.
Item id
1782226691395_519
Heading id
11.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.1 to state that clear procurement information must be provided not only in accessible formats, but also through accessible communication methods where needed. The clause should recognize Deaf, DeafBlind, and Hard-of-Hearing users, bidders, employees, business owners, evaluators, and end users who may need communication access throughout the procurement process.
What should we change it to?
What should we change it to? Add language stating that clear procurement information should include accessible communication methods, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, transcripts, text-based communication, relay-compatible communication, accessible video communication, and accessible customer support. Add language stating that people who need accessible procurement information may include Deaf, DeafBlind, and Hard-of-Hearing clients, procurement professionals, employees, end users, bidders, business owners, subcontractors, evaluators, and members of the public affected by the procured good or service.
Why should we change it?
Why should we change it? Accessible format and accessible communication are related but not the same. A document may be technically accessible but still not provide effective communication access for DDBHH users. For example, procurement information may require ASL or LSQ explanation, captioned video, relay-compatible contact options, text-based support, accessible video meetings, or DeafBlind communication supports. Without these options, DDBHH participants may face barriers when trying to understand procurement requirements, ask questions, participate in engagement activities, submit bids, evaluate solutions, or report accessibility issues. This change would make Clause 11.1 more complete and more practical.
Heading text
11.1 General
Heading number portion
11.1
Item id
1782227177763_417
Heading id
11.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.2 to clarify that plain language and accessible formats must include communication access where needed. Plain language is important, but it should not be treated as a substitute for ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, or other communication supports.
What should we change it to?
What should we change it to? Add language stating that plain language documents and accessible formats should be accompanied by accessible communication options where needed, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, transcripts, accessible video, and text-based support. Add language stating that sign-language video should be easy to find, clearly labelled, captioned where appropriate, and produced with adequate lighting, contrast, framing, pacing, signer visibility, and accessible video controls. Add language stating that procurement documents involving public-facing services, emergency communication, digital platforms, customer support, or accessibility requirements should provide plain language summaries and, where appropriate, ASL and LSQ summaries.
Why should we change it?
Why should we change it? For DDBHH people, accessibility is not achieved simply by converting complex procurement documents into plain written text. ASL and LSQ are distinct languages, and some users may require sign-language access, captioning, DeafBlind communication supports, or accessible video communication to fully understand and participate. Procurement documents can be highly technical. If accessibility requirements, bidder instructions, engagement information, debriefing information, or user support materials are not provided through effective communication methods, DDBHH people may be excluded from procurement participation and from understanding procured services that affect them. This change would help ensure that plain language and accessible formats support real communication access.
Heading text
11.2 Plain language and accessible formats
Heading number portion
11.2
Item id
1782227281298_325
Heading id
11.2.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.2.1 to clarify that plain language documents must not be treated as the only accessibility solution for Deaf, DeafBlind, and Hard-of-Hearing people. Where procurement documents affect DDBHH users, bidders, employees, or end users, plain language should be paired with accessible communication options, including ASL, LSQ, DeafBlind communication supports, captioning, transcripts, relay-compatible communication, accessible video communication, and text-based support.
What should we change it to?
What should we change it to? Add language stating that the documents listed in Clause 11.2.1 should also be available through accessible communication methods where needed. Add language stating that instructional training materials, contracting notices and alerts, customer service and help desk support documentation, and communications to businesses should include accessible communication options for Deaf, DeafBlind, and Hard-of-Hearing users. Add language stating that, where documents explain accessibility requirements, public-facing services, emergency communication, digital platforms, customer support, or user rights, organizations should consider plain language summaries, ASL summaries, LSQ summaries, captioned video, transcripts, and accessible contact options.
Why should we change it?
Why should we change it? Plain language is important, but plain written text alone does not guarantee communication access for DDBHH users. ASL and LSQ are distinct languages, and DeafBlind users may require different communication supports. Procurement documents often contain complex instructions, deadlines, contract requirements, accessibility criteria, technical terms, and complaint or support procedures. If these are only provided in written form, some DDBHH users may not have full and equal access. This change would make Clause 11.2.1 stronger by ensuring that plain language supports real communication access across procurement policies, forms, training materials, notices, alerts, help desk documentation, and business communications.
Heading text
11.2.1 Plain language documents
Heading number portion
11.2.1
Item id
1782227391241_840
Heading id
11.2.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.2.2 to clarify that plain language summaries must include essential accessibility and communication-access information. Where a full plain language document is not possible, the plain language summary should still provide enough information for Deaf, DeafBlind, and Hard-of-Hearing users, bidders, employees, and end users to understand the procurement, deadlines, requirements, accessibility criteria, support options, and complaint or remediation pathways.
What should we change it to?
What should we change it to? Add language stating that a plain language summary shall include essential information about: * the purpose of the procurement; * key dates and deadlines; * accessibility requirements; * communication-access requirements; * how to request accessible formats or communication supports; * how to ask questions; * how to participate in engagement activities; * how to submit a bid or response; * how to report accessibility barriers; * how to access debriefing or support. Add language stating that, where appropriate, plain language summaries should also be available through ASL summaries, LSQ summaries, captioned video, transcripts, DeafBlind communication supports, and accessible digital formats.
Why should we change it?
Why should we change it? A plain language summary is only useful if it includes the information people need to participate. If the summary leaves out accessibility requirements, communication supports, deadlines, contact options, or complaint pathways, people with disabilities may still face barriers. For DDBHH people, plain written summaries may need to be supported by ASL, LSQ, captioning, DeafBlind communication supports, relay-compatible contact options, or accessible video communication. This is especially important for complex procurement documents, public-facing services, emergency communication tools, digital platforms, and customer support systems. This change would make plain language summaries more effective and more consistent with meaningful accessibility.
Heading text
11.2.2 Plain language summary
Heading number portion
11.2.2
Item id
1782227493599_233
Heading id
11.2.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.2.3 to clarify that compliance with CAN-ASC-EN 301 549:2024 is necessary but may not be sufficient to ensure full communication access for Deaf, DeafBlind, and Hard-of-Hearing people. Accessible formats should include not only technically accessible documents, but also communication-access formats where needed.
What should we change it to?
What should we change it to? Add language stating that accessible formats may include accessible digital documents, plain language, captioned video, transcripts, ASL summaries, LSQ summaries, DeafBlind communication supports, braille, large print, and other formats or communication methods required for effective access. Add language stating that where sign-language video is provided, it should be easy to locate, clearly labelled, captioned where appropriate, and produced with appropriate lighting, contrast, camera framing, signer visibility, pacing, and accessible video controls. Add language stating that organizations should verify accessible formats with affected users where documents are essential for participation in procurement, public services, emergency communication, customer support, or accessibility complaints.
Why should we change it?
Why should we change it? A document can meet technical digital accessibility requirements and still not provide effective communication access for DDBHH users. For example, a procurement notice or support document may be screen-reader accessible but still lack ASL, LSQ, captioning, accessible video, relay-compatible contact options, or DeafBlind communication supports. For Deaf, DeafBlind, and Hard-of-Hearing people, accessible formats must support actual understanding, participation, and use. This is especially important for procurement deadlines, accessibility requirements, bidder instructions, customer support documentation, emergency communication, and complaint or remediation processes. This change would make Clause 11.2.3 more complete by connecting technical accessibility with practical communication access.
Heading text
11.2.3 Accessible formats
Heading number portion
11.2.3
Item id
1782227592783_386
Heading id
11.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.3 to clarify that compliance with CAN-ASC-EN 301 549:2024 is necessary but should be accompanied by practical communication-access requirements for Deaf, DeafBlind, and Hard-of-Hearing users. DWCC also notes a likely typo: “CAN-ASC-EN 301 549:20204” should be corrected to “CAN-ASC-EN 301 549:2024.”
What should we change it to?
What should we change it to? Add language stating that websites and digital applications used in planning, bidding, contract award, contract management, and closeout shall support communication access where applicable. This should include captioned video, transcripts, accessible video controls, text-based support, relay-compatible communication, ASL and LSQ video where appropriate, DeafBlind communication supports, accessible alerts, accessible forms, keyboard access, screen reader compatibility, and accessible processes for asking questions or reporting barriers. Add language stating that websites and digital applications should not rely on phone-only support, audio-only instructions, inaccessible video, inaccessible CAPTCHA, inaccessible identity verification, or inaccessible customer support as the only method of participation.
Why should we change it?
Why should we change it? Websites and digital applications are often the main gateway into procurement. If they are inaccessible, Deaf, DeafBlind, and Hard-of-Hearing people may be blocked from finding opportunities, reading documents, asking questions, attending bidder events, submitting responses, receiving notices, managing contracts, or reporting accessibility issues. Technical compliance is important, but DDBHH access also requires effective communication. A website may meet some digital accessibility requirements while still excluding users through audio-only content, missing captions, lack of relay-compatible contact options, inaccessible video meetings, phone-only help desks, or identity verification systems that assume hearing or speech. This change would make the clause stronger and would ensure that digital procurement access works in practice for DDBHH users.
Heading text
11.3 Websites and digital applications
Heading number portion
11.3
Item id
1782227847883_874
Heading id
11.4
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4 to make communication access a core requirement for all procurement engagement activities, including industry days, bidder meetings, public consultations, one-on-one meetings, site visits, debriefings, virtual meetings, and hybrid events. Engagement activities should not rely on spoken discussion, audio-only participation, phone access, inaccessible video platforms, or after-the-fact summaries as the main method of participation.
What should we change it to?
What should we change it to? Add language stating that engagement activities shall provide effective communication access for Deaf, DeafBlind, and Hard-of-Hearing participants where applicable. This should include ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, qualified interpreters, real-time captioning, transcripts, relay-compatible communication, accessible video communication, accessible chat or text functions, accessible meeting platforms, preparation materials, and clear procedures for reporting and resolving communication barriers during the event. Add language stating that organizers should provide accessibility materials in advance, including agendas, presentation decks, technical terms, procurement documents, speaker names, acronyms, and other information needed by interpreters, captioners, DeafBlind intervenors, and participants. Add language stating that accessibility failures during engagement activities should be documented and remediated before decisions are finalized.
Why should we change it?
Why should we change it? Engagement activities are where procurement requirements are shaped, clarified, and tested. If DDBHH people cannot participate effectively in these activities, their needs may be excluded before the procurement is finalized. For Deaf, DeafBlind, and Hard-of-Hearing participants, meaningful engagement requires more than an invitation. It may require ASL, LSQ, captioning, relay-compatible communication, accessible video quality, interpreter visibility, DeafBlind communication supports, advance materials, and real-time troubleshooting. If communication access fails during an engagement activity, the resulting procurement may reflect incomplete evidence and may purchase barriers into the final good, service, platform, or contract. This change would help ensure that engagement activities produce reliable accessibility information.
Heading text
11.4 Engagement activities
Heading number portion
11.4
Item id
1782227946299_648
Heading id
11.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.1 to clarify that accessible and inclusive engagement activities must include communication access for Deaf, DeafBlind, and Hard-of-Hearing participants. The clause should also clarify that hybrid participation and stable network services are essential accessibility requirements when participants rely on ASL, LSQ, captioning, relay-compatible communication, accessible video communication, or DeafBlind communication supports.
What should we change it to?
What should we change it to? Add language stating that engagement activities shall be designed with communication access from the beginning, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, qualified interpreters, real-time captioning, transcripts, accessible chat or text functions, relay-compatible communication, and accessible video platforms. Add language stating that organizers should confirm video quality, interpreter visibility, captioning quality, platform accessibility, relay compatibility, and troubleshooting procedures before the engagement activity begins. Add language stating that stable network services are not only a technical preference, but an accessibility requirement for participants who rely on visual language, video relay, video remote interpreting, captioning, or real-time communication supports.
Why should we change it?
Why should we change it? Engagement activities affect procurement outcomes. If Deaf, DeafBlind, and Hard-of-Hearing participants cannot fully participate, the organization may receive incomplete input and may miss accessibility barriers before procurement decisions are made. For DDBHH participants, unstable network services, poor video quality, missing captions, lack of interpreter visibility, inaccessible chat, no relay compatibility, or weak troubleshooting procedures can make engagement ineffective even when accommodations were technically offered. This change would strengthen the standard by recognizing that communication access must be planned, tested, and maintained throughout engagement activities.
Heading text
11.4.1 General
Heading number portion
11.4.1
Item id
1782228044877_964
Heading id
11.4.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.2 to state that information from engagement activities should capture accessibility barriers, communication-access needs, user experience, and required refinements identified by persons with disabilities. Where engagement activities involve or affect Deaf, DeafBlind, and Hard-of-Hearing people, the information gathered should include DDBHH communication-access requirements and should be used to refine procurement requirements before solicitation documents are finalized.
What should we change it to?
What should we change it to? Add language stating that information from engagement activities should help clients determine whether accessibility requirements, communication-access requirements, evaluation criteria, timelines, cost estimates, testing requirements, and contract terms need to be refined. Add language stating that, where DDBHH users may be affected, engagement information should identify requirements related to ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital platforms. Add language stating that accessibility issues raised during engagement activities should be documented and reflected in procurement planning, solicitation documents, evaluation criteria, testing requirements, and contract management.
Why should we change it?
Why should we change it? Engagement activities are only useful if the information gathered changes the procurement when barriers are identified. If DDBHH communication-access issues are discussed but not documented or translated into procurement requirements, the engagement becomes consultation without accountability. For Deaf, DeafBlind, and Hard-of-Hearing people, engagement may reveal barriers in video platforms, captioning, relay compatibility, ASL or LSQ access, DeafBlind communication supports, customer support, emergency communication, AI tools, or digital applications. These findings should directly shape the procurement strategy, evaluation criteria, cost estimates, timelines, and contract obligations. This change would ensure that engagement information is used to prevent barriers before goods or services are purchased.
Heading text
11.4.2 Information from engagement activities
Heading number portion
11.4.2
Item id
1782228201689_130
Heading id
11.4.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC supports Clause 11.4.3 and recommends strengthening it to more fully address communication access for Deaf, DeafBlind, and Hard-of-Hearing participants. The clause should expand the list of communication requirements beyond simultaneous interpretation, real-time captioning, ASL, and LSQ to include DeafBlind communication supports, Indigenous Sign Languages where applicable, relay-compatible communication, accessible video communication, interpreter preparation materials, and accessible troubleshooting during the engagement activity.
What should we change it to?
What should we change it to? Add language stating that communication requirements may include: * ASL; * LSQ; * Indigenous Sign Languages where applicable; * DeafBlind communication supports; * tactile sign language; * intervenor services; * real-time captioning; * transcripts; * relay-compatible communication; * accessible chat or text functions; * accessible video communication; * interpreter pinning or spotlighting; * clear camera framing, lighting, contrast, and video quality; * preparation materials for interpreters, captioners, DeafBlind intervenors, and participants. Add language stating that all required documents should be provided early enough for meaningful review and preparation. Two business days should be treated as a minimum, not the default, especially for complex procurement materials, technical terminology, ASL/LSQ interpretation, DeafBlind supports, or captioning preparation. Add language stating that the remediation protocol should identify a person with authority to fix access barriers in real time, pause the engagement if communication access fails, and ensure that no procurement decision is finalized based on an inaccessible engagement process.
Why should we change it?
Why should we change it? Identifying accommodation needs is essential, but effective participation requires more than asking participants what they need. Organizers must plan, test, and maintain communication access before and during the engagement. For Deaf, DeafBlind, and Hard-of-Hearing participants, barriers may arise from missing interpreters, poor video quality, captions that are delayed or inaccurate, lack of DeafBlind supports, inaccessible chat, no relay compatibility, unavailable preparation materials, or no person with authority to fix access failures in real time. If communication access fails during an engagement activity, the information gathered may be incomplete or unreliable. This can lead to procurement requirements that miss DDBHH barriers and result in inaccessible goods, services, systems, or contracts. Strengthening this clause would help ensure that engagement activities provide meaningful participation, not only formal accommodation.
Heading text
11.4.3 Identifying accommodation needs
Heading number portion
11.4.3
Item id
1782228330090_42
Heading id
11.4.4
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.4 to clarify that in-person engagement accessibility includes communication access, not only physical access to facilities. In-person engagement must support Deaf, DeafBlind, and Hard-of-Hearing participants through accessible room setup, sightlines, lighting, interpreter placement, captioning equipment, DeafBlind communication supports, visual emergency information, and hybrid access where needed.
What should we change it to?
What should we change it to? Add language stating that in-person engagement planning shall include communication-access requirements such as: * ASL and LSQ interpreter placement; * DeafBlind communication supports; * tactile sign language or intervenor space where needed; * real-time captioning equipment and screen visibility; * clear sightlines to presenters, interpreters, captioning, and visual materials; * appropriate lighting and contrast; * reduced background noise and visual distractions; * accessible seating near interpreters, captionists, support persons, or note takers; * accessible power and internet access for assistive technology; * visual and tactile emergency information; * hybrid participation options where in-person access is not effective. Add language stating that organizers should test the room setup before the event begins and fix communication-access barriers before proceeding.
Why should we change it?
Why should we change it? In-person accessibility is often understood mainly as physical access, but Deaf, DeafBlind, and Hard-of-Hearing participants also require communication access. A room may be physically accessible while still being inaccessible because of poor lighting, blocked sightlines, poor interpreter placement, no captioning screen, no DeafBlind supports, unclear emergency procedures, or inaccessible hybrid connection. For DDBHH participants, visual and tactile communication conditions are essential. If communication access is not built into the room setup, engagement may be inaccessible even when accommodations were formally arranged. This change would help ensure that in-person engagement activities provide meaningful participation and reliable accessibility input for procurement decisions.
Heading text
11.4.4 In-person engagement
Heading number portion
11.4.4
Item id
1782228454985_753
Heading id
11.4.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.4.1 to clarify that accessible in-person engagement requires both facility accessibility and communication access. The clause should not only expand on the need to ask attendees about accommodation requirements. It should also require organizers to proactively design in-person engagement so that Deaf, DeafBlind, and Hard-of-Hearing participants can participate effectively.
What should we change it to?
What should we change it to? Add language stating that accessible in-person engagement includes communication-access planning, including ASL, LSQ, DeafBlind communication supports, real-time captioning, accessible seating, clear sightlines, appropriate lighting, interpreter placement, captioning screen visibility, accessible emergency information, and space for support persons, intervenors, captionists, and interpreters. Add language stating that organizers should not rely only on individual accommodation requests. They should proactively plan common accessibility measures that support participants who may not feel safe disclosing disability or accommodation needs. Add language stating that room setup and communication access should be checked before the engagement begins.
Why should we change it?
Why should we change it? In-person events can be inaccessible even when the facility itself is physically accessible. Deaf, DeafBlind, and Hard-of-Hearing participants may face barriers if interpreters are poorly placed, lighting is inadequate, captioning is not visible, sightlines are blocked, DeafBlind supports are not planned, or emergency information is audio-only. Asking about accommodation needs is important, but it is not enough. Organizers should proactively design in-person engagement so that communication access is built into the event. This change would help ensure that in-person engagement activities produce meaningful participation and reliable accessibility input for procurement decisions.
Heading text
11.4.4.1 General
Heading number portion
11.4.4.1
Item id
1782228699336_590
Heading id
11.4.4.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
DWCC recommends strengthening Clause 11.4.4.2 to require that in-person facility assessments include communication-access conditions for Deaf, DeafBlind, and Hard-of-Hearing participants. The site assessment should not be limited to physical access. It should also assess whether the space supports visual language, captioning, DeafBlind communication supports, accessible emergency information, interpreter placement, and hybrid or virtual participation where needed.
What should we change it to?
Add language stating that a facility assessment shall include review of communication-access conditions, including: * clear sightlines to presenters, interpreters, captioning screens, and visual materials; * appropriate lighting, contrast, and camera visibility; * space for ASL, LSQ, and DeafBlind communication supports; * space for interpreters, captionists, intervenors, support persons, and assistive technology; * availability of reliable internet and power; * reduced background noise and visual distractions; * visual and tactile emergency alerts or procedures; * accessible seating locations; * hybrid access where in-person participation is not effective; * procedures to fix communication-access barriers before or during the event.
Why should we change it?
A facility can meet physical accessibility requirements but still be inaccessible for Deaf, DeafBlind, and Hard-of-Hearing participants. Poor lighting, blocked sightlines, lack of captioning screen visibility, no DeafBlind support space, weak internet, poor interpreter placement, or audio-only emergency information can prevent meaningful participation. Facility assessment should therefore include communication access as part of accessibility, not as a separate afterthought. This change would help ensure that in-person outreach sessions and procurement engagement activities are accessible in practice.
Heading text
11.4.4.2 Facility assessment
Heading number portion
11.4.4.2
Item id
1782228789801_290
Heading id
11.4.4.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
DWCC recommends strengthening Clause 11.4.4.3 to clarify that access to facilities for in-person engagement should include access to the communication-access environment inside the facility, not only exterior circulation and vehicular access. Physical entry into a facility does not guarantee meaningful participation if Deaf, DeafBlind, and Hard-of-Hearing participants cannot access interpreters, captioning, visual information, DeafBlind supports, or emergency communication once inside.
What should we change it to?
What should we change it to? Add language stating that access to facilities should include accessible routes to meeting rooms, registration desks, information desks, interpreter locations, captioning displays, support-person seating, DeafBlind communication-support areas, assistive technology locations, washrooms, emergency exits, and accessible transportation or pickup/drop-off points. Add language stating that wayfinding and event information should include visual, plain language, and accessible digital information, and should not rely only on audio announcements or spoken directions.
Why should we change it?
A facility can meet physical accessibility requirements but still be inaccessible for Deaf, DeafBlind, and Hard-of-Hearing participants. Poor lighting, blocked sightlines, lack of captioning screen visibility, no DeafBlind support space, weak internet, poor interpreter placement, or audio-only emergency information can prevent meaningful participation. Facility assessment should therefore include communication access as part of accessibility, not as a separate afterthought. This change would help ensure that in-person outreach sessions and procurement engagement activities are accessible in practice.
Heading text
11.4.4.3 Access to facilities
Heading number portion
11.4.4.3
Item id
1782228895542_103
Heading id
11.4.4.4
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.4.4 to include facility specifications that support communication access for Deaf, DeafBlind, and Hard-of-Hearing participants. The current list includes important built-environment requirements, but it should more clearly address visual communication, tactile communication, captioning visibility, interpreter visibility, visual alerts, and accessible event information.
What should we change it to?
What should we change it to? Add language stating that facility specifications for in-person engagement should include: * clear sightlines to presenters, interpreters, captioning screens, visual materials, and emergency information; * appropriate lighting for ASL, LSQ, and visual communication; * visual contrast that supports sign-language visibility, captioning, wayfinding, and written information; * space and seating for DeafBlind communication supports, intervenors, support persons, interpreters, and captionists; * reliable power and internet access for captioning, interpreting, relay-compatible communication, and assistive technology; * visual and tactile alerts for emergency and safety information; * accessible information desks or registration points with text-based or visual communication options; * signage that does not rely on audio announcements alone. Add language stating that public telephones should not be treated as sufficient communication access for DDBHH participants unless accessible alternatives are also available, such as text-based contact, relay-compatible communication, video relay compatibility, or accessible digital contact options.
Why should we change it?
Why should we change it? A facility may meet general built-environment requirements but still fail to support DDBHH communication access. Deaf participants may need clear sightlines, lighting, and interpreter visibility. DeafBlind participants may need tactile communication space, support-person seating, and accessible wayfinding. Hard-of-Hearing participants may need captioning, assistive listening systems, reduced background noise, and visual information. In-person engagement cannot be considered accessible if participants can enter the building but cannot follow the meeting, receive emergency information, communicate with organizers, or access support services. This change would make facility specifications more complete and would better support meaningful participation in procurement engagement activities.
Heading text
11.4.4.4 Facility specifications
Heading number portion
11.4.4.4
Item id
1782229028867_135
Heading id
11.4.4.5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC supports Clause 11.4.4.5 and recommends strengthening it to ensure meeting rooms are designed for effective visual, tactile, and captioned communication. Meeting rooms should not only provide space for interpreters and captioning equipment. They should also ensure clear sightlines, lighting, video visibility, interpreter placement, captioning screen visibility, DeafBlind communication supports, and seating arrangements that allow Deaf, DeafBlind, and Hard-of-Hearing participants to participate fully.
What should we change it to?
What should we change it to? Add language stating that meeting rooms used for in-person outreach events shall provide: * clear sightlines to presenters, interpreters, captioning screens, visual materials, and participants; * appropriate lighting for ASL, LSQ, and visual communication; * interpreter placement that allows Deaf participants to see both the interpreter and visual materials; * captioning display screens that are visible from accessible seating areas; * space for DeafBlind communication supports, intervenors, tactile communication, support persons, and assistive technology; * seating arrangements that support visual communication and reduce the need to turn away from interpreters, captioning, or presenters; * reliable power and internet access for captioning, interpreting, relay-compatible communication, and hybrid access; * visual emergency information inside the room; * procedures to adjust the room setup if communication access is not effective.
Why should we change it?
Why should we change it? A meeting room can technically include interpreters or captioning equipment but still be inaccessible if sightlines are blocked, lighting is poor, captions are not visible, interpreters are placed too far away, or DeafBlind communication supports do not have enough space. For DDBHH participants, room design directly affects whether engagement is meaningful. ASL and LSQ require clear visual access. DeafBlind participants may require tactile communication, intervenor support, close seating, and accessible movement through the room. Hard-of-Hearing participants may require captioning, assistive listening systems, reduced background noise, and clear visual information. This change would ensure that meeting rooms support actual participation, not only the formal presence of accessibility services.
Heading text
11.4.4.5 Meeting rooms
Heading number portion
11.4.4.5
Item id
1782229936194_853
Heading id
11.4.4.6
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.4.6 to include accessible emergency communication for Deaf, DeafBlind, and Hard-of-Hearing participants. Emergency egress planning should not rely only on audio alarms, spoken instructions, or a list of individual evacuation needs. It should include visual, tactile, text-based, and communication-access procedures.
What should we change it to?
What should we change it to? Add language stating that facility emergency egress plans for in-person events shall include accessible emergency communication, including visual alerts, tactile alerts where appropriate, text-based instructions, accessible digital alerts, clear visual signage, and procedures for communicating with Deaf, DeafBlind, and Hard-of-Hearing participants during an emergency. Add language stating that emergency information should be provided in advance and during the event in accessible formats and communication methods. Add language stating that organizers should ensure interpreters, captionists, intervenors, support persons, and event staff understand emergency communication procedures and how to support DDBHH participants during evacuation or shelter-in-place situations. Add language stating that participant evacuation information must be handled with privacy and confidentiality safeguards.
Why should we change it?
Why should we change it? Emergency egress is not accessible if emergency information is only provided by sound, voice announcements, or spoken instructions. Deaf, DeafBlind, and Hard-of-Hearing participants may not hear alarms, instructions, or updates during an emergency. For DDBHH participants, safety communication must be visual, tactile, text-based, and accessible in real time. This includes emergency alerts, evacuation instructions, shelter-in-place instructions, route changes, and instructions from staff or facility managers. This change would help ensure that emergency egress protects communication access and safety for all participants, not only physical movement out of the facility.
Heading text
11.4.4.6 Facility emergency egress
Heading number portion
11.4.4.6
Item id
1782230027111_98
Heading id
11.4.5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.5 to explicitly require virtual engagement platforms and procedures to support Deaf, DeafBlind, and Hard-of-Hearing communication access. Virtual engagement should not rely on audio-only participation, phone-only access, inaccessible video platforms, automatic captions without quality control, or after-the-fact summaries as substitutes for real-time participation.
What should we change it to?
What should we change it to? Add language stating that virtual engagement shall support communication access where applicable, including: * ASL and LSQ interpretation; * Indigenous Sign Languages where applicable; * DeafBlind communication supports; * real-time captioning; * transcripts; * interpreter pinning or spotlighting; * stable video quality; * screen layout control; * accessible chat or text functions; * relay-compatible communication; * keyboard navigation; * accessible platform controls; * preparation materials for interpreters, captioners, DeafBlind intervenors, and participants; * real-time troubleshooting procedures. Add language stating that organizers should test the virtual platform, captioning, interpreter visibility, relay compatibility, chat access, screen sharing, and recording or transcript access before the engagement begins. Add language stating that if communication access fails during a virtual engagement, organizers should pause, fix the barrier, document the issue, and ensure that procurement decisions are not based on inaccessible participation.
Why should we change it?
Why should we change it? Virtual engagement can improve access, but only if it is designed correctly. For DDBHH participants, poor video quality, missing captions, inaccessible chat, inability to pin interpreters, lack of relay compatibility, audio-only instructions, or weak troubleshooting can make participation ineffective. ASL and LSQ require clear, stable visual access. DeafBlind participants may require specific communication supports. Hard-of-Hearing participants may require accurate real-time captioning and accessible audio controls. Because procurement engagement shapes requirements, inaccessible virtual engagement can lead directly to inaccessible procurement outcomes. This change would help ensure that virtual engagement produces reliable input and meaningful participation.
Heading text
11.4.5 Virtual engagement
Heading number portion
11.4.5
Item id
1782230134586_779
Heading id
11.4.5.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.5.1 to clarify that virtual engagement accessibility must include real-time communication access for Deaf, DeafBlind, and Hard-of-Hearing participants. Digital accessibility and accommodations are important, but virtual engagement must also support visual language, captioning, relay-compatible communication, DeafBlind communication supports, accessible video interaction, and real-time troubleshooting.
What should we change it to?
What should we change it to? Add language stating that virtual engagement activities shall be designed to support effective real-time communication access, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, real-time captioning, transcripts, accessible chat or text functions, relay-compatible communication, stable video quality, interpreter pinning or spotlighting, screen layout control, and accessible platform controls. Add language stating that organizers should not assume that a virtual platform is accessible because it has basic digital accessibility features. The platform must be tested for practical communication access before the event begins.
Why should we change it?
Why should we change it? Virtual events can still exclude Deaf, DeafBlind, and Hard-of-Hearing participants if communication access is not planned. A platform may allow people to log in but still fail because captions are inaccurate, interpreters cannot be pinned, video quality is unstable, chat is inaccessible, relay services do not work properly, or participants cannot control the screen layout. For DDBHH participants, virtual engagement must support real-time participation, not just passive viewing or after-the-fact summaries. This change would help ensure that virtual engagement activities are accessible in practice and produce reliable input for procurement decisions.
Heading text
11.4.5.1 General
Heading number portion
11.4.5.1
Item id
1782230260286_333
Heading id
11.4.5.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.5.2 to specify practical communication-access requirements for virtual engagement. The clause should not rely only on general relay services and web platform compliance. It should require virtual engagement to support real-time participation by Deaf, DeafBlind, and Hard-of-Hearing participants.
What should we change it to?
What should we change it to? Add language stating that if an engagement event is hosted virtually, the organizer shall ensure the platform and event procedures support: * ASL and LSQ interpretation; * Indigenous Sign Languages where applicable; * DeafBlind communication supports; * real-time captioning; * transcripts; * relay-compatible communication; * interpreter pinning or spotlighting; * stable video quality; * screen layout control; * accessible chat and text functions; * keyboard navigation; * accessible screen sharing; * accessible documents; * accessible identity verification or login procedures; * real-time troubleshooting if communication access fails. Add language stating that relay services should include compatibility with video relay services, text relay, IP relay, and other relay or intermediary communication services where applicable. Add language stating that phone-only access, audio-only instructions, automatic captions without quality control, or inaccessible video platforms should not be considered sufficient virtual engagement access.
Why should we change it?
Why should we change it? Virtual engagement accessibility depends on real-time communication access. For DDBHH participants, a platform may technically comply with some digital accessibility requirements but still be inaccessible if interpreters cannot be pinned, captions are inaccurate, relay services do not work, video quality is poor, chat is inaccessible, or login procedures assume hearing or speech. Procurement engagement shapes requirements and decisions. If virtual engagement is inaccessible, DDBHH input may be excluded and the procurement may proceed with incomplete understanding of accessibility barriers. This change would make virtual engagement requirements more practical, testable, and reliable.
Heading text
11.4.5.2 Virtual engagement requirements
Heading number portion
11.4.5.2
Item id
1782230407590_587
Heading id
11.4.5.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 11.4.5.3 by requiring event testing, not only recommending it, when accessibility accommodations or communication access are needed for virtual engagement. The clause should specifically require testing of DDBHH communication access, including ASL, LSQ, captioning, relay compatibility, accessible video quality, chat access, screen sharing, interpreter visibility, and troubleshooting procedures.
What should we change it to?
What should we change it to? Change “should” to “shall” where identified accessibility needs or communication-access requirements are present. Add language stating that the organizer shall complete a run-through with sufficient lead time to test: * ASL and LSQ interpreter visibility; * interpreter pinning or spotlighting; * real-time captioning quality; * relay-compatible communication; * accessible chat and text functions; * screen sharing and visual materials; * platform login and identity verification; * stable video quality; * audio and caption synchronization; * DeafBlind communication supports where applicable; * recording, transcript, or follow-up access where applicable; * real-time troubleshooting and escalation procedures. Add language stating that if testing identifies barriers, the organizer shall fix them before the event or provide an effective alternative before proceeding.
Why should we change it?
Why should we change it? For Deaf, DeafBlind, and Hard-of-Hearing participants, virtual engagement can fail even when accommodations have been arranged. Captions may not work, interpreters may not be visible, relay access may fail, video quality may be unstable, screen sharing may block interpreter views, or chat may be inaccessible. Testing after the event starts is too late. If communication access fails during a procurement engagement activity, DDBHH participants may miss important information, be unable to ask questions, or be excluded from shaping procurement requirements. Requiring event testing where access needs are identified would help ensure meaningful participation and prevent inaccessible engagement from producing incomplete procurement decisions.
Heading text
11.4.5.3 Event testing
Heading number portion
11.4.5.3
Item id
1782238711884_523
Heading id
s11
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Section 12 to state that accessibility, including communication access, must be identified and built into procurement planning before requirements, budgets, timelines, evaluation criteria, testing methods, and contract terms are finalized. Planning a procurement should include early assessment of whether the good, service, system, platform, application, or contract may affect Deaf, DeafBlind, or Hard-of-Hearing users.
What should we change it to?
What should we change it to? Add language stating that procurement planning shall include an early accessibility impact assessment. Where the procurement may affect DDBHH users, the planning process shall consider ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital interaction. Add language stating that clients should consult affected users and relevant accessibility subject-matter experts before finalizing procurement requirements. Add language stating that planning should identify accessibility requirements, testing requirements, evaluation criteria, remediation obligations, contract deliverables, support obligations, and outcome measures before solicitation documents are released.
Why should we change it?
Why should we change it? Planning is the stage where barriers are either prevented or purchased. If accessibility is not included during planning, organizations may define requirements, budgets, timelines, and evaluation criteria in ways that exclude DDBHH communication access. For Deaf, DeafBlind, and Hard-of-Hearing people, missing planning requirements can lead to inaccessible video platforms, phone-only customer support, missing captions, no ASL or LSQ access, inaccessible emergency communication, no relay compatibility, inaccessible public-facing digital services, or AI tools that are not tested with affected users. This change would help ensure that accessibility is treated as a core planning requirement and not added later as an individual accommodation or remediation problem.
Heading text
12. Planning a procurement
Heading number portion
12.
Item id
1782238842745_2
Heading id
12.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 12.1 to explicitly require clients to assess whether the procurement may affect communication access for Deaf, DeafBlind, or Hard-of-Hearing users before requirements are finalized. The clause should also clarify that consultation with end users and subject-matter experts must include relevant lived experience and expertise. Where DDBHH users may be affected, this should include Deaf, DeafBlind, Hard-of-Hearing, ASL, LSQ, DeafBlind communication access, telecom, digital accessibility, emergency communication, and accessible procurement expertise.
What should we change it to?
What should we change it to? Add language stating that, when defining requirements, clients shall assess whether the procurement may affect communication access, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital interaction. Add language stating that clients shall consult affected users and relevant accessibility subject-matter experts before finalizing requirements where a procurement affects DDBHH users. Add language stating that accessibility conformance testing should include user testing with affected users, not only vendor claims or technical documentation. Add language stating that curated source lists should include Deaf-led organizations, DeafBlind organizations, DDBHH accessibility evaluators, and suppliers with demonstrated communication-access expertise. Add language stating that engagement with industry should not replace consultation with affected users and disability-led subject-matter experts.
Why should we change it?
Why should we change it? Defining requirements is the point where accessibility is either built into the procurement or lost before the solicitation is released. If DDBHH communication access is not identified at this stage, it may be excluded from evaluation criteria, testing, contract terms, pricing, and implementation. For Deaf, DeafBlind, and Hard-of-Hearing people, missing requirements can lead to phone-only support, inaccessible video platforms, missing captions, no ASL or LSQ access, no DeafBlind communication supports, inaccessible emergency communication, weak relay compatibility, and AI-enabled tools that are not tested with affected users. This change would help ensure that procurement requirements are defined with the people most affected by the barriers and that communication access is treated as a core requirement from the beginning.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782238965079_168
Heading id
12.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC supports Clause 12.1.1 and recommends strengthening it to explicitly recognize communication-related accommodation procurement for Deaf, DeafBlind, and Hard-of-Hearing individuals. The clause should clarify that individual accommodation procurement may include ASL or LSQ interpretation, DeafBlind communication supports, video remote interpreting, relay-compatible services, captioning, accessible video communication tools, assistive technologies, and service providers familiar with the individual’s communication needs.
What should we change it to?
What should we change it to? Add language stating that individual accommodation procurement may include communication-access goods and services, including qualified sign language interpreters, ASL services, LSQ services, DeafBlind intervenor services, tactile communication supports, captioning, relay-compatible communication tools, video remote interpreting, accessible video communication platforms, and other individualized communication supports. Add language stating that evaluation may consider communication preference, language match, provider familiarity, cultural and linguistic competence, confidentiality, trust, urgency, continuity of service, and compatibility with the individual’s work, service, or participation needs. Add language stating that procurement rules shall not delay or prevent timely and effective accommodation where delay would create barriers, deny participation, or undermine the individual’s dignity and autonomy.
Why should we change it?
Why should we change it? DWCC supports the recognition that standard competitive procurement rules may need flexibility for individual accommodations. This is especially important for Deaf, DeafBlind, and Hard-of-Hearing people because communication access often depends on language match, provider familiarity, trust, timing, and compatibility. For example, an ASL user, LSQ user, or DeafBlind person may require a specific interpreter, intervenor, captioning provider, relay-compatible solution, or communication-access tool to participate effectively. A lowest-cost or generic procurement approach may not meet the person’s actual communication needs. This change would help ensure that individual accommodation procurement is timely, effective, person-centred, and consistent with dignity and autonomy.
Heading text
12.1.1 Exception - Individual accommodation procurement
Heading number portion
12.1.1
Item id
1782239084104_920
Heading id
12.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 12.2 to require accessibility testing with affected users where a procurement may affect Deaf, DeafBlind, or Hard-of-Hearing people. Vendor demonstrations, self-declarations, and general third-party testing should not be the only evidence used to determine accessibility. Testing should include practical communication-access testing with relevant users and subject-matter experts.
What should we change it to?
What should we change it to? Add language stating that clients shall identify requirements for user testing with affected people with disabilities where the good or service may affect accessibility. Where a procurement may affect DDBHH users, testing should include ASL users, LSQ users, DeafBlind users, Hard-of-Hearing users, and relevant communication-access experts where applicable. Add language stating that testing should assess practical usability of: * captioning; * transcripts; * ASL and LSQ access; * DeafBlind communication supports; * relay-compatible communication; * accessible video communication; * visual and tactile alerts; * accessible emergency communication; * accessible customer support; * AI-enabled transcription, captioning, sign-language, avatar, or automated support tools; * digital forms, login, identity verification, chat, help desk, and complaint processes. Add language stating that bidders should provide verifiable evidence of accessibility, such as accessibility conformance reports, testing results, user-testing results, remediation plans, and documentation of known limitations.
Why should we change it?
Why should we change it? Accessibility cannot be confirmed only by vendor claims or a short demonstration. Many DDBHH barriers appear during real use: captions may be inaccurate, relay services may not function, video quality may not support sign language, customer support may require phone calls, emergency alerts may be audio-only, or AI tools may fail for ASL, LSQ, or DeafBlind users. Testing with affected users helps reveal these barriers before a contract is awarded. This is especially important for public-facing services, telecom services, emergency communication systems, digital platforms, education, employment, health, transportation, and AI-enabled tools. This change would help ensure that accessibility testing measures real-world usability and prevents barriers before goods or services are purchased.
Heading text
12.2 Identifying requirements for testing
Heading number portion
12.2
Item id
1782239192915_457
Heading id
12.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 12.3 to clarify that solicitation documents and amendments must include clear accessibility and communication-access requirements, not only comply with accessible document-format requirements under Clause 11. Solicitation documents should clearly state what accessibility requirements bidders must meet, how accessibility will be evaluated, what evidence is required, and what remediation obligations will apply if accessibility barriers are identified.
What should we change it to?
What should we change it to? Add language stating that solicitation documents shall identify applicable accessibility requirements, communication-access requirements, evaluation criteria, testing requirements, evidence requirements, accessibility cost treatment, reporting obligations, and remediation expectations. Where the procurement may affect Deaf, DeafBlind, or Hard-of-Hearing users, solicitation documents should identify requirements related to ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital interaction. Add language stating that amendments to solicitation documents shall also be provided in accessible formats and shall clearly identify any changes affecting accessibility requirements, timelines, testing, evaluation, or contract deliverables.
Why should we change it?
Why should we change it? If accessibility requirements are not clearly stated in solicitation documents, bidders may not understand what they must deliver and evaluators may not have a clear basis for assessing accessibility. This can lead to vendor claims of accessibility without evidence, weak testing, unclear pricing, and inaccessible contract deliverables. For Deaf, DeafBlind, and Hard-of-Hearing users, missing solicitation requirements can result in inaccessible video platforms, phone-only customer support, missing captioning, no ASL or LSQ access, weak relay compatibility, inaccessible emergency communication, and AI tools that are not tested with affected users. This change would help ensure that accessibility is defined before bids are submitted and before contracts are awarded.
Heading text
12.3 Preparing solicitation documents
Heading number portion
12.3
Item id
1782239315211_684
Heading id
12.4
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 12.4 to require that accessibility evaluation be planned before solicitation documents are released and before bids are received. Evaluation planning should identify who will evaluate accessibility, what evidence bidders must provide, how accessibility will be scored or assessed, how user testing will be conducted, and how communication-access requirements will be evaluated where Deaf, DeafBlind, or Hard-of-Hearing users may be affected.
What should we change it to?
What should we change it to? Add language stating that evaluation planning shall include: * accessibility evaluation criteria; * required bidder evidence; * user testing requirements; * accessibility conformance testing; * communication-access testing; * qualified accessibility evaluators; * sufficient evaluation time; * conflict-of-interest safeguards; * procedures for resolving accessibility concerns before award. Where the procurement may affect DDBHH users, evaluation planning should include Deaf, DeafBlind, and Hard-of-Hearing evaluators or subject-matter experts with relevant expertise in ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and digital accessibility. DWCC also recommends that federal procurement authorities develop and maintain regional rosters of qualified Deaf, DeafBlind, and Hard-of-Hearing accessibility evaluators to support procurement evaluation across Canada.
Why should we change it?
Why should we change it? Accessibility evaluation cannot be improvised after bids are submitted. If evaluation planning does not include relevant expertise, sufficient time, clear criteria, and user testing, inaccessible goods or services may be selected based on incomplete vendor claims. For Deaf, DeafBlind, and Hard-of-Hearing users, accessibility may depend on practical details that general evaluators may miss, including caption quality, sign-language visibility, relay compatibility, video quality, emergency communication, customer support, login processes, AI transcription accuracy, and DeafBlind access. This change would help ensure that accessibility is evaluated by people with relevant expertise before contracts are awarded, preventing barriers from being purchased.
Heading text
12.4 Planning the evaluation
Heading number portion
12.4
Item id
1782239464740_635
Heading id
12.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 12.4.1 to clarify that the “best responsive bid” must include responsiveness to accessibility requirements. A bid should not be considered responsive if it does not meet mandatory accessibility requirements, does not provide required accessibility evidence, or does not demonstrate capacity to meet communication-access requirements where Deaf, DeafBlind, or Hard-of-Hearing users may be affected.
What should we change it to?
Why should we change it? If accessibility is not part of responsiveness, accessibility may be treated as secondary to price, schedule, or general technical features. This can result in the selection of goods or services that meet business requirements but create barriers for people with disabilities. For Deaf, DeafBlind, and Hard-of-Hearing users, a bid may appear technically strong but still fail communication access through missing captions, no ASL or LSQ access, no relay compatibility, inaccessible video, phone-only support, inaccessible emergency communication, or AI tools that are not tested with affected users. This change would help ensure that accessibility is evaluated as part of bid responsiveness, not as an optional feature after award.
Why should we change it?
Why should we change it? If accessibility is not part of responsiveness, accessibility may be treated as secondary to price, schedule, or general technical features. This can result in the selection of goods or services that meet business requirements but create barriers for people with disabilities. For Deaf, DeafBlind, and Hard-of-Hearing users, a bid may appear technically strong but still fail communication access through missing captions, no ASL or LSQ access, no relay compatibility, inaccessible video, phone-only support, inaccessible emergency communication, or AI tools that are not tested with affected users. This change would help ensure that accessibility is evaluated as part of bid responsiveness, not as an optional feature after award.
Heading text
12.4.1 General
Heading number portion
12.4.1
Item id
1782239587226_572
Heading id
12.4.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 12.4.2 to clarify that sufficient evaluation time must include time for accessibility testing, communication-access testing, user testing with affected users, and review by relevant accessibility subject-matter experts. Where a procurement may affect Deaf, DeafBlind, or Hard-of-Hearing users, the evaluation timeline should allow enough time to assess practical communication access, not only written bid responses.
What should we change it to?
What should we change it to? Add language stating that sufficient evaluation time shall include time for: * accessibility conformance review; * demonstrations; * user testing with affected users; * communication-access testing; * review by relevant accessibility subject-matter experts; * review of bidder evidence; * clarification of accessibility claims; * testing of remediation plans or roadmaps where applicable. Where DDBHH users may be affected, the timeline should allow time to test captioning, ASL and LSQ access, DeafBlind communication supports, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and AI-enabled accessibility features where applicable.
Why should we change it?
Why should we change it? Accessibility evaluation takes time. If evaluation timelines are too short, evaluators may rely on vendor claims instead of testing whether the good or service works for affected users. For DDBHH users, real accessibility may depend on details that require testing: caption accuracy, interpreter visibility, relay compatibility, video quality, emergency alerts, customer support pathways, login processes, and AI transcription or captioning performance. This change would help ensure that evaluation timelines allow accessibility to be assessed properly before contract award.
Heading text
12.4.2 Determining the evaluation timeline
Heading number portion
12.4.2
Item id
1782239728613_71
Heading id
12.4.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC strongly supports Clause 12.4.3 and recommends strengthening it to require that evaluation panels include relevant lived experience and subject-matter expertise for the accessibility requirements being evaluated. Where a procurement may affect Deaf, DeafBlind, or Hard-of-Hearing users, the evaluation panel should include Deaf, DeafBlind, and Hard-of-Hearing evaluators or subject-matter experts with relevant communication-access expertise.
What should we change it to?
What should we change it to? Add language stating that evaluation panels shall include people with relevant lived experience and subject-matter expertise where accessibility requirements affect specific disability communities. Where the procurement may affect DDBHH users, evaluation panels should include qualified Deaf, DeafBlind, or Hard-of-Hearing evaluators with relevant expertise in ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, telecom services, digital accessibility, and AI-enabled accessibility tools. DWCC further recommends that Accessibility Standards Canada and federal procurement authorities develop and maintain regional rosters of qualified Deaf, DeafBlind, and Hard-of-Hearing accessibility evaluators to support procurement evaluation across Canada, province by province and region by region. This would help ensure that accessibility evaluation is not concentrated only in Ottawa or limited to general disability expertise.
Why should we change it?
Why should we change it? Evaluation panels determine whether accessibility requirements are actually understood and applied before a contract is awarded. General accessibility expertise is important, but it is not always enough to evaluate DDBHH communication access. For Deaf, DeafBlind, and Hard-of-Hearing users, accessibility may depend on practical communication details such as caption quality, sign-language visibility, relay compatibility, video quality, DeafBlind communication supports, emergency communication, customer support pathways, and AI transcription or captioning accuracy. Including qualified DDBHH evaluators would improve procurement decisions, reduce the risk of purchasing inaccessible systems, and support the principle that affected users should have meaningful decision-making roles in accessibility evaluation.
Heading text
12.4.3 Identifying the evaluation panel
Heading number portion
12.4.3
Item id
1782239919919_593
Heading id
s12
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Section 13 to ensure that bidding and contract award processes do not disadvantage Deaf, DeafBlind, Hard-of-Hearing, disabled, or Deaf-led bidders, and do not weaken accessibility requirements during award. The section should clarify that communication access, accessibility costs, accessible bidder conferences, accessible site visits, accessible amendments, and accessible debriefings are part of fair procurement participation.
What should we change it to?
Add language stating that bidding and contract award processes shall preserve accessibility requirements from the solicitation stage through contract award. Add language stating that bidders should not be penalized for legitimate accessibility-related costs, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, video remote interpreting, relay-compatible communication, accessible video communication, and Deaf-led consultation. Add language stating that bidder conferences, site visits, bidding inquiries, amendments, award notices, and debriefings shall be accessible to Deaf, DeafBlind, and Hard-of-Hearing participants. Add language stating that accessibility commitments made by bidders should become enforceable contract deliverables after award.
Why should we change it?
Why should we change it? Accessibility can be lost during bidding and contract award if it is treated as secondary to price, schedule, or general technical scoring. DDBHH bidders and businesses employing DDBHH people may also be disadvantaged if their communication-access costs are treated as extra costs rather than legitimate accessibility costs. For Deaf, DeafBlind, and Hard-of-Hearing participants, barriers can arise in bidder conferences, site visits, Q&A processes, amendments, contract award notices, and debriefings if these activities rely on spoken communication, phone-only contact, inaccessible documents, missing captions, no ASL or LSQ access, or no relay-compatible communication. This change would help ensure that bidding and contract award processes are fair, accessible, and consistent with the accessibility requirements established earlier in the procurement process.
Heading text
13. Bidding and contract award
Heading number portion
13.
Item id
1782240110240_294
Heading id
13.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 13.1 to clarify that a reasonable solicitation period must include enough time for bidders with disabilities to access, review, understand, and respond to solicitation documents using the communication supports they need. For Deaf, DeafBlind, and Hard-of-Hearing bidders, this may require additional time for ASL, LSQ, DeafBlind communication supports, captioned materials, relay-compatible communication, accessible video support, text-based clarification, and consultation with accessibility advisors or interpreters.
What should we change it to?
What should we change it to? Add language stating that the solicitation period should account for the time required to obtain and review accessible formats and communication-access materials, including ASL summaries, LSQ summaries, captioned video, transcripts, DeafBlind communication supports, and accessible digital formats where applicable. Add language stating that the solicitation period should also account for the time required to request accommodations, arrange interpreters or captioning, use relay-compatible communication, ask questions through accessible channels, attend accessible bidder conferences, and prepare accessibility-related bid content. Add language stating that when significant accessibility-related amendments are issued, the solicitation period should be extended enough to allow bidders using accessible formats or communication supports to review and respond meaningfully.
Why should we change it?
Why should we change it? A solicitation period may meet minimum trade agreement timelines but still be inaccessible if bidders with disabilities do not have enough time to access the solicitation in usable formats and communication methods. For DDBHH bidders, time may be needed to review ASL or LSQ explanations, arrange interpretation, use relay services, review captioned materials, consult with DeafBlind supports, or ask questions through accessible communication channels. If timelines do not account for these needs, DDBHH bidders and businesses employing DDBHH people may be disadvantaged. This change would make solicitation timelines more equitable and would support fair participation in procurement.
Heading text
13.1 Determining the solicitation period
Heading number portion
13.1
Item id
1782240971378_214
Heading id
13.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC strongly supports Clause 13.1.1 and recommends strengthening it to explicitly recognize communication-access costs as legitimate accessibility costs that must not disadvantage bidders. This should include costs related to ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, video remote interpreting, video relay-compatible communication, accessible video communication, text-based support, accessible customer support, and Deaf-led consultation or evaluation.
What should we change it to?
What should we change it to? Add language stating that accommodation-related costs include communication-access costs needed by bidders, employees, subcontractors, consultants, or end users during performance of the work. Add language stating that communication-access costs may include qualified sign language interpreters, ASL services, LSQ services, DeafBlind intervenor services, tactile communication supports, captioning, transcripts, video remote interpreting, relay-compatible communication, accessible meeting platforms, accessible video communication, accessible customer support, and Deaf-led accessibility consultation or testing. Add language confirming that these costs shall not reduce the competitiveness of a financial proposal and shall not be treated as optional extras when they are necessary for accessible contract performance. Add language stating that validation of costs should consider market realities, interpreter availability, regional availability, specialized expertise, preparation time, team interpreting, DeafBlind communication supports, and linguistic or cultural competence.
Why should we change it?
Why should we change it? Disabled bidders and businesses employing disabled people should not be penalized for the cost of participating or performing work accessibly. For Deaf, DeafBlind, and Hard-of-Hearing bidders, communication-access costs are not extra benefits. They are necessary access costs. If these costs are included in the evaluated financial proposal, DDBHH bidders may appear more expensive only because they are including the real cost of accessibility. This creates an inequitable bidding process and discourages accessibility transparency. This change would support fair competition, disability-owned businesses, Deaf-led organizations, and businesses employing DDBHH people. It would also help ensure that accessibility costs are recognized and funded rather than hidden, ignored, or shifted onto disabled participants.
Heading text
13.1.1 Accessibility cost treatment in bidding
Heading number portion
13.1.1
Item id
1782241081504_593
Heading id
13.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 13.2 to state that bidders conferences must provide effective communication access for Deaf, DeafBlind, and Hard-of-Hearing bidders and participants. Simply referring to Clause 11 is useful, but bidders conferences are high-risk communication events where procurement requirements, questions, clarifications, and amendments may be discussed in real time.
What should we change it to?
What should we change it to? Add language stating that bidders conferences shall provide accessible communication options where needed, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, real-time captioning, transcripts, relay-compatible communication, accessible video communication, accessible chat or text functions, and accessible Q&A procedures. Add language stating that organizers should provide agendas, presentation materials, technical terms, procurement documents, speaker names, and acronyms in advance to participants, interpreters, captioners, and DeafBlind communication-support providers. Add language stating that questions and answers from bidders conferences shall be provided afterward in accessible formats and plain language, and where appropriate through captioned video, ASL summaries, LSQ summaries, or transcripts.
Why should we change it?
Why should we change it? Bidders conferences can determine whether a bidder understands the procurement and can compete fairly. If the conference is inaccessible, DDBHH bidders may miss key information, be unable to ask questions, or lose equal access to clarifications. For Deaf, DeafBlind, and Hard-of-Hearing participants, real-time access may require ASL, LSQ, captioning, DeafBlind supports, relay compatibility, accessible video quality, text-based Q&A, and advance materials. This change would make bidders conferences more accessible and would help ensure fair participation in procurement opportunities.
Heading text
13.2 Planning a bidders conference
Heading number portion
13.2
Item id
1782241172020_859
Heading id
13.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 13.3 to clarify that accessible site visits must include communication access for Deaf, DeafBlind, and Hard-of-Hearing participants. Clients and procurement professionals should proactively identify whether the site visit requires ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video participation, accessible safety information, or accessible emergency instructions.
What should we change it to?
What should we change it to? Add language stating that when site visits are required, clients and procurement professionals shall provide accessible communication options where needed, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, transcripts, relay-compatible communication, accessible video communication, and text-based communication. Add language stating that site visit information, safety instructions, emergency procedures, maps, directions, technical explanations, and follow-up questions and answers shall be provided in accessible formats and communication methods. Add language stating that where a site visit cannot be made accessible, an equivalent accessible alternative shall be provided, such as an accessible virtual tour, captioned video walkthrough, ASL or LSQ interpreted walkthrough, accessible written materials, or an individualized accessible briefing.
Why should we change it?
Why should we change it? Site visits can affect a bidder’s ability to understand the procurement and submit a competitive bid. If the site visit is inaccessible, Deaf, DeafBlind, and Hard-of-Hearing bidders may not receive the same information as other bidders. For DDBHH participants, barriers may include spoken-only explanations, audio-only safety instructions, lack of interpreters or captioning, inaccessible emergency information, no relay-compatible contact option, or inaccessible virtual alternatives. This change would help ensure that site visits provide equal access to procurement information and do not disadvantage DDBHH bidders or businesses employing DDBHH people.
Heading text
13.3 Requiring site visits
Heading number portion
13.3
Item id
1782241248914_994
Heading id
13.4
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 13.4 to clarify that responses to bidding inquiries must be accessible to Deaf, DeafBlind, and Hard-of-Hearing bidders and must not rely only on written text where communication access is needed. Written plain language responses are important, but accessible communication may also require captioning, transcripts, ASL or LSQ summaries, relay-compatible communication, accessible video, DeafBlind communication supports, or text-based clarification channels.
What should we change it to?
What should we change it to? Add language stating that responses to bidding inquiries shall be provided in plain language and accessible formats, and where needed through accessible communication methods. Add language stating that where inquiries involve accessibility requirements, communication-access requirements, bidder accommodations, site visits, bidder conferences, amendments, or contract deliverables, the response should clearly explain any impact on accessibility obligations, timelines, evaluation criteria, or bid submission requirements. Add language stating that responses should be shared with all bidders in an accessible manner, while protecting confidentiality where required, so that Deaf, DeafBlind, Hard-of-Hearing, disabled, and Deaf-led bidders receive equal access to procurement clarifications.
Why should we change it?
Why should we change it? Bidding inquiries can affect how bidders understand the solicitation and prepare their responses. If inquiry responses are inaccessible or unclear, DDBHH bidders may not receive the same information as other bidders. For Deaf, DeafBlind, and Hard-of-Hearing bidders, access may require more than a written response. Some may need ASL, LSQ, captioned video, DeafBlind communication supports, relay-compatible communication, or accessible text-based clarification to fully understand the response. This change would help ensure fair access to bidding information and prevent communication barriers during the bidding process.
Heading text
13.4 Responding to bidding inquiries
Heading number portion
13.4
Item id
1782241333991_117
Heading id
13.5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 13.5 to clarify that when a solicitation amendment affects accessibility requirements, communication-access requirements, evaluation criteria, timelines, or bid submission requirements, the remaining bid period must be adjusted to give bidders using accessible formats or communication supports enough time to respond. The clause should also clarify that amendments must be communicated through accessible formats and communication methods, not only standard written notices.
What should we change it to?
What should we change it to? Add language stating that when an amendment affects accessibility or communication-access requirements, clients and procurement professionals shall assess whether the bid period must be extended to allow meaningful review and response by bidders with disabilities. Add language stating that amendments shall be communicated in plain language, accessible formats, and where needed through ASL, LSQ, captioned video, transcripts, DeafBlind communication supports, relay-compatible communication, accessible digital notices, and text-based contact options. Add language stating that amendments should clearly identify any changes to accessibility requirements, communication-access requirements, evaluation criteria, testing requirements, bidder evidence, pricing, timelines, or contract deliverables.
Why should we change it?
Why should we change it? Solicitation amendments can materially change what bidders must understand and submit. If amendments are issued close to the deadline or only in standard written format, Deaf, DeafBlind, Hard-of-Hearing, disabled, and Deaf-led bidders may not have equal time to review, ask questions, arrange communication supports, and update their bids. For DDBHH bidders, meaningful response may require ASL or LSQ review, DeafBlind communication supports, captioned explanations, relay-compatible communication, or accessible clarification processes. This change would help ensure that amendments do not create new barriers during the bidding period.
Heading text
13.5 Amending (or modifying) a solicitation
Heading number portion
13.5
Item id
1782241447894_108
Heading id
13.6
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC supports Clause 13.6 and recommends strengthening it to ensure unsuccessful bidder debriefings provide effective communication access for Deaf, DeafBlind, and Hard-of-Hearing bidders. The clause should clarify that accessible debriefings may require ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, transcripts, relay-compatible communication, accessible video communication, and accessible written follow-up.
What should we change it to?
What should we change it to? Add language stating that accessible debriefings shall provide communication access where required, including qualified ASL or LSQ interpretation, DeafBlind communication supports, real-time captioning, transcripts, relay-compatible communication, accessible video communication, and text-based communication options. Add language stating that sign-language translation or interpretation for debriefings should be provided by qualified providers with appropriate linguistic competence, confidentiality, impartiality, preparation materials, and familiarity with procurement terminology. Add language stating that reasonable time extensions should account for the time needed to arrange interpreters, captioning, DeafBlind communication supports, accessible video debriefs, or sign-language translation. Add language stating that if the bidder raises an accessibility barrier experienced during the procurement process, the debriefing should include a process to document and address that barrier for future procurement improvement.
Why should we change it?
Why should we change it? Debriefings are important for fairness, learning, and accountability. If debriefings are inaccessible, Deaf, DeafBlind, and Hard-of-Hearing bidders may be denied equal opportunity to understand why their bid was unsuccessful, improve future bids, or identify accessibility barriers in the procurement process. For DDBHH bidders, a written debrief alone may not be enough. Effective communication may require ASL, LSQ, captioning, DeafBlind communication supports, relay-compatible communication, accessible video, and enough time to arrange qualified providers. This change would strengthen fairness and ensure that accessibility barriers in the bidding process can be identified, documented, and corrected.
Heading text
13.6 Providing an unsuccessful bidder debriefing
Heading number portion
13.6
Item id
1782241524900_669
Heading id
s13
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Section 14 to clarify that accessibility requirements are enforceable contract deliverables, not optional features or post-award accommodations. Contract management should require clients to monitor, verify, remediate, and report on accessibility throughout the contract, including communication access for Deaf, DeafBlind, and Hard-of-Hearing users.
What should we change it to?
What should we change it to? Add language stating that accessibility requirements included in the solicitation and contract shall be treated as enforceable contract deliverables. Add language stating that contract management shall include monitoring of accessibility performance, user-reported barriers, remediation timelines, accessibility testing, communication-access testing, reporting obligations, and consequences if accessibility requirements are not met. Where the contract affects DDBHH users, contract management should monitor ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital interaction. Add language stating that accessibility failures should be treated as contract performance issues and should be addressed through remediation, corrective action, contract amendments, payment controls, renewal decisions, or other contract remedies where appropriate.
Why should we change it?
Why should we change it? Procurement accessibility does not end when a contract is awarded. Many barriers appear during implementation, updates, service delivery, customer support, emergency communication, and use by end users. For Deaf, DeafBlind, and Hard-of-Hearing users, a contracted service may fail if captions are poor, ASL or LSQ access is missing, relay compatibility does not work, video quality is inadequate, customer support relies on phone calls, emergency communication is not accessible, or AI-enabled tools perform poorly for DDBHH users. This change would ensure that accessibility remains accountable throughout the contract life cycle and that accessibility failures are treated as contract performance issues.
Heading text
14. Contract management
Heading number portion
14.
Item id
1782241646706_810
Heading id
14.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 14.1 to clarify how clients confirm that accessibility requirements are being met throughout the contract. Monitoring should include practical verification, user feedback, accessibility testing, communication-access testing, documentation of barriers, remediation timelines, and confirmation that task authorizations, amendments, renewals, and work orders preserve accessibility requirements.
What should we change it to?
What should we change it to? Add language stating that clients shall monitor accessibility performance through evidence such as testing results, user feedback, accessibility reports, barrier logs, remediation updates, and confirmation of deliverables. Where the contract affects Deaf, DeafBlind, or Hard-of-Hearing users, monitoring should include communication-access performance, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital interaction. Add language stating that accessibility issues identified during the contract shall be tracked with assigned responsibility, timelines for resolution, interim access measures, and confirmation that barriers have been resolved. Add language stating that contract amendments, task authorizations, renewals, extensions, and work orders shall not reduce or bypass accessibility requirements.
Why should we change it?
Why should we change it? Accessibility requirements can fail during implementation even when they appear in the contract. Without active monitoring, barriers may continue for months or years. For DDBHH users, contract failures may include missing or poor captions, inaccessible video communication, no ASL or LSQ access, weak relay compatibility, inaccessible customer support, audio-only emergency alerts, or AI-enabled tools that perform poorly for Deaf, DeafBlind, or Hard-of-Hearing users. This change would make contract monitoring more accountable and would help ensure that accessibility issues are resolved during the contract, not only noticed after harm occurs.
Heading text
14.1 Monitoring contract progress
Heading number portion
14.1
Item id
1782241734529_460
Heading id
14.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 14.2 to clarify that deliverables should not be accepted as complete until accessibility requirements have been verified by people with relevant lived experience and subject-matter expertise. Where deliverables affect Deaf, DeafBlind, or Hard-of-Hearing users, confirmation should include communication-access testing and inspection by DDBHH users or qualified DDBHH accessibility evaluators.
What should we change it to?
What should we change it to? Add language stating that clients shall confirm accessibility deliverables through practical testing, user feedback, accessibility conformance evidence, and inspection by persons with disabilities before acceptance. Where deliverables affect DDBHH users, confirmation should include testing of ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, accessible digital interaction, and AI-enabled accessibility features where applicable. Add language stating that deliverables with unresolved accessibility barriers should not be accepted as complete unless an approved remediation plan, interim access measure, timeline, and accountability mechanism are in place.
Why should we change it?
Why should we change it? A deliverable can appear complete from a technical or administrative perspective while still being inaccessible to affected users. Accessibility must be verified before acceptance, not after users encounter barriers. For Deaf, DeafBlind, and Hard-of-Hearing users, unresolved barriers may include missing captions, poor caption quality, no ASL or LSQ access, inaccessible video communication, no relay compatibility, inaccessible emergency alerts, phone-only customer support, or AI-enabled tools that fail to provide effective communication access. This change would help ensure that accessibility is confirmed before delivery and that clients do not accept inaccessible goods, services, systems, or platforms as complete.
Heading text
14.2 Confirming deliverables
Heading number portion
14.2
Item id
1782241806006_955
Heading id
14.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 14.3 to clarify that end users must have accessible ways to report accessibility issues and that reported issues must be tracked, resolved, and verified with affected users where appropriate. For Deaf, DeafBlind, and Hard-of-Hearing users, the process for reporting and resolving issues must include accessible communication options.
What should we change it to?
What should we change it to? Add language stating that clients shall confirm that contracted businesses provide an accessible process for end users to report accessibility barriers. Where end users include Deaf, DeafBlind, or Hard-of-Hearing people, reporting options should include text-based communication, relay-compatible communication, accessible video communication, ASL or LSQ access where appropriate, DeafBlind communication supports, captioning, and accessible customer support. Add language stating that reported accessibility issues shall be tracked with clear responsibility, timelines for resolution, interim access measures, and confirmation that the barrier has been resolved. Add language stating that end user feedback should be used to improve future procurement requirements, contract terms, testing, and accessibility evaluation.
Why should we change it?
Why should we change it? End users often discover barriers that were missed during procurement, testing, or implementation. If the reporting process is inaccessible, the same users affected by barriers may be unable to report them. For Deaf, DeafBlind, and Hard-of-Hearing users, inaccessible reporting systems may include phone-only support, no relay compatibility, no captioning, no ASL or LSQ access, inaccessible video communication, or customer service that assumes hearing and speech. This change would help ensure that accessibility issues are not only reported, but actually resolved, verified, and used to prevent future barriers.
Heading text
14.3 Resolving end user issues
Heading number portion
14.3
Item id
1782241885967_678
Heading id
14.4
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 14.4 to require organizations to measure whether procured goods and services are actually accessible to end users, including Deaf, DeafBlind, and Hard-of-Hearing users. Outcome measurement should not only track whether accessibility was mentioned in procurement documents. It should measure whether accessibility requirements worked in practice.
What should we change it to?
What should we change it to? Add language stating that procurement outcome measures should include: * whether accessibility requirements were included; * whether accessibility requirements were evaluated; * whether accessibility requirements were included in the contract; * whether accessibility deliverables were tested before acceptance; * whether end users reported barriers; * whether barriers were resolved; * whether accessibility failures affected renewal, payment, remediation, or future procurement decisions. Where procured goods or services affect DDBHH users, outcome measures should track the inclusion and effectiveness of ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, accessible digital interaction, and Deaf-led user testing. Add language stating that organizations should use outcome data to improve future procurement templates, evaluation criteria, accessibility testing, vendor requirements, and contract management.
Why should we change it?
Why should we change it? Accessibility must be measured by outcomes, not only by process. A procurement may include accessibility wording but still fail if the final good or service is not usable by people with disabilities. For Deaf, DeafBlind, and Hard-of-Hearing users, real outcomes include whether communication access works, whether captions are accurate, whether ASL or LSQ access is available, whether relay communication works, whether emergency information is accessible, whether customer support can be used without phone-only barriers, and whether digital platforms support accessible interaction. This change would help organizations identify whether accessible procurement is preventing barriers or simply documenting accessibility intentions.
Heading text
14.4 Measuring procurement outcomes
Heading number portion
14.4
Item id
1782241963094_303
Heading id
s14
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Section 15 to require accessible procurement training to include communication access for Deaf, DeafBlind, and Hard-of-Hearing people. Training should not only cover general disability awareness, plain language, accessible documents, or accessible engagement. It should also train procurement professionals, clients, service-design teams, and senior management on DDBHH communication-access requirements and how to include them in procurement.
What should we change it to?
What should we change it to? Add language stating that training shall include: * Deaf cultural competence; * DeafBlind communication access; * the difference between ASL, LSQ, English, and French access; * Indigenous Sign Languages where applicable; * captioning and transcript requirements; * relay-compatible communication; * video relay service and video remote interpreting compatibility; * accessible video communication; * accessible emergency communication; * accessible customer support; * how to procure qualified interpreters, captioners, DeafBlind intervenors, and communication-access providers; * how to include communication access in specifications, evaluation criteria, testing, contract deliverables, and contract management; * how to avoid treating sign language, captioning, relay, or DeafBlind supports as afterthoughts; * how to assess AI-enabled tools involving transcription, captioning, avatars, automated customer support, or sign-language technologies.
Why should we change it?
Why should we change it? Procurement staff cannot include accessibility requirements they do not understand. Without training on DDBHH communication access, organizations may continue to purchase goods and services that rely on phone-only support, audio-only information, inaccessible video, missing captions, no ASL or LSQ access, no DeafBlind communication supports, weak relay compatibility, or untested AI tools. Training is necessary to turn the standard into practice. It should give clients, procurement professionals, evaluators, contract managers, and senior management the knowledge needed to define, evaluate, purchase, monitor, and enforce communication-access requirements.
Heading text
15. Training
Heading number portion
15.
Item id
1782242097512_740
Heading id
15.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 15.1 to ensure training is provided to all people who influence accessibility outcomes in procurement, not only those formally responsible for procurement. Training should also apply to evaluators, contract managers, project authorities, technical authorities, service delivery teams, help desk and customer support teams, accessibility leads, information technology staff, communications staff, and anyone involved in testing, approving, monitoring, or remediating accessibility deliverables.
What should we change it to?
What should we change it to? Add language stating that accessible procurement training shall also be provided to: * evaluation panel members; * accessibility evaluators; * contract managers; * project authorities and technical authorities; * people responsible for task authorizations, work orders, amendments, renewals, and contract closeout; * information technology and digital service teams; * communications and public engagement staff; * help desk and customer support staff; * emergency communication or safety communication staff where applicable; * senior officials responsible for approving procurement strategies or excluding accessibility requirements. Add language stating that where a procurement affects Deaf, DeafBlind, or Hard-of-Hearing users, training should include communication-access responsibilities related to ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible digital interaction.
Why should we change it?
Why should we change it? Accessibility outcomes are shaped by many people beyond the procurement officer. Requirements may be written by project authorities, evaluated by panels, implemented by contractors, monitored by contract managers, supported by help desks, and approved by senior management. For DDBHH users, barriers can appear at any of these stages. A procurement may include accessibility language but still fail if evaluators do not understand communication access, contract managers do not enforce captioning or relay compatibility, help desks rely on phone-only support, or senior management approves exclusion of accessibility without understanding the impact. This change would ensure that everyone who can create, prevent, or fix accessibility barriers receives appropriate training.
Heading text
15.1 Persons who must receive training
Heading number portion
15.1
Item id
1782242191302_283
Heading id
15.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 15.2 to ensure training includes practical content on Deaf, DeafBlind, and Hard-of-Hearing communication access. Training should go beyond general communication with people with disabilities. It should teach procurement staff, clients, evaluators, contract managers, senior management, and service teams how to include, evaluate, contract, monitor, and enforce DDBHH communication-access requirements.
What should we change it to?
What should we change it to? Add language stating that training shall include: * Deaf cultural competence; * DeafBlind communication access; * the difference between ASL, LSQ, English, and French access; * Indigenous Sign Languages where applicable; * captioning and transcript requirements; * relay-compatible communication; * video relay service and video remote interpreting compatibility; * accessible video communication; * accessible emergency communication; * accessible customer support; * how to procure qualified interpreters, captioners, DeafBlind intervenors, and communication-access providers; * how to include communication access in specifications, evaluation criteria, testing, solicitation documents, contract deliverables, contract monitoring, and remediation; * how to identify when phone-only, audio-only, text-only, or inaccessible digital processes create barriers; * how to evaluate AI-enabled tools involving transcription, captioning, automated customer support, sign-language technologies, avatars, or accessibility automation; * how to treat accessibility failures as contract performance issues.
Why should we change it?
Why should we change it? Training determines whether the standard is applied correctly in practice. People involved in procurement may not understand that DDBHH accessibility is not limited to plain language or accessible documents. It also includes sign language, captioning, relay-compatible communication, accessible video, DeafBlind supports, accessible emergency communication, and accessible customer support. Without this training, organizations may continue to purchase systems that rely on phone-only support, audio-only instructions, inaccessible video platforms, missing captions, no ASL or LSQ access, no DeafBlind supports, weak relay compatibility, or untested AI tools. This change would help ensure that people involved in procurement can identify DDBHH communication barriers before they are purchased and can enforce accessibility requirements after contract award.
Heading text
15.2 Contents of training
Heading number portion
15.2
Item id
1782242317124_998
Heading id
15.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 15.3 to clarify that training development and delivery must be accessible to Deaf, DeafBlind, and Hard-of-Hearing participants and should include Deaf-led and disability-led expertise where the training addresses communication access. Training about accessible procurement should model the accessibility practices it teaches.
What should we change it to?
What should we change it to? Add language stating that training development and delivery shall include accessible communication methods where needed, including ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, transcripts, relay-compatible communication, accessible video communication, accessible digital materials, and accessible participation options. Add language stating that training delivery should include Deaf, DeafBlind, Hard-of-Hearing, and disability-led trainers or subject-matter experts where the training covers communication access, digital accessibility, emergency communication, customer support, telecom services, or AI-enabled accessibility tools. Add language stating that training materials should include practical examples showing how communication access is included in procurement specifications, evaluation criteria, testing, contract deliverables, monitoring, and remediation.
Why should we change it?
Why should we change it? Training cannot teach accessible procurement effectively if the training itself is inaccessible or if it lacks relevant lived experience. For DDBHH participants, accessible training may require ASL, LSQ, captioning, DeafBlind communication supports, accessible video, and accessible digital materials. Including Deaf-led and disability-led expertise would make the training more practical and credible. It would help procurement teams understand real communication barriers and how to prevent those barriers from being purchased into goods, services, systems, platforms, and contracts.
Heading text
15.3 Development and delivery method
Heading number portion
15.3
Item id
1782242396463_678
Heading id
15.3.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC supports Clause 15.3.1 and recommends strengthening it to require training to be developed with people with disabilities who have relevant lived experience and subject-matter expertise for the accessibility topics being taught. Where training addresses communication access, digital services, emergency communication, customer support, telecom services, AI-enabled accessibility tools, or procurement affecting Deaf, DeafBlind, and Hard-of-Hearing people, training development should include DDBHH and Deaf-led expertise.
What should we change it to?
What should we change it to? Add language stating that training shall be developed in consultation and, where appropriate, co-development with people with disabilities who have relevant lived experience and subject-matter expertise. Add language stating that training on DDBHH communication access should be developed with Deaf, DeafBlind, and Hard-of-Hearing people and organizations with expertise in ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, digital accessibility, and AI-related accessibility risks. Add language stating that people with disabilities and disability organizations involved in training development shall be appropriately compensated for their time, expertise, preparation, review, and follow-up.
Why should we change it?
Why should we change it? Consultation is important, but training will be stronger if it is developed with people who have direct knowledge of the barriers the training is intended to prevent. For DDBHH people, procurement barriers often involve communication systems, meetings, captions, sign-language access, relay compatibility, emergency communication, customer support, digital platforms, and AI tools. These issues require relevant lived experience and technical understanding. This change would help ensure that training is accurate, practical, and grounded in real accessibility barriers. It would also support fair compensation for disabled and Deaf-led expertise.
Heading text
15.3.1 Development
Heading number portion
15.3.1
Item id
1782242547069_47
Heading id
15.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC supports Clause 15.3.2 and recommends strengthening it so that people with disabilities are included as key members of the training delivery team when the training addresses barriers affecting their communities. Where training covers Deaf, DeafBlind, and Hard-of-Hearing communication access, delivery should include DDBHH trainers, Deaf-led organizations, or subject-matter experts with relevant lived experience.
What should we change it to?
What should we change it to? Change “should be included” to “shall be included” where the training addresses accessibility barriers affecting a specific disability community. Add language stating that training delivery on DDBHH communication access should include Deaf, DeafBlind, and Hard-of-Hearing trainers or subject-matter experts with relevant expertise in ASL, LSQ, Indigenous Sign Languages where applicable, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, customer support, digital accessibility, telecom services, and AI-enabled accessibility tools. Add language stating that training delivery itself shall be accessible, including ASL, LSQ, DeafBlind communication supports, captioning, transcripts, accessible digital materials, accessible video controls, and accessible participation options where needed. Add language stating that trainers and disability organizations shall be appropriately compensated for preparation, delivery, review, and follow-up.
Why should we change it?
Why should we change it? Training is more effective when delivered by people with relevant lived experience and expertise. General accessibility training may not adequately explain DDBHH communication barriers, sign-language access, captioning, relay compatibility, DeafBlind communication supports, emergency communication, customer support, or AI-related risks. For procurement professionals and clients, hearing directly from DDBHH experts can improve practical understanding of how barriers are created and how they can be prevented through procurement requirements, evaluation criteria, testing, contract deliverables, and monitoring. This change would strengthen training quality, accountability, and accessibility.
Heading text
15.3.2 Delivery method
Heading number portion
15.3.2
Item id
1782242669330_969
Heading id
15.3.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
What should we change? DWCC recommends strengthening Clause 15.3.3 to require training before a person makes or approves procurement decisions that affect accessibility. Training should also be required when a procurement involves communication access, emergency communication, telecom services, digital platforms, customer support, AI-enabled tools, or goods and services that have received accessibility complaints from Deaf, DeafBlind, or Hard-of-Hearing users.
What should we change it to?
What should we change it to? Add language stating that training shall be provided before a person is assigned responsibility for defining requirements, evaluating bids, approving accessibility exclusions, managing contracts, confirming deliverables, or resolving accessibility issues. Add language stating that refresher training should be required when accessibility complaints identify barriers affecting DDBHH users, including barriers related to ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, digital accessibility, or AI-enabled tools. Add language stating that training should also be updated when new technologies, procurement templates, accessibility standards, AI tools, emergency communication systems, or customer support systems create new accessibility risks.
Why should we change it?
Why should we change it? Training provided after procurement decisions are made may be too late to prevent barriers. Accessibility knowledge is needed before requirements are defined, before evaluation criteria are set, before contracts are awarded, and before deliverables are accepted. For Deaf, DeafBlind, and Hard-of-Hearing users, barriers can be built into procurement through phone-only support, missing captioning, no ASL or LSQ access, inaccessible video platforms, weak relay compatibility, inaccessible emergency communication, or AI-enabled tools that are not tested with affected users. This change would ensure that training happens early enough to prevent barriers and is refreshed when complaints, new standards, or new technologies reveal accessibility risks.
Heading text
15.3.3 Timing
Heading number portion
15.3.3
Item id
1782242758523_340
Heading id
s15
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?
What should we change? DWCC recommends expanding Annex A to include more Deaf, DeafBlind, Hard-of-Hearing, sign-language, communication-access, telecommunications, emergency communication, digital accessibility, and AI-accessibility resources. The bibliography should better reflect the evidence base needed to support accessible procurement for DDBHH users.
What should we change it to?
What should we change it to? Add relevant Deaf-led, disability-led, and communication-access resources to the bibliography, including resources addressing: * ASL and LSQ access; * Indigenous Sign Languages where applicable; * DeafBlind communication supports; * captioning and transcripts; * relay-compatible communication; * video relay service and video remote interpreting; * accessible video communication; * accessible emergency communication; * accessible customer support; * accessible telecommunications and wireless services; * AI-enabled transcription, captioning, avatars, automated customer support, and sign-language technologies; * accessibility testing with affected users; * Deaf-led and disability-led procurement evaluation. DWCC also recommends ensuring that existing references to DDBHH-related research, including Canadian Association of the Deaf research and other relevant Deaf, DeafBlind, and Hard-of-Hearing accessibility evidence, are retained and strengthened where appropriate.
Why should we change it?
Why should we change it? Bibliographies influence how organizations interpret and apply standards. If the bibliography lacks DDBHH communication-access evidence, organizations may rely mainly on general accessibility, plain language, digital, or built-environment resources and miss barriers specific to Deaf, DeafBlind, and Hard-of-Hearing users. For DDBHH people, accessible procurement requires knowledge of sign language, captioning, relay compatibility, accessible video communication, DeafBlind supports, emergency communication, customer support, telecom services, and emerging AI-related risks. Expanding the bibliography would help procurement professionals, clients, evaluators, trainers, and contract managers find relevant evidence and apply the standard more effectively.
Heading text
16. Annex A: Bibliography (Informative)
Heading number portion
16.
Item id
1782242867438_557
Heading id
16.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?
What should we change? DWCC recommends expanding Clause 16.1 to include other relevant federal legal references that support accessible procurement, equality, human rights, and the duty to accommodate. The Accessible Canada Act is essential, but accessible procurement is also connected to other legal obligations and public-sector responsibilities.
What should we change it to?
What should we change it to? Add relevant legal references such as: * Canadian Human Rights Act; * Employment Equity Act; * Financial Administration Act, where procurement and accommodation flexibility are discussed in the standard; * Canadian Charter of Rights and Freedoms, where equality and non-discrimination principles are relevant; * Accessible Canada Regulations, where applicable; * other federal legal instruments that affect accessibility, procurement, service delivery, communication access, or duty to accommodate. DWCC also recommends that the standard cross-reference these legal obligations where procurement flexibility, individual accommodation procurement, accessible service delivery, communication access, and exclusion of accessibility requirements are discussed.
Why should we change it?
Why should we change it? Accessible procurement does not operate only under the Accessible Canada Act. Procurement decisions can also affect human rights, equality, employment, service delivery, accommodation, and public-sector accountability. For Deaf, DeafBlind, and Hard-of-Hearing people, procurement choices can determine whether communication access is available through ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, and accessible customer support. Adding relevant legal references would help users understand that accessibility requirements may connect to broader legal obligations and should not be treated as optional procurement preferences.
Heading text
16.1 Acts
Heading number portion
16.1
Item id
1782243028760_91
Heading id
16.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?
What should we change? DWCC recommends expanding Clause 16.2 to include standards, codes, or guidance that more directly address Deaf, DeafBlind, and Hard-of-Hearing communication access. The listed standards are important, but they do not fully address ASL, LSQ, Indigenous Sign Languages, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, accessible emergency communication, accessible customer support, and accessible telecommunications services.
What should we change it to?
What should we change it to? Add or cross-reference relevant standards, codes, or guidance addressing: * ASL and LSQ access; * Indigenous Sign Languages where applicable; * DeafBlind communication supports; * captioning and transcripts; * relay-compatible communication; * video relay service and video remote interpreting compatibility; * accessible video communication; * accessible emergency communication; * accessible customer support; * accessible telecommunications and wireless services; * accessible AI-enabled tools, including transcription, captioning, automated customer support, avatars, and sign-language technologies; * user testing with affected Deaf, DeafBlind, and Hard-of-Hearing users. If no existing standard fully addresses these areas, the standard should state that organizations should consult Deaf-led, DeafBlind, Hard-of-Hearing, and disability-led subject-matter experts to define appropriate communication-access requirements.
Why should we change it?
Why should we change it? Standards and codes guide how procurement professionals define and evaluate accessibility. If the reference list focuses mainly on general ICT accessibility, plain language, service delivery, and built environment, organizations may miss DDBHH communication-access requirements. For Deaf, DeafBlind, and Hard-of-Hearing users, accessibility may depend on sign-language access, captioning, relay compatibility, accessible video, accessible emergency communication, accessible customer support, and DeafBlind communication supports. These requirements may not be fully captured by general standards alone. This change would help organizations use the standard with a stronger communication-access lens and reduce the risk of purchasing inaccessible goods, services, systems, or platforms.
Heading text
16.2 Standards and codes
Heading number portion
16.2
Item id
1782243158222_365
Heading id
16.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?
What should we change? DWCC recommends expanding Clause 16.3 to include online resources that help organizations procure accessible communication services, digital services, emergency communication tools, customer support systems, telecommunications services, and AI-enabled accessibility tools. The current resources are useful, but they should be supplemented with resources that address Deaf, DeafBlind, and Hard-of-Hearing communication access.
What should we change it to?
What should we change it to? Add online resources or guidance addressing: * how to procure ASL and LSQ services; * how to procure qualified sign-language interpretation and sign-language translation; * how to procure DeafBlind communication supports and intervenor services; * how to procure captioning and transcripts; * how to procure relay-compatible communication systems; * how to procure accessible video communication platforms; * how to procure accessible emergency communication tools; * how to procure accessible customer support and help desk services; * how to evaluate AI-enabled transcription, captioning, sign-language, avatar, and automated support tools; * how to test accessibility with affected Deaf, DeafBlind, and Hard-of-Hearing users; * how to include DDBHH accessibility requirements in mandatory justification forms when accessibility is excluded.
Why should we change it?
Why should we change it? Procurement professionals need practical tools, not only general principles. Without online resources that explain DDBHH communication-access procurement, organizations may not know how to write requirements, assess vendor claims, evaluate bids, test accessibility, or manage contracts. For DDBHH users, barriers are often created by procurement choices involving customer support, video platforms, emergency alerts, captioning, relay compatibility, sign-language services, DeafBlind supports, and AI-enabled tools. Clear online resources would help organizations prevent these barriers before goods or services are purchased.
Heading text
16.3 Online Resources
Heading number portion
16.3
Item id
1782243290235_848
Heading id
16.4
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?
What should we change? DWCC supports the inclusion of Canadian Association of the Deaf’s 2023 publication, Advancing Accessibility Standards for Deaf, Deaf-Blind and Hard of Hearing Canadians. DWCC recommends expanding Clause 16.4 to include additional Deaf-led, DeafBlind, Hard-of-Hearing, communication-access, telecommunications, emergency communication, digital accessibility, and AI-accessibility publications. The publication list should better reflect the evidence base needed to support accessible procurement for DDBHH users.
What should we change it to?
What should we change it to? Add additional publications and research addressing: * Deaf-led accessibility governance; * ASL and LSQ access; * Indigenous Sign Languages where applicable; * DeafBlind communication supports; * captioning and transcripts; * relay-compatible communication; * video relay service and video remote interpreting; * accessible video communication; * accessible emergency communication; * accessible customer support; * accessible telecommunications and wireless services; * accessible mobile devices; * AI-enabled transcription, captioning, sign-language technologies, avatars, automated customer support, and accessibility automation; * accessibility testing with affected Deaf, DeafBlind, and Hard-of-Hearing users; * procurement evaluation by qualified Deaf, DeafBlind, and Hard-of-Hearing evaluators. DWCC also recommends that future updates to the bibliography include relevant submissions, research, and publications from Deaf-led and disability-led organizations with direct expertise in communication access and accessible procurement.
Why should we change it?
Why should we change it? Publications shape how users understand and apply the standard. The existing list includes important accessibility procurement resources, but accessible procurement for DDBHH people requires a stronger communication-access evidence base. For Deaf, DeafBlind, and Hard-of-Hearing users, procurement can determine whether people have access to ASL, LSQ, DeafBlind communication supports, captioning, relay-compatible communication, accessible video communication, emergency communication, customer support, telecom services, and AI-enabled tools. A stronger publication list would help procurement professionals, clients, evaluators, trainers, and contract managers understand DDBHH barriers and prevent those barriers from being purchased into goods, services, systems, platforms, and contracts.
Heading text
16.4 Publications
Heading number portion
16.4
Submission ID
65655
Submitted by
chair@deafwireless.ca
Submitted on
Tue, 06/23/2026 - 16:26
Consent to contact
Yes

Individual 65656's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782153259006_679
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?
See attached
What should we change it to?
See attached
Why should we change it?
See attached
Heading text
10. General requirements
Heading number portion
10.
Submission ID
65656
Submitted by
jantao@itic.org
Submitted on
Mon, 06/22/2026 - 14:34
Consent to contact
Yes

Individual 65657's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782154645604_512
Heading id
11.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Current text: “All internal and external facing websites and digital applications shall comply with CAN-ASC-EN 301 549:20204.”
What should we change it to?
Revise to: “All internal and external facing websites and digital applications shall comply with CAN-ASC-EN 301 549:2024 and include usability testing with persons with disabilities, including people who are blind, low vision, and Deafblind, using assistive technologies such as screen readers, screen magnification, and refreshable braille displays.”
Why should we change it?
Technical compliance alone does not always mean a website or application is usable. People who are blind, low vision, or Deafblind may still face barriers such as unlabeled buttons, inaccessible forms, poor keyboard navigation, inaccessible CAPTCHAs, or incompatibility with screen readers and magnification software. Usability testing with people with lived experience helps ensure procurement systems are accessible in real-world use and not only technically compliant.
Heading text
11.3 Websites and digital applications
Heading number portion
11.3
Item id
1782154795836_940
Heading id
11.4.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Current text: “vi) All required documents are provided at least two (2) business days before the engagement begins.”
What should we change it to?
Revise to: “vi) All required documents are provided in accessible formats at least five (5) business days before the engagement begins to allow participants using screen readers, braille, magnification software, or support services adequate time to review materials.”
Why should we change it?
People who are blind, low vision, or Deafblind often require additional time to independently review materials using assistive technologies or alternative formats. Two business days may not allow sufficient time to access, review, or prepare meaningful feedback on procurement materials. Providing materials earlier in accessible formats supports equitable participation and meaningful engagement.
Heading text
11.4.3 Identifying accommodation needs
Heading number portion
11.4.3
Item id
1782154903304_33
Heading id
11.4.4.4
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Current text: “iv) Signage”
What should we change it to?
Revise to: “iv) Signage, including tactile, braille, high contrast, and large-print wayfinding signage that supports independent navigation for people who are blind or low vision.”
Why should we change it?
People who are blind or partially sighted often experience barriers navigating unfamiliar procurement engagement spaces, meeting venues, or consultation environments. Signage requirements should explicitly include tactile, braille, large print, and high-contrast considerations to support independent navigation and reduce reliance on others for assistance.
Heading text
11.4.4.4 Facility specifications
Heading number portion
11.4.4.4
Item id
1782155112936_867
Heading id
11.4.4.5
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?
Current text: “ww) Limited background noise.”
What should we change it to?
Revise to: “ww) Limited background noise and clear verbal identification of speakers throughout meetings.”
Why should we change it?
People who are blind, low vision, or Deafblind cannot rely on visual cues to identify who is speaking or follow transitions in discussion. Verbal speaker identification helps ensure equitable participation, improves clarity during meetings, and supports meaningful engagement for participants with sight loss.
Heading text
11.4.4.5 Meeting rooms
Heading number portion
11.4.4.5
Item id
1782155240200_870
Heading id
12.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?
Current text: “ii) consult with end users, including people with disabilities, in the planning phase and throughout the procurement process;”
What should we change it to?
“ii) consult with end users, including people with disabilities and individuals with lived experience relevant to the procurement, in the planning phase and throughout the procurement process, including testing and validation phases;”
Why should we change it?
Accessibility barriers are often only identified during testing or implementation. Meaningful involvement of people who are blind, low vision, or Deafblind throughout the procurement process helps ensure inaccessible products or services are not purchased and reduces the need for costly remediation after implementation.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782155609084_305
Heading id
12.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Current text: “a) as part of an evaluation, a demonstration is required for the good or service being procured to determine conformance to established accessibility requirements;”
What should we change it to?
Revise to: “a) as part of an evaluation, a demonstration and usability testing with persons with disabilities, including people who are blind, low vision, and Deafblind, is required for the good or service being procured to determine conformance to established accessibility requirements;”
Why should we change it?
Vendor demonstrations do not always reveal practical accessibility barriers. A product may appear compliant but remain inaccessible to users of screen readers, braille displays, or magnification software. Real-world usability testing with people with lived experience helps ensure procured goods and services are independently usable and accessible in practice.
Heading text
12.2 Identifying requirements for testing
Heading number portion
12.2
Item id
1782155732308_41
Heading id
12.4.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?
Current text: “ii) people with disabilities or lived experience who are end users of the good or service;”
What should we change it to?
Revise to: “ii) people with disabilities or lived experience who are representative end users of the good or service, including individuals with relevant disability-specific expertise where accessibility requirements are being evaluated;”
Why should we change it?
Accessibility barriers vary across disability groups. For procurements involving digital platforms, navigation systems, customer-facing technologies, or information access, it is important to include people who are blind, low vision, or Deafblind in evaluation activities to identify barriers that may otherwise go unnoticed.
Heading text
12.4.3 Identifying the evaluation panel
Heading number portion
12.4.3
Item id
1782155838748_78
Heading id
14.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Current text: “yyy) Inspection for barriers by persons with disabilities before delivery whether it be at the contractor or the delivery site.”
What should we change it to?
“yyy) Inspection and usability testing for barriers by persons with disabilities, including people who are blind, low vision, and Deafblind, before delivery whether it be at the contractor or the delivery site.”
Why should we change it?
Accessibility barriers are often only identified through actual use. For people who are blind, low vision, or Deafblind, barriers such as inaccessible interfaces, poor contrast, unlabeled controls, inaccessible documentation, or incompatibility with assistive technologies may not be identified through standard inspections alone. Including usability testing helps ensure accessibility requirements are meaningfully met prior to implementation.
Heading text
14.2 Confirming deliverables
Heading number portion
14.2
Item id
1782156073828_822
Heading id
12.4
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?
Section 12.4 – Evaluation Criteria
What should we change it to?
Add a requirement that: “Procurement evaluations shall include accessibility benefit measures that assess how well a product, service, or solution exceeds minimum accessibility requirements and supports the widest range of users, including people with disabilities.”
Why should we change it?
The standard currently focuses primarily on accessibility requirements and compliance. However, accessibility should not be treated solely as a pass/fail criterion. Procurement processes should also recognize and reward solutions that demonstrate inclusive design, superior usability, meaningful involvement of people with disabilities in design and testing, and enhanced accessibility outcomes. Accessibility benefit measures would encourage innovation and help organizations procure solutions that provide greater accessibility and usability beyond minimum compliance requirements.
Heading text
12.4 Planning the evaluation
Heading number portion
12.4
Submission ID
65657
Submitted by
rosalyn.commisso@cnib.ca
Submitted on
Mon, 06/22/2026 - 15:17
Consent to contact
Yes

Individual 65665's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782197381734_515
Heading id
9.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
A number of definitions were added to the procurement standard from other standards that were not fully vetted by the committee before release of this document. One of those definitions was circular in nature and in reviewing the document again there are other circular definition in the document. A circular definition occurs when the term being defined is used within the definition itself, or relies on a chain of definitions that loops back to the original term (e.g., "An automobile is a vehicle that has the characteristics of an automobile"). This creates a logical loop that fails to provide new information. A circular definition is not appropriate or acceptable in a standard because it introduces ambiguity and lacks operational utility. If a definition loops back on itself, it cannot be verified, measured, or audited, defeating the fundamental purpose of a standardized specification. Of the new definition the following is an example of a circular definition: Circular Term: "Service" • Original Text: "A service is obtained through formal arrangements such as contracts, memoranda of understanding, and letters of agreement, to support the realization of specific outcomes." • The Flaw: It defines a "service" by how it is acquired (contracts, MOUs) rather than explaining what a service actually is. • Proposed Alternatives: 1) An intangible commodity consisting of labor, time, expertise, or intellectual effort delivered by a contractor to achieve a specific operational outcome or capability for the organization. 2) “The performance of specialized activities or the application of expertise and resources by one party for the direct benefit of another, without transferring ownership of tangible goods, usually under agreed conditions of scope, standards, and remuneration.” 3) “The deliberate provision of specialized labor, expertise, or resources by one party to another, performed over time or on demand, primarily for the benefit of the recipient rather than for the transfer of physical goods, typically governed by explicit or implied terms regarding scope, quality, duration, and compensation.” The other definition that are circular in nature are: The following circular definitions have been identified, along with proposed alternative language to resolve the ambiguity and ensure an impartial process. 1. Circular Term: "Procurement" • Original Text: "The process of obtaining goods, services or construction from the planning and the completion of the procurement life cycle." • The Flaw: Defining "procurement" by referencing the "procurement life cycle" creates a closed logical loop. • Proposed Alternative: Procurement — The comprehensive acquisition process of securing goods, services, or construction works from external sources. It spans the identification of a need through to requirement definition, sourcing, contract award, performance monitoring, and asset disposal. 2. Circular Term: "Procurement Life Cycle" • Original Text: "The continuum of effective and efficient management of procurement phases including: planning; acquisition and execution; use and maintenance; and disposal and closeout." • The Flaw: This relies entirely on the root word "procurement" to explain its own operational timeline. • Proposed Alternative: Procurement Life Cycle — The complete multi-phase timeline governing an acquisition, beginning with initial project planning and requirement validation, progressing through solicitation and contract execution, and concluding with asset management, contract closeout, or disposal. 3. Circular Term: "Procurement Professional" • Original Text: "A procurement professional is anyone responsible for facilitating the procurement function within an organization and has the responsibility to enter into a contract or contractual agreement to purchase goods, services, and construction on behalf of a business owner." • The Flaw: Uses both "procurement" and "professional" (by implication of role) to define the person. • Proposed Alternative: Procurement Professional — An designated specialist or designated authority tasked with executing and managing an organization’s acquisition processes, ensuring compliance with relevant policies, trade agreements, and accessibility standards throughout the contracting timeline. 4. Circular Term: "Purchasing" • Original Text: "The buying process within the procurement cycle." • The Flaw: While slightly less direct, defining purchasing using "procurement cycle" (which relies on procurement) creates an indirect circular dependency in the terminology framework. • Proposed Alternative: Purchasing — The specific transactional subset of activities within an acquisition process focused on ordering, receiving, and finalizing payment for goods or services.
What should we change it to?
see above.
Why should we change it?
see above.
Heading text
9.1 Definitions
Heading number portion
9.1
Item id
1782197921128_307
Heading id
13.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
In Clause 13.1.1 of the Canadian draft standard (CAN-ASC-4.1), which is titled "Accessibility cost treatment in bidding". This specific clause directs clients and procurement professionals to allow bidders to separately itemize costs for accommodating themselves or their employees, and explicitly states that they must "ensure the accommodation-related costs are not included in the evaluation of the financial proposals". The clause establishes a specific mechanism to ensure that businesses are not penalized for the costs of accommodating their own employees with disabilities. According to the standard, procuring organizations must allow bidders to separately itemize the expected costs to accommodate themselves or their employees during the contract. Crucially, these accommodation-related costs must not be included in the evaluation of the financial proposals. Instead, the procuring organization validates that the costs are fair and reasonable prior to the contract award, and then reflects them in the basis of payment for the resulting contract. There is no explicit parallel in the European Union procurement standards that mandates removing a supplier's internal employee accommodation costs from the financial evaluation of a bid. However, the EU deals with the underlying goal of promoting inclusive and accessible practices through a broader, holistic evaluation framework rather than a specific financial carve-out: The Most Economically Advantageous Tender (MEAT) Criterion instead of relying strictly on the lowest price, EU contracting authorities are required to award public contracts based on the "Most Economically Advantageous Tender" (MEAT) criterion. This approach emphasizes the best price-quality ratio, allowing procuring entities to evaluate bids based on a combination of cost, quality, and social and environmental factors. Because lowest price is not the only metric, a supplier whose bid is slightly higher due to fair labor practices or inclusive employment accommodations can still win if they score highly on the qualitative and social criteria. Social Procurement and Social Inclusion The EU strongly advocates for "Strategic Public Procurement," which includes social procurement initiatives designed to foster social inclusion and support marginalized groups. Contracting authorities can address these goals in several ways: Award Criteria: The EU Public Procurement Directive (Directive 2014/24/EU) explicitly allows authorities to use "social characteristics" as part of their award criteria linked to the subject matter of the contract. Dividing Contracts: The rules encourage the division of contracts into smaller lots and promote measures that make procurement friendlier to small and medium-sized enterprises (SMEs) and social economy enterprises. Integration of Accessibility Costs: While the Canadian model separates supplier accommodation costs from the bid's financial evaluation, the EU approach expects suppliers to integrate their costs directly into their bids. While in this document Canada uses a targeted financial exclusion rule to level the playing field for suppliers employing persons with disabilities, the European Union relies on the MEAT evaluation framework to ensure that public buyers can reward social inclusion and quality without being forced to automatically select the cheapest bid. Despite policies encouraging the evaluation of social and qualitative criteria (like the Most Economically Advantageous Tender), 55% of EU procurement procedures still use the lowest price as the only award criterion. This indicates a practical challenge in shifting the culture of public buyers away from strictly financial metrics toward prioritizing quality, sustainability, and inclusion. The EU experience indicates that despite the policies that cost is still a significant determinant in the final decision. Given that in practice in Canada there is no funding source that compensates the procuring agency for those real accommodates costs and given that in practice overall cost is still the strongest determining factor in the large major of procurement processes, the clause as it sits may still not be sufficient ensure proposal that have accommodation costs, especially if significant given the overall cost of the contract, will by fairly evaluated. Other reasons can still be used to exclude a supplier. The MEAT process suggests that points being given for social inclusion might another approach.
What should we change it to?
Perhaps some combination of the two approaches might be worth considering as there are specific points awarded for social inclusion in MEAT for the evaluation process, which is harder to get around.
Why should we change it?
It does achieve the objective that was discussed at the committee level.
Heading text
13.1.1 Accessibility cost treatment in bidding
Heading number portion
13.1.1
Item id
1782198234585_279
Heading id
10.1.3.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?
Loopholes in the "Flexible Procurement" & Roadmap Exception (Clause 10.1.3) The standard permits clients to buy Commercial Off-The-Shelf (COTS) solutions that do not comply with accessibility requirements at contract award, provided the vendor delivers a "roadmap" for remediation. • The Flaw: This relies entirely on vendor promises and creates an uneven playing field. A non-compliant vendor offering a lower price could win a contract over a fully compliant vendor by submitting an ambitious "roadmap". • The Gap: There are no clawbacks, penalties, or contract-termination protocols explicitly defined if the vendor fails to meet their remediation timeline. Furthermore, leaving remediation methods to be "agreed upon by all parties" during contract execution introduces massive subjective variability and weakens enforcement.
What should we change it to?
See above.
Why should we change it?
See above.
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Item id
1782198348220_688
Heading id
10.1.4.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?
Discretionary Vulnerabilities in "Mandatory Justification" (Clause 10.1.4) The standard requires a written, signed justification if accessibility is excluded from a procurement file. • The Flaw: While Note 1 advises "discretion must be used," the standard relies heavily on a "challenge function" performed by the procurement professional. It lacks an independent oversight board or mandatory secondary sign-off. • The Gap: If an agency operates under tight deadlines, procurement professionals face cultural and systemic pressure to accept weak justifications just to keep files moving, turning a mandatory gatekeeping exercise into a rubber-stamping formality.
What should we change it to?
See above.
Why should we change it?
See above.
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782198465273_679
Heading id
12.4.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?
Subjectivity in the "Evaluation Panel" Selection (Clause 12.4.3) Clause 12.4.3 states the panel shall include subject matter experts, individuals with lived experience, or independent third-party experts. • The Flaw: The draft uses the word "or" rather than "and". This means an evaluation panel could completely bypass individuals with lived experience or independent third parties by simply asserting that their internal project staff qualify as "subject matter experts". The standard states that the evaluation panel shall include individuals with subject matter expertise, including: o the grammatical use of the word "or" at the end of the list. In legislative and standard drafting, this construction means the list is disjunctive rather than conjunctive. Because it uses "or" rather than "and", an organization is only strictly required to fulfill one of those bullet points. Therefore, : a procuring entity could completely bypass people with lived experience by claiming their internal project staff satisfy the first bullet point ("subject matter experts") • The Gap: Without a mandatory baseline requiring cross-disability representation directly on the scoring panel, the evaluation of complex technical accessibility criteria remains vulnerable to un-vetted, non-expert interpretation. no mandatory baseline requiring cross-disability representation on the scoring panel. By leaving the inclusion of people with lived experience as an option (using "or"), the standard permits evaluation panels to grade complex technical accessibility requirements without the necessary lived expertise on the actual scoring team. This introduces massive subjectivity and undermines the core principle of inclusive procurement.
What should we change it to?
Change the word from "or" to "and".
Why should we change it?
See above.
Heading text
12.4.3 Identifying the evaluation panel
Heading number portion
12.4.3
Item id
1782198596359_875
Heading id
s15
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?
Over-Reliance on Informative/Draft References (Section 8 & Annex A) To define core execution protocols (such as training delivery or proactive physical accommodations), the standard heavily references CAN-ASC-5.2.1 Part 1, which is explicitly listed as a draft standard. • The Flaw: A standard relying on another unfinalized standard creates legal and operational instability. If the referenced draft changes significantly before publication, it introduces compliance contradictions. This is a comment more on procedure.
What should we change it to?
see above
Why should we change it?
see above
Heading text
16. Annex A: Bibliography (Informative)
Heading number portion
16.
Submission ID
65665
Submitted by
harryl@neilsquire.ca
Submitted on
Tue, 06/23/2026 - 03:13
Consent to contact
Yes

Individual 65666's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782217447501_801
Heading id
s4
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?
Include references to the intersecting published standards (ASC will likely to this, but including here regardless.)
What should we change it to?
1) CAN-ASC-5.2.1, Accessible Service Delivery 2) AN-ASC-EN 301 549:2024-Accessibility requirements for ICT products and services (EN 301 549:2021, IDT); 3) CAN-ASC-1.1:2024 (REV-2025)-Employment; 4) CAN-ASC-3.1:2025-Plain Language; 5) CSA/ASC B651:23 Accessible design for the built environment; and 6) CSA/ASC B651.2:25 Accessible design for self-service interactive devices including automated banking
Why should we change it?
For consistency across the published standards.
Heading text
5. Preface
Heading number portion
5.
Item id
1782217848964_834
Heading id
s5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
The text in the opening paragraph
What should we change it to?
This Standard provides a framework to help organizations create an equitable and accessible procurement process. This framework includes requirements and guidance to help individuals responsible for initiating a procurement, employees who support procurement operations, and businesses who bid on procurements and sell their goods and services to organizations.
Why should we change it?
The opening paragraph has some repetitive text. Additionally, the standard provides more of a framework and guidance, and not technical in nature.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782217989716_39
Heading id
s5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
i) defining the required capabilities,
What should we change it to?
i) defining the requirements for the work,
Why should we change it?
For clarity of terminology.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782218197266_750
Heading id
s5
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
d) End users by ensuring that individuals who use or interact with the goods or services procured are consulted throughout the procurement process to identify and remove barriers.
What should we change it to?
d) End users by ensuring that individuals who will use a good or service are consulted to identify barriers and to ensure that the good or service procured addresses the barriers.
Why should we change it?
For clarity and flow.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782218397335_988
Heading id
s5
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
e) ...Businesses are also expected to demonstrate how they will meet accessibility requirements and implement them. This will be monitored and evaluated no differently than other contractual obligations.
What should we change it to?
e)...Businesses are also expected to demonstrate how they meet the accessibility requirements specified in a procurement and to deliver goods or services that comply with these requirements.
Why should we change it?
For clarity - the use of "implement" is not appropriate for this sentence. Businesses are required to demonstrate how they meet the specifications when submitting a bid, and then are required to comply/meet the deliverables in the resulting contract.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782218631563_343
Heading id
s6
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
b) defining accessibility requirements for a procurement and a mandatory justification, with the decision-making process, when accessibility is not included;
What should we change it to?
b) defining accessibility requirements for a procurement and providing a mandatory written justification that explains the decision-making process when requirements for accessibility are not included;
Why should we change it?
Clarify content, and the logic.
Heading text
7. Scope
Heading number portion
7.
Item id
1782218775565_665
Heading id
s6
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
e) accessibility procurement life cycle; and
What should we change it to?
e) accessibility throughout the procurement life cycle; and
Why should we change it?
For clarity - there are many phases of procurement, and accessibility can be applied throughout the process.
Heading text
7. Scope
Heading number portion
7.
Item id
1782218987315_228
Heading id
s7
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 an ASC standard
What should we change it to?
include: CAN-ASC-1.1:2024 (REV-2025) – Employment
Why should we change it?
There may be value to include this reference in relation to "accommodation" for employees with disabilities within an organization, and potentially alignment with the section on training.
Heading text
8. References
Heading number portion
8.
Item id
1782220081667_405
Heading id
10.1.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
ii) include accessibility requirements when specifying criteria for goods and services procured;
What should we change it to?
ii) include accessibility requirements when defining the specifications for goods and services procured;
Why should we change it?
For clarity - we are including requirements for accessibility when we define the specifications for the work (Statement of Work, Statement of Requirements)
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782220246303_171
Heading id
10.1.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
iii) include technical evaluation criteria to assess the bidder’s capacity to deliver against accessibility specifications;
What should we change it to?
iii) include technical evaluation criteria to assess the bidder’s capacity to deliver against accessibility requirements;
Why should we change it?
For consistency of terminology, as mentioned in previous comment.
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782220314411_193
Heading id
10.1.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
iv) verify that contract deliverables incorporated accessibility requirements as defined in the solicitation; and
What should we change it to?
v) verify that contract deliverables incorporate accessibility requirements as defined in the solicitation; and
Why should we change it?
tense of verb incorporate
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782220409958_568
Heading id
10.1.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
iv) verify that contract deliverables incorporated accessibility requirements as defined in the solicitation; and
What should we change it to?
iv) verify that contract deliverables incorporated accessibility requirements as defined in the specifications; and
Why should we change it?
As previously mentioned, the requirements are part of the specifications for the work.
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782220835136_718
Heading id
s8
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 a definition for specifications (statement of work, statement of requirements)
What should we change it to?
A sample definition: Specifications - are written requirements and standards for products, systems, workmanship, quality, and the services necessary for the performance of the Work. Source: https://publications.gc.ca/collections/collection_2023/spac-pspc/P68-4-2-2023-eng.pdf
Why should we change it?
The term is used throughout the Standard and not defined.
Heading text
9. Definitions
Heading number portion
9.
Item id
1782221143365_219
Heading id
10.1.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Note: An example of applying a flexible approach is for the purchase of a commercial, off-the-shelf solution that does not meet accessibility standards at contract award.
What should we change it to?
Note: An example of where a flexible approach may be used is for the purchase of a commercial, off-the-shelf solution that does not meet the specified accessibility standards at the time of solicitation closing.
Why should we change it?
To strengthen the example used, and to use the technically correct terminology.
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Item id
1782221369832_161
Heading id
10.1.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
c. At the request of the client and in addition to the roadmap, the contractor shall provide methods of remediation to end users when accessibility barriers are reported during the remediation period.
What should we change it to?
c. At the request of the client and in addition to the remediation roadmap, the contractor shall provide accommodation to end-users. This accommodation will be provided when accessibility barriers are reported by end-users during the remediation period.
Why should we change it?
there is a distinction between the remediation roadmap (an agreement to address known issues) and addressing barriers that may be encountered by end-users during this period.
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Item id
1782221521306_732
Heading id
10.1.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
d. The remediation shall be agreed upon by all parties.
What should we change it to?
d. The roadmap (plan) shall be agreed upon by all parties.
Why should we change it?
it is unclear if remediation in this context about the roadmap or the issues encountered by end users. For flow of content, I understood this to mean the "roadmap".
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Item id
1782222776852_214
Heading id
10.1.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Note 1: Discretion must be used when determining the reasons why accessibility requirements might not be applicable. For example, there is a difference in the reasons why accessibility is not applicable for a procurement looking to acquire construction materials as compared to a procurement looking to implement a new human resource platform for employees.
What should we change it to?
Note 1: Discretion must be used when determining the reasons why accessibility requirements might not be applicable. For example, a procurement for the services of one contractor to perform a minor repair to a piece of equipment may not have requirements for accessibility. However, a digital platform used by employees will have requirements for accessibility including conformance requirements to applicable accessibility standards.
Why should we change it?
This example is not sufficient; a suggestion provided for additional discussion.
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782222925125_139
Heading id
10.1.4.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?
Note 2: An example of such a justification form can be found at the link: https://www.canada.ca/en/public-services-procurement/services/acquisitions/temporary-help/templates-for-federal-department-clients/accessibility-criteria-procurement-justification-form.html
What should we change it to?
Unsure - will need a new resource
Why should we change it?
This link is not up-to-date; a new resource will be required.
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782223064489_67
Heading id
11.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
c) Employees responsible for procurement-related policies and programs.
What should we change it to?
c) Employees responsible for developing and administering procurement-related policies and programs.
Why should we change it?
Improve clarity of intention.
Heading text
11.1 General
Heading number portion
11.1
Item id
1782223143451_338
Heading id
11.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
d. Users who interact with the good, service, or construction.
What should we change it to?
d. End users who interact with the good, service, or construction.
Why should we change it?
For consistency of terminology
Heading text
11.1 General
Heading number portion
11.1
Item id
1782228983993_115
Heading id
11.2.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
d. Instructional training materials (internal and external facing)
What should we change it to?
d. Training materials (internal facing for employees of the organization, and external facing for businesses)
Why should we change it?
For clarity.
Heading text
11.2.1 Plain language documents
Heading number portion
11.2.1
Item id
1782229063796_870
Heading id
11.2.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
h. Communications to businesses (for example, news items or correspondence)
What should we change it to?
h) Communications to businesses (for example, news items or supplier debrief letters)
Why should we change it?
For an additional reference to supplier debriefs, which are important forms of communication to suppliers.
Heading text
11.2.1 Plain language documents
Heading number portion
11.2.1
Item id
1782229181731_45
Heading id
11.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
All internal and external facing websites and digital applications shall comply with CAN-ASC-EN 301 549:20204. This includes those used in: planning; bidding and contract award; contract management; closeout phases; and clauses
What should we change it to?
All internal and external facing websites and digital applications shall comply with CAN-ASC-EN 301 549:20204. This includes websites and digital applications used in: ⦁ procurement planning; ⦁ issuing tender opportunities; ⦁ receiving and evaluating bid submissions; ⦁ awarding contracts; ⦁ managing contracts; and ⦁ closing out contracts.
Why should we change it?
For clarity, and consistent use of procurement terminology.
Heading text
11.3 Websites and digital applications
Heading number portion
11.3
Item id
1782232024984_892
Heading id
11.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
3. Businesses’ information and outreach activities
What should we change it to?
3. Information and outreach activities intended for businesses.
Why should we change it?
Revise for clarity.
Heading text
11.4.1 General
Heading number portion
11.4.1
Item id
1782232145123_522
Heading id
11.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Note 2: Where it is not possible for an individual in the procurement process to attend a meeting in person, a hybrid protocol will be offered such that this person can attend an event virtually, in concert with others that are there in-person.
What should we change it to?
Note 2: Where it is not possible for an individual to attend an in-person procurement engagement activity, a hybrid approach will be used. This approach will ensure that the individual can attend the event virtually, in concert with other participants who attend in-person.
Why should we change it?
Original text is a long sentence, and not clear.
Heading text
11.4.1 General
Heading number portion
11.4.1
Item id
1782232248449_534
Heading id
11.4.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
v. goods and services requirements; or
What should we change it to?
v. specifications for goods and services; or
Why should we change it?
For consistency of terminology.
Heading text
11.4.2 Information from engagement activities
Heading number portion
11.4.2
Item id
1782232341787_361
Heading id
11.4.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
c. enhance their understanding of industry goods and service offerings in the areas of interest; and
What should we change it to?
c. enhance their understanding of the market availability of the goods and services in the area of interest; and
Why should we change it?
Revised for clarity.
Heading text
11.4.2 Information from engagement activities
Heading number portion
11.4.2
Item id
1782232511270_547
Heading id
11.4.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?
Whether an engagement activity will be held in-person or virtually, the organizers shall:
What should we change it to?
Require clarity on "who" the organiser is.
Why should we change it?
This creates ambiguity/confusion on whose role /responsibility is it (client, procurement professional).
Heading text
11.4.3 Identifying accommodation needs
Heading number portion
11.4.3
Item id
1782232746636_354
Heading id
11.4.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
vii) A clear protocol for remediation during engagements is established so participants whose needs are not met can contact the organizer directly.
What should we change it to?
vii) A clear process to address accessibility issues that occur during engagements is established. This includes ensuring that participants who experience barriers can contact the organizer directly.
Why should we change it?
Long sentence, and revised for plain language, and clarity.
Heading text
11.4.3 Identifying accommodation needs
Heading number portion
11.4.3
Item id
1782232957847_214
Heading id
11.4.4.4
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
2) comply with CAN-ASC-5.2.1 Part 1 (draft standard)
What should we change it to?
Replace with the published standard. CAN-ASC-5.2.1:2026 - Accessible Service Delivery https://accessible.canada.ca/creating-accessibility-standards/can-asc-521-design-and-delivery-accessible-programs-and-services
Why should we change it?
now official standard.
Heading text
11.4.4.4 Facility specifications
Heading number portion
11.4.4.4
Item id
1782233025374_74
Heading id
11.4.4.5
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Meeting rooms that are used for in-person outreach events shall provide the following, including but not limited to:
What should we change it to?
Meeting rooms that are used for in-person outreach activities shall provide the following, including but not limited to:
Why should we change it?
replace "events" with "activities" for consistency of terms.
Heading text
11.4.4.5 Meeting rooms
Heading number portion
11.4.4.5
Item id
1782233080658_114
Heading id
11.4.4.6
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
To facilitate emergency egress for in-person events, facilities shall:
What should we change it to?
To facilitate emergency egress for in-person activities, facilities shall:
Why should we change it?
replace "events" with "activities" for consistency of terms.
Heading text
11.4.4.6 Facility emergency egress
Heading number portion
11.4.4.6
Item id
1782233229159_553
Heading id
12.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?
i) identify applicable accessibility standards, guidelines, and best practices, and in such cases where no applicable references are available, continue to follow the procurement process and make reasonable efforts to identify a solution;
What should we change it to?
The introduction of "solution" has created confusion in this section. Cannot propose a response, as it is unclear what was intended including "...make reasonable efforts to identify a solution".
Why should we change it?
The introduction of "solution" has created confusion in this section. Does solution mean "procurement", or does it mean find ways to include requirements for accessibility by other means? Request that this be discussed with the committee to clarify intent, and reword.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782233304508_398
Heading id
12.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
iv) consult with accessibility subject matter experts including persons with disabilities; and
What should we change it to?
iv) consult with subject matter experts in accessibility including persons with disabilities; and
Why should we change it?
This term does not match the definition in the “Definitions” section. The term “subject matter expert” should be reviewed throughout the Standard and align with the intended definition. Not consistently used in the Standard.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782233553368_749
Heading id
12.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
v. where no clear suitable solution can be found, follow the mandatory justification for excluding accessibility set out in Clause 10.1.4
What should we change it to?
v. when no requirements for accessibility have been included in the specifications, follow the mandatory justification for excluding accessibility set out in Clause 10.1.4
Why should we change it?
The subject of section 12.1 is identifying and defining accessibility requirements for inclusion in the specifications for a procurement. There are a series of steps to consider and identify accessibility requirements. If after all of these steps are undertaken, and it is determined that accessibility is not applicable to the procurement, or the business owner has made the decision to exclude accessibility requirements, they must document this decision/rationale in the justification. Request and recommend that this language be reviewed and rewritten for clarity.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782233910426_790
Heading id
12.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Note: Organizations are encouraged to collaborate with vendors to develop curated source lists that prioritize accessibility, while also identifying suppliers and organizations with demonstrated accessibility expertise to maintain a current and reliable list of resources and services.
What should we change it to?
Note: Organizations shall prioritize requirements for accessibility when defining specifications for source lists and methods of supply.
Why should we change it?
When we create source lists, we should consider and integrate requirements for accessibility in the specifications for a source list, supply arrangement, standing offer. So, by default a source list or method of supply should include accessibility requirements. The notion of "expertise" is also difficult to demonstrate, as there is currently very little by way of certifications to validate this expertise.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782234057281_861
Heading id
12.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
i. engage with industry (network of potential suppliers) and organizations who have procured similar goods or services to understand market capacity to help develop a procurement strategy that includes accessibility requirements; and
What should we change it to?
i. engage with industry (network of potential suppliers) and organizations who have procured similar goods or services to understand market capacity; and
Why should we change it?
The sentence in b) preceding this list indicates that the purpose of doing this is to identify and define accessibility requirements for procurement.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782234381924_938
Heading id
12.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Where procurement is conducted to meet the specific accommodation needs of a person with a disability, standard competitive procurement rules may be set aside in recognition of obligations under the Accessible Canada Act, the Employment Equity Act, and the Financial Administration Act. In such cases: the individual shall be involved in evaluating and selecting the solution; evaluation may include personal factors such as communication preferences, provider familiarity, and service compatibility; and procurement policies shall not override the duty to accommodate. Flexibility must be exercised to ensure accommodations are timely, effective, and uphold the individual’s dignity and autonomy.
What should we change it to?
Organizations shall ensure that the accommodation needs of a person with a disability are met in recognition of obligations under the Accessible Canada Act, the Canada Labour Code, the Canadian Human Rights Act, and the Employment Equity Act. When procurement is required to meet the accommodation needs, the approach shall ensure that: a) the individual is involved in evaluating and selecting the service provider; b) evaluation may include personal factors such as communication preferences and service compatibility; and c) flexibility must be exercised to ensure accommodations are timely, effective, and uphold the individual’s dignity and autonomy.
Why should we change it?
This section requires further discussion, and revision for clarity as this will represent some challenges for federal procurement (to understand goals and the parameters to explore for possible implementation). Why is the FAA referenced? Provider familiarity is an issue in procurement, as fairness is a guiding principle of procurement. It might also be relevant to include a reference to the CAN/ASC-1.1:2024 (REV-2025)- Employment in this section, as is addresses “supports” and “accommodation” for employees. Recommend further review and clarification.
Heading text
12.1.1 Exception - Individual accommodation procurement
Heading number portion
12.1.1
Item id
1782234682827_957
Heading id
12.4.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
d. the time period for which a bid(s) will be valid.
What should we change it to?
Delete.
Why should we change it?
The bid validity period should be determined by the factors in the list.
Heading text
12.4.2 Determining the evaluation timeline
Heading number portion
12.4.2
Item id
1782234910806_952
Heading id
12.4.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
The evaluation panel responsible for evaluating bids shall include: individuals with subject matter expertise to evaluate the accessibility requirements of the procurement including: subject matter experts on the good, service or construction being provided; people with disabilities or lived experience who are end users of the good or service; or if required, independent third-party experts with accessibility knowledge of the good, service or construction being procured.
What should we change it to?
The evaluation panel responsible for evaluating bids shall include individuals with subject matter expertise in accessibility to evaluate the accessibility requirements of the procurement, as applicable, such as: a) subject matter experts on the good, service or construction being provided; or b) people with disabilities or lived experience who are end users of the good or service; or c) if required, independent third-party experts with accessibility knowledge of the good, service or construction being procured.
Why should we change it?
To improve the flow of the logic; also provided a separate comment regarding the practicality of this role for all procurements.
Heading text
12.4.3 Identifying the evaluation panel
Heading number portion
12.4.3
Item id
1782235016146_640
Heading id
13.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Note: A reasonable amount of time will vary depending on the solution. Solicitations could consider the time required for a supplier to respond. Solicitations could also factor the time required to prepare documents in accessible formats. It would be important to note that people with disabilities may need to be given enough time to prepare and submit a response to a solicitation.
What should we change it to?
Note: A reasonable amount of time will vary depending on the complexity of the solicitation requirements. The solicitation period should consider the time required by a supplier to review and respond to a bid. It is important to note that businesses owned by a person with a disability may require additional time to prepare and submit a response to a solicitation.
Why should we change it?
As previously identified, the introduction and use of the term “solution” creates confusion. This term should be removed from this standard.
Heading text
13.1 Determining the solicitation period
Heading number portion
13.1
Item id
1782235461080_414
Heading id
13.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
This section requires additional review to clarify a number of questions below.
What should we change it to?
Requires more consideration to address What costs are included? How are costs determined? How to mitigate the risk for the organization?
Why should we change it?
a) What costs can be offset? For example personal support worker, sign language interpreter? Would facility and IT be included? b) How are these costs determined? Are there suggestions for this? For example consulting with businesses owned by persons with disabilities to develop a list of common costs, and then research costs, etc. c) Also missing in this list is the organization's rights if the costs are not determined to be fair and reasonable. As stewards of public funds, the federal government has a responsibility to assess this. For example, the GC may need to negotiate these costs, and set aside bids with unreasonable costs.
Heading text
13.1.1 Accessibility cost treatment in bidding
Heading number portion
13.1.1
Item id
1782235793971_331
Heading id
12.4.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?
Identifying the evaluation panel content
What should we change it to?
If there are requirements for accessibility, then the evaluation panel responsible for evaluating bids shall include:
Why should we change it?
Require some clarity on when accessibility expertise is required in an evaluation. Are there exemptions to this (small dollar value procurements; emergency procurements)? As written this may be perceived as a barrier for an organization.
Heading text
12.4.3 Identifying the evaluation panel
Heading number portion
12.4.3
Item id
1782236121159_389
Heading id
13.6
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
c) if required, provides an equivalent accessible debrief, such as sign language translation of the debrief, in complying with EN 301 549:2024; and
What should we change it to?
c) if required, provides an equivalent accessible debrief, complying with EN 301 549:2024 if provided virtually
Why should we change it?
Suggested for clarity.
Heading text
13.6 Providing an unsuccessful bidder debriefing
Heading number portion
13.6
Item id
1782236204434_188
Heading id
13.6
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Note: When accessibility or translation service is required, the steps should be taken to prevent any conflict of interest. Where possible the service should be provided in-house to the organization, or the bidder may be invited to propose a qualified interpreter or translator for approval. This may include the translation of written debrief to sign language video format to ensure accessibility while maintaining confidentiality and impartiality.
What should we change it to?
Note: When sign language interpretation or a video translation service is required, the steps should be taken to prevent any conflict of interest. Where possible the service should be provided by an employee of the organization, or the bidder may be invited to propose a qualified interpreter or translator for approval by the organization.
Why should we change it?
Required for clarity of role/responsibility.
Heading text
13.6 Providing an unsuccessful bidder debriefing
Heading number portion
13.6
Item id
1782236397237_429
Heading id
14.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
c. Inspection for barriers by persons with disabilities before delivery whether it be at the contractor or the delivery site
What should we change it to?
Unsure that this is practical. As written, would delete.
Why should we change it?
As worded, this requires that for every procurement, persons with disabilities must validate the delivery of the good or service. This is not practical for organizations who have large volumes of procurement. The client is responsible to validate that the deliverables meet all the requirements as set in the specifications for the procurement. Part of the requirements, if accessibility is included in the specifications, could be to require end user acceptance testing at time of deliverables.
Heading text
14.2 Confirming deliverables
Heading number portion
14.2
Item id
1782236476228_581
Heading id
14.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Clients shall be responsible for confirming that the contracted business resolved any end user reported accessibility issues in accordance with the contract.
What should we change it to?
Clients are responsible for confirming that the contractor has resolved any end user reported accessibility issues in accordance with the contract.
Why should we change it?
Revise for clarity
Heading text
14.3 Resolving end user issues
Heading number portion
14.3
Item id
1782236582978_199
Heading id
15.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
i) the purposes of the Accessible Canada Act;
What should we change it to?
a) the purposes of the Accessible Canada Act , resulting Accessible Canada Act Regulations, and the role of Accessibility Standards Canada
Why should we change it?
Recommend adding a reference to the regulations, and Accessibility Standards Canada.
Heading text
15.2 Contents of training
Heading number portion
15.2
Item id
1782236792032_283
Heading id
15.3.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
b. before or immediately after the person joins an organization or begins work with the organization;
What should we change it to?
b. within the 6 months that an employee joins an organization or begins work with the organization;
Why should we change it?
Immediate does not seem reasonable, as federal organizations have on boarding processes that include mandatory training in many areas.
Heading text
15.3.3 Timing
Heading number portion
15.3.3
Item id
1782236864819_934
Heading id
15.3.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
e) whenever a procurement involves a good or service that has received multiple accessibility complaints, or when a new or updated standard becomes available.
What should we change it to?
e) whenever a procurement involves a good or service that has received multiple accessibility complaints, or when a new or updated standard or regulation becomes available.
Why should we change it?
to include changing standards and regulations.
Heading text
15.3.3 Timing
Heading number portion
15.3.3
Item id
1782236911303_625
Heading id
16.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Example of Justification form https://www.canada.ca/en/public-services-procurement/services/acquisitions/temporary-help/templates-for-federal-department-clients/accessibility-criteria-procurement-justification-form.html
What should we change it to?
No suggestion at this time, however, it is not up-to-date.
Why should we change it?
This is not up to date.
Heading text
16.3 Online Resources
Heading number portion
16.3
Item id
1782242041869_109
Heading id
10.1.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
d. The remediation shall be agreed upon by all parties.
What should we change it to?
Recommend further discussion to clarify "parties" and what is included in remediation (roadmap or accommodations)?
Why should we change it?
Questions for further clarification: 1) Who are the parties referred to in this sentence? Contractor/organization? Contractor/end-user? Contractor/end-user/organization? End-user/organization? 2) What does “remediation” mean in the context of this sentence (understanding that remediations may be part of a road map). Does this flow back to the remediations as part of the roadmap approach in item b? Or, does it refer to the temporary remediation/accommodation required to address an end-user complaint reported as a barrier (under item c). IF the latter, these remediations/temporary fixes are considered to be work arounds that are provided by a contractor, while they work towards fully correcting the issues that are documented in the roadmap (plan). 3) Is there any guidance on how to proceed if the accommodation requested by the end user results in undue hardship to the organization or the supplier as this would imply that all parties do not agree to the remediation proposed?
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Submission ID
65666
Submitted by
Andrea.Zervos@tpsgc-pwgsc.gc.ca
Submitted on
Tue, 06/23/2026 - 16:28
Consent to contact
Yes

Individual 65667's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782219030012_299
Heading id
s5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
This Standard provides requirements to create an equitable and accessible procurement process. These requirements provide technical guidance to help organizations facilitate an equitable and accessible procurement process
What should we change it to?
This Standard provides technical requirements and guidance to help organizations create an equitable and accessible procurement process.
Why should we change it?
The first two lines are repetitive and should be streamlined. Also note that requirements tend to be perceived as mandatory whereas guidance tends to be perceived as optional or recommendations.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782219467895_391
Heading id
s5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Procurement professionals can include: i. supply specialists; ii. the contracting authority; iii. contracting officers; iv. materiel management specialists; and v. procurement officers.
What should we change it to?
Procurement professionals can include: i. supply specialists; ii. contracting authorities; iii. contracting officers; iv. buyers; v. materiel management specialists; and vi. procurement officers.
Why should we change it?
Since this standard is written in the federal procurement context, suggest adding “Buyer” to this list as this the new terminology used in the PSPC Buyer’s Portal and Guide. Secondly, items in the list should be parallel with one another in both meaning and form. In this particular list all items are plural except for contracting authority.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782219647587_468
Heading id
s5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
This includes individuals responsible for procurement, employees who support these processes, and businesses who bid on these processes or sell their products.
What should we change it to?
This includes individuals responsible for procurement, employees who support procurement operations, and businesses who bid on these processes or sell their products.
Why should we change it?
The current wording is narrowly focused on individuals who support specific procurements. This should also include individuals, like policy makers, who support the function at a higher level.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782220095642_272
Heading id
s5
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
c. Procurement policy and program service and delivery teams within organizations by ensuring that the user experience and accessibility requirements are incorporated when developing web and non-web content, websites, forms, and digital applications. This also includes, but is not limited to services such as:...
What should we change it to?
c) Procurement policy and program service and delivery teams within organizations by ensuring that the user experience is considered and accessibility requirements are incorporated when developing web and non-web content, websites, forms, and digital applications.
Why should we change it?
I find this to be worded oddly: “ensuring that the user experience…. [is] incorporated when developing web and non-web content, websites, forms, and digital applications”.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782220468770_450
Heading id
s5
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
i. usage tutorials;
What should we change it to?
i. tutorials
Why should we change it?
Is it necessary to specify "usage" tutorial. Would this not be inferred based on the definition of tutorial? Are there other types of tutorials that would not need to be accessible?
Heading text
6. Introduction
Heading number portion
6.
Item id
1782221703231_189
Heading id
s5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
d. End users by ensuring that individuals who use or interact with the goods or services procured are consulted throughout the procurement process to identify and remove barriers.
What should we change it to?
d. End users by ensuring that individuals who use or interact with the goods or services procured are consulted throughout the procurement process to identify and remove barriers, and ensuring that the goods or services procured are usable by the broadest range of end users.
Why should we change it?
This section omits the overall intent, which, is to ensure that the things we buy can be accessed and used by all end users.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782221973470_231
Heading id
s5
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Businesses by ensuring that the procurement process is accessible to those involved in businesses, including those owned by persons with disabilities, or where employees with disabilities support procurement processes.
What should we change it to?
Businesses by ensuring that the procurement process is accessible to individuals involved in businesses, including those owned by persons with disabilities, or where employees with disabilities support procurement processes.
Why should we change it?
This is confusing: "Businesses by ensuring that the procurement process is accessible to those involved in businesses..." By the logic of the next statement those means businesses so here you are saying “businesses involved in businesses”. You may be using “those” in two different contexts in this sentence, where the first use means “individuals”. If that is the case, suggest changing the first instance of “those” to “individuals”.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782222476644_74
Heading id
s5
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Above all and in the spirit of this Standard, people with disabilities are involved in procurement.
What should we change it to?
I am unsure what to suggest, as it's unclear what you are trying to communicate.
Why should we change it?
It feels like something is missing from this statement. It is accurate that persons with disabilities can be involved in procurement (as suppliers, clients, buyers, etc.) but what's missing is why are you stating this. Is the intent to state that people with disabilities should be or must be involved in procurement somehow? Or that the procurement process should be barrier-free so that persons with disabilities can participate? The current wording simply states that they are involved with no further explanation or context.
Heading text
6. Introduction
Heading number portion
6.
Item id
1782223063599_96
Heading id
s6
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
This Standard specifies the technical requirements to help an organization integrate accessibility in procurement. It includes specifications for:
What should we change it to?
This Standard specifies the technical requirements to help an organization integrate accessibility in procurement. It includes technical requirements and guidance on:
Why should we change it?
Overall, the standard uses different words to convey the same thing, rather than using consistent language throughout. Instead, consistent terminology should be used throughout. In this section you state that the standard specifies technical requirements and includes specifications, whereas in the beginning you state that it includes "requirements" that provide "technical guidance". I suggested a modification to the introduction and have suggest a revision here to align with that.
Heading text
7. Scope
Heading number portion
7.
Item id
1782223372367_227
Heading id
7.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
This Standard respects and is complementary to the principles, purpose, and requirements of federal government procurement. Although written in the federal context, the principles should be adapted to other procurement contexts.
What should we change it to?
This Standard respects and is complementary to the principles, purpose, and requirements of federal government procurement. Although written in the federal context, the technical guidance in this Standard should be adapted to other procurement contexts.
Why should we change it?
This is confusing because you are using principles twice but referring to different sets of principles (I believe). In other words, when you say “principles” in the second sentence are you referring to the principles of federal government procurement mentioned in the first sentence or are you referring to the technical guidance included in the standard? I presume the latter and have suggested a revision accordingly.
Heading text
7.2 Other relevant restrictions or considerations
Heading number portion
7.2
Item id
1782223555420_784
Heading id
9.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Accessible format — includes other formats of communicating information including, but not limited to, audio formats, braille, large print, plain language, and sign language.
What should we change it to?
Accessible format — Formats that collectively present information in ways that can be perceived, understood, and used by all individuals. Note 1: There is no one format that is fully accessible to all. Accessible formats are responsive to the needs of the person using the format. Note 2: Examples include (but are not limited to) digital formats, audio formats, braille, print, large print, plain language, and signed languages.
Why should we change it?
Why does this definition refer to an accessible format as an “other format”. It seems to be positioning the “accessible format” as a secondary format whereas, instead, the primary format of the material should be accessible. I prefer the definition used in 9. Definitions - Accessibility Standards Canada (which I inserted in the What should we change it to box).
Heading text
9.1 Definitions
Heading number portion
9.1
Item id
1782223984630_838
Heading id
9.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Competitive contract — a contract that is entered into by soliciting more than one bid.
What should we change it to?
Delete.
Why should we change it?
This term is not used in this document. Note: You do use these other terms "Competitive solicitation" and "Competitive procurement". As an option, you could use the term "competitive procurement"; change all instances of "competitive solicitation" to "competitive procurement" add a definition for it. Here is the definition of "competitive procurement" from the Policy on the Planning and Management of Investments (https://www.tbs-sct.canada.ca/pol/doc-eng.aspx?id=32593): competitive procurement (approvisionnement concurrentiel) The solicitation of bids from more than one supplier.
Heading text
9.1 Definitions
Heading number portion
9.1
Item id
1782229055665_274
Heading id
9.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Non-competitive contract — a contract that is entered into without soliciting bids.
What should we change it to?
Delete.
Why should we change it?
This term is not used in this document. Note: You do use this other "non-competitive solicitation".
Heading text
9.1 Definitions
Heading number portion
9.1
Item id
1782229157715_758
Heading id
9.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Purchasing — the buying process within the procurement cycle.
What should we change it to?
Delete.
Why should we change it?
This term is not used in this document.
Heading text
9.1 Definitions
Heading number portion
9.1
Item id
1782229311113_821
Heading id
9.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Subject matter expert in accessibility — means a person who has knowledge of a specified field such as the built environment, information and communication technology, and human resources based on a combination of the following factors, which may be weighted differently depending on the circumstances: Lived experience relating to accessibility. Relevant industry work experience. Formal education or training. Professional practice within the subject area.
What should we change it to?
Accessibility subject matter expert — means a person who has knowledge of a specified field such as the built environment, information and communication technology, and human resources based on a combination of the following factors, which may be weighted differently depending on the circumstances: a. Lived experience relating to accessibility. b. Relevant industry work experience. c. Formal education or training. d. Professional practice within the subject area.
Why should we change it?
The term "Subject matter expert in accessibility" is not used in this Standard. You do however use the term Accessibility subject matter expert, so I have suggested a revision to the term to align.
Heading text
9.1 Definitions
Heading number portion
9.1
Item id
1782235957550_377
Heading id
10.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Policies and procedures shall state that accessibility requirements: a. be included throughout the procurement process including: i. all phases of procurement (planning, bidding and contract award, and contract management and closeout); and ii. any competitive or non-competitive solicitation and resulting method of supply such as contracts, standing offers, or supply arrangements; b. be included in the specifications for the procurement of goods and services including: i. developing evaluation criteria and throughout the evaluation process; ii. identifying testing requirements at the solicitation and contract phase; iii. developing solicitation and contract documents; and iv. delivering industry engagement activities; and
What should we change it to?
Policies and procedures shall state that for any competitive or non-competitive solicitation and resulting method of supply (such as contracts, contract amendments, standing offers, or supply arrangements): a. accessibility requirements be included throughout all phases of procurement process (planning, bidding and contract award, and contract management and closeout) including when; i. developing evaluation criteria and throughout the evaluation process; ii. identifying testing requirements at the contract phase; iii. developing solicitation and contract documents; iv. delivering industry engagement activities; and b. accessibility requirements be included in the specifications for the procurement of goods and services including: i. identifying testing and conformance requirements; and
Why should we change it?
Assuming that “specifications” refers to technical or performance specifications; the following items are not included in specifications: evaluation criteria used to select the best supplier, testing carried out during the solicitation phase, solicitation and contract documents, and industry engagement activities. Therefore, these items should be removed from this list. They can be added to the above list instead. If “specifications” is intended to mean something else, suggest clarifying and adding a definition, although given this standard reflects the federal context I would suggest using terminology consistent with that used in the federal context. WTO-AGP definition of Technical Specification: (u) technical specification means a tendering requirement that: i. lays down the characteristics of goods or services to be procured, including quality, performance, safety and dimensions, or the processes and methods for their production or provision; or ii. addresses terminology, symbols, packaging, marking or labelling requirements, as they apply to a good or service. https://www.wto.org/english/tratop_e/gproc_e/gpa_1994_e.htm
Heading text
10.1.1 Incorporating accessibility
Heading number portion
10.1.1
Item id
1782236337824_876
Heading id
10.1.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Policies and procedures shall state that accessibility requirements: be included throughout the procurement process including: all phases of procurement (planning, bidding and contract award, and contract management and closeout); and any competitive or non-competitive solicitation and resulting method of supply such as contracts, standing offers, or supply arrangements; be included in the specifications for the procurement of goods and services including: developing evaluation criteria and throughout the evaluation process; identifying testing requirements at the solicitation and contract phase; developing solicitation and contract documents; and delivering industry engagement activities; and when accessibility requirements are not included in the specifications for a procurement, a mandatory written justification complying with Clause 10.1.4 shall be provided.
What should we change it to?
Policies and procedures shall state that for any competitive or non-competitive solicitation and resulting method of supply (such as contracts, contract amendments, standing offers, or supply arrangements): a. accessibility requirements be included throughout all phases of procurement process (planning, bidding and contract award, and contract management and closeout) including when; i. developing evaluation criteria and throughout the evaluation process; ii. identifying testing requirements at the contract phase; iii. developing solicitation and contract documents; iv. delivering industry engagement activities; and b. accessibility requirements be included in the specifications for the procurement of goods and services including: i. identifying testing and conformance requirements; and
Why should we change it?
Grammatically item C does not fit with the list which starts with “Policies and procedures shall state that accessibility requirements. Note: There is a general issue with Parallelism in the lists used in the Standard. A review of all lists should be conducted to ensure that all items in bullet lists follow a consistent format and structure.
Heading text
10.1.1 Incorporating accessibility
Heading number portion
10.1.1
Item id
1782237580648_339
Heading id
10.1.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
include technical evaluation criteria to assess the bidder’s capacity to deliver against accessibility specifications;
What should we change it to?
include technical evaluation criteria to assess the bidder’s capacity to deliver against accessibility requirements;
Why should we change it?
For consistency with all other sections change “specifications” to “requirements”.
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782237913492_961
Heading id
10.1.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
d) verify that contract deliverables incorporated accessibility requirements as defined in the solicitation.
What should we change it to?
d) verify that contract deliverables incorporate accessibility requirements as defined in the specifications.
Why should we change it?
Change verb tense as the deliverables should continue to incorporate accessibility requirements. Change solicitation to specifications as this is the document that includes the accessibility requirements for the work to be done under the contract.
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782238208121_320
Heading id
10.1.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
provide a mandatory written justification complying with Clause 10.1.4 when accessibility requirements are not included in the specifications for a procurement; and
What should we change it to?
provide a mandatory written justification complying with Clause 10.1.4 when accessibility requirements are not included in the specifications; and
Why should we change it?
It is not necessary to repeat the statement "for a procurement" as it is addressed in the lead in paragraph which states: "Policies and procedures shall outline roles and responsibilities for clients and procurement professionals when defining the requirements of the procurement including:"
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782238756911_661
Heading id
10.1.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
when applicable, advise the client of their responsibility to include accessibility requirements in the specifications for the goods and services being procured;
What should we change it to?
advise the client of their responsibility to include accessibility requirements in the specifications, where applicable;
Why should we change it?
It’s not clear what “when applicable” means in this bullet. Does it mean that they need to advise clients when the requirement to consider accessibility is applicable (inferring that sometimes its not)? Does it mean that that they need to advise the client of their responsibility to include accessibility requirements when accessibility requirements are applicable to the good or service being procured? Additionally, it is not the procurement professional's responsibility to identify when accessibility requirements apply to the good or service (as they may not have the technical knowledge to make this assessment). This is the client's responsibility. The language here should be mindful of the division of responsibilities. The role of the procurement professional in this context is to remind the client of their responsibility to consider accessibility and include accessibility requirements. It is not to determine when accessibility requirements apply.
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782239637506_867
Heading id
10.1.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
the responsibility of the procurement professional to: when applicable, advise the client of their responsibility to include accessibility requirements in the specifications for the goods and services being procured; Note: Item b) i) of this Clause applies to the procurement professional if they are responsible for creating and defining the requirements for a method of supply such as a supply arrangement or standing offer. assist the client by identifying subject matter experts and relevant resources that can help to develop accessibility requirements; when applicable, play a challenge function when clients have not included accessibility requirements in the procurement; and when accessibility requirements are not included in the specifications for a procurement, verify that a mandatory written justification complying with Clause 10.1.4 is provided.
What should we change it to?
a) the responsibility of the procurement professional to: i) advise the client of their responsibility to include accessibility requirements in the specifications, where applicable; ii) assist the client by identifying subject matter experts and relevant resources that can help to develop accessibility requirements; iii)play a challenge function when clients have not included accessibility requirements in the specifications; and iv)when accessibility requirements are not included in the specifications, verify that a mandatory written justification complying with Clause 10.1.4 is provided.
Why should we change it?
1) Consider adding a definition for “specifications” then streamlining this section to remove extra words. For example, WTO-AGP definition of Technical Specification: (u) technical specification means a tendering requirement that: i. lays down the characteristics of goods or services to be procured, including quality, performance, safety and dimensions, or the processes and methods for their production or provision; or ii. addresses terminology, symbols, packaging, marking or labelling requirements, as they apply to a good or service. https://www.wto.org/english/tratop_e/gproc_e/gpa_1994_e.htm 2) I believe the note is in the wrong place. Instead it should be under item a) and it should state: Note: Item a) applies to the procurement professional if they are responsible for creating and defining the requirements for a method of supply such as a supply arrangement or standing offer. 3) For consistency change "procurement" in item b(iii) to specifications. If you keep this as procurement it could imply that if accessibility requirements are included in the process (accessible bid solicitation documents for example), they don't need to play a challenge function if they are not included in the specifications. 4) Bullet b(iii) already states when it applies so it’s not necessary to say “when applicable” at the beginning. 5)It is not necessary to repeat "for a procurement" in the bullets as it is already stated in the lead in paragraph.
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782240083454_80
Heading id
10.1.3.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Flexibility in the procurement strategy shall provide an opportunity to integrate accessibility requirements into a procurement instead of excluding it.
What should we change it to?
Procurement professionals shall design procurement strategies that provide opportunities to integrate accessibility requirements into the procurement instead of excluding them.
Why should we change it?
The statement is not easy to understand. I have proposed a revision but generally, I'm unsure what message the statement is trying to convey.
Heading text
10.1.3.1 General
Heading number portion
10.1.3.1
Item id
1782240326081_560
Heading id
10.1.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
a. Procurement policies shall specify that clients adopt a flexible approach to meeting accessibility requirements when conformance at the time of solicitation closing is not possible.
What should we change it to?
a. Procurement policies shall specify that clients adopt a flexible approach that permits suppliers to meet accessibility requirements after the solicitation closing date when conformance at the time of solicitation closing is not possible.
Why should we change it?
The current wording reads like you are referring to the approach for the client to meet the requirements as opposed to the supplier.
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Item id
1782240641362_49
Heading id
10.1.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Note: An example of applying a flexible approach is for the purchase of a commercial, off-the-shelf solution that does not meet accessibility standards at contract award.
What should we change it to?
Note: A flexible approach could be applied for the purchase of a commercial, off-the-shelf product that does not meet accessibility standards at solicitation closing.
Why should we change it?
This example is incomplete. It provides an example of a commodity where the approach could be applied but does not provide an example of how the approach would apply in this context. Secondly in the statement directly above you refer to solicitation closing and in the example you refer to contract award.
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Item id
1782241311296_864
Heading id
10.1.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
The remediation shall be agreed upon by all parties.
What should we change it to?
Define who the parties are, ensure that it is clear what remediation this item is referring to and include guidance about what to do when the parties do not agree (for example, where one party's preferred accommodation would result in undue hardship to the organization or supplier).
Why should we change it?
1) Who are the parties referred to in this sentence? 2) What does “remediation” mean in the context of this sentence (understanding that remediations may be part of a road map). Do you mean the remediations proposed in the roadmap (under item b) or do you mean the remediations provided in response to an end user reported barrier (under item c). If you mean item C, these are typically considered accommodations or work arounds (that are offered while an organization is working towards fully remediating an issue). 3) Is there any guidance on how to proceed if the accommodation requested by the end user results in undue hardship to the organization or the supplier as this would imply that all parties do not agree to the remediation (assuming that the parties include the end-user).
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Item id
1782241510021_157
Heading id
10.1.3.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
At the request of the client and in addition to the roadmap, the contractor shall provide methods of remediation to end users when accessibility barriers are reported during the remediation period.
What should we change it to?
At the request of the client and in addition to the roadmap, the contractor shall provide workarounds or accommodations to end users when accessibility barriers are reported during the remediation period.
Why should we change it?
I don’t think remediation is the right word in this context. Remediation would mean repair the non-conformance issue and removing barriers. The whole purpose of the roadmap is to remediate the solution. I think in this context you mean temporary accommodations or workarounds while the repair is being done (for example, refer to Accessibility remediation roadmap template- Digital Accessibility Toolkit https://a11y.canada.ca/en/accessibility-remediation-roadmap-template/)
Heading text
10.1.3.2 Flexible procurement requirements
Heading number portion
10.1.3.2
Item id
1782241864744_171
Heading id
10.1.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
provide the reasons why accessibility requirements were not included in the procurement and provide information on the decision-making process to exclude accessibility requirements, including the following activities, if applicable:
What should we change it to?
provide the reasons why accessibility requirements were not included in the specifications and provide information on the decision-making process to exclude accessibility requirements, including the outcome of the following activities, if applicable:
Why should we change it?
The justification should describe the outcome of the each of the sub bullets. For example, it's helpful to indicate that research was done to identify accessibility standards but it should also clarify why standards weren't added.
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782241960789_342
Heading id
10.1.4.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
developing a flexible procurement approach complying with Clause 10.1.3; and
What should we change it to?
considering the use of a flexible procurement approach complying with Clause 10.1.3; and
Why should we change it?
If the client is providing a justification, this would mean that they considered using a flexible approach and decided not to, so I don't think developing is the right word to use here.
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782242211467_981
Heading id
10.1.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Note 1: Discretion must be used when determining the reasons why accessibility requirements might not be applicable. For example, there is a difference in the reasons why accessibility is not applicable for a procurement looking to acquire construction materials as compared to a procurement looking to implement a new human resource platform for employees[P
What should we change it to?
Note 1: Discretion must be used when determining the reasons why accessibility requirements might not be applicable. For example, the justification provided for excluding accessibility requirements from one procurement may not be applicable to another.
Why should we change it?
This example implies that accessibility could not be included for a digital employee facing HR platform. Given the the recent amendments to Accessible Canada Regulations, accessibility requirements should be included for these types of procurement. Suggest removing this example.
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782242948186_43
Heading id
10.1.4.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
a. require a mandatory written justification from clients if accessibility requirements were excluded from the procurement. b. provide the reasons why accessibility requirements were not included in the procurement and provide information on the decision-making process to exclude accessibility requirements, including the following activities, if applicable:
What should we change it to?
a. require a mandatory written justification from clients if accessibility requirements were excluded from the specification. b. provide the reasons why accessibility requirements were not included in the specifications and provide information on the decision-making process to exclude accessibility requirements, including the outcome of the following activities, if applicable:
Why should we change it?
In this section, you say "require a mandatory written justification from clients if accessibility requirements were excluded from the procurement." Under the Directive on the Management of Procurement, procurement is defined as: The process related to obtaining goods, services or construction from the planning to the completion of the procurement life cycle. In the context of this requirement, if a contracting authority includes accessibility requirements in the procurement process (for example, they create an accessible solicitation document), is it necessary to provide a justification? Technically, this would constitute including accessibility requirements in the procurement. Furthermore, under the Directive, business owners (or clients) are required to ensure clear justification is documented if it is determined that accessibility considerations are not consistent with modern treaties or trade agreements, or if it is not appropriate to include them as part of commodity specifications, or if it is not possible to obtain goods, services or construction that comply. The Directive also refers to including accessibility considerations in the specifications. Suggest changing "procurement" to "specifications.
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782243631750_362
Heading id
11.4.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Information from engagement activities should provide clients with the information necessary to: determine whether to proceed with planned requirements for procurement; determine if refinements should be made to the procurement including: the procurement strategy; the procurement structure; cost estimates; timelines; goods and services requirements; or any other aspect of the procurement requirements; enhance their understanding of industry goods and service offerings in the areas of interest; and assess alternative solutions that would meet its requirements, such as accessibility requirements for goods.
What should we change it to?
Information from engagement activities should provide clients with the information necessary to: a. determine whether to proceed with planned requirements for procurement; b. determine if refinements should be made to the procurement including: i. the procurement strategy; ii. the procurement structure; iii. cost estimates; iv. timelines; v. goods and services requirements including accessibility requirements; or vi. any other aspect of the procurement requirements; c. enhance their understanding of industry goods and service offerings in the areas of interest; and d. assess alternative solutions that would meet its requirements including its accessibility requirements.
Why should we change it?
The language in item d. is confusing. When I first read it I thought it was positioning the accessibility requirements for goods as an alternative solution.
Heading text
11.4.2 Information from engagement activities
Heading number portion
11.4.2
Item id
1782243817557_943
Heading id
11.4.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
follow the list of considerations below to tailor in-person and virtual activities, including but not limited to:
What should we change it to?
when planning the activity, incorporate accessibility requirements, including but not limited to:
Why should we change it?
This section is unclear. As the reader I am unsure what I need to do with the list? Do I need to ensure that when I plan my event I incorporate these accessibility features? This list identifies different types of accessibility requirements but doesn’t explain what “following” them means.
Heading text
11.4.3 Identifying accommodation needs
Heading number portion
11.4.3
Item id
1782244319841_986
Heading id
11.4.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Any physical mobility requirements, with the opportunity to specify the requirement.
What should we change it to?
Unsure what to propose as the statement is unclear. Perhaps: Any built environment requirements, including: 1.compliance with CSA/ASC B651:23 2. accessible meeting rooms 3. facility emergency egress
Why should we change it?
This bullet doesn't follow the same logic as the subsequent bullets. The subsequent items provide examples of accessibility features whereas this list provides none. By physical mobility requirements, do you mean built environment requirements (such as those identified in the facilities specifications below). Who has the opportunity to specify the requirement? And what requirement are they specifying.
Heading text
11.4.3 Identifying accommodation needs
Heading number portion
11.4.3
Item id
1782244612105_16
Heading id
11.4.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
e. proactively implement accessibility measures that support participants who may not feel safe disclosing their disability or accommodation needs. These measures should reference and align with CAN-ASC-5.2.1:Part 1 (draft standard). While not all accommodations can be universally applied, many can be adopted without overburdening the process or reducing the quality of engagement.
What should we change it to?
e. proactively implement accessibility measures that support participants who may not feel safe disclosing their disability or accommodation needs. These measures should reference and align with CAN-ASC-5.2.1:Part 1 (draft standard). While not all accommodations can be universally applied, many can be adopted without overburdening the process or reducing the quality of engagement.
Why should we change it?
Bullet e initially speaks to implement measures to support participants who may not feel safe disclosing. The sentence that follows reads as a separate concept. "While not all accommodations can be universally applied, many can be adopted without overburdening the process or reducing the quality of engagement." Perhaps it should be removed from the list and included at the same level as "Whether an engagement activity will be held in-person or virtually, the organizers shall:"
Heading text
11.4.3 Identifying accommodation needs
Heading number portion
11.4.3
Item id
1782244714707_194
Heading id
11.4.4.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
When an outreach session is planned in-person, the client shall conduct a site assessment to comply with the requirements of Clauses 11.4.4.3 through 11.4.4.6.
What should we change it to?
When an engagement activity is planned in-person, the client shall conduct a site assessment to verify that the facility complies with the requirements of Clauses 11.4.4.3 through 11.4.4.6.
Why should we change it?
1) Suggest revising language to align with the overall section which refers to engagement activities. 2) Are you saying that the site assessment needs comply with these requirements or that the facility needs to do so? I believe the latter and have suggested a revision.
Heading text
11.4.4.2 Facility assessment
Heading number portion
11.4.4.2
Item id
1782244939267_391
Heading id
11.4.4.4
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
The following built environment elements that facilitate in-person events shall:
What should we change it to?
Facilities that are used for in-person events shall:
Why should we change it?
Using item 3 as an example, this what this sentence reads as: The following built environment elements that facilitate in-person events shall have eating facilities that are accessible including braille or large-print menus available in eating facilities. This is confusing and unclear.
Heading text
11.4.4.4 Facility specifications
Heading number portion
11.4.4.4
Item id
1782245754538_808
Heading id
11.4.4.4
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Reduce functional and cognitive barriers Environmental intolerances;
What should we change it to?
Delete from this list and create a separate section for these two items or revise them so that they align with the other items in the list.
Why should we change it?
The lead in sentence says "1) comply with CSA/ASC B651:23 for:". Reduce functional and cognitive barriers and Environmental intolerances read as if they were added to this section without considering the context of the lead in sentence.
Heading text
11.4.4.4 Facility specifications
Heading number portion
11.4.4.4
Item id
1782245847941_926
Heading id
11.4.4.5
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Meeting rooms that are used for in-person outreach events shall provide the following, including but not limited to:
What should we change it to?
Meeting rooms that are used for in-person engagement activities shall provide the following, including but not limited to:
Why should we change it?
Consistency with the introduction section.
Heading text
11.4.4.5 Meeting rooms
Heading number portion
11.4.4.5
Item id
1782245903456_402
Heading id
11.4.5.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
If an engagement event is hosted virtually, the organizer of the event shall:
What should we change it to?
If an engagement activity is hosted virtually, the organizer of the event shall:
Why should we change it?
Consistency with the introduction section.
Heading text
11.4.5.2 Virtual engagement requirements
Heading number portion
11.4.5.2
Item id
1782246474087_741
Heading id
11.4.5.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
b) provide relay services complying with CAN/ASC EN-301 549:2024;
What should we change it to?
b) provide relay services, when requested, complying with CAN/ASC EN-301 549:2024;
Why should we change it?
Does this mean that relay services need to be provided by default for all engagement events or is the idea that when they are provided they comply with the CAN/ASC EN-301 549:2024? Is it practical to provide relay service by default for every event?
Heading text
11.4.5.2 Virtual engagement requirements
Heading number portion
11.4.5.2
Item id
1782246606113_508
Heading id
11.4.5.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
provide documents complying with Clause 11; and
What should we change it to?
provide documents complying with Clause 11.2; and
Why should we change it?
Consistency with other sections that refer specifically to clause 11.2.
Heading text
11.4.5.2 Virtual engagement requirements
Heading number portion
11.4.5.2
Item id
1782246818679_992
Heading id
12.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
identify applicable accessibility standards, guidelines, and best practices, and in such cases where no applicable references are available, continue to follow the procurement process and make reasonable efforts to identify a solution;
What should we change it to?
i) identify applicable accessibility standards, guidelines, and best practices;
Why should we change it?
This portion of the sentence is confusing: "continue to follow the procurement process and make reasonable efforts to identify a solution;" I don't understand what this means so I have no suggestion on how to improve it.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782247074338_656
Heading id
12.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
v. where no clear suitable solution can be found, follow the mandatory justification for excluding accessibility set out in Clause 10.1.4.
What should we change it to?
I don’t understand what is meant by the term solution in this context so I have no suggestion on how to improve this statement.
Why should we change it?
I don’t understand what is meant by the term solution in this context so I have no suggestion on how to improve this item. If solution means a good or service, if you can’t find a solution then you would technically not be buying anything and there would be no need to write a justification. Or do you mean a solution to an issue and if so what is the issue?
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782247241314_273
Heading id
12.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Note: Organizations are encouraged to collaborate with vendors to develop curated source lists that prioritize accessibility, while also identifying suppliers and organizations with demonstrated accessibility expertise to maintain a current and reliable list of resources and services.
What should we change it to?
Organizations shall prioritize accessibility when establishing source lists and methods of supply.
Why should we change it?
If the intent of standard is to consider accessibility in everything we are buying, why are we creating “curated source lists”; shouldn’t all source lists prioritize accessibility? On the second portion, are you suggesting setting up a source list for business support services specializing in accessibility? In terms of “demonstrated accessibility expertise” how would this be assessed? What constitutes sufficient expertise?
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782247327413_19
Heading id
12.1
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
engage with industry (network of potential suppliers) and organizations who have procured similar goods or services to understand market capacity to help develop a procurement strategy that includes accessibility requirements; and
What should we change it to?
engage with industry (network of potential suppliers) and organizations who have procured similar goods or services to understand market capacity; and
Why should we change it?
The lead in sentence says the purpose of doing this is to identify and define accessibility requirements for procurement so it's not necessary to repeat it.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782249099623_281
Heading id
12.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Where procurement is conducted to meet the specific accommodation needs of a person with a disability, standard competitive procurement rules may be set aside in recognition of obligations under the Accessible Canada Act, the Employment Equity Act, and the Financial Administration Act. In such cases:
What should we change it to?
I do not have a suggestion on how to change this. I think this section requires a comprehensive review in consideration of the federal procurement context (which the Standard states it is intended to be consistent with). The section implies that obligations under the GCRs and Trade Agreements can be set aside without providing a legal rationale for doing so. This could result in legal risks for federal departments and agencies.
Why should we change it?
In the federal procurement context, the Government Contracts Regulations require procurements to be competed subject to certain exceptions. Additionally, Canada is a party to various Trade Agreements which require procurements to be competed (also subject to certain exceptions). The Trade Agreements are enabled by Acts of Parliament. The justification or rationale to "set aside" these legal obligations based on the Accessible Canada Act, the Employment Equity Act, and the Financial Administration Act is not provided. Was a legal opinion sought on the rationale for "setting aside" the GCRs? That said, the Trade Agreements and GCRs allow for limited tendering or directing contracts in certain circumstances with a documented justification for doing so. Perhaps the message of this section should be to work within the parameters of the existing legal framework to procure the accommodation.
Heading text
12.1.1 Exception - Individual accommodation procurement
Heading number portion
12.1.1
Item id
1782249484039_754
Heading id
12.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
the individual shall be involved in evaluating and selecting the solution;
What should we change it to?
the individual may be involved in evaluating and selecting the solution;
Why should we change it?
In the above section there is note that refers to setting up “curated source lists” that prioritize accessibility. Sometimes when establishing a source list, products are evaluated against certain technical requirements at the time the list is created. If you then direct clients to use these pre-evaluated source lists, it may not be feasible for the individual to be included in the evaluation process. For example, the individual may have joined the team after the source list was established, the individual may not have the technical expertise to evaluate the product (against the EN 301 549, for example) or it may not be practical to include all potential end users in the evaluation process.
Heading text
12.1.1 Exception - Individual accommodation procurement
Heading number portion
12.1.1
Item id
1782250717984_372
Heading id
12.1.1
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
b) evaluation may include personal factors such as communication preferences, provider familiarity, and service compatibility; and
What should we change it to?
b) evaluation may include personal factors such as communication preferences, and service compatibility; and
Why should we change it?
Suggest removing the item referring to "provider familiarity". This could result in a risk of challenge on the basis of unfair advantage or conflict of interest as there could be a perception of preferential treatment or advantages to the provider. For example, the PSPC Code of Conduct states the following: "Official duties and responsibilities, including contracting In your day-to-day work: avoid making decisions that could benefit or disadvantage someone you have a personal relationship with—this includes decisions related to program operations, financial awards or penalties, transfer payments, or any other exercise of responsibility recuse yourself if a relationship could affect your objectivity" https://www.canada.ca/en/public-services-procurement/corporate/accountability/code-conduct/managing-conflicts-interest.html
Heading text
12.1.1 Exception - Individual accommodation procurement
Heading number portion
12.1.1
Item id
1782251191101_256
Heading id
12.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
include subcontracting requirements for this testing within the requirements of the procurement; and
What should we change it to?
Delete.
Why should we change it?
Would it not be permissible for the organization to conduct it's own testing or hire a testing company directly as opposed to subcontracting it out through the supplier? Why would we restrict ourselves to this approach? Note: the Accessible Canada Regulations use the terms “conduct or obtain” when referring to the accessibility conformance assessment.
Heading text
12.2 Identifying requirements for testing
Heading number portion
12.2
Item id
1782251303222_243
Heading id
12.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
state that third-party testing will be required in solicitation documents.
What should we change it to?
state that third-party testing is required or will be conducted in solicitation documents.
Why should we change it?
Would it not be permissible for the organization to conduct it's own testing or hire a testing company directly as opposed to subcontracting it out through the supplier? Why would we restrict ourselves to this approach? Note: the Accessible Canada Regulations use the terms “conduct or obtain” when referring to the accessibility conformance assessment.
Heading text
12.2 Identifying requirements for testing
Heading number portion
12.2
Item id
1782251367542_652
Heading id
12.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Any solicitation documents including amendments shall comply with Clause 11.
What should we change it to?
Any solicitation documents including amendments shall comply with Clause 11.2.
Why should we change it?
Consistency with other sections that refer specifically to clause 11.2.
Heading text
12.3 Preparing solicitation documents
Heading number portion
12.3
Item id
1782251455018_677
Heading id
12.4.2
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
the complexity of the bid, including accessibility requirements, of the bid;
What should we change it to?
the complexity of the bid, including accessibility requirements;
Why should we change it?
Of the bid repeated twice.
Heading text
12.4.2 Determining the evaluation timeline
Heading number portion
12.4.2
Item id
1782251845134_485
Heading id
12.4.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
the time period for which a bid(s) will be valid.
What should we change it to?
Delete.
Why should we change it?
The bid validity period should consider a and b as well.
Heading text
12.4.2 Determining the evaluation timeline
Heading number portion
12.4.2
Item id
1782252109554_595
Heading id
12.4.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
12.4.3 Identifying the evaluation panel The evaluation panel responsible for evaluating bids shall include: individuals with subject matter expertise to evaluate the accessibility requirements of the procurement including: subject matter experts on the good, service or construction being provided; people with disabilities or lived experience who are end users of the good or service; or if required, independent third-party experts with accessibility knowledge of the good, service or construction being procured.
What should we change it to?
12.4.3 Identifying the evaluation panel The evaluation panel responsible for evaluating bids shall include: individuals with subject matter expertise to evaluate the accessibility requirements of the procurement including: subject matter experts on the good, service or construction being provided; or people with disabilities or lived experience who are end users of the good or service; or if required, independent third-party experts with accessibility knowledge of the good, service or construction being procured.
Why should we change it?
Formatting is confusing in this list. Is this supposed to mean evaluators include: i and ii ? OR i and iii ? OR i or ii or iii ? I believe the last one in my list above is the most appropriate option.
Heading text
12.4.3 Identifying the evaluation panel
Heading number portion
12.4.3
Item id
1782252708206_758
Heading id
13.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?
13.1.1 Accessibility cost treatment in bidding To promote equitable and inclusive participation in procurement opportunities, clients and procurement professionals shall: provide bidders an opportunity to itemize any costs expected to be incurred to accommodate themselves or their employees during the performance of the work under the contract; request that bidders provide these costs separately from other costs associated to the financial proposal (e.g., these should be provided in an appendix or cost breakdown table); describe in the solicitation document how these accommodation-related costs will be assessed; ensure the accommodation-related costs are not included in the evaluation of the financial proposals; validate, prior to contract award, that the accommodation-related costs are fair and reasonable; and, ensure that the accommodation-related costs are reflected in the basis of payment of the resulting contract.
What should we change it to?
Refer to comments below.
Why should we change it?
One thing that is missing in this list is the organization's rights if the costs are not determined to be fair and reasonable. In the federal procurement context, as stewards of public funds, we have a responsibility to ensure that prices are fair and reasonable. Examples of our rights might be to: negotiate these costs, and set aside bids with unreasonable costs.
Heading text
13.1.1 Accessibility cost treatment in bidding
Heading number portion
13.1.1
Item id
1782252804464_147
Heading id
13.4
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
When preparing responses to bidding inquiries, procurement professionals and clients shall prepare a written response in plain language complying with Clause 11.2.
What should we change it to?
When preparing written responses to bidding inquiries, procurement professionals and clients shall use plain language complying with Clause 11.2.
Why should we change it?
Editorial changes to simplify the text.
Heading text
13.4 Responding to bidding inquiries
Heading number portion
13.4
Item id
1782252852944_221
Heading id
13.6
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
provides documents in an accessible format and in plain language complying with Clause 11;
What should we change it to?
provides documents in an accessible format and in plain language complying with Clause 11.2;
Why should we change it?
Consistency with other sections that refer to 11.2.
Heading text
13.6 Providing an unsuccessful bidder debriefing
Heading number portion
13.6
Item id
1782252995087_882
Heading id
13.6
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
if required, provides an equivalent accessible debrief, such as sign language translation of the debrief, in complying with EN 301 549:2024; and
What should we change it to?
if required, provides an equivalent accessible debrief complying with EN 301 549:2024 when delivered virtually; and
Why should we change it?
Unclear reference to EN 301 549:2024. Is there a specific clause you are referring to or is the intent to say that if delivered virtually the platform needs to conform with the EN 301 549. Also, the sign language interpretation requirement is included in the prior clause.
Heading text
13.6 Providing an unsuccessful bidder debriefing
Heading number portion
13.6
Item id
1782253439851_678
Heading id
13.6
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
if required, ensures sign language interpretation is provided to debrief meetings, and allow reasonable time extension past the deadline to unsuccessful bidders.
What should we change it to?
if required, provides sign language interpretation.
Why should we change it?
Unclear why the deadline to submit submit the request for debriefing would need to be extended in this case. Perhaps this can be clarified? Perhaps you a referring to another timeline? If yes, suggest clarifying which timeline you are referring to.
Heading text
13.6 Providing an unsuccessful bidder debriefing
Heading number portion
13.6
Item id
1782253938754_238
Heading id
14.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
Inspection for barriers by persons with disabilities before delivery whether it be at the contractor or the delivery site
What should we change it to?
Delete or make an optional (with examples of when this might be completed).
Why should we change it?
Unsure that this requirement can practically be implemented as it would require persons with disabilities to inspect all contract deliverables on all contracts with accessibility requirements (which ideally should be included in almost everything we buy).
Heading text
14.2 Confirming deliverables
Heading number portion
14.2
Item id
1782254078499_52
Heading id
14.3
What kind of suggestion are you making?
Editorial such as spelling, grammar, formatting and accessibility
What should we change?
Clients shall be responsible for confirming that the contracted business resolved any end user reported accessibility issues in accordance with the contract.
What should we change it to?
Clients are responsible for confirming that the contractor has resolved any end user reported accessibility issues in accordance with the contract.
Why should we change it?
Consistency of language.
Heading text
14.3 Resolving end user issues
Heading number portion
14.3
Item id
1782254287080_593
Heading id
15.3.3
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
15.3.3 Timing Training complying with Clause 15.2 shall be provided: to all individuals listed in Clause 15.1; before or immediately after the person joins an organization or begins work with the organization; when there are changes to policies, practices, and information regarding accessible procurement; at a minimum of every 2 years; and whenever a procurement involves a good or service that has received multiple accessibility complaints, or when a new or updated standard becomes available.
What should we change it to?
Perhaps training should be completed within 3-6 months of joining the organization as opposed to immediately.
Why should we change it?
Is it feasible to require individuals to complete the training immediately?
Heading text
15.3.3 Timing
Heading number portion
15.3.3
Item id
1782255289561_903
Heading id
11.2.2
What kind of suggestion are you making?
Technical such as dimensions or application of the standard
What should we change?
The following documents shall comply with CAN-ASC-3.1:2025: ... Solicitation and contract award documents
What should we change it to?
Refer to comments below.
Why should we change it?
This will be very difficult and costly to implement, considering the thousands of solicitation documents that the government issues each year. How does the requirement align with the Plain Language requirements in the Accessible Service Delivery standard? Instead of requiring the full solicitation to be in plain language, another option could be to require the Tender Notice to be in Plain Language. The Tender Notice summarizes solicitation. The provisions for public advertisement/notification and what needs to be included in Tender Notice are described in each of the trade agreements, including: ⦁ Canada-European Union Comprehensive Economic and Trade Agreement (CETA): Article 19.6: Notices ⦁ World Trade Organization - Agreement on Government Procurement (WTO-AGP): Article VII: Notices ⦁ Canadian Free Trade Agreement (CFTA): refer to “Tender Notices” article. Note that publishing the Tender Notice in Plain Language will still be challenging to implement as procurement professionals and their clients will require upskilling and tools to support them.
Heading text
11.2.2 Plain language summary
Heading number portion
11.2.2
Submission ID
65667
Submitted by
heather.wilson@tpsgc-pwgsc.gc.ca
Submitted on
Tue, 06/23/2026 - 19:25
Consent to contact
Yes

Individual 65668's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782223772554_225
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?
- What is the expectation with regards to the roadmap in 10.1.3.2 (b), if remediation is not achieved? - Is the expectation to comply with accessibility standards in all situations, including for procurement to respond to emergency situations?
What should we change it to?
.
Why should we change it?
.
Heading text
10. General requirements
Heading number portion
10.
Item id
1782223808012_711
Heading id
s10
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?
- There are several references to “organizers” without a clear definition, and this could lead to possible confusion regarding certain responsibilities between the Contracting Authority and the Client. - More specifically, paragraph 11.4.3 outlines a list of responsibilities assigned to organizers in relation to engagement activities. - There is a concern that these responsibilities may be interpreted as falling under the contracting authorities. Could we clarify that , in this context, “organizers” refers to the “client”? - Is the requirement to summarize documents in the context of solicitations referring to the Notice of Proposed Procurement (NPP) or something else in 11.2.2.
What should we change it to?
.
Why should we change it?
.
Heading text
11. Procurement information, websites, and applications
Heading number portion
11.
Item id
1782223843538_995
Heading id
s11
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?
- PSPC has a high volume of procurement and schedule may be impacted with the requirements related to the evaluation panel.
What should we change it to?
.
Why should we change it?
.
Heading text
12. Planning a procurement
Heading number portion
12.
Item id
1782223878978_330
Heading id
s12
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?
- Is it expected that a separate line item for accommodation-related costs be included in the basis of payment for the resources providing the services requested under a contract? o If so, will standard clauses be provided in CMI to support this? At a minimum, the PG community would require examples of basis of payment clauses and basis of payment line items to ensure consistency across all procurements. - Additionally, how will we validate that accommodation-related costs are fair and reasonable? Given that these costs will not form part of the financial evaluation (see 13.1.1 d)), how do we mitigate the risk that bidders may include unrelated costs in this line item to make their financial proposals more competitive? This approach appears to create a heightened risk of complaints from unsuccessful bidders.
What should we change it to?
.
Why should we change it?
.
Heading text
13. Bidding and contract award
Heading number portion
13.
Submission ID
65668
Submitted by
Marie-Eve.Benoit@tpsgc-pwgsc.gc.ca
Submitted on
Tue, 06/23/2026 - 10:11
Consent to contact
No

Individual 65671's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782226017052_154
Heading id
10.1.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?
Providing mandatory written justification related to this section on each procurement can potentially delay or stop activities meaningful to operations, including, but not limited to emergencies
What should we change it to?
Can there be exclusions or an amended process that takes into account time to action key purchases
Why should we change it?
The standard that is written is broad, it makes it difficult and in some cases impossible to adhere to
Heading text
10.1.2 Roles and responsibilities
Heading number portion
10.1.2
Item id
1782229956109_15
Heading id
10.1.4
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?
Providing mandatory written justification (regardless of the dollar value) can cause a significant delay in the procurement process. Include exceptions as not all procurements have accessibility requirements, for example: some that are technical in nature, such as mechanical equipment and parts.
What should we change it to?
Add exceptions and/or amended process that takes into consideration low risk or non-applicable procurements.
Why should we change it?
Causes delays in procurements. Difficult to incorporate this into the process as it applies to all procurements should include exceptions
Heading text
10.1.4 Mandatory justification for excluding accessibility
Heading number portion
10.1.4
Item id
1782229990113_157
Heading id
10.1.4
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?
b) Vague statement, there is a lack of clarity on who determines applicability
What should we change it to?
Add explicit statement: “Applicability shall be assessed and approved by"
Why should we change it?
What is the intention? Remove ambiguity and ensures there are clear, objective criteria for when the requirement applies, reducing interpretation risk
Heading text
10.1.4 Mandatory justification for excluding accessibility
Heading number portion
10.1.4
Item id
1782230041308_886
Heading id
10.1.4.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?
b) (i) - This is a new requirement, which is assumed that an internal structure is in place, however it may even require a consultation model, slowing down procurement activities. Needs to be an achievable model that doesn't slow down the procurement.
What should we change it to?
Organizations may leverage existing advisory bodies as required. Consultation should be applied using a risk-based approach, focused on procurements where accessibility considerations materially impact end users
Why should we change it?
To provide an achievable, scalable approach as the requirement could result in increased time, cost, and administrative burden, particularly if applied broadly across all procurements
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782230078104_246
Heading id
10.1.4.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?
b) (vi) - There is a need to clearly define the scope and components of the risk assessment
What should we change it to?
Provide clarity on what the risk assessment entails and identify if needed for repeat purchases
Why should we change it?
This statement is overly broad and does not clarify whether the requirement applies to subsequent or repeat procurements.
Heading text
10.1.4.1 Justification
Heading number portion
10.1.4.1
Item id
1782230106132_681
Heading id
11.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?
Looking for clarity on the type of procurement
What should we change it to?
Need clarity if this is for solicitations posted internally and externally on digital platforms which include planning, bidding and contract award, contract management, close out phases; and clauses
Why should we change it?
It is important that clear guidance be provided, as the current requirement may be difficult to implement in lower-value or transactional procurements (e.g., P-card purchases).
Heading text
11.3 Websites and digital applications
Heading number portion
11.3
Item id
1782230130697_340
Heading id
11.4.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?
It is not clear if this is a new mandatory requirement to have engagement in person or virtual events for procurements or only when it arises. Currently, engagements are not requirement with all procurements
What should we change it to?
In instances, where engagement may be required, organizations should adhere to the requirements outlined in clause 11.4.3.
Why should we change it?
In person or virtual engagements are not always required for procurements
Heading text
11.4.1 General
Heading number portion
11.4.1
Item id
1782230164065_231
Heading id
12.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?
12.1 (a) - Not all procurements have a related accessibility, for example engine parts or electrical components). This statement needs to allow flexibility for these types of exclusions
What should we change it to?
Add word related….To identify and define relevant accessibility requirements for related procurements, clients shall:
Why should we change it?
Not all procurements have an accessibility requirement. This may also place additional burden on advisory bodies and/or disability groups as the volume of asks from many organizations would be expected to rise significantly.
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782230273389_993
Heading id
12.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?
(a) (ii) - This is a new requirement, which is assumed that an internal structure is in place, however it may even require a consultation model, slowing down procurement activities. Needs to be an achievable model that doesn't slow down the procurement.
What should we change it to?
Organizations may leverage existing advisory bodies as required. Consultation should be applied using a risk-based approach, focused on procurements where accessibility considerations materially impact end users
Why should we change it?
To provide an achievable, scaleable approach as the requirement could result in increased time, cost, and administrative burden, particularly if applied broadly across all procurements
Heading text
12.1 Defining requirements
Heading number portion
12.1
Item id
1782230362575_310
Heading id
12.4.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?
(a) (ii) - The evaluation panel includes subject matter experts and it will be difficult to comply from a resource, governance and regulatory compliance perspective
What should we change it to?
Maybe the language should be modified to include "wherever possible"
Why should we change it?
This is a difficult statement to uphold, it is a complex framework and not all subject matter experts could be expected to navigate
Heading text
12.4.3 Identifying the evaluation panel
Heading number portion
12.4.3
Item id
1782230394387_90
Heading id
13.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?
Cost treatment is a vague statement that requires clarity
What should we change it to?
Need guidance to understand how things such as accommodation-related costs are to be included an evaluation.
Why should we change it?
Additional guidance is needed to ensure consistency with procurement fairness principles and trade agreement obligations
Heading text
13.1 Determining the solicitation period
Heading number portion
13.1
Item id
1782230413797_308
Heading id
14.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?
Need clarity regarding the expectation around accessibility requirements being established, are they being reviewed upon each amendment
What should we change it to?
To ensure that monitoring requirements are clear, especially when it comes to amendments
Why should we change it?
It is not clear on what the expectation is.
Heading text
14.1 Monitoring contract progress
Heading number portion
14.1
Item id
1782230435500_118
Heading id
14.4
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?
Need to define what type of monitoring and measures are required
What should we change it to?
Provide steps that need to be taken
Why should we change it?
Need clarity of reporting requirements and measures of success
Heading text
14.4 Measuring procurement outcomes
Heading number portion
14.4
Item id
1782230555720_350
Heading id
10.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?
Guidance to include exceptions as not all procurements have accessibility requirements, for example: some that are technical in nature, such as mechanical equipment and parts.
What should we change it to?
Include more details to improve understanding of applicability
Why should we change it?
Current description is too broad and makes this standard feel unattainable. Specifically, due to the dollar value, do the same rules apply to a $10 purchase as a $500,000 purchase.
Heading text
10.1 Policies and procedures
Heading number portion
10.1
Submission ID
65671
Submitted by
spothier@ma.ca
Submitted on
Tue, 06/23/2026 - 14:34
Consent to contact
Yes

Individual 65674's submission

CAN-ASC-4.1 Accessible Procurement
Feedback items
Item id
1782229651567_191
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?
This Standard provides requirements to create an equitable and accessible procurement process. These requirements provide technical guidance to help organizations facilitate an equitable and accessible procurement process.
What should we change it to?
Add wording to make clear that the Standard covers both the procurement process and the accessibility of what is purchased. Suggested wording: This Standard provides requirements to create an equitable and accessible procurement process, and to ensure that goods, services and construction procured through that process are accessible, usable, and do not create new barriers.
Why should we change it?
From AEBC’s standpoint, accessibility cannot stop at the procurement process. A procurement website can be accessible while the product being purchased remains inaccessible to blind, Deafblind and partially sighted end users. The Standard should state this clearly at the beginning. Please note that the attached file contains all our feedback on the standard.
Heading text
6. Introduction
Heading number portion
6.
Submission ID
65674
Submitted by
president@blindcanadians.ca
Submitted on
Tue, 06/23/2026 - 11:50
Consent to contact
Yes

Pagination

  • First page first
  • Previous page Prev
  • Page 64
  • Page 65
  • Current page 66
  • Page 67
  • Page 68
  • Next page Next
  • Last page last

Report a problem on this page

Report a problem on this page
Please select all that apply (required)

Share widget block

Date modified:
2026-08-02

Follow Us

  • Facebook
  • X
  • LinkedIn

Accessibility Standards Canada

  • Login
  • Create an account

About government

Government of Canada

  • All contacts
  • Departments and agencies
  • About government

Themes and topics

  • Jobs
  • Immigration and citizenship
  • Travel and tourism
  • Business
  • Benefits
  • Health
  • Taxes
  • Environment and natural resources
  • National security and defence
  • Culture, history and sport
  • Policing, justice and emergencies
  • Transport and infrastructure
  • Canada and the world
  • Money and finances
  • Science and innovation
  • Indigenous Peoples
  • Veterans and military
  • Youth
  • Manage life events

Brand

  • Social Media
  • Mobile Applications
  • About Canada.ca
  • Terms and conditions
  • Privacy
  • Accessibility Statement
  • Site map
Top of Page
Symbol of the Government of Canada