Closed VijayanRamachandran closed 3 years ago
I filed a bug with the extension here: https://bugs.chromium.org/p/chromium/issues/detail?id=1232133
But it looks like the extension is in maintenance mode and that users should use the built-in screen reader: https://support.google.com/chromebook/answer/7031755
@justinfagnani , @AndrewJakubowicz : Thanks for the help and fast response...
Hi @VijayanRamachandran,
I made a small patch to the extension that should improve the style situation. The extension still breaks parts of pages in certain difficult contexts - i.e. iframes. But from my testing it's far more reliable.
Otherwise echoing Justin that the extension is in maintenance mode. Let me know how the updated extension works and thank you for the issue report!
Hi,
We are facing a problem related to Accessibility topic for LitElement control in combination with Google Chrome Screen Reader Extension.
Below, a quick sample WebComponent ( abc-toggle.js ) created using LitElement and hosted in chrome.
abc-toggle.js
Until enabling chrome screen reader everything works as expected...
Google Chrome Screen Reader => https://chrome.google.com/webstore/detail/screen-reader/kgejglhpjiefppelpmljglcjbhoiplfn?hl=en
Before enabling chrome screen reader
The above WebComponent is displayed in HTML page as below
After enabling Chrome Screen Reader
For accessibility purpose after enabling the extension, the above WebComponent is displayed in HTML page as below
Without Chrome Screen Reader
DOM Structure
Styles applied to div tag inside #shadow-root
After enabling Chrome Screen Reader
DOM Structure
Styles applied to div tag inside #shadow-root
PS:
Hereby below, the entire WebComponent along with package.json ToogleButton.zip
I tried hosting the same in chrome Unsafe mode and there also same problem.
Can you please help us regarding this or if there is already some information related to scenario please let me know ?