I was having trouble getting screen readers to consistently handle
<paper-toggle-button>. I've pared it down to a very simple example
<http://jsbin.com/codotuhuna/1/edit?html,output>.
I have a tiny custom element:
<polymer-element name="my-button" role="button" aria-pressed="false"
tabindex="0" noscript>
<template>
*<link rel="stylesheet" href="whatever">*
<button>Hello</button>
</template>
</polymer-element>
On Windows with NVDA, a <my-button> is read as a "Toggle button" (which is
correct). But a <my-button style="display: inline-block"> is read as
"Button, pressed."
Weirdly the issue reproduces under a lot of circumstances:
- The <link rel="stylesheet"> can point to anything: a stylesheet, a
blank page, a 404.
- The inline display value can be block, inline-block, flex, etc.
- Even if the <link>'d stylesheet and the inline style use the same
property value for display.
I've tested this exact example
<http://jsbin.com/codotuhuna/1/edit?html,output> with both NVDA and
Windows-Eyes, getting similar results in Chrome 41 and 42.
Note that JSBin only has Polymer 0.3.3, but I've tested locally with 0.5.4
as well.
Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/polymer-dev/ce30236d-351d-4477-bcf5-b86a5afa5f10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
