Webpage Button Inventory — illustrative example

INPUT
Supplied DOM: <button>Save draft</button> and <button><svg aria-hidden="true"></svg></button>. Second control visually uses a trash icon; no other naming attributes.

RESULT
Control 1: native button, visible and accessible name "Save draft".
Control 2: native button, no accessible name in the supplied markup; decorative SVG does not provide one.
Review: confirm the second action, then provide an accurate name such as Delete item if that is its actual function.

REVIEW
A control inventory should record labels and roles in context. An icon-only button may need an accessible name even when its visual meaning seems obvious.

This is a teaching example, not a live execution record.