icon-ops

# icon-ops Getting an icon onto a page is easy. Getting one that themes correctly, carries the right licence, matches the twelve icons beside it, and behaves for a screen reader is where the work actually is. ## Helps with An icon that won't change colour on hover, in dark mode, or when the theme switches — almost always a hardcoded `#000` in the file where `currentColor` should be. A UI where the icons "look off" without an obvious cause. Usually two icon sets mixed: different grid size, different stroke width, different corner language. Individually fine, together visibly wrong. Choosing an icon set at the start of a project, when the choice is cheap, rather than after 60 icons are embedded. Using a brand logo — GitHub, Google, a client's mark — and needing to know whether you actually may. The file licence does not answer this; trademark does. Needing a logo for an arbitrary company that no icon set carries. That is a different category from icon sets — a runtime lookup by domain, not a committed glyph — with its own quota, caching and trademark consequences. Icon-only buttons that a screen reader announces as "button", or announces twice. Both come from putting the accessible name in the wrong place. Vendor SVGs carrying Inkscape/Figma metadata, fixed `width`/`height` that fights CSS, and inline styles that resist theming. Deciding between inline SVG, a `<symbol>` sprite, framework components, and an icon font — and discovering too late that `<img src="icon.svg"...