The Hidden Profit in Accessibility: Why Smart Developers Should Embrace the Digital Curb Cut Effect

"It turns out 'building for the few' was just a clever disguise for accidentally making the product usable for the rest of us!"

Computers, Software, and Digital Interfaces

Imagine a developer building a feature to help a small group of users who cannot use a keyboard. The goal is modest: remove a barrier so that those users can interact with the computer. A few years later, the same feature becomes the preferred way millions of people send messages, dictate notes, and interact with their devices.

This story has repeated itself many times in the history of computing.

Features originally designed to assist persons with disabilities have quietly reshaped mainstream technology. Voice recognition, captions, predictive text, adjustable interfaces, and speech output systems all began as accessibility innovations. Today, they are everyday conveniences used by people who may never have heard the word “accessibility”.

This phenomenon is known as the curb cut effect.

In the first article of this series, we explored curb cuts in the built environment—those small ramps at street corners originally introduced to help wheelchair users navigate sidewalks. Urban planners soon discovered that the ramps also helped parents with prams, travellers with suitcases, delivery workers with carts, and cyclists. What began as a disability accommodation became a universal design improvement.

This article turns to the digital world—computers, operating systems, software applications, smartphones, and other digital devices. Here too, accessibility innovations have repeatedly produced design improvements that benefit everyone.

For developers and technology designers, this history carries an important lesson: accessibility is not merely about compliance. It is often the starting point for the next generation of mainstream technological innovation.

From Pavement to Processor: The Digital Curb Cut

Software development culture often prioritises functionality, speed, and aesthetics. Accessibility is sometimes treated as a secondary concern—something to be added later if time permits. Many development teams still assume that people with disabilities represent a small niche audience.

In reality, that assumption does not hold.

The World Health Organisation estimates that more than one billion people globally live with some form of disability. If temporary or situational limitations are included—such as injuries, ageing, fatigue, environmental constraints, or multitasking—the number of people who benefit from accessible design grows substantially.

Digital technologies interact with human abilities in complex ways. A user may rely on voice input while driving, captions in a noisy environment, or large text on a bright outdoor screen. Accessibility features therefore do not only assist persons with disabilities. They support a wide range of everyday situations.

Just as curb cuts improved the usability of city streets for everyone, accessibility features improve the usability of digital systems.

Why Developers Often Overlook Accessibility

Despite its benefits, accessibility frequently remains underrepresented in software development.

One reason is education. Many programmers receive little or no training in accessibility during their formal studies. Programming courses focus on algorithms, data structures, and software architecture, but rarely discuss inclusive interface design.

Another reason is the invisibility of accessibility barriers. Developers who rely on a mouse and a high-resolution display may never encounter the obstacles faced by users who depend on keyboard navigation, screen readers, voice input, or magnification tools. Without direct exposure, accessibility challenges remain abstract.

Project timelines also influence priorities. Agile development environments reward rapid feature delivery. Accessibility improvements may appear to slow development cycles, particularly if they are introduced late in the process. As a result, accessibility tasks are often postponed or removed from development roadmaps.

Yet this approach ultimately creates weaker products. When accessibility is incorporated early, developers often discover that their systems become more flexible, more robust, and easier to maintain.

Accessibility Innovation: A Brief Historical Perspective

Several important computing technologies originated in efforts to remove barriers for disabled users.

One early example is speech recognition. In 1952, researchers at Bell Laboratories created a system called Audrey that could recognise spoken digits. Although primitive by modern standards, the technology was explored partly as a way to help individuals who could not easily use keyboards or physical input devices. Over the decades, advances in machine learning and processing power have transformed speech recognition into the voice assistants and dictation tools now embedded in smartphones and operating systems.

Another example involves screen-reading technology. In the 1980s and 1990s, developers began creating software that could translate text displayed on a computer screen into synthetic speech. These systems allowed blind users to navigate operating systems and access digital information independently. Today, the same text-to-speech technology powers audiobooks, navigation systems, automated customer service, and digital assistants used by millions of people.

A third example comes from closed captioning. Captions were introduced to make television accessible to Deaf viewers. As digital video platforms emerged, captions became a standard feature across streaming services and social media. A large proportion of caption users today are not Deaf; they simply prefer watching videos silently in public spaces, noisy environments, or workplaces.

These examples illustrate a recurring pattern. Technologies created to remove barriers for specific users often evolve into mainstream tools that redefine how people interact with technology.

The Curb Cut Effect in Computing

The curb cut effect in computing occurs when accessibility solutions address broader human needs. Once introduced, these features often spread far beyond their original purpose.

Several widely used technologies illustrate this pattern.

