VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

The Gold Standard of Justice | Digital Justice, Connectivity, Platform Access, Automation and Remedy

View of Singapore's Civic District.

Gold Standard · Justice specialist guide

Find the nearest question, then follow the evidence

Digital justice asks whether people can reach, understand, use, challenge and obtain remedy from digital systems—not merely whether a service has been placed online.

A portal can be available every hour and still be unjust. A person may lack a stable connection, compatible device, private place, accepted identity document, readable language or accessible interface. Another person may complete every form yet be affected by a data error or automated recommendation that nobody can explain or correct.

Digital justice follows the entire journey from need to outcome and remedy. It examines infrastructure, affordability, accessibility, identity, data, automation, private platforms and public accountability together. The goal is not to reject digital systems; it is to ensure that convenience for institutions does not become hidden work, exclusion or unanswerable power for the people they serve.

Choose a reading route

ROUTE 1 · CHAPTERS 1–3
Map access
Justice, connectivity, devices and accessibility.
ROUTE 2 · CHAPTERS 4–5
Inspect gates
Accounts, identity, data and representation.
ROUTE 3 · CHAPTERS 6–7
Work the journey
Test a fictional portal and its automation.
ROUTE 4 · CHAPTERS 8–10
Secure remedy
Human review, platforms, privacy and security.
ROUTE 5 · CHAPTERS 11–12
Govern and audit
Participation, procurement and end-to-end evidence.

Open the full chapter index · Use the field check · Return to the Justice root

Chapter contents

Chapters 1–3 · Access, affordability and accessibility
  1. 1. Define digital justice across the whole journey
  2. 2. Treat connectivity, devices and data cost as service conditions
  3. 3. Design for disability, language and cognitive access from the start
Chapters 4–6 · Identity, data and automated decisions
  1. 4. Examine accounts, identity and authentication as distributional choices
  2. 5. Test whether data represent people and circumstances fairly
  3. 6. Worked example: audit a fictional housing-support portal
Chapters 7–9 · Power, privacy and effective remedy
  1. 7. Separate automated support from authority and accountability
  2. 8. Make notice, contestability and human review effective
  3. 9. Recognise platform power, dependency and hidden labour
Chapters 10–12 · Participation, procurement and audit
  1. 10. Balance privacy, security and protection without false trade-offs
  2. 11. Include affected people in standards, procurement and change control
  3. 12. Audit from need to outcome and remedy

CHAPTER 1 OF 12 · Map access

1. Define digital justice across the whole journey

Back to contents

Digital justice concerns fair capability, treatment, voice and remedy across digital environments. Availability is only the first gate. A system is not just when people can technically open it but cannot understand the process, supply accepted evidence, complete it with assistive technology, learn why a decision occurred or secure correction.

Map the journey from recognising a need through discovery, connection, authentication, comprehension, submission, decision, notification, review and remedy. At each gate identify required resources, who bears the work, which groups encounter barriers and what non-digital or assisted path remains. Test outcomes rather than equating launch with access.

A fictional benefits portal reports ninety-five per cent successful logins. Journey mapping shows that people without one accepted identity credential never reach the login denominator, while screen-reader users abandon an unlabeled upload control. The headline rate hid two prior exclusions.

Changed-context transfer check

Transfer the journey to online school enrolment. Identify a barrier before authentication, one during evidence upload and one after the decision.

Limit and misconception

No single metric captures justice. Access, outcome and remedy can conflict, and the relevant groups and burdens vary by context.

Evidence practice

Keep journey steps, requirements, subgroup completion, abandonment, assisted routes, decisions and remedy outcomes. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: declaring a service inclusive because the homepage is public or average completion is high. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Next chapter

CHAPTER 2 OF 12 · Map access

2. Treat connectivity, devices and data cost as service conditions

Back to contents

A digital service depends on networks, electricity, devices, software, data allowances and time. These are not external inconveniences when the institution makes digital participation necessary. Unstable bandwidth, older phones, shared devices and costly uploads can turn a nominal right into an unequal burden.

