Required fields are not read as being required without aria-required
Reported by
willstei...@gmail.com,
Oct 12 2016
|
||||
Issue descriptionChrome Version : 53.0.2785.143 OS Version: OS X 10.11.6 URLs (if applicable): http://plnkr.co/edit/QXNlfaNUP5TGNB227i62 What steps will reproduce the problem? 1. Enable ChromeVox 2. Click the run button in the Plunkr 3. Click in one of the input fields to have ChromeVox read the field and you will not hear the field read as required. What is the expected result? Required input fields marked with the required attribute should be read as required. What happens instead of that? The field is not read as being required UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
,
Nov 8 2016
For me, neither of these input fields are being read out as 'required' by ChromeVox on Chrome 54.0.2840.71. I'm not sure if this is working-as-intended, since when you inspect them in dev tools, neither of them actually have aria-required="true" in their HTML. This is what I get for both Textfields, respectively: <input type="text" required="" placeholder="Should have aria-required"> <input type="text" ng-required="true" placeholder="Should have aria-required" required="required"> Adding aria-required="true" for either of those input fields does make ChromeVox tell you they're required. Again, not sure if this is WAI, sending to other components where hopefully someone else knows more.
,
Nov 8 2016
,
Dec 5 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by kkaluri@chromium.org
, Oct 14 2016Labels: Needs-Feedback