Proposed API mappings for typed ruby proposal

[aleventhal]

In w3c/aria#1620 (comment) @cookiecrook proposes 3 <ruby> annotation types. In addition, there can be the absence of a type, which is currently the case of all ruby markup on the web. Software heuristics could be used when a type is not specified, to attempt to guess the type.

This proposal builds on what has been proposed for typeless ruby in #351 and #352. (Ruby would be expose as a description with a description-from attribute. When the Ruby type is unknown, "description-from" could be set to "ruby-annotation"). Chrome currently already implements this.

If ruby types become standardized, and the Ruby type is known, "description-from" could have a suffix that matches one of the type values in @cookiecrook's proposal, e.g. "ruby-annotation-phonetic-required", "ruby-annotation-phonetic-optional", "ruby-annotation-complementary". Having the default case use plain "ruby-annotation" would allow ATs to recognize that the author has not supplied a type, and allow a heuristic to be supplied.

[cookiecrook]

To be clear, the linked comment in w3c/aria#1620 (comment) was a brainstorm, not a fully fleshed out proposal. Please read the linked thread for full context.

[aleventhal]

@cookiecrook yes, that's clear

This is a proposed mapping for your proposal, to help understand it more deeply.