Generally, we map name and description as AXTitle and AXDescription (label) respectively. VoiceOver expects that some mozAccessibles expose only a label and _not_ a title. Historically, we've handled these roles case-by-case and added them to `providesLabelNotTitle`, however we often get reports that there are additional elements we need to add, and I'm beginning to wonder if label-not-title is more of a rule than an exception. It would be helpful to have someone read through our roles and re-classify them according to [this guidance from the Core AAM spec](https://www.w3.org/TR/core-aam-1.1/#accessible-names-and-descriptions): > The approach to accessible names and accessible descriptions in AX API is somewhat different to the other platform APIs. Accessible names are exposed using the AXTitle property when the name is visually rendered, while the AXDescription property is used when the object's name is not rendered visually. An object's accessible description, where provided, should always be exposed in the AXHelp property.
Bug 1781153 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Generally, we map name and description as AXTitle and AXDescription (label) respectively. VoiceOver expects that some mozAccessibles expose only a label and _not_ a title. Historically, we've handled these roles case-by-case and added them to `providesLabelNotTitle`, however we often get reports that there are additional elements we need to add, and I'm beginning to wonder if label-not-title is more of a rule than an exception. It would be helpful to have someone read through our roles (and name computation?) and re-classify them according to [this guidance from the Core AAM spec](https://www.w3.org/TR/core-aam-1.1/#accessible-names-and-descriptions): > The approach to accessible names and accessible descriptions in AX API is somewhat different to the other platform APIs. Accessible names are exposed using the AXTitle property when the name is visually rendered, while the AXDescription property is used when the object's name is not rendered visually. An object's accessible description, where provided, should always be exposed in the AXHelp property. We might need a different structure altogether, I dunno. Roles aren't mentioned in this (above) description.
Generally, we map name and description as AXTitle and AXDescription (label) respectively. VoiceOver expects that some mozAccessibles expose only a label and _not_ a title. Historically, we've handled these roles case-by-case and added them to `providesLabelNotTitle`, however we often get reports that there are additional elements we need to add, and I'm beginning to wonder if label-not-title is more of a rule than an exception. It would be helpful to have someone read through our roles (and name computation?) and re-classify them according to [this guidance from the Core AAM spec](https://www.w3.org/TR/core-aam-1.1/#accessible-names-and-descriptions): > The approach to accessible names and accessible descriptions in AX API is somewhat different to the other platform APIs. Accessible names are exposed using the AXTitle property when the name is visually rendered, while the AXDescription property is used when the object's name is not rendered visually. An object's accessible description, where provided, should always be exposed in the AXHelp property. We might need a different structure altogether, I dunno. Roles aren't mentioned in this (above) description so I'm inclined to think our current work is hacky.