It appears that Google has changed the way the Search control is coded. Based on everyone's observations, this change probably occurred within the past few days. The Search control on the Google home page has a rich feature set and has characteristics of both an edit box and a combo box. The Google developers wanted to take advantage of the latest coding techniques in an effort to make the control more usable for all users including screen reader users. For those that aren't interested in the details, just note that if you used to use the browse mode navigation key E to get to this element, you will now need to use C instead. Since your focus is placed in this control when you open the page, this shouldn't be too big of a deal. You can still type your search string into the control and press Enter to perform the search. For those who are interested in the details, please read on.
Here is an excerpt from the HTML used to create the search element: <input title="Search" type="text" role="combobox" aria-haspopup="false" aria-autocomplete="both" maxlength="2048"> The input element has a title of Search and this helps Window-Eyes identify its name. The input element has a type of text which tells Window-Eyes it is an edit box. The input element now has an ARIA role of combobox. This ARIA role is the reason that the element is now being announced as a combo box. The role helps the screen reader identify that this element also has properties of a combo box. The input element currently has the aria-haspopup attribute set to false. This is because no text was entered in the search edit combo box at the time I reviewed the source code. Once you start typing, a drop down list of suggestions is displayed and aria-haspopup is set to true dynamically via JavaScript. The last attribute I will mention is the aria-autocomplete and it is set to both. The value both means that a list of choices appears and the currently selected suggestion also appears inline. As of today, Window-Eyes supports some ARIA attributes but not others. For example, Window-Eyes supports the ARIA role attribute and is why it announces combo box but it doesn't support aria-haspopup and explains why Window-Eyes does not announce when the drop down list of suggestions is displayed. The next version of Window-Eyes will certainly offer robust support for ARIA. This means that soon, you will be able to take full advantage of all of the functionality offered by these types of dynamic and complex widgets. Keep in mind that Internet Explorer and Firefox offer different levels of support for ARIA and use different implementations. This means you may get different results depending on the browser you are using. I hope you find this information helpful. Regards, Marc Interesting, i did this and the search box still shows up as a combo box. It doesn't bother me, now that i know what it is. On 8/21/2014 10:07 AM, George B wrote: > At the top of the page there is a link that says screen readers click here > to turn off google instant and it will not be a combo box any more > > -----Original Message----- > From: Edward [mailto:[email protected]] > Sent: Thursday, August 21, 2014 07:01 > To: [email protected] > Subject: FW: why is the page www.google.com <http://www.google.com> search > box now A combo box > > It started doing that for me yesterday as well. > Edward > > > -----Original Message----- > From: Casey [mailto:[email protected]] > Sent: Thursday, August 21, 2014 9:59 AM > To: [email protected] > Subject: why is the page www.google.com <http://www.google.com> search box > now A combo box > > hi I am posting this hear because I don't know if it is A window-eyes issue > or not. > But when I go to www.google.com <http://www.google.com> > And want to type something in the search box for it to search for something. > It is A combo box and not an edit box like it used to be. > Now I didn't change nothing in window-eyes that i know of. > So maybe the Google page changed something. > But if this was A window-eyes change how then do I re correct it and bring > it back the way it was? > > > -- > Casey If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
