Form elements not exposed as form landmark role
Reported by
scottaoh...@gmail.com,
Mar 3 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0 Example URL: http://www.scottohara.me/testing/form/ Steps to reproduce the problem: 1. Go to the test page provided, or any website with a properly setup form on it. 2. Using JAWS, NVDA, VoiceOver, or TalkBack, attempt to navigate the page via landmarks or regions. 3. A form is only exposed as a landmark if using the ARIA role="form". Native form elements are not surfaced. What is the expected behavior? User agents should be treating native form elements as landmarks. What went wrong? Native forms are not being exposed as landmarks. Elements with a role of form *are* being exposed as landmarks. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? No Safari 11, IE11, Firefox ESR, Latest Edge Chrome version: 64.0.3282.186 (Official Build) (64-bit) Channel: stable OS Version: OS X 10.13.2 Flash Version: Shockwave Flash 28.0 r0
,
Mar 4 2018
,
Mar 4 2018
,
Mar 6 2018
Firefox bug on same issue has been fixed https://bugzilla.mozilla.org/show_bug.cgi?id=1442196
,
Mar 12 2018
I can confirm this on windows also.
,
Mar 12 2018
,
Mar 12 2018
,
Apr 5 2018
Adding a11y-secondary label since this is Blink related. If actually UI related, please indicate in a comment.
,
May 26 2018
For both <form></form> and <div role="form"></div> the AXSubrole is AXLandmarkForm which is correct IMO. For <div role="contentinfo"> the AXSubrole is AXLandmarkContentInfo which is identified as landmark in Voice Over. Isn't it the issue with Screen readers that don't show AXLandmarkForm as landmark? |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by scottaoh...@gmail.com
, Mar 3 2018