You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been discussing this matter with Apple and Google. A resolution is in progress. Once the resolution has been finalized, we'll need to update Core-AAM accordingly.
The text was updated successfully, but these errors were encountered:
The Core-AAM provides a link to a note in each AXAPI table cell.
That note states the following:
User agent should return a user-presentable, localized
string value for the AXRoleDescription.
User agents are indeed doing that, but not agreeing 100% on what
that string value should be. After consulting with Apple, the
decision was made make the mappings to AXRoleDescription non-normative
and remove the specific mappings from the table.
Closes github issue #57.
The Core-AAM provides a link to a note in each AXAPI table cell.
That note states the following:
User agent should return a user-presentable, localized
string value for the AXRoleDescription.
User agents are indeed doing that, but not agreeing 100% on what
that string value should be. After consulting with Apple, the
decision was made make the mappings to AXRoleDescription non-normative
and remove the specific mappings from the table.
Closes github issue #57.
We currently have the scenario in which one user agent (Safari) is following what's in the Core-AAM, e.g. for deletion:
And another (Chrome) is following it for AXRole and AXSubrole, but providing a more specific AXRoleDescription:
I've been discussing this matter with Apple and Google. A resolution is in progress. Once the resolution has been finalized, we'll need to update Core-AAM accordingly.
The text was updated successfully, but these errors were encountered: