AAPI

Review Action Items

Everyone has had hectic travel schedules. Jason has not made any further updates to the page we've been working on, and he's discovered that a number of layout/markup changes he made got overwritten. He has to figure out how to get his changes back. Cynthia suggested that he talk to Mike Smith.

Cynthia says that there were some discussions in PF F2F that might impact AAPI. She has action items related to the ARIA version of the doc, and some are about how ARIA and HTML interact.

Jason caught Cynthia up on our previous discussion about nested links firing for screen readers when the nested links are the first item in a <summary>. Cynthia recapped the issues as she sees them:

• Should we use links inside summary in our doc?
• Do we consider links inside summary an authoring error? Are there places where it isn't allowed? (For example, <button> <a href></button> is not allowed; spec says no interactive content within a <button>.)
• What should screen readers do when they encounter nested interactive elements? It's unclear what the appropriate screen reader behavior should be. Jason asks, should role="button" be interpreted as "is a button with all the characteristics of a <button>"?
• No issue with mapping, because the AAPI tree can support it.

We need to wait and see if Steve's change proposal goes through before working any more on nested interactive elements.

We need to figure out how to add links to the appropriate section in the spec.

Jason has filed bugs with both NVDA and JAWS on their behaviour with links nested as first item in <summary> or other interactive content, eg. a heading. He's also publishing an article on the screen reader and details/summary issues around nested links in the next few days and will send Cynthia a link when it's finished.