PaymentHandler not reading text in Order Summary (etc.) dialogs |
||||||
Issue descriptionGoogle Chrome 68.0.3400.0 (Official Build) canary (64-bit) (cohort: Clang-64) Windows 10 Enterprise Version 1607 Large Monitor set in Windows Dislay Scaling settings to be 200% magnified JAWS 2018.1804.26 64-bit English NVDA 2018.1.1 ZoomText 2018.1804.37 Private Beta ___ Google Chrome OS 68.0.3400.0 (Official Build) canary (64-bit) Firmware Version Google_Samus.6300.276.0 ___ macOS High Sierra version 10.13.4 with VoiceOver 8 (562.18.4) Google Chrome 68.0.3400.0 (Official Build) canary (64-bit) ___ Android 8.1.0 Pixel Phone (1st edition) Talkback Beta 6.2.0.188490928 Google Chrome 68.0.3400.0 (Official Build) canary (32-bit) ___ No Linux hardware available to test (should be same as Windows) ___ Enable flags: chrome://flags/#enable-experimental-web-platform-features chrome://flags/#service-worker-payment-apps Open https://rsolomakhin.github.io/pr/apps/basic-card/. Tap “Install”. VERIFY: The page prints: - Scope: https://rsolomakhin.github.io/pr/apps/basic-card/ - Method: basic-card - Capabilities: - Network: visa - Type: credit Tap “Test it out”. Tap “Buy”. VERIFY: The default payment method has an icon and the following text: - Test Payment Handler - https://rsolomakhin.gtihub.io/ Tap “Pay”. VERIFY: The page contains: - “methodName”: “basic-card”, - “cardNumber”: “4111111111111111” - “cardSecurityCode”: “123” Cleanup: Navigate back. Tap “Uninstall”. _____ JAWS and NVDA on Windows: FAIL Text inside the dialog is not read at all. Note that the screen reader focus highlight does not move to the words in these sections while the keyboard focus does move. I am able to press space or enter to open more information even though the screen reader isn't saying anything. Buttons are read as expected. Mac + Voiceover FAIL Text and section names are not read, VoiceOver only says "You are currently on a text element." when focus is on the order information. Buttons such as Pay and Cancel are both read and word as expected. TalkBack on Android: PASS but not ideal All text in dialogs is read in both basic and Bob versions. Buttons are read as expected. After expanding the Order summary text, TalkBack says "double tap to activate" at the end even though double tapping does nothing. It also says "double tab to activate" after each text section. This should perhaps be replaced with clearer text like "double tab to expand".
,
Jun 2 2018
When this bug is fixed, please verify that the focus is no longer split between the screen reader and the keyboard like shown in this video: https://drive.google.com/file/d/104UH-0xvfPyvae4_ZheszHeYoIR0uVUV/view
,
Jun 19 2018
,
Jun 20 2018
Friendly ping - any further updates?
,
Jun 20 2018
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone. All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 20 2018
I think Anthony landed something here.
,
Jun 20 2018
Ah yes, I landed a patch against Issue 848859 . Laura, is it possible for you to validate the fix on Canary (or any version that includes change #564911 for that matter)? Thanks!
,
Jun 25 2018
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone. All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 26 2018
Ping lpalmaro@
,
Jun 28 2018
I'm traveling so only have my Mac and Chromebook. Just tested on Mac and this looks better to me now. Thank you!
,
Jun 28 2018
Thanks! OK to mark as fixed?
,
Jul 18
Is this fixed on Android side also? |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by leberly@chromium.org
, Jun 2 2018