Hi, I feel there is no solid algorithm defined to determine accessible name of an 6.1 input type="text" Current algorithm has the problem that when aria-label is not defined for a text input the value is used. Problem (s) with this a. If you have an empty form with multiple textinputs beeing empty they all have accessibility name=”” b. As soon as you start typing in an input type = text the accessibility name is changing (to be equal to the value entered) c. As name keeps changing its harder to define a finding algorithm based on the accessibility name
Current Algorithm 1. If the control has an aria-label or an aria-labelledby attribute then use this as the accessible name 2. If the control has an value attribute then use this as the accessible name (This i find really silly as name would change when value is changing) Algorithm that makes more sense in my opinion 1. If the control has an aria-label or an aria-labelledby attribute then use this as the accessible name 2. If the control has an id attribute then use this as the accessible name 3. If the control has an name attribute then use this as the accessible name 4. If the control has an placeholder attribute then use this as the accessible name 5. If the control has an value attribute then use this as the accessible name (This i find really silly as name would change when value is changing) References referring to HTML to Platform Accessibility APIs Implementation Guide W3C Editor's Draft 28 August 2013 6. Accessible Name and Description calculation which refers to section 5.2.7. Accessible Name Calculation for determining the accessible name of an inputbox. The terms accessible name and accessible description are properties provided in all accessibility APIs. The name of the properties may differ across APIs but they serve the same function: as a container for a short (name) or longer (description) string of text. regards, Elwin
