- From: Sailesh Panchang <spanchang02@yahoo.com>
- Date: Tue, 24 Sep 2013 18:19:52 -0700 (PDT)
- To: WCAG <w3c-wai-gl@w3.org>, "w3c-wai-pf@w3.org Formats" <w3c-wai-pf@w3.org>
Hello, 1. On tabbing to the button neither NVDA nor JAWS (in FF or IE) read the aria-labelledby attribute when it refers to its own "value" attribute. Both screen readers read the "value" text. The aria-label works best in this situation based on current AT support. <h3 id="policy2">Whole Life Policy 1</h3> <input type="button" id="sbtn2" value="Select Policy" aria-labelledby="sbtn2 policy2" /> JAWS does read aria-labelledby when one uses quick-nav to move to the button. === Question: AT should expose the aria-labelledby i.e. the h3 text and the value attribute of the button in the above example, right? 2. When the aria-labelledby for a BUTTON element refers to visible button text within , only JAWS reads it. NVDA only reads visible button text. <h3 id="policy1">Term Policy 1</h3> <button id="sbtn1" aria-labelledby="sbtn1 policy1">Select Policy</button> In this case I suppose this will be considered an NVDA bug, right? Thanks, Sailesh Panchang
Received on Wednesday, 25 September 2013 01:20:20 UTC