AXCustomContent localizable strings

[mattgarrish]

The question was raised in #15 (comment) about whether the new AXCustomContent strings are localizable.

I noticed that the core AAM document has this note:

User agent should return a user-presentable, localized string value for the AXRoleDescription.

@cookiecrook, @aleventhal do you think this could be solved by adding this note to the DPUB document and also have it reference AXCustomContent?

User agent should return a user-presentable, localized string value for the AXRoleDescription and AXCustomContent.

[aleventhal]

Although only part of AXCustomContent is localized, correct?

For example:

{ label: "type", value: "abstract" }

I assume only the value field is localized.

[mattgarrish]

I assume only the value field is localized.

Ya, I was trying to avoid saying value twice. It's probably not necessary to say "string value" for the description, so what if we move it to describe the AXCC field:

User agents should return a user-presentable, localized string for the AXRoleDescription and the AXCustomContent value.

[aleventhal]

SGTM

…

On Thu, Jan 5, 2023 at 3:43 PM Matt Garrish ***@***.***> wrote: I assume only the value field is localized. Ya, I was trying to avoid saying value twice. It's probably not necessary to say "string value" for the description, so what if we move it to describe the AXCC field: User agents should return a user-presentable, localized string for the AXRoleDescription and the AXCustomContent value. — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKQAZWDUBHWW3QDDSPYKXTWQ4W5PANCNFSM6AAAAAATSHM6OQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mattgarrish]

Closing with #20