FreedomScientific / standards-support

Contains documentation for Vispero software support of Web standards
https://freedomscientific.github.io/standards-support/
GNU General Public License v3.0
110 stars 12 forks source link

Selecting text in a web page disconnects browser focus from JAWS focus #702

Open mitchellevan opened 1 year ago

mitchellevan commented 1 year ago

Summary

  1. Start JAWS, then start Google Chrome browser.
  2. Go to https://www.w3.org/WAI/tutorials/forms/labels/#associating-labels-explicitly
  3. Press CTRL + SHIFT + RIGHT ARROW to select the first word of the "Associating labels explicitly" heading.
  4. Press TAB once to move focus to the next tab-focusable element after the selection, in this case the "First name" field. JAWS announces the "First name" field as expected.
  5. Press TAB once to move focus to the next tab-focusable element after the "First name" field, in this case the "Subscribe to newsletter" checkbox.
  6. Press SPACE to select or activate the focused element.

Expected result

At step 5, visual focus should move to the "Subscribe to newsletter" checkbox, and JAWS should announce this checkbox.

At step 6, the checkbox should become checked.

Actual result

At step 5, visual focus moves to the checkbox, but JAWS repeats the announcement of the "First name" field.

At step 6, a space character becomes entered in the "First name" field, and visual focus jumps back to the "First name" field.

This problem is not specific to forms. Selecting text in web pages then moving focus causes numerous inconsistencies like this.

Additional Information

The problem does not occur in JAWS with Firefox.

The problem does not occur in NVDA with Chrome.

JAWS version and build number

JAWS 2023.2302.15

Operating System and version

Windows 10

Browser and version:

Chrome 110.0.5481.178

JAWS-test commented 1 year ago

Can confirm the problem.

No matter which text I select: when I navigate through the page with TAB afterwards, the input fields are output correctly, but other controls are not. This applies e.g. to checkboxes and links. For example, if I have the following on the page:

then the checkbox is output as the first input field and the link as the second input field

JAWS-test commented 1 year ago

I think this is a serious problem that should be fixed soon!

BrettLewisVispero commented 1 year ago

Imported into ADO as bug 17973