Component API brief

How should consumers use this component?

When should consumers use something else?

Which native meaning should the component preserve?

Which props does the component need?

Which variants belong in the public API?

Which parts may consumers replace?

Which defaults make the common case simple?

Which invalid combinations should the API prevent?

Which state should a consumer control?

Which state may the component manage itself?

Which state can be derived from other props?

When should internal state reset?

Which user actions should emit public events?

What should each event payload contain?

In what order should related events fire?

Which events may consumers cancel?

How should public events relate to native browser events?

Which accessibility behavior does the API guarantee?

Which accessibility relationships must consumers provide?

Which keyboard behavior is built in?

How does the component manage focus?

Which changes should assistive technology announce?

How should consumers compose the component safely?

Which compositions would create invalid markup?

Which styling controls are public?

Which styles must remain internal?

How will breaking API changes be introduced?

Which version change signals a breaking update?

How will deprecated features be communicated?

What API migration support will component consumers receive?

Which tests protect existing consumers?