Closes#2631

Right now, the spec says thataria-valuenow should default to 0 even if on an element like<input type="text"> with a nativevalue.

This PR updates the spec to specify that the nativevalue should be used if it exists andaria-valuenow is undefined, falling back on 0 if both are absent.

A few questions to resolve include:

• shouldelement.ariaValueNow be mapped tovalue ifaria-valuenow is not present, or should it be an AAM thing?
• This came up because ofrole=spinbutton, but I think it's equally appropriate if less frequent on otheraria-valuenow-supporting roles. Does that seem reasonable?

Test, Documentation and Implementation tracking

Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.

• "author MUST" tests:
• "user agent MUST" tests:
• Browser implementations (link to issue or commit):
  • WebKit:
  • Gecko:
  • Blink:
• ACT review?
• Does this need AT implementations?
• Related APG Issue/PR:
• MDN Issue/PR:

Preview |Diff