Illustrate how attributes and properties could be distinct concepts

[annevk]

This could be a potential solution to #1895. The idea here would be to define all the ARIA attributes in terms of DOM/HTML types. This example shows what aria-orientation would look like defined as an enumerated attribute.

And then separately define how identically-named ARIA properties end up using those attributes to compute their own state for use by AT.

I think applying this throughout would resolve a lot of ambiguity and would help end up solving the reflect problem as well.

Closes #????

Describe Change Here!

PR tracking

Check these when the relevant issue or PR has been made, OR after you have confirmed the related change is not necessary (add N/A). Leave unchecked if you are unsure. Read the Process Document or Test Overview for more information.

• [ ] Related Core AAM Issue/PR:
• [ ] Related AccName Issue/PR:
• [ ] Related APG Issue/PR:
• [ ] Any other dependent changes?

Implementation tracking

• [ ] "author MUST" tests:
• [ ] "user agent MUST" tests:
• [ ] Browser implementations (link to issue or when done, link to commit):
  • WebKit:
  • Gecko:
  • Blink:
• [ ] Does this need AT implementations?

---

Preview | Diff