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.

Sign up for GitHub

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

Jump to bottom

CSS text content is not output correctly (Chrome, IE 11) #297

Closed
JAWS-test opened this issue Sep 9, 2019 · 4 comments
Closed

CSS text content is not output correctly (Chrome, IE 11) #297

JAWS-test opened this issue Sep 9, 2019 · 4 comments
Labels
triaged Works in JAWS 2024

Comments

@JAWS-test
Copy link

JAWS-test commented Sep 9, 2019 •
edited
Loading

Summary

CSS text content is not output correctly (Chrome, IE 11)

  1. save as HTML file:
<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8">
		<title>CSS content</title>
		<style>
			.text::before {content:"before"}
			.text::after {content:"after"}
		</style>
	</head>
	<body>
		<p class=text>1</p>
		<a href=# class=text>2</a>
		<button class=text>3</button>
		<fieldset>
			<legend class=text>4</legend>
			<label class=text>5 <input></label>
			<label class=text for=6>6</label> <input id=6>
		</fieldset>
	</body>
</html>
  1. read with arrow keys
  2. navigate with Tab key

Expected result

  • Consistent output between browsers
  • CSS content is output

Actual result

  • IE 11: no output
  • Firefox: is output correctly
  • Chrome: only output sometimes:
    • button, legend: no output
    • label: Output only when reading with the arrow keys
    • text, link: correct output

Additional Information

JAWS version and build number

JAWS 2019.1907.42

Operating System and version

Windows 8
Windows 10

Browser and version:

Chrome 76.0.3809.100
Firefox 68.0.2
Internet Explorer 11.0.9600.19431
@JAWS-test JAWS-test mentioned this issue Feb 10, 2020
Open
@stevefaulkner
Copy link
Contributor

stevefaulkner commented Feb 10, 2020 •
edited
Loading

IE 11: no output

not expected as IE11 does not expose content in the acc tree.

also
test case

@carmacleod
Copy link

This is most likely due to Chrome bug 1130491.

@JAWS-test
Copy link
Author

@carmacleod Yes, that's my guess as well. What is strange, though, is that even with the link and button, only the text content and not the CSS pseudo-content is transmitted by Chrome. Nevertheless, JAWS outputs the link correctly, i.e. completely, and NVDA outputs the link and the button correctly. I.e. there are elements where the Chrome error has no effect on the screen reader output

@carmacleod
Copy link

Hmmm, yep, that's strange. :)
Possibly both JAWS and NVDA are trying to work around the Chrome issue, but JAWS missed the button use case.

@JAWS-test JAWS-test mentioned this issue Jan 19, 2021
Closed
@JAWS-test JAWS-test mentioned this issue Apr 21, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triaged Works in JAWS 2024
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@stevefaulkner @carmacleod @JAWS-test