• Voice Recognition and Voice Typing: Voice recognition systems were initially designed to assist individuals who could not use keyboards due to mobility impairments. Early systems were limited, recognising only small vocabularies or specific commands. Modern systems are vastly more powerful. Smartphones, laptops, and operating systems now include built-in dictation features that allow users to compose emails, messages, and documents through speech.  Outside disability contexts, voice input has become valuable for drivers, cyclists, chefs, journalists, and professionals working in hands-free environments. Many people now dictate messages rather than typing them.  A technology that began as an accessibility solution has become a mainstream interaction method.
• Closed Captions and Subtitles: Closed captions were originally introduced to enable Deaf and hard-of-hearing viewers to access television programming. Over time, legislation in several countries required televisions to include caption decoding capabilities. Today,y captions appear across video platforms, social media, and video conferencing tools.  Their use extends far beyond disability. People watch videos in noisy environments such as airports or public transport. Others view content silently in offices or libraries. Language learners rely on captions to improve comprehension. Captions demonstrate how accessibility features often solve broader communication challenges.
• Predictive Text and Autocomplete:  Predictive text systems were developed to assist users who experienced difficulty typing due to mobility impairments or dyslexia. By suggesting words or phrases, these systems reduce the effort required to enter text.  Today, our predictive algorithms appear everywhere: smartphone keyboards, search engines, email applications, and programming environments. Developers themselves benefit from advanced autocomplete tools embedded in code editors. These tools accelerate programming by predicting functions, variables, and code structures.  Once again, an accessibility-driven innovation has evolved into a universal productivity tool.
• Keyboard Shortcuts: Keyboard navigation is essential for users who cannot rely on a mouse. Accessible software, therefore, ensures that commands can be executed through keyboard input alone. Over time, keyboard shortcuts became indispensable productivity tools for expert users. Programmers, writers, and designers frequently rely on keyboard commands to perform tasks rapidly without interrupting their workflow. Shortcuts such as copy, paste, undo, and search have become so common that many users consider them fundamental aspects of computing.  
• Dark Mode and Display Customisation:  Display customisation options—such as dark mode, high contrast themes, and adjustable colour settings—were originally introduced to support users with visual impairments or light sensitivity.  Dark mode has now become one of the most widely requested interface features. Many users prefer darker interfaces during evening use or extended work sessions. On certain display technologies, dark themes can also improve battery efficiency. What began as a visual accessibility feature has become a mainstream design preference.
• Text-to-Speech Systems:  Text-to-speech systems convert written content into spoken audio, enabling blind and low-vision users to access digital information. Screen readers built upon these technologies allow users to navigate documents and applications through speech output.  Today, text-to-speech has expanded into many other domains. Audiobooks, voice navigation systems, language learning tools, and automated announcements all rely on similar technologies.  Increasingly, users listen to written content while commuting, exercising, or performing other tasks.
• Adjustable Fonts and Interface Scaling:  Operating systems now allow users to enlarge text, adjust spacing, and modify contrast settings. These features were initially designed for users with low vision.  Yet many others benefit from adjustable interfaces. Ageing populations, users reading on small mobile screens, and individuals working in bright outdoor environments all rely on larger text and improved contrast.  Flexible typography has therefore become a core principle of modern interface design.

Accessibility as a Business Opportunity

Developers sometimes assume that accessibility concerns a relatively small group of users. In reality, accessible design significantly expands the potential user base for digital products.  More than one billion people globally live with disabilities. Many more experience temporary or situational limitations—injuries, fatigue, ageing, environmental noise, or restricted mobility.  Products that accommodate diverse users reach broader markets. They also tend to perform better in unpredictable environments.

Accessible design can therefore produce competitive advantages. Applications that are easier to use attract wider adoption and stronger customer loyalty. Inclusive interfaces also reduce user frustration and support international adoption.  Major technology companies have begun to recognise this relationship. Accessibility is increasingly integrated into product development strategies rather than treated as an afterthought.

The Legal Landscape Is Changing

Accessibility is not only a design consideration. It is increasingly a legal requirement.  Several jurisdictions have extended disability rights legislation into the digital domain. In the United States, courts have interpreted the Americans with Disabilities Act to apply to digital services and mobile applications. Similar regulatory frameworks are emerging across Europe.  India’s Rights of Persons with Disabilities Act, 201,6 recognises the importance of accessible information and communication technologies.

Public procurement policies are also evolving. Governments and large institutions often require software vendors to demonstrate accessibility compliance before purchasing digital systems.  For developers and organisations that ignore accessibility, the legal risks are growing. Litigation and regulatory enforcement actions are increasing, particularly in relation to inaccessible mobile applications and digital services.

Designing Technology for Human Diversity

The history of computing repeatedly demonstrates that accessibility innovations often lead to better technology.  By designing systems that accommodate diverse abilities, developers create interfaces that are more flexible, adaptable, and resilient. Applications that support multiple forms of input—keyboard, touch, voice—are better suited to real-world environments.  Accessibility also encourages designers to question assumptions about the “average user”. In practice, there is no such user. People interact with technology in many different contexts, with varying abilities and constraints.  When developers design for the edges of human experience, they often discover improvements that benefit everyone.

A Message to Developers

For developers and software designers, the lesson of the curb cut effect is clear.  Accessibility should not be treated as a specialised feature or regulatory burden. It should be integrated into the earliest stages of product design.  Developers who embrace accessibility gain an opportunity to build more innovative and widely usable technologies. Those who ignore it risk excluding millions of potential users while missing opportunities for design improvement.

In the physical world, curb cuts transformed the way cities function. In the digital world, accessibility continues to reshape the way we interact with computers.  The next major innovation in user interfaces may well emerge from the same place curb cuts once did: from the effort to remove barriers.

Resources and References

• Byrne-Haber, Sheri. Getting Developers to Care about Accessibility: Carrots and Sticks.
• Level Access. The Curb Cut Effect: How Digital Accessibility Improves UX.
• UsableNet Blog. Disability Pride Month: The Origins of Assistive Technology.
• Rev.com. The History of Closed Captioning.
• Nielsen Norman Group. Dark Mode: Best Practices.
• World Health Organisation. World Report on Disability.
• Apple Assistive Technology Demonstrations.
• World Wide Web Consortium. Web Content Accessibility Guidelines.
• Government of India. Rights of Persons with Disabilities Act, 2016.

