'Use WAI-ARIA mapping' is not descriptive

[asurkov]

It's not readers friendly to say 'Use WAI-ARIA mapping' suggesting the reader to go and read another spec on his own. So we could take two approaches to address the issue: 1) turn 'use ARIA mapping' into a link - easy to implemented, should be ok for the readers 2) create a pool of mappings in JS shared between specs - harder to implement, need to support non-JS version; but it has to be #1 reader's choice.

@joanmarie , @jasonkiss your thinking?

[marcoscaceres]

So, yeah, I ran into this too. We might need think of something different as right now, it’s not very friendly to people who land at one of those tables.

[marcoscaceres]

Option 2 as suggested above is now maybe an option, as ReSpec now provides automatic cross document references.

However, before we talk solutions, we should figure out what the table actually is trying to achieve.

I came to the table from Mozilla’s bugzilla in the hope of figuring out how to implement one of these in the browser. Traditionally, the spec would lead me to an algorithm or some idl.

So, let’s put ourselves in an implementer’s shoes: I land at a table, now what?

[scottaohara]

@spectranaut @jnurthen now that we have IDs working in the AAM specs again (thank you), I'm wondering if this might be something that could be scripted?

e.g., for each element/attribute that is identified as "use wai-aria mapping", would it be possible to pull the mappings form Core AAM and have them render in the necessary table cells here?

It'd definitely help cut down on the need to go back and forth between specs, yet also make sure that Core AAM was the source of truth for the role mappings. Maybe we can discuss this at some point?

[scottaohara]

@pkra @spectranaut, do you think this might be an issue we can talk about in the editors' meeting? arguably now that all the specs are in the same repo, this should be "easier" to do something about.

[pkra]

I've tagged it so it can be found more easily.