…rkType (#639)

This is redundant and not required for implementers. Localized
{Landmark, Control} Types are supposed to provide additional information;
not duplicate the same information available in {Landmark, Control} Type.

Makes editing easier and will also help when programmatically generating
testable statements.

When aria-sort is used on a columnheader, it does not change the platform
role; aria-sort is mapped to NSAccessibilitySortDirectionAttribute.

These will be needed by some not-yet-committed tools to generate testable
statements automatically.

Write mappings in a consistent format, both for readability and for easier
programmatic generation of testable statements

Also fix typo in markup.

Should be AXToggle; not AXToggleButton

…a-owns

This change reflects what is seen in (at least) Gecko, but leaves the
possibility of continuing to use the accessible relation types which
were previously used by Gecko and may still be used by other user agents.

This is not a change; merely a clarification.

These notations were in place to ensure changes we must test as part of
the CR process were not missed. These changes are now all noted in the
testable statements wiki for Core AAM.

Also addresses github issue #645.

… in Core-AAM (#647)

Clarify the criteria for elements with children presentational true to specify that:
1. Text content of excluded elements is included
2. Exceptions, such as focusability, also apply

This is already stated in the ARIA specification, but was not clear from
the text present in the Core AAM.

Fixes github issue #492.

mostly by converting to regular note

Use https

A single mapping-tables.js that checks for respec context, and executes
accordingly. This is instead of having two versions, one for the respec
context in the master branch, and a different version for the snapshot
gh-pages branch. See related w3c/html-aam issue 74:
w3c/html-aam#74

…for AXAPI

This mapping is already mentioned in the narrative content; it was just
absent from the table.

In the last release we made a change to map placeholder attribute and aria-placeholder to the UIA HelpText property (https://msdn.microsoft.com/en-us/library/dd757479(v=vs.85).aspx). This change reflects that.

Note: AriaProperties gets automatically populated with ALL aria-* properties, which is very easy way to "map" something, when there is no better alternative. Now that we found alternative for placeholder - we can actually specify it properly.

UIA mapping for aria-placeholder

Addresses github issue #7.

Addresses github issue #15.

The rules regarding tree inclusion and exclusion are platform independent
and have nothing to do with accessibility API mappings. Furthermore, we
wouldn't want those rules, which are important, missed because they are
not in the ARIA spec. Now that #792 has been merged, remove the
redundant content from Core AAM.

Fixes github issue #17.

* The "planned" documents should point to 1.2
* The current documents should point to 1.1

Fixes github issue #23.

Editorial: "controller-for" is not a good example for semantic significance #24

See w3c/accname#34.

Move Special Document Handling Section to ARIA

Remove ID Errors Section (move to ARIA)

… (in ARIA)

The ARIA spec now contains error handling content, including what user agents
should do when the current value is requested but not set by the author.

This one-sentence subsection of "General Rules" doesn't offer anything
of value. In addition, it's odd that states are being singled out here:
There are roles, properties, and relations whose exposure is also defined
in this spec, but the lack similar one-line subsections.

The States and Properties Mapping table includes the reverse relationships
which user agents MUST implement. Therefore, remove the table which
duplicates this information and update the text to point to the correct
table.

…as discussed in issue #28.

Some of this content will be added to the new Accessibility Tree section of the ARIA spec.

Remove discussion of semantic significance of elements from Core-AAM …

Editorial nits in Comparing Accessibility APIs section

Addresses github issue #37.

2bb7c8b moved the widget values section
to the ARIA spec. Based on the commit comment, I'm updating links to
that section as best as I can figure out.

This will help with automating test generation.