An Open Letter on Transgender Law Reform, Accessibility, and Constitutional Equality in India

 To:

Dr Virendra Kumar,
Hon’ble Minister
Social Justice and Empowerment, Government of India
Room No. 201, C‑Wing, Shastri Bhawan,
New Delhi – 110001, India

Subject: Concern over Transgender Persons (Protection of Rights) Amendment Bill, 2026 and related disability issues

Hon’ble Minister,

I  write as a disability rights advocate deeply concerned for the welfare of the transgender community. I applaud the government’s historic achievements: from the Supreme Court’s NALSA ruling recognising transgender persons’ rights, to the Transgender Persons (Protection of Rights) Act 2019 and recent welfare schemes such as the National Council for Transgender Persons and the SMILE scheme launched by your Ministry. These have been important steps towards inclusion. However, I am alarmed that the Transgender Persons (Protection of Rights) Amendment Bill, 2026, introduced by your Ministry, would require transgender individuals to obtain identity certificates only after approval by a designated medical board.

This medical‑board‑centred approach is deeply troubling from a human‑rights and disability‑studies perspective. Transgender people already face social stigma; subjecting them to intrusive examinations would reinforce a medical model of identity that depends on “certification” by doctors, instead of respecting the self‑perceived identity that the original Act had affirmed in line with NALSA. In effect, trans persons with disabilities would suffer a double burden: first, to prove their disability, often repeatedly, to access the 5 per cent reservation and other entitlements, and then to prove their gender identity as well. Nothing in disability rights law justifies such additional gates. Courts, including the Supreme Court and High Courts, have repeatedly said that disability should not bar someone from education or employment unless it truly prevents them from performing essential duties; they have emphasised functional assessment and reasonable accommodation over rigid exclusions. By that logic, endless reassessments simply because a person is transgender or disabled violate both dignity and rights.

Real‑world experience from disability certification already shows the dangers of this model. NEET qualifiers with disabilities have been forced to travel across states for repeated assessments, even when they already hold permanent certificates and UDID cards. One visually impaired student, Lakshay Sharma, topped NEET but was told by a hospital board that he had “0 per cent” disability for quota purposes, until he went back for reassessment and finally regained recognition of 40 per cent disability after much effort and public scrutiny. Disability rights activists report that every year, persons with disabilities face unnecessary hassles, conflicting opinions from different boards and avoidable legal fights just to secure what the law already promises them.

Even interim guidance from the Supreme Court directions on NEET, requiring boards to focus on functional capacity and not use the 40 per cent benchmark as a blunt bar, is being ignored in practice. Reports and testimonies show wheelchair users being asked to walk, candidates cleared by one state being rejected in another, and young students being humiliated in the name of “fitness”. Expecting the same medical board system to handle transgender identity certificates will simply reproduce these insensitivities in a new context. As Dr Satendra Singh and many others have warned in the context of NEET, every additional medical or bureaucratic hurdle entrenches stigma, wastes years of people’s lives, and deters capable candidates. 

I must emphasise that none of this is to question the government’s intent. Protecting vulnerable persons from exploitation, including trafficking and forced procedures, is a worthy goal; stronger penalties for coercion are understandable. The aim of your Ministry’s welfare initiatives for transgender persons, including SMILE and the National Portal for Transgender Persons, is also commendable. My concern is that we must not confuse identity with a medical condition. Under the disability framework, the rules make it clear that once a disability certificate is issued by a competent authority, it is generally meant to be valid for all purposes, so that people can apply for schemes and benefits without facing constant re‑testing. The 2019 Transgender Persons Act similarly allowed self‑identification via a certificate from a District Magistrate; an administrative process, not a medical examination.

On paper, a uniform national procedure for transgender ID certificates might look like a way to ensure transparency. In practice, requiring all trans persons to go through state hospitals and medical boards risks recreating the very gatekeeping that the old, narrow, binary view of gender imposed on them. It will delay legal recognition of transgender identities and expose people to invasive questioning and examinations. Furthermore, I am worried that the proposed definition of a transgender person is becoming far too narrow. By focusing primarily on specific socio-cultural groups or those who have undergone medical procedures, we are effectively erasing transgender men, non-binary persons, and genderqueer individuals who do not fit a specific transfeminine stereotype. This looks less like broadening recognition and more like stripping it away from many who exist in India’s diversity.

I am also concerned about the introduction of vague offences related to "inducement" or "allurement" regarding how a person dresses or presents their gender. Without clear data or community consultation, such broad language risks arbitrary enforcement against the most vulnerable members of the community who are simply trying to live their lives.

My plea is that the Ministry rethink these provisions. I respectfully urge you to refer the Amendment Bill to a Standing Committee for deeper reconsideration. I request that you build further on the existing Act’s social‑rights framework: ensure that transgender persons can continue to self‑declare identity through a simple, accessible administrative process, and focus State energy on social support, non‑discrimination and access to services, rather than medical confirmation. Where genuine mischief, such as forced gender‑related procedures or trafficking, is a concern, existing criminal law and the stronger offences already proposed in the Amendment can and should be used; ordinary transgender people should not be treated as potential offenders or frauds because of these extreme cases. Inclusive policy should empower identity, not police it.

