Review mappings once new roles are added

[scottaohara]

ARIA 1.2 will introduce various new roles and mappings for greater parity with HTML.

After publication, we should review the HTML AAM's element mappings and ensure that any necessary elements are mapped to their appropriate WAI ARIA roles.

For instance, del, ins, meter, dl, dt, dd, strong, em, among others and many that will map to ARIA's role=generic but would also likely benefit from continued exposure of API specific information.

EDIT:

list of mappings to track in this issue. generic will be handled separately

• blockquote => <blockquote>
• caption => <caption> and <figcaption>
• code => <code>
• deletion => <del>
• emphasis => <em>
• insertion => <ins>
• meter => <meter>
• paragraph => <p>
• strong => <strong>
• subscript => <sub>
• superscript => <sup>
• time => <time>

[scottaohara]

note generic in Core AAM Editor's draft: w3c/core-aam@3d7477d

[joanmarie]

note generic in Core AAM Editor's draft: w3c/core-aam@3d7477d

Related: It looks divesque rather than div+spanesque because we haven't yet landed text separation. Treating generic as a div means we can proceed with implementation.

[MarcoZehe]

Note: Also map the <code> element to what ARIA 1.2 proposes. Especially the ATK and IA2 mappings differ.

[stevefaulkner]

@scottaohara dl will map to generic?