Test low bandwidth, interrupted sessions, small screens, older supported software and capped data. Measure page weight, upload size, timeout behaviour and recovery after disconnection. Provide save-and-resume, lightweight formats, nearby assistance and a meaningful alternative channel. Assess the total user cost rather than only institutional savings.

A fictional application requires six photographed documents and resets after ten minutes. On a shared prepaid phone, repeated uploads consume data and expose private records. Compression, resumable upload and an assisted counter reduce the burden without lowering evidence standards.

Changed-context transfer check

Apply the test to a telehealth appointment. Include electricity, camera, audio privacy, caregiver help and the cost of a failed connection.

Limit and misconception

Offline or assisted routes can also be slow, stigmatizing or geographically inaccessible. Merely listing a telephone number does not establish equivalence.

Evidence practice

Keep device and network tests, page weights, recovery logs, user costs, assisted-channel capacity and outcome parity. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: assuming smartphone ownership means reliable, private and affordable digital access. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 12 · Map access

3. Design for disability, language and cognitive access from the start

Back to contents

Accessibility is a condition of equal participation, not a decorative compliance step. Visual, auditory, motor, speech, cognitive and learning differences interact with language, literacy, fatigue and stressful circumstances. A technically conforming page can still fail when the workflow is confusing or evidence is presented in only one mode.

Use recognised accessibility standards, semantic structure, keyboard operation, labelled controls, captions, contrast and predictable focus. Add plain-language explanations, tested translations, error recovery and enough time. Involve disabled users and language communities in task testing, including the complete authentication and remedy path rather than a sample page.

A portal passes an automated scan but its one-time code expires before a screen-reader user can navigate back to the field. Observed task testing exposes the timing barrier and leads to a longer window, preserved focus and an accessible alternative.

GateJustice questionEvidence
ConnectCan the person afford and sustain access?Device, bandwidth and cost tests
UnderstandCan the person perceive and interpret the task?Accessibility, language and task tests
ActCan the person complete and recover?Completion, error and assistance data
ChallengeCan the person learn, contest and correct?Notice, review and remedy outcomes
Digital justice requires evidence at every gate, not one access statistic.

Changed-context transfer check

Transfer the test to a video evidence process. Design an equivalent route for a person who cannot record speech or safely appear on camera.

Limit and misconception

Automated checkers detect only part of accessibility. Translation quality and cognitive clarity require human review and community testing.

Evidence practice

Keep standards mapping, assistive-technology tests, language review, task results, issue ownership and retest evidence. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: treating an accessibility score or overlay as proof that real users can complete the journey. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 12 · Inspect gates

4. Examine accounts, identity and authentication as distributional choices

Back to contents

Accounts and identity checks allocate trust. They can exclude people with changed names, shared addresses, limited records, unstable housing, migration histories or no accepted device. Stronger authentication can protect people while also increasing lockouts, surveillance and dependence on private identity providers.

State why identity is necessary, what level of assurance the decision needs and which attributes are actually relevant. Offer proportionate methods, recovery without the original device and staffed review for mismatches. Measure false rejection, recovery time and subgroup impact. Separate fraud signals from conclusions and prevent an identity discrepancy from becoming an unreviewable denial.

A fictional resident cannot receive a code because the registered number belonged to a former caregiver. The revised process permits verified recovery through a service officer, records the reason and prevents the old number from remaining a permanent gate.

Changed-context transfer check

Apply the method to a platform requiring facial verification. Identify less intrusive alternatives and an appeal path for failure.

Limit and misconception

Alternative checks can create new risks for staff and users. Proportionality requires both security modelling and equity evidence.

Evidence practice

Keep purpose and assurance level, accepted methods, rejection and recovery rates, subgroup review and audit logs. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: treating every mismatch as deception or making one commercial account the only route to a public service. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 12 · Inspect gates

5. Test whether data represent people and circumstances fairly

Back to contents

Digital decisions inherit the categories, missing values, histories and institutional practices in their data. A record may be accurate about a past transaction yet misleading about present need. People who were poorly served can be under-recorded, while heavily monitored groups can appear disproportionately risky.