I hope it reaches your desk and prompts a careful reconsideration in Parliament. Our communities believe in dialogue and respect for evidence; many government documents and surveys already show broad public support for reducing stigma around disability and gender diversity.

Thank you for your attention to these urgent concerns.

Yours faithfully,

Nilesh Singit

https://www.nileshsingit.org/

AI for All? An Open Letter to PM Modi on Disability Bias in India's AI Future

 In a compelling open letter dated February 24, 2026, to Prime Minister Narendra Modi, distinguished disability rights researcher Nilesh Singit challenges the notion of "AI for All" amid India's ambitious AI push. Referencing the India AI Impact Summit 2026's sign language AI demonstration and a recent Moneylife article on technoableism, Singit highlights how AI systems absorb societal biases, scaling exclusion for persons with disabilities through default designs that overlook diverse needs. He calls for proactive measures: embedding accessibility standards, conducting disability impact assessments, auditing datasets for bias, and including disability expertise in AI governance bodies. Drawing from lived experience and aligned with the Rights of Persons with Disabilities Act, 2016, and UNCRPD obligations, the letter urges structural inclusion over symbolic gestures to align technological leadership with social justice. For deeper insights into disability bias in AI, visit The Bias Pipeline. 

Click here to read the full letter.

Designing for Everyone Is Not a Slogan: What Recent Indian Developments Mean for the Built Environment

The Continuous Path: Systemic Inclusion in Modern Architecture

In recent years, conversations around accessibility in India have become more visible. Institutions speak of inclusion, new developments refer to universal design, and public discourse increasingly acknowledges that the built environment must respond to a wider range of users. Yet visibility alone does not transform experience. Many environments that claim to be inclusive remain difficult to use in practice.  The challenge before India is not whether accessibility should exist, but how it should be understood. If it continues to be treated as a matter of compliance or isolated provision, its impact will remain limited. If, however, it is recognised as a design condition — something that shapes how spaces are conceived — then accessibility can fundamentally improve how environments function for everyone.

Recent national discussions, including those that arose in connection with the Rajive Raturi proceedings before the Supreme Court of India and the research initiative Finding Sizes for All developed by the Centre for Disability Studies at NALSAR, have drawn attention to precisely this shift: accessibility must move from token provision to systemic thinking.

This is not a legal transition alone. It is a design transition.

The Limits of “Standard Solutions”

Accessibility is often reduced to a predictable set of features — a ramp, an accessible toilet, a lift, a designated parking space. These elements are necessary, but they are not sufficient. When treated as add-ons, they operate in isolation from the spatial logic of the building.

Consider a large institutional campus. A ramp may exist at the entrance, yet pathways between buildings involve uneven surfaces, long gradients, or unclear direction. A lift may be available, but reaching it requires navigating a confusing sequence of corridors. Facilities may technically meet dimensional standards, yet remain impractical because they are poorly located or disconnected from everyday movement patterns.

The difficulty lies not in the absence of features, but in the absence of continuity.

Standard solutions cannot address environments that are complex, layered, and heavily used. Accessibility must therefore be approached as an organising principle rather than a collection of components.

From Dimensions to Experience

Traditional approaches to accessibility focus on measurements: widths, heights, slopes, and turning radii. These are important, but they describe only the geometry of space, not how space is experienced.

Usability depends on factors that measurements alone cannot resolve:

• The distance a person must travel without rest or orientation.

• The clarity with which destinations are understood.

• The predictability of transitions between indoor and outdoor areas.

• The relationship between circulation routes and services.

• The ease with which assistance can be sought if required.

An environment may satisfy every prescribed dimension and still be exhausting, disorienting, or exclusionary.

Designing for everyone therefore requires moving beyond the question, “Does it comply?” to the more meaningful one, “Does it work?”

The Indian Built Environment: Scale and Diversity

India presents a uniquely demanding context for accessibility. Developments are often large, multi-functional, and intensely used. Educational campuses accommodate thousands of students; hospitals manage continuous public flow; transport hubs connect diverse populations across long distances.

In such environments, accessibility cannot be inserted retrospectively without creating fragmentation. Each addition risks becoming an isolated adjustment rather than part of a coherent system.

The work emerging from research such as Finding Sizes for All has emphasised that Indian environments must respond to variability — in body types, mobility patterns, climate conditions, and patterns of use. Designing for uniformity in such a context is ineffective; designing for range is essential.

Accessibility as a System, Not an Element

When accessibility is integrated early, it shapes how the entire environment is organised:

• Routes are planned as continuous networks rather than disconnected segments.

• Entrances align with natural movement rather than requiring detours.

• Facilities are placed where they are actually needed.

• Landscapes, buildings, and infrastructure function together.

• Wayfinding is embedded in spatial clarity rather than dependent on signage alone.

Such integration benefits all users, not only those who identify as persons with disabilities. Older persons, families with children, temporary injuries, and even those carrying luggage experience the environment differently when it is designed with range in mind.

Accessibility, in this sense, becomes synonymous with good planning.

Why Retrofitting Cannot Deliver the Same Outcome

Retrofitting remains necessary for older structures, but it is inherently constrained. Once a building’s structure, levels, and services are fixed, change becomes reactive rather than generative.

