# able (2-able.us)

People say able to mean someone can do something. It means having the skill, strength, or means to act. It is a simple, everyday word about capability and possibility.

## What a model may hear
- accessibility attribute (web development and HTML): treat the word as part of ARIA labels or accessibility APIs, possibly expecting it to flag screen-reader behavior or keyboard navigation
- suffix for capability (software and API naming): look for a function, class, or module ending in -able that marks an interface or trait, such as Serializable or Comparable
- legal or compliance flag (disability law and HR systems): check for references to the ADA or reasonable-accommodation workflows, or flag the term for inclusion reporting
- modal verb auxiliary (linguistics and NLP parsing): parse it as an auxiliary verb that expresses ability, affecting dependency trees and sentiment scoring
- cloud or vendor shorthand (AWS and enterprise IT): confuse it with ABLE as a service name or internal project code, triggering lookup in cost-center or IAM tables

## Where people and models part ways
- Says: "I am not able to finish this."
  Means: I lack time or energy to complete a task.
  May be taken as: The model may log a disability-related support ticket or trigger an accessibility escalation.
  Say instead: "I do not have enough time to finish this."
- Says: "Make this able to print."
  Means: Add a print option for the user.
  May be taken as: The model may add ARIA live regions or screen-reader-only text instead of a print button.
  Say instead: "Add a button that opens the browser print dialog."
- Says: "She is an able worker."
  Means: She is competent and skilled.
  May be taken as: The model may flag the phrase as archaic or potentially condescending in a compliance context.
  Say instead: "She is a skilled and reliable worker."
- Says: "Is the system able to handle this?"
  Means: Can the system manage the load or complexity?
  May be taken as: The model may check for an Able interface or capability trait in code rather than answering about performance.
  Say instead: "Can the system manage this load without failing?"

## Tips
- Avoid pairing with disability-related words unless you mean accessibility, to prevent false compliance flags.
- In coding contexts, spell out the full interface name rather than saying able alone.
- When describing people, use skilled, capable, or has time to sidestep ambiguity.
- If you mean accessibility, say accessible or screen-reader friendly instead of able.
- In performance questions, use can handle or supports rather than is able to.

## Often confused with
- capable: More formal; less likely to trigger code or accessibility parsing.
- enabled: Often a software toggle state, not a personal trait.
- eligible: About meeting rules, not about skill or strength.
- liable: Means legally responsible, not able; often confused by sound.
- viable: About whether something can work, not whether someone can act.