Issue metadata
Sign in to add a comment
|
Adda patch for chrome electron 61
Reported by
irfa...@gmail.com,
Aug 2
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: Here is a test page to reproduce the issue. http://ets-research.org/ia11ylab/CATS/acc_demos/ibis_rb_test/test.html Problem: “clickable” announcements. ·Adding a “role” of “presentation” to parent/grandparent nodes that have a click/ng-click handler but no role did, in fact, fix the problem in regular Chrome, but not in 61. ·Addressing propagation issues did not fix the problem in 61. Please add a patch in electron 61 to fix this, I consider this to be a showstopper to implementing Electron 61. We can’t have confusing “clickable” announcements in an assessment Problem: No announcement of aria-posinset and aria-setsize in JAWS browse mode What is the expected behavior? What went wrong? Our IT department is reporting that in Chrome Electron 61, announcement of the aria-setsize and aria-posinset attributes (with role="radio") is not announced in JAWS 18 browse mode. It is announced only in forms mode. They indicated that the announcement was previously made in both browse and forms mode in Electron 51. This problem is preventing them from upgrading our test delivery system to Electron 61, as announcement of the number of the option and the total number of options is essential for our test takers, and any changes to the behavior will necessitate changing all test documentation and help screens. We need to complete the Electron 61 upgrade within the next week or so, so we would like to have this expedited if you could fix it in Chrome Electron 61. We have further investigated it and have concluded that it is a bug in Chrome that does not occur in the latest chrome Version 68.0.3440.84 (Official Build) (64-bit). The issue is apparent regardless of JAWS version (tested in 17/18/2018). The issue appears to stem from differences in the accessibility tree representation of the grouping element and its children, between chrome version 61 (the ETS browser) and the later version of chrome in general release. We attempted to work around it by using aria-owns to provide an explicit relationship between the grouping element and the radio buttons, in the hope that this would cause an expression of the setsize/posinset, it did not. We also modified aspects of the coding in an attempt to expose the setsize/posinset, to no avail. Why does it work in ‘forms’ mode in the ETS browser but not the virtual cursor mode? In forms mode JAWS interacts directly with the interactive controls in the UI, rather than with a representation of the UI created by JAWS, from the information provided in the accessibility tree. This direct interaction provides better access to the available states and properties of the radio buttons. Here is a test page to reproduce the issue. http://ets-research.org/ia11ylab/CATS/acc_demos/ibis_rb_test/test.html Problem: “clickable” announcements. ·Adding a “role” of “presentation” to parent/grandparent nodes that have a click/ng-click handler but no role did, in fact, fix the problem in regular Chrome, but not in 61. ·Addressing propagation issues did not fix the problem in 61. Please add a patch in electron 61 to fix this, I consider this to be a showstopper to implementing Electron 61. We can’t have confusing “clickable” announcements in an assessment Problem: No announcement of aria-posinset and aria-setsize in JAWS browse mode Please add a patch in Chrome electron 61 to fix this issue. Did this work before? Yes Electron 51 Does this work in other browsers? N/A Chrome version: 67.0.3396.99 Channel: n/a OS Version: 10 Flash Version:
,
Aug 3
Thanks for filing the issue! This issue seems to be related to chrome electron, which is out of scope for TE end, hence adding TE-NeedsTriageHelp for further investigation on the issue. Thanks!
,
Aug 3
It sounds that accessibility folks would be interested in this issue.
,
Aug 6
The correct place for filing Electron issues is https://github.com/electron/electron/issues .
,
Aug 6
Chromium does not own the Electron project. We have no ability to change anything in Electron. I'm sorry, but we can't help you here.
,
Aug 6
You do not need to make changes in Electron project. Electron is using google chrome 61 version and you need to make the changes in chrome 61.
,
Aug 6
Chrome 61 is nearly a year old. We will not be changing it. There is no such thing as "Chrome Electron". Electron is not a Chrome project or a Google project. I am happy to help you connect with the Electron folks I know to figure out the best way forward, but this is not an issue we can handle directly in Chrome.
,
Aug 6
Hello. I work with irfa...@gmail.com. To elaborate, our developers have built an Electron app that uses Chrome 61 as the browser. It is being used as a secure browser in a standardized testing environment, and our strict build and testing schedule prohibits us from upgrading the Electron app to a newer version of Chrome at this time. We are requesting a patch to Chrome 61 to address the issues. Without the fixes, a student using assistive technology, such as a screen reader and a refreshable Braille device, will likely be confused by the test options and form controls and may be unable to answer the questions. These features were working correctly in versions of Chrome prior to 61 and have been since been fixed in later versions of Chrome. Thank you.
,
Aug 6
Mac TL here. #8: No. We will not & cannot update Chrome 61 further - in fact, we do not have the technical capability to ship updates to branches older than stable at all. We do not support any release earlier than the current stable, which is M68. Your options are: 1) Fix the issue yourself. 2) Live with the issue. Sorry.
,
Aug 6
Mac TL, you are rude. It shows that your testing team sucks and is not enough when release new version. How come things are broken in 61 which were working in 51? Do you know that everything is working fine in M68? Or do you want us to work on M68 as well if things are broken with it?
,
Aug 6
,
Aug 6
#10: We don't have the ability to provide updates or fixes to Chrome 61. I'm sorry to hear that your software is pinned to 61. When we fix bugs in Chrome we usually do so by fixing them in subsequent major releases (and, if they are severe, merging fixes to the current stable), so any strategy based on pinning yourselves to a specific Chrome version older than stable will inherently lead to you experiencing bugs that were only found and fixed in later releases. We do not backport fixes to branches older than the current stable branch. This has been Chrome's practice - and indeed the practice of all major browsers - for some years now. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Aug 3