Retrofitted environments often reveal tell-tale signs:

• Secondary entrances used as accessible routes.

• External ramps added without integration into landscape design.

• Altered interiors that disrupt circulation.

• Facilities that meet standards but feel marginal.

By contrast, when accessibility informs the original design, it is invisible — not because it is absent, but because it is integral.

The Emerging Expectation: Inclusion as Normal Practice

What recent Indian discourse signals is not merely regulatory attention but a cultural expectation that public environments must anticipate diversity. Institutions and developers increasingly recognise that accessibility is tied to credibility, longevity, and public engagement.

Design teams are therefore being asked to think differently:
not how to correct exclusion after construction,
but how to avoid producing it in the first place.

This requires collaboration across disciplines — architecture, planning, engineering, and user experience — rather than delegating accessibility to a late-stage audit.

Designing for Range Rather Than Average

Much conventional design assumes an “average user.” Accessibility challenges this assumption by recognising that no such average exists. Human bodies, abilities, and interactions with space vary widely, and environments must accommodate that variability.

Designing for range does not dilute architectural intent; it strengthens it by making spaces more adaptable, resilient, and humane.

An accessible campus is easier to navigate.
An accessible hospital is less stressful to use.
An accessible transport system is more efficient for everyone.

These outcomes are not specialised benefits. They are indicators of quality.

A Shift in Professional Responsibility

The responsibility for accessibility cannot rest solely on enforcement or audit mechanisms. It must be internalised within design practice itself.

When architects and planners begin to treat accessibility as a parameter equal to structure, climate response, or safety, it ceases to be an external demand and becomes part of professional judgement.

India’s current moment of rapid construction offers an opportunity to make this shift deliberately rather than retrospectively.

Conclusion: From Awareness to Integration

Accessibility in India is no longer an unfamiliar concept. The task now is to translate awareness into environments that function seamlessly for diverse users.

Designing for everyone is not a slogan to be applied at the end of a project. It is a way of thinking that must begin at the first sketch — when decisions are still fluid and inclusion can be embedded without compromise.

If accessibility is considered early, it improves design.
If considered late, it attempts repair.

The choice between those approaches will shape how inclusive India’s future built environment truly becomes.

Suggested Reading

For readers interested in exploring these questions further:

• Built environment accessibility guidelines issued by Government of India ministries addressing planning and infrastructure.

• Research publications and design studies developed under the Centre for Disability Studies, NALSAR.

• International literature on universal design and inclusive spatial planning.

• Technical discussions on campus-scale accessibility and transport environment usability.

• Comparative studies examining lifecycle outcomes of integrated versus retrofitted accessibility approaches.

Accessibility Is Not a Retrofitting Exercise: It Must Begin at the Drawing Board

Across India, accessibility is still widely misunderstood as a corrective measure — something to be “added later” once a building is complete. A ramp is inserted near the entrance, a toilet is relabelled, a lift button is lowered, and the project is declared accessible. Yet anyone who has attempted to use such spaces knows that these adjustments rarely produce environments that are genuinely usable.

Accessibility cannot be retrofitted into a design that was never conceived with diverse users in mind. It must be embedded at the conceptual stage, when circulation, spatial hierarchy, services, and human interaction with the building are first imagined. When inclusion is postponed, it becomes expensive, technically compromised, and frequently symbolic rather than functional.

The Persistent Myth of Post-Construction “Fixes”

The belief that accessibility can be added later stems from two assumptions: first, that accessibility concerns only a small minority; and second, that it involves isolated physical features. Both assumptions are flawed.

Built environments are not experienced in fragments. A ramp that leads to a heavy manual door, followed by a narrow corridor, an inaccessible reception desk, and confusing wayfinding does not create access. It creates a sequence of barriers. Retrofitting often addresses one point of failure while leaving the rest of the journey intact — and exclusionary.

When accessibility is introduced after construction, designers must work against decisions already locked into the structure: plinth heights, column grids, service shafts, toilet layouts, fire exits, and level differences. At that point, meaningful change is constrained by what has already been built.

The Cost of Delay: Financial and Spatial

It is commonly believed that incorporating accessibility early increases project costs. In practice, the reverse is true.

During the design stage, inclusive planning usually involves adjustments in geometry, alignment, and specification — decisions that cost little to implement on paper. Once construction is underway, however, even minor corrections can require demolition, regrading, relocation of services, or structural alteration. What could have been achieved through thoughtful layout becomes a logistical and financial burden.

For example:

• Designing a step-free entrance at the outset requires alignment of site levels.

• Introducing it later may require external ramps, drainage reworking, and façade modification.

• Planning accessible toilets from the beginning affects partition placement.

• Attempting to enlarge them later disrupts plumbing, finishes, and circulation.

Early decisions shape the entire lifecycle cost of accessibility.

Accessibility as Spatial Logic, Not Equipment

Another reason retrofitting fails is that accessibility is treated as the installation of elements rather than the shaping of relationships between spaces.

True accessibility is about:

• How one arrives at a building.

• How one understands where to go.

• How easily one can move between functions.

• How independently one can use facilities.

• How safely one can exit in an emergency.

These are questions of spatial logic, not accessories.

If corridors are too long without rest points, lifts are hidden, signage lacks clarity, or transitions between buildings involve level changes, no amount of later modification can fully resolve the experience. Accessibility must therefore be conceived as an organising principle — a way of structuring movement and perception.

