Disability, Neurodivergence and Unequal Measurement

Monitoring software measures input patterns against an implicit norm. People who work differently are measured as working worse, and in several jurisdictions that is an unlawful outcome rather than an unfortunate one.

The distinction in “Disability, Neurodivergence and Unequal Measurement” is important when operational records are interpreted. Organisations researching time tracking with screenshots can use explore the solution to add time and project context, while outcomes, direct feedback and human review remain necessary to explain what the numbers do not show.

Where the mismatches occur

Screen reader users navigate by keyboard in patterns the software was not built to interpret, and tasks legitimately take longer.

For an independent reference relevant to “Disability, Neurodivergence and Unequal Measurement”, consult the W3C Web Accessibility Initiative; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.

Voice input produces almost no keystroke activity.

Switch access and other alternative input produce patterns that read as low activity or as anomalous.

Fatigue management means working in shorter blocks with genuine rest, which registers as idle.

And agreed adjustments — later starts, longer breaks, reduced hours — produce patterns the system flags.

Neurodivergence

Attention patterns that involve intense focus followed by movement away.

Work done at unusual hours by agreement.

Reliance on written communication over meetings, or the reverse.

None of these is a performance signal and all of them show up in the data as deviation from a norm nobody declared.

The compounding problem

Somebody managing a condition is already expending effort the measure does not see.

Then they must explain their figures repeatedly, which is an additional burden placed on them rather than on the system that produced the figure.

That repeated explaining is the thing people report as most wearing, and it is entirely avoidable.

The legal dimension

General orientation, not legal advice; obligations differ by jurisdiction.

Where measurement disadvantages disabled employees, duties around adjustments and discrimination are engaged.

A system that flags agreed adjustments as anomalies is producing evidence against the organisation, which is an argument that lands with people who are unmoved by the fairness one.

What to do

Record agreed adjustments and exclude those individuals from flagging, automatically rather than by somebody remembering.

Do not produce individual scores for anybody, which removes the problem at source.

Involve disabled colleagues in the design, who will identify mismatches nobody else sees.

And train anybody using the data that an unusual pattern has many explanations, which is the management note's argument.

The accessibility of the software itself

The employee-facing portion — dashboards, notifications, consent screens — is frequently inaccessible.

Which means the people most affected by the measurement have the least access to what it says about them.

Test it with assistive technology before deployment.

The underlying point

Every measurement encodes an assumption about its subject.

Here the assumption is a person typing steadily at a keyboard for a standard day.

Knowing that is what lets you notice when a decision is about to be made about somebody who does not fit it.

What to check

Are agreed adjustments recorded and excluded from flagging?

Has anybody using assistive technology seen their own data?

Would your measures disadvantage somebody managing fatigue?

And were disabled colleagues involved before deployment?