Act A — The Disclosure Dilemma
Applicants with disabilities face a specific, structural dilemma in the job market.
They need to know whether the job's actual working environment can accommodate their needs before they commit to disclosing those needs. But the only way to find out is to ask — which requires disclosing. And disclosing before they have an offer carries documented risk, because disability discrimination in hiring is real, underreported, and difficult to prove.
HR officers face a parallel problem. They want to accommodate. They have legal obligations to accommodate. But they don't know, in advance of a candidate disclosing, which of their fifty-plus job classifications have working environments compatible with which accommodation profiles. The GIS analyst position: does the GIS software the team uses have a screen reader interface? Kevin in HR doesn't know. He's responsible for fifty-three job classifications. He cannot maintain working knowledge of the technology environment of each one.
The result is a matching process that is systematically late: accommodation needs are disclosed after offer, when the position is already specified, the team is already selected, and modifying the arrangement requires renegotiation that feels like burden rather than inclusion.
The following is a fictional account of how MarketForge structures this matching — before the disclosure, before the application, before the mismatch.
Act B — The Story
Nadia is a data analyst with low vision. She uses JAWS screen reader software and ZoomText magnification. She has a master's degree in geographic information science and five years of experience in spatial analysis. She has applied to four GIS positions in the past year. Two offered her positions but could not accommodate her screen reader software (their GIS platforms didn't have JAWS-compatible interfaces). One withdrew the offer after she disclosed her accommodation needs — she cannot prove it was causal.
She registers on the MarketForge municipal employment platform. Her profile encodes her skills and an accommodation specification under a protected protocol: screen reader software (JAWS), specific GIS software compatibility required (ESRI ArcGIS Pro with accessibility mode, or equivalent), monitor height adjustment, remote work flexibility preferred.
The profile is visible to matching algorithms but not to individual employers until she specifically authorizes disclosure.
Kevin is an HR generalist for a mid-sized Ontario municipality. His department has an open GIS analyst position — the incumbent has retired. He has updated the position profile on the MarketForge platform as part of the municipality's participation in a regional HR accessibility pilot program. The position profile encodes Technology Environment: ESRI ArcGIS Pro 3.2 (JAWS-compatible accessibility mode confirmed by IT department), hardware: 32-inch monitor with height-adjustable mount, work location: primarily in-office with two remote days per week available.
The platform matches Nadia's accommodation profile against the GIS analyst position. JAWS compatibility: confirmed for ArcGIS Pro 3.2. Monitor configuration: height-adjustable confirmed. Remote flexibility: two days per week available. Skills match: strong (GIS specialization, spatial analysis experience).
Nadia receives a match notification. The notification tells her, in plain language, that the specific software environment of this position is confirmed compatible with her screen reader — without disclosing her specific accommodation profile to the employer.
She authorizes disclosure and applies. Kevin receives her application with her accommodation specification and the platform's position compatibility confirmation. The Generative Match Story explains to Kevin — and to the hiring manager — why this specific candidate's accommodation is already structurally available in this specific role: the software is compatible, the hardware configuration is already in place, the work schedule flexibility is within existing team norms. No modification to the position is required. The accommodation is built into the environment.
Kevin's hiring manager reads the scenario. His concern — "won't accommodating this person require significant changes?" — is directly addressed. The accommodation requires no changes. He hires Nadia.
Act C — Why This Market Stays Broken Without Infrastructure
The disability employment market in the public sector is not broken because municipalities don't want to hire people with disabilities. It's broken because the information architecture of job matching was built for a world in which accommodation is not a first-class variable in the hiring decision.
Rehabilitation counsellors, disability employment coaches, and individual advocates try to bridge this gap one candidate at a time. It is expensive, slow, and dependent on relationship networks. It does not scale to the size of the problem.
What thin market infrastructure does is make accommodation compatibility a searchable, matchable, and documentable variable in the hiring process — structured in a way that protects the candidate's disclosure until she chooses to authorize it, and provides the employer with a clear, factual basis for decision-making.
Nadia and Kevin are fictional. The accessibility standards, software tools, and legal frameworks described — AODA employment standards, Ontario Human Rights Code duty to accommodate, JAWS screen reader, ArcGIS Pro — are real. DeeperPoint is building the infrastructure this story describes.