The "name and desc" section of HTML-AAPI oversimplifies the steps to determine alternatives when encountering specific HTML elements. For example, the AAPI doc says that aria-label should always trump value on controls, when that's only the case if it's not being calculated recursively for another element. The simplified lists with instructions like "use aria-labelledby" even seem to conflict with the ARIA algorithm in places.

http://www.w3.org/TR/2013/WD-html-aapi-20131001/#accessible-name-and-description-calculation

I would recommend rewriting the section to include the following changes:

1. Remove all the processing order lists. Defer to the ARIA spec for these.
2. Add a new section declaring the order and importance of host language labeling mechanisms (e.g. table>caption, img[alt], and so on) for each element. Note in the section that these will be used in rule 2A bullet 3 of the ARIA computation.
3. Add a new section declaring whether each element is a control (e.g. input) whose value should be used in the rule 2B of the ARIA. Remember to define how to determine the control value per element.
4. Declare any special-case attribute usage (e.g. @placeholder) in the same section where you declare the tooltip attribute (e.g. @title).