Skip to main content
Use these terms when describing Akron in issues, suggestions, screenshots, or setup notes. They match the overlay’s own layout and labels.

Quick vocabulary

How to describe a problem

Start with the broad location, then narrow down to the exact row and control type.
Good reports describe what happened and what was expected:

What to include in issues

  • The tab name and column, if the screenshot shows more than one column.
  • The exact row label.
  • Whether the control is a toggle, input box, submenu, button, slider, or status row.
  • The visible attempt status and policy badge when reporting classification behavior.
  • The map SID when the behavior depends on the current map.
  • A screenshot or short clip when the issue is visual, input-driven, or timing-sensitive.
Use Overlay for the main overlay guide and the Feature guide for the current list of rows by tab.