Create a data map showing source, purpose, collection context, update path, missingness and known proxies. Compare coverage and error across relevant groups, distinguish absence from a negative value and provide a route for people to see and correct consequential data. Assess whether a variable is necessary, current and appropriate for the decision.

A fictional eligibility model reads no recorded income as zero income in one source and as unknown in another. The same symbol produces opposite outcomes. A data contract and explicit missing-value rules prevent the silent conversion.

Changed-context transfer check

Transfer the check to school attendance data. Explain why absence, late entry and missing registration cannot be treated as the same condition.

Limit and misconception

Perfect representation is impossible, and protected data may be necessary to test disparities. Collection for audit needs lawful purpose, minimisation and safeguards.

Evidence practice

Keep data lineage, definitions, missingness, error rates, correction requests, retention and subgroup analysis. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: calling historical data neutral or using a convenient proxy without testing what it actually measures. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 12 · Work the journey

6. Worked example: audit a fictional housing-support portal

Back to contents

A city moves emergency housing support to a portal. Applicants create an account, prove address, describe household needs, upload documents and receive a priority recommendation reviewed by an officer. A denial can be reconsidered within fourteen days.

The audit recruits people using low-cost phones, assistive technology and several languages. It maps every gate, measures data and time costs, inspects the priority variables, observes officer overrides and follows reconsideration outcomes. It finds that people in temporary accommodation often lack accepted address evidence and receive lower data-completeness scores.

The city adds an attestation route, separates missing evidence from adverse evidence, provides a status timeline and funds assisted applications. The model remains advisory; officers must record reasons, and applicants receive a plain-language notice with the evidence used and review route.

FindingRiskResponse
Unaccepted address evidenceExcludes unstable housingAttestation and staffed verification
Missing data scored lowConverts uncertainty into disadvantageSeparate unknown from adverse
Opaque priority outputPrevents meaningful challengeReasoned notice and evidence list
Short review windowRemedy unavailable in practiceAccessible notice and supported review
The worked audit follows exclusion from first gate through remedy.

Changed-context transfer check

Change the case so demand exceeds available housing. Explain which allocation questions technology cannot resolve and what democratic or legal authority must set them.

Limit and misconception

The example is fictional. Better procedure cannot create scarce housing or settle the just allocation principle by itself.

Evidence practice

Keep journey tests, accessibility results, data definitions, recommendation logs, officer reasons, notices and review outcomes. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: optimising portal completion while ignoring whether eligible people are identified, prioritised and heard. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 12 · Work the journey

7. Separate automated support from authority and accountability

Back to contents

Automation can rank, recommend, detect, summarise or decide. The justice risk depends on the decision, stakes, affected right, error pattern and practical human control—not on the label artificial intelligence. A human click does not create oversight when the reviewer lacks time, information or authority to disagree.

Inventory each automated function and state its legal or institutional role. Define prohibited uses, decision authority, evidence available to reviewers and when human escalation is mandatory. Test performance and error costs by subgroup and operating condition. Record model version, inputs, output, reviewer action and reason without treating the score as an objective fact.

In the housing example, a priority score suggests order but cannot close a case. Officers can inspect supporting factors, request missing information and override with a recorded reason. Audits compare acceptance, override and outcome patterns.

Changed-context transfer check

Transfer the controls to automated moderation of a student forum. Decide which actions can be temporary, which require human judgement and when the speaker is notified.

Limit and misconception

Explanation tools can be incomplete or misleading. Some models remain unsuitable where meaningful reasons and contestability cannot be provided.

Evidence practice

Keep use inventory, authority matrix, validation, subgroup errors, version logs, overrides, reasons and outcomes. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: keeping a nominal human in the loop while workload and interface make agreement automatic. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 12 · Secure remedy

8. Make notice, contestability and human review effective

Back to contents

A remedy is effective when a person can learn that an adverse outcome occurred, understand the material basis, present relevant correction, reach an authorised reviewer and obtain a timely response that can change the outcome. A generic contact form is not remedy if nobody can inspect or reverse the decision.

Give specific, accessible notice of outcome, material evidence, rules, deadlines and review channels. Preserve the records needed to challenge the decision. Offer assistance, pause irreversible consequences where appropriate and measure whether reviews correct errors. Keep the reviewer sufficiently independent and empowered, and communicate reasons for the review result.

