removing label and cc after chat w/ chaok@

Chrome Version: 60.0.3112.101 (Official Build) (64-bit) (cohort: Stable)
OS: Win 10 Enterprise Version 1607 build 14393.1593
Screen reader: JAWS 18.0.4101, NVDA 2017.2

Hi, I am able to reproduce your issue using the following steps and configuration above. This will be sent to triage.

Open JAWS or NVDA 
Go to calendar.google.com
Press Create button to create new event, new event page opens

JAWS results:
Focus is in the Event Title, JAWS speaks “Event title Edit Untitled event Type in text. Loading complete” 
Use find-in-page for example pressing ctrl + f, which invokes the JAWS virtual find, and searching for Guest
Hear earcon, JAWS speaks “Guests Tab”  
Focus remains in the event box, though green highlight is not visible on screen. Focus never moves on to occurrence of Guest 
Use Virtual find again to search for next instance of Guest
Hear earcon, JAWS speaks “Guests Tab”, that is, keeps finding the first instance and never moves on to other instances of Guests 

NVDA results:
Focus is in the Event Title, NVDA speaks “Event title  edit selected Untitled event Loading complete” 
CTRL + F for in-browser search of “Guest”
Focus moves to in-browser search box 
All instances of Guest are highlighted, repeated CTRL + F will cycle through them all, but NVDA does not read any of the words. 

Bug reproducibility rate: 5/5 times 

Please note that Find Next for Jaws and Chrome is F3, not Ctrl+F.

I think that this is three separate bugs:
1. Jaws doesn't highlight the first occurrence of the word guests when you search for it using Jaws Find dialog.
2. Chrome Find in Page dialog doesn't announce search results both when using Jaws and NVDA. To use Chrome Find in Page with Jaws, first allow the next key to be past through to the application by pressing JawsKey+3 and then invoke the Find command using Ctrl+F.
3. When you send an invitation to guests by Saving the event, the dialog that says "Send invitations", doesn't get focus.

For number 1, please try turning on Virtual Cursor on first by pressing Numpad Plus or JawsKey+Semicolon when using laptop layout and then repeat the find.

First of three updates, now using JAWS 2018 Beta. Still using 62.0.3200.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 14393.1593


First, a summary of what behavior I see now with JAWS + Chrome. After that will be trying it in NVDA and JAWS + FireFox, and after that I will go through your steps listed here. 

F3 is now working for me, opening the native Chrome search dialog. This highlights all 4 instances of the word Guest on the page. As I press F3, it cycles through all 4 instances and focus follows because I am able to interact with them. For example, the 4th instance, see guest list, is a checkbox. Pressing enter after it is read will check and uncheck the box. I am assuming the focus is following because of this, not because I am able to see the focus indicator since that feature doesn't work in my setup. This appears to work as expected. 

Further tests reveals another problem. I press the back button to go back to calendar.google.com, then press the Create button again, then press F3 again to search again on the newly launched page. This time, I am not prompted to enter a new search term and it continues to use the word Guest from before. Pressing F3 does cycle through the 4 instances of the word Guest.

Reproducibility rate of the bug of retaining the word Guest: 5/5 times. 

I then kill the browser process and restart it. It still retains the word Guest. 

I reboot my computer. This time, when I press F3, the JAWS Find dialog appears with the word Guest pre-populated but I have the ability to change it. After I accept that dialog, F3 retains the word Guest again.  

Part two, digging into this find on page bug on other variants. 

In FireFox, when I go to the new event page in Google Calendar (in the same gmail account), it still retains the search term Guest. It's as if JAWS has tied the search term to the URL. On other pages, F3 opens the search dialog as expected. 

In NVDA + Chrome, I create a new event, press F3 to search for Guest using the Chrome search, and see the original bug behavior for this issue, which is that Guest is found but focus does not shift and the 4 instances of the word Guest are not read out. 

In NVDA + Firefox, I see the same behavior as NVDA + Chrome. I create a new event, press F3 to search, type in Guest, and none of the instances of Guest are read. 

This is now looking like two bugs: JAWS retaining the search term every time it sees the same URL and Google Calendar not allowing NVDA to read the find-in-page terms.        

Part three, testing your explicit next steps. 

"try turning on Virtual Cursor on first by pressing Numpad Plus or JawsKey+Semicolon when using laptop layout and then repeat the find."

JAWS + Chrome, I create a new event, press Numpad plus to turn on Virtual Cursor, then F3, all 4 instances of the word Guest are read and focus moves as expected. It then reproduces the same bug as earlier where I am unable to change the search terms. 

All of this said, we have just been focusing on the find-in-page feature. The bug originally was about after inviting a guest to a meeting, focus does not land on the dialog to send the invitation. Now to test that. 

JAWS + Chrome
When I create a new event, add a guest, and press Save, focus does land on the Send invitations? web-popup dialog. I then saw two behaviors: 

1. Tabbing around that dialog says "Send invitations? Dialog" each time I tab, not reading the name of the buttons. 

2. I closed and reopened this web-popup dialog by pressing Save again. This time, tabbing worked as expected, reading the following.  

Send invitations? dialog 
Close Button 
Send Button 
Don’t send Button

 

Calendar has released a new version. It's completely redesigned.