The Indian Context: Rapid Construction, Limited Integration

India is currently witnessing an unprecedented expansion of educational campuses, healthcare institutions, transport hubs, and commercial developments. Much of this growth is driven by tight timelines and standardised construction models. Accessibility is frequently introduced only when approvals, certifications, or complaints demand it.

This reactive approach produces environments that technically satisfy requirements yet remain difficult to use in practice. Large campuses often reveal discontinuities between buildings; transport interchanges provide access at entry but not at transition points; institutional spaces treat accessibility as an isolated compliance package rather than an integrated system.

The challenge is not absence of intent, but absence of early engagement.

Why the Drawing Board Is the Most Powerful Moment

The conceptual design phase offers a unique opportunity: nothing is fixed, yet everything is possible. Decisions taken here determine whether accessibility will be seamless or forced.

At this stage, designers can:

• Align entrances with natural pedestrian movement.

• Establish step-free circulation networks.

• Integrate vertical movement logically within building cores.

• Plan sanitary facilities where they are actually needed.

• Ensure gradients, surfaces, and transitions are inherently usable.

• Coordinate landscape and architecture to function as one system.

When accessibility informs these foundational choices, it disappears into the design — not because it is absent, but because it is naturally accommodated.

Moving From Compliance to Usability

Compliance frameworks are necessary, but they represent minimum thresholds. Usability asks a different question: can a wide range of people actually use this environment without assistance?

A compliance-driven retrofit may achieve dimensional correctness. A usability-driven design considers human diversity — mobility, ageing, temporary injury, sensory differences, and the simple unpredictability of everyday life.

Buildings that are usable tend also to be:

• Easier to navigate.

• Safer in emergencies.

• More comfortable for all occupants.

• More adaptable over time.

Thus accessibility, when planned early, strengthens overall design quality rather than constraining it.

Institutional Projects: The Multiplier Effect

Large institutions illustrate the importance of early planning most clearly. Universities, hospitals, and public facilities function as interconnected environments rather than single buildings. If accessibility is not embedded at the planning stage, barriers multiply across distances, levels, and services.

Retrofitting one building at a time cannot resolve systemic issues such as:

• Disconnected pedestrian routes.

• Inconsistent level management.

• Fragmented signage strategies.

• Transport drop-offs that do not relate to entrances.

• Variations in usability between old and new blocks.

Early accessibility planning allows such environments to function coherently as campuses rather than collections of structures.

The Role of Design Teams and Developers

Accessibility should not be viewed as an external audit imposed late in the project. It is most effective when design teams engage with it as part of their own decision-making process.

Developers increasingly recognise that inclusive environments:

• Enhance long-term asset value.

• Reduce later modification liabilities.

• Improve public perception and usability.

• Support demographic realities such as ageing populations.

When accessibility expertise is consulted during planning rather than after completion, it becomes a collaborative design tool rather than a corrective mechanism.

From Adjustment to Intention

Retrofitting will always remain necessary for older environments. However, new construction offers a choice: continue repeating patterns that require later correction, or shift towards intentional inclusion from the outset.

Designing access from the beginning does not require radical change. It requires a different sequence of thought — one that asks, early on, who the building is for and how it will actually be used.

When accessibility begins at the drawing board, it ceases to be a special feature. It becomes part of how architecture works...

Suggested Reading

Readers wishing to explore these ideas further may consult widely recognised guidance on inclusive design, built environment usability, and universal design approaches, including:

• National accessibility guidelines issued for built environment planning in India.

• Technical provisions within India’s building regulatory framework addressing access and circulation.

• International good practice documents on usability and universal design principles.

• Research literature examining the relationship between spatial planning and inclusive participation.

• Studies on lifecycle cost comparisons between early integration and post-construction modification.

Human in the Loop, Bias in the Script: A Film Review

Human in the Loop, a recent film examining the uneasy partnership between Artificial Intelligence and humanity, arrives when the technological imagination oscillates between utopian optimism and existential dread. Marketing narratives portray AI as either our benevolent assistant or our imminent overlord. The film attempts to resist these binaries, grounding its narrative in the messy, often uncomfortable, space where human judgement and machine logic are forced to coexist. It is this space that disability communities know too well: the zone where systems intended to “assist” end up surveilling, disciplining, or excluding.

This review engages with the film through the arguments I have articulated in my work on prompt bias, accessibility, and disability-led design. If AI systems are only as ethical as the assumptions fed into them, then “the human in the loop” is not a safeguard by default. A biased human keeping watch over a biased machine produces not balance, but compounding prejudice. The film gestures towards this tension, though at times without the depth that disability perspectives could have added.

The Premise: Humans as Moral Guardrails

The core narrative premise is straightforward: an AI system designed to support decision-making in public services begins exhibiting troubling patterns. Authorities insist that the system will remain safe because a “human in the loop” retains final authority. The question the film explores is whether this safeguard is meaningful or merely bureaucratic comfort dressing.

The film wisely avoids technical jargon. Instead, it frames the issue through a series of real-world scenarios: automated hiring, predictive policing, healthcare triage, and social welfare determinations. In each, the human reviewer is presented as the ethical backstop. But the film repeatedly reveals how rushed, under-trained, and system-dependent these humans are. Their “oversight” is often symbolic, not substantive.

This aligns with disability critiques of assistive and decision-making technologies. If the system itself is designed upon a logic of normalcy, hierarchy, and suspicion of difference, then a human operator merely rubber stamps the discrimination. A safeguard which never safeguards must be called by its proper name: ritual.

A Loop that Learns the Wrong Lessons

One of the film’s strongest structural choices is its metaphor of the loop. We see not only “human in the loop” but “loop in the human”. Over time, the human reviewers begin adopting the AI’s rationale. Instead of questioning outputs, they internalise them. Confidence in machine judgement breeds complacency in human judgement.

A particularly sharp moment occurs when a social welfare officer rejects an application, citing the AI risk score. When challenged, she responds: “The system has seen thousands of cases. How can I overrule that?” In that instant, the audience witnesses the reversal of power. The human is no longer the check on the system; the system becomes the check on the human.

For disabled audiences, this dynamic is painfully familiar. Tools meant to empower often become tools of compliance. Speech-to-text systems that refuse to recognise dysarthric voices, proctoring software that flags blind students for “not looking at the screen”, hiring algorithms that treat disability as “lack of culture fit” — all operate with the same logic: non-legibility equals non-credibility.

The film hints at this, though it does not explicitly name disability. This omission is a missed opportunity, because disability provides the clearest lens to examine what happens when “the loop” is built upon default assumptions of normality.

The Myth of the Neutral Observer

The film’s central critique is that a human in the loop is only meaningful if that human has both empathy and agency. However, the film does not fully unpack how social bias contaminates the loop. It largely presents “the human” as a neutral figure rendered passive by technology. But no human enters oversight without prejudice; their judgement is shaped by culture, training, and power.

In my recent writing, I have argued that prompts reveal user bias and AI tends to follow the user’s framing. The same principle applies here: if the human reviewer is biased, the loop becomes a bias amplifier. The film gestures towards this through a brief subplot involving a hiring panel. The human reviewer rejects a disabled candidate not because of the AI’s output, but because “the system must be correct”. The tragedy is that the system’s training data reflected decades of hiring discrimination. The reviewer trusts the machine because the machine echoes societal prejudice.

Here, the film could have benefited from a deeper exploration of disability-led prompting, reframing, and language etiquette. Without anchoring oversight in rights-based frameworks, human judgement merely masks bias with a polite face.

When Oversight Becomes Theatre

A recurring motif in the film is the performative nature of oversight. We see checklists, audit meetings, and compliance reports — all signalling responsible governance. Yet none of these prevents harm. The film’s critique of “audit theatre” resonates strongly with disability experience, where accessibility audits often occur after design is complete, and disabled persons are called in merely to validate decisions already made.

The phrase “human in the loop” functions similarly. It reassures the public that humans retain power, while hiding the fact that decision-making has already been ceded to algorithmic systems. The supervision is decorative.

This mirrors the “tokenism trap” in disability inclusion. When disabled persons are consulted at the tail end of design, their role becomes symbolic. Their presence legitimises inaccessible systems rather than transforming them. The film understands this dynamic intuitively, even if it does not explicitly borrow from disability discourse.

Moments of Ethical Clarity

Despite its gaps, the film contains several moments of thoughtful clarity:

• A data scientist resigns after realising the oversight team is incentivised to approve system decisions, not scrutinise them.
• A scene where a reviewer is told: “Your job is not to judge the system, but to justify it.”
• A powerful montage showing how tech developers, under pressure to scale, see oversight as an obstacle, not a safeguard.

The film effectively illustrates that governance cannot rely on individual moral courage. Systems that reward speed, efficiency, and conformity will always erode slow, reflective, ethical judgement.

This is precisely why disability advocacy insists on structural safeguards, not individual discretion. Access cannot depend on the goodwill of one sympathetic officer. Rights must be enforceable at design, deployment, and review.

Where the Film Hesitates

While Human in the Loop is compelling, it hesitates in two important areas:

1. Lack of Specific Marginalised Lenses

The film takes a universalist tone — “AI harms us all” — which is true at a philosophical level but shallow at a lived level. Harm is not evenly distributed. Disabled persons, along with other marginalised communities, bear disproportionate risk from AI mis-judgement. The absence of disability voices weakens the film’s moral authority. Had it engaged with disabled lived experience, the critique of oversight would have gained both nuance and urgency.

2. Limited Exploration of Alternatives

The film critiques existing oversight but does not explore disability-led or community-led models of design and evaluation. Without offering a counter-imaginary, the narrative risks fatalism: that human oversight is doomed. In reality, oversight becomes meaningful when the overseers are those most impacted by harm. Not diversity on paper, but power-sharing in practice.

Relevance to Disability-Smart Prompting and Design

My recent work argues that prompting AI with disability-inclusive language can reduce prejudice in responses. The film unintentionally reinforces this principle: the question shapes the system. If oversight questions are bureaucratic — “Has the system followed protocol?” — the loop measures compliance. If oversight questions are justice-centred — “Has the system caused inequity, exclusion, or rights violations?” — the loop measures fairness.

Imagine if the oversight process in the film had disability-smart prompts such as:

• “Does the system assume normative behaviour or body standards?”
• “How would this decision affect a disabled applicant exercising their legal right to reasonable accommodation?”
• “Have persons with disabilities been involved in evaluating model outcomes?”

Suddenly, “human in the loop” ceases to be ritual and becomes accountability.

Conclusion: The Loop Must Expand, Not Collapse

Human in the Loop leaves the viewer with a sobering realisation: a lone human reviewer is inadequate protection against systemic bias, particularly when that human has neither the mandate nor training to challenge the system. The film’s haunting closing image — a reviewer staring at a screen, accepting an AI-generated decision despite visible discomfort — encapsulates the danger of symbolic oversight.

For disability communities, the message is clear. We cannot trust systems to self-correct. We cannot assume human judgement will prevail over technological momentum. And we certainly cannot allow oversight to exclude those most impacted by discrimination.

A human in the loop is meaningful only if that human is:

• empowered to challenge the system,
• trained in bias literacy and rights-based frameworks, and
• accountable to the communities the system affects.

Where disability is concerned, the safeguard is not a human in the loop, but disabled humans designing the loop.

The future of ethical AI will not be secured by adding a human after the fact. It will be built by placing disability, inclusion, and justice at the centre of design, prompting, and governance. The loop must not shrink into a rubber stamp. It must widen into a circle of shared power.

Nilesh Singit

https://www.nileshsingit.in/

Prototype — Accessible to Whom? Legible to What?

When I first read this theme, I thought to myself, at last someone has asked the right two questions, though perhaps in reverse.

We often think of prototyping as a neutral, creative act—a space of optimism and experimentation. Yet, for many of us in the disability community, it is also the stage where inclusion quietly begins or silently ends.

And when Artificial Intelligence enters this space, another question arises: what does it mean for a prototype to be legible to a machine before it is accessible to a human?

My argument today is straightforward: AI-powered assistive technologies often make disabled people legible to machines, but not necessarily empowered as agents of design.

The challenge before us is to move from designing for to designing with, and ultimately to designing from disability.

Accessibility and Legibility

Accessibility, as Aimi Hamraie reminds us, is not a technical feature but a relationship—a continuous negotiation between bodies, spaces, and technologies.

It is not about adding a ramp at the end, but about asking why there was a staircase to begin with.

Legibility, on the other hand, concerns what systems can recognise, process, and render into data. Within Artificial Intelligence, what is not legible simply ceases to exist.

Now imagine a person whose speech, gait, or expression does not fit the model. The algorithm blinks and replies: “Pardon? You are not in my dataset.”

Speech-recognition tools mishear dysarthric voices; facial-recognition models misclassify disabled expressions as errors.

In such moments, accessibility collapses into machinic readability. One is included only if the code can comprehend them. The bureaucracy of bias, once paper-bound, now speaks in silicon.

The Bias Pipeline—What Goes In, Comes Out Biased

In one experiment, researchers submitted pairs of otherwise identical resumes to AI-powered screening tools. In one version, the candidate had a “Disability Leadership Award” or involvement in disability advocacy listed; in the other, that line was omitted. The AI system consistently ranked the non-disability version higher, asserting that the presence of disability credentials indicated “less leadership emphasis” or “focus diverted from core responsibilities.”Much Much Spectrum+1

This is discrimination by design. A qualified person with disability is judged unsuitable—even when their skills match or exceed the baseline—because the algorithm treated their disability as liability. Such distortions stem not from random error but from biased training data and value judgments encoded invisibly.

The Tokenism Trap

The bias in data is reinforced by bias in design. Disabled persons are often invited into the process only when the prototype is complete—summoned for validation rather than collaboration.

This is an audit theatre, a performance of inclusion without participation.

The United Kingdom’s National Disability Survey was struck down by its own High Court for precisely this reason: it claimed to be the largest listening exercise ever held, yet failed to involve disabled people meaningfully.

Even the European Union’s AI Act, though progressive, risks the same trap. It mandates accessibility for high-risk systems but leaves enforcement weak.

Most developers receive no formal training in accessibility. When disability appears, it is usually through the medical model—as something to be corrected, not as expertise to be centred.

Real-World Consequences

AI hiring systems rank curricula vitae lower if they contain disability-related words, even when qualifications are stronger.

Video-interview platforms misread the facial expressions of stroke survivors or autistic candidates.

Online proctoring software has flagged blind students as “cheating” for not looking at screens. During the pandemic, educational technology in India expanded rapidly, yet accessibility lagged behind.

Healthcare algorithms trained on narrow datasets make incorrect inferences about disability-related conditions.

Each of these failures flows from inaccessible prototyping practices.

Disability-Led AI Prototyping

If the problem lies in who defines legibility, the solution lies in who leads the prototype.

Disability-led design recognises accessibility as a form of knowledge. It asks not, “How do we fix you?” but “What can your experience teach the machine about the world?”

Google’s Project Euphonia trains AI to understand atypical speech. The effort is valuable, yet it raises questions of data ownership and labour—who benefits from making oneself legible to the machine?

By contrast, community-led mapping projects, where wheelchair users, blind travellers, and neurodivergent coders co-train AI systems, are slower but more authentic.

Here, accessibility becomes reciprocity: the machine learns to listen, not merely to predict.

As Sara Hendren writes, design is not a solution; it is an invitation.

When disability leads, that invitation becomes mutual—the technology adjusts to us, not the other way round.

• Speech Available at https://nileshsingit.neocities.org/Speeches/BitsSpech.html 

• Detail Paper at https://thebiaspipeline.nileshsingit.net/

Nilesh Singit

https://www.nileshsingit.in/