# Avoid language that defines people by disability (EK00030)

import { Aside, Badge } from '@astrojs/starlight/components';

People-first wording names the person before the condition, which keeps your documentation accurate and respectful instead of reducing someone to a disability. EkLine flags terms that describe a person as their disability, such as `handicapped` or `a victim of` (rule EK00030).

## Why use people-first language in documentation?

Terms like "handicapped" or "crippled" reduce a person to a single trait and often carry outdated connotations. People-first phrasing, such as "users with disabilities", describes the same group without that framing. This wording matches the accessibility standards most documentation teams follow, so it also keeps your content consistent with related guidelines.

## What EkLine flags

EK00030 matches terms that define people by a disability, including "handicapped", "crippled", "able-bodied", and "a victim of".

- ❌ **Incorrect:** The feature helps handicapped users navigate the app.
- ✅ **Correct:** The feature helps users with disabilities navigate the app.
- ❌ **Incorrect:** The layout is tested with able-bodied users.
- ✅ **Correct:** The layout is tested with users without disabilities.

## How to fix

Rewrite the phrase to put the person first, then describe the condition: "handicapped users" becomes "users with disabilities", and "able-bodied users" becomes "users without disabilities".

<Aside type="note">
If a flagged term appears inside a quotation or a proper name — for example, an official program title — keep it and ignore the rule for that line.
</Aside>

## FAQ

### What is people-first language?

People-first language names the person before any condition, such as "users with disabilities" rather than "handicapped users". It describes the same group without reducing anyone to a single trait.

### What can you write instead of "handicapped" or "able-bodied"?

Write "users with disabilities" in place of "handicapped users", and "users without disabilities" in place of "able-bodied users". Both put the person first and describe the condition accurately.

## Rule details

| Property | Value |
|----------|-------|
| Rule ID | `EK00030` |
| Category | Inclusive language |
| Default severity | <Badge text="Error" variant="danger" /> |
| Enabled by default | Yes |

## Ignore this rule

To keep a flagged term on one line, add an inline comment with a reason:

```markdown
<!-- ekline-ignore-next-line EK00030 -- official program name -->
Apply through the Handicapped Access Grant program.
```

To disable the rule across your project, add it to the `ignore` list in your [configuration file](/reviewer/configuration/ignoring-rules/#ignore).

## Related rules

- [EK00035](/reviewer/rules/ek00035/) — Use inclusive technical terms
- [EK00013](/reviewer/rules/ek00013/) — Prefer inclusive phrasing