An applicant learns that an address mismatch reduced completeness. The notice identifies the mismatch without exposing security rules, accepts alternative evidence and routes the case to an officer who can restore priority and remedy delay.

Changed-context transfer check

Apply the standard to an account suspension by a private platform. Identify what information, timing and escalation are necessary for a meaningful appeal.

Limit and misconception

Full disclosure can conflict with privacy, security or the rights of others. Reasons can be appropriately bounded while still enabling a meaningful challenge.

Evidence practice

Keep notices, delivered formats, preserved records, assistance logs, review authority, correction rate and time to remedy. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: offering an appeal link that repeats the automated result or cannot alter the decision. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 12 · Secure remedy

9. Recognise platform power, dependency and hidden labour

Back to contents

People increasingly access work, learning, speech, payments and services through private platforms. Terms, ranking, moderation, fees and account controls distribute opportunities and risks. Users also perform unpaid work—verification, data entry, content labelling and repeated appeals—to make the system function.

Map dependencies and switching costs, including data portability, network effects and loss of reputation. Examine worker and user voice, moderation consistency, fee transparency and routes for collective representation. In public procurement, require continuity, audit access, portability and remedy rather than outsourcing accountability with the technology.

A delivery worker loses access after an identity check fails. The platform offers only scripted chat while income stops. An effective process provides prompt human review, preserves earnings evidence and compensates proven wrongful suspension.

Changed-context transfer check

Transfer the analysis to an educational platform used as the only submission channel. Identify the obligations created by institutional dependence.

Limit and misconception

Platforms balance many rights and safety interests. Individual appeals alone cannot resolve market concentration or every systemic rule.

Evidence practice

Keep dependency map, terms and changes, fee and ranking evidence, workload, appeals, restoration and portability tests. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: treating consent to platform terms as proof that power, burden and remedy are fair. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 12 · Secure remedy

10. Balance privacy, security and protection without false trade-offs

Back to contents

Privacy and security support justice by protecting dignity, autonomy and safe participation. They can also be invoked vaguely to block transparency or impose disproportionate surveillance. Conversely, weak security can expose people whose data were collected because they needed a service.

Minimise collection, separate purposes, restrict access and set deletion rules. Conduct threat and rights assessments together. Test whether monitoring is necessary and proportionate, whether less intrusive controls exist and whether affected people receive notice and redress. Publish useful aggregate evidence without exposing individuals or exploitable detail.

A portal wants continuous device fingerprinting to reduce fraud. The team compares targeted step-up checks, retention limits and staffed review, then rejects indefinite tracking because it adds broad surveillance without commensurate evidence.

Changed-context transfer check

Apply the analysis to public Wi-Fi in a shelter. Protect users from account theft without creating a permanent log of sensitive browsing.

Limit and misconception

No system is risk-free. Minimisation can limit later audit, while transparency can reveal security information; decisions need documented reasons and review.

Evidence practice

Keep data inventory, purpose tests, threat model, rights assessment, access logs, retention, incidents and remedies. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: calling intrusive collection necessary without alternatives, evidence or a deletion plan. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 12 · Govern and audit

11. Include affected people in standards, procurement and change control

Back to contents

Participation is more than a survey after deployment. People affected by a system hold knowledge about barriers, harms, workarounds and acceptable remedies. Procurement and change control can otherwise lock public values inside vendor defaults, inaccessible contracts or metrics chosen for institutional convenience.

Involve affected groups early, pay for expertise, publish the decision questions and show how input changed requirements. Put accessibility, interoperability, audit rights, incident reporting, service continuity, data return and termination assistance into contracts. Reassess material changes, not only initial launch.

A community panel shows that telephone assistance is unsafe for people sharing accommodation. Procurement adds secure in-person support and a text-based channel, then tracks whether each route produces equivalent outcomes.

Changed-context transfer check

Transfer the approach to a school buying automated writing feedback. Identify students, teachers, parents and accessibility specialists who need a voice and which contract rights preserve future choice.

