Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect output for quick navigation to list entries with I #327

Open
JAWS-test opened this issue Oct 5, 2019 · 4 comments
Open

Incorrect output for quick navigation to list entries with I #327

JAWS-test opened this issue Oct 5, 2019 · 4 comments

Comments

@JAWS-test
Copy link

Summary

Incorrect output for quick navigation to list entries with I

  1. Go to https://codepen.io/jaws-test/pen/RwwwaQW
  2. Navigate with I to the list entries

Expected result

  • Consistent output between browsers
  • Complete output of the list entries or, in the case of very long list entries, note that the list entry was not output completely.
  • Consistent output independent of li or role=listitem.

Actual result

  • No consistent output between browsers
  • No complete output of the list entries (output aborted as soon as a certain block-forming HTML element or element with certain roles is contained)
  • Chrome: Output depends on li or role=listitem (e.g. for links and images)
    • li: Abort output before element
    • listitem: Abort output after element

Related: #317

Additional Information

JAWS version and build number

JAWS 2019.1907.42

Operating System and version

Windows 8

Browser and version:

Chrome 76.0.3809.100
Firefox 68.0.2
Internet Explorer 11.0.9600.19431

@scottaohara
Copy link
Contributor

scottaohara commented May 13, 2020

@BenKeyFSI, talked about this one with steve and thought maybe you might take a look to see if this is an issue, or potentially expected behavior (JAWS not automatically reading all content of a list item when content is mixed of inline and block content / or mixed with text nodes vs other inline content with properties exposed to the accessibility tree).

@JAWS-test
Copy link
Author

The problem also occurs if the list entry has no block content and therefore no inline and block elements are mixed

@scottaohara
Copy link
Contributor

yup, sorry, corrected my summary.

@JAWS-test
Copy link
Author

I have retested it with Chrome and JAWS 2024 - the problems remain unchanged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants