Rich commented on 4.4 Role mapping

<change neither of the examples meet the intent of this step as "log" and "search" are valid non-abstract ARIA roles. Also, "search" belongs on a regional landmark and not a single input field>
If the element does not have a role attribute, or if the role attribute contains no tokens matching the name of a non-abstract WAI-ARIA role, the user agent MUST fall back on normal processing of the base markup for the element with the role attribute. For example, for <table role="log"> use the tag name "table" to determine what platform accessibility API role to use. For <input type="text" role="search">, use the platform accessibility API for a text input.
</change>
<to>
If the element does not have a role attribute, or if the role attribute contains no tokens matching the name of a non-abstract WAI-ARIA role, the user agent MUST fall back on normal processing of the base markup for the element with the role attribute. For example, for <table role="beancounter"> use the tag name "table" to determine what platform accessibility API role to use. For <input type="text" role="foo">, use the platform accessibility API for a text input.
</to>