Limit and misconception

Participation can be unrepresentative or burdensome. It does not replace accountable decision makers, legal duties or independent oversight.

Evidence practice

Keep participant selection, compensation, issue log, requirement changes, contract clauses, change notices and monitoring. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: treating consultation attendance as approval or letting vendors define the justice standard. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 12 · Govern and audit

12. Audit from need to outcome and remedy

Back to contents

An end-to-end audit asks who never enters, who abandons, who receives which outcome, who challenges, who succeeds and what burden each path imposes. It connects technical records with qualitative evidence and institutional decisions so that a polished interface cannot conceal unequal consequences.

Preserve versions of forms, rules, models and notices. Reconstruct representative and edge-case journeys, test accessibility and low-resource conditions, sample decisions to source data and compare outcomes across groups. Review overrides, complaints, incidents and remedies. Assign owners and deadlines, then retest after changes.

The fictional portal audit discovers that a redesigned upload step improves average completion but raises abandonment for users of older phones. The team restores a lightweight route and monitors both completion and eligibility outcomes rather than declaring the redesign successful.

Audit layerCore evidenceFailure signal
AccessCost, device and task testsEligible people never enter
DecisionData lineage, rules and outcomesErrors or disparities lack explanation
ReviewNotice, records and authorityAppeal cannot change outcome
GovernanceParticipation, contracts and change logsResponsibility disappears across vendors
The audit follows the service as people experience it and as institutions govern it.

Changed-context transfer check

Design an audit where protected attributes are unavailable. Specify lawful proxies, qualitative sampling, privacy-preserving analysis and the uncertainty that must remain explicit.

Limit and misconception

Audits observe selected periods and categories. Small groups, unreported harms and future changes can escape detection; monitoring and accessible reporting channels remain necessary.

Evidence practice

Keep versioned artefacts, journey samples, subgroup metrics, decision traces, complaints, corrective actions and retest results. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.

Deliberately test for this failure: auditing model accuracy alone while connection, identity, notice and remedy failures remain outside scope. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.

Contents · Previous chapter · Connected articles

Advanced boundary cases

Intersectional burden

Barriers combine rather than simply add. Test journeys that include disability, language, income, caregiving, migration status and device constraints together instead of reviewing one characteristic at a time.

Systemic remedy

Repeated individual corrections can reveal a common rule, dataset or interface defect. Escalation should repair the system, identify similarly affected people and address past harm where possible.

Cross-border platforms

Data location, contractor chains and differing legal regimes can complicate accountability. Map controllers, processors, decision authority and enforceable remedy before dependence becomes irreversible.

A practical field check

Use this check before launching, procuring or materially changing a digital service, platform dependency or automated decision tool.

  1. Map the complete user journey and every gate.
  2. Test affordability, devices, bandwidth and recovery.
  3. Test accessibility, language and assisted routes.
  4. Justify identity and data requirements.
  5. Inventory every automated function and authority.
  6. Design specific notice, review and remedy.
  7. Review privacy, security and platform dependency.
  8. Audit outcomes, burdens and corrections across groups.

Run the check as a small workbook

Use sheets for journey gates, user requirements, accessibility and network tests, identity failures, data lineage, automation roles, notices, reviews, complaints, vendors and corrective actions. Link every aggregate metric to its denominator and collection method.

GatePass conditionStop condition
AccessAffordable and accessible routes complete successfullyWhole groups cannot enter
DecisionData and authority can be reconstructedOpaque score controls outcome
RemedyReviewer can correct and repair harmAppeal only repeats result
GovernanceOwners, contracts and change logs are explicitResponsibility is outsourced
A digital service should stop or narrow when access, decision, remedy or governance cannot be evidenced.

Chapter-by-chapter evidence audit

ChapterEvidence to keepFailure to catch
1. Define digital justice across the whole journeyJourney steps, requirements, subgroup completion, abandonment, assisted routes, decisions and remedy outcomesDeclaring a service inclusive because the homepage is public or average completion is high
2. Treat connectivity, devices and data cost as service conditionsDevice and network tests, page weights, recovery logs, user costs, assisted-channel capacity and outcome parityAssuming smartphone ownership means reliable, private and affordable digital access
3. Design for disability, language and cognitive access from the startStandards mapping, assistive-technology tests, language review, task results, issue ownership and retest evidenceTreating an accessibility score or overlay as proof that real users can complete the journey
4. Examine accounts, identity and authentication as distributional choicesPurpose and assurance level, accepted methods, rejection and recovery rates, subgroup review and audit logsTreating every mismatch as deception or making one commercial account the only route to a public service
5. Test whether data represent people and circumstances fairlyData lineage, definitions, missingness, error rates, correction requests, retention and subgroup analysisCalling historical data neutral or using a convenient proxy without testing what it actually measures
6. Worked example: audit a fictional housing-support portalJourney tests, accessibility results, data definitions, recommendation logs, officer reasons, notices and review outcomesOptimising portal completion while ignoring whether eligible people are identified, prioritised and heard
7. Separate automated support from authority and accountabilityUse inventory, authority matrix, validation, subgroup errors, version logs, overrides, reasons and outcomesKeeping a nominal human in the loop while workload and interface make agreement automatic
8. Make notice, contestability and human review effectiveNotices, delivered formats, preserved records, assistance logs, review authority, correction rate and time to remedyOffering an appeal link that repeats the automated result or cannot alter the decision
9. Recognise platform power, dependency and hidden labourDependency map, terms and changes, fee and ranking evidence, workload, appeals, restoration and portability testsTreating consent to platform terms as proof that power, burden and remedy are fair
10. Balance privacy, security and protection without false trade-offsData inventory, purpose tests, threat model, rights assessment, access logs, retention, incidents and remediesCalling intrusive collection necessary without alternatives, evidence or a deletion plan
11. Include affected people in standards, procurement and change controlParticipant selection, compensation, issue log, requirement changes, contract clauses, change notices and monitoringTreating consultation attendance as approval or letting vendors define the justice standard
12. Audit from need to outcome and remedyVersioned artefacts, journey samples, subgroup metrics, decision traces, complaints, corrective actions and retest resultsAuditing model accuracy alone while connection, identity, notice and remedy failures remain outside scope
Understanding is demonstrated when the evidence and failure test survive a changed setting.

Connected articles across the eduKate ecosystem

Start with the governing route

Continue into verified specialist studies

Questions readers often ask

Is internet access enough for digital justice?

No. Devices, affordability, privacy, accessibility, identity, comprehension, decisions and remedy all shape effective access.

Does human review make an automated system fair?

Only when the reviewer has time, evidence, authority and a practical way to disagree and correct harm.

Can accessibility be proved by an automated scan?

No. Standards checks help, but full task testing with assistive technologies and affected users is essential.

Must every decision reveal the whole model?

Not necessarily, but people need enough specific information and evidence to understand and meaningfully challenge consequential outcomes.

Are alternative channels automatically equivalent?

No. Compare wait, cost, dignity, evidence requirements, outcomes and remedy rather than merely listing another channel.

What makes a digital remedy effective?

Timely notice, accessible assistance, preserved evidence, an empowered reviewer, a reasoned response and the ability to correct the outcome and resulting harm.

Sources and scope

UN Human Rights: Digital Policy Brief — human-rights framework for digital infrastructure, inclusion, governance and accountability.

UN Human Rights: Guidance on Digital Technologies — official guidance for rights-respecting design and use of digital technologies.

UN Human Rights: Access to Remedy, Concepts and Principles — official framework for effective remedy and accountability.

UN High Commissioner for Human Rights: Human rights at the core of generative AI — official statement on equality, participation, transparency and remedy in AI governance.

W3C Web Accessibility Initiative: WCAG overview — authoritative accessibility standards and supporting guidance for web content.

The housing, platform, education and service examples are fictional. This guide is educational and does not replace applicable law, accessibility duties, cybersecurity review, professional advice or the participation of affected communities.

“Gold standard” describes the educational benchmark explained in this guide. It is not an official accreditation, legal opinion, policy determination or professional certification.

Back to contents · Return to the Justice root · Return to the Gold Standard of Education