Layer naming conventions versus Accessibility panel metadata with symbol overrides

Designers need a consistent way to author accessibility metadata on artboards, symbols and shared components that remains accurate through library updates and is faithfully exposed in Sketch Cloud inspect.

Sketch provides an Accessibility panel per layer for role, label and description intended for handoff, while consistent layer naming keeps semantics visible in the Layers list and survives simple exports. For symbols, metadata can be defined on the master and inherited by instances, but instance-level overrides can replace or hide master values.

The unresolved decision is source of truth under nested symbol overrides, where manual authoring also risks drift between visual changes and authored semantics.

When an instance overrides a layer's accessibility label or role, which value is surfaced in Sketch Cloud inspect? Should teams treat layer names as canonical semantics and the Accessibility panel as handoff-only, or the reverse for symbols with overrides? What governance keeps authored labels in sync with visual changes in nested symbols?