Comment 1 by jteh on 2014-05-23 00:02
Confirmed. Test case:

<style>
div:before {
 content: "before ";
}
</style>
<div>div</div>

As usual in IE, we'll have to process the CSS ourselves, since IE doesn't bother to expose this via accessibility APIs. We can get this using window.getComputedStyle(element, ":pseudo"), where pseudo is "before" or "after". It'll be pretty difficult to support values other than a string. You can also have counters, attribute values, etc. and I'm not sure it's worth the effort to support these, at least initially.

More info about the content property

Comment 2 by jteh on 2014-05-23 00:02
Changes:
Changed title from "Nvda and css content properity." to "MSHTML: Support for CSS content property"

@jcsteh @khsbory Could you please clarify the versions of Internet Explorer the reported issues applies to? In case this has been fixed by any chance in Internet Explorer 10/11, then we may safely close this ticket. Otherwise, we may need to mark this as P4.

STR:

1. Paste the test case above into an empty HTML file.
2. Open it in Internet Explorer.
3. Read the document in browse mode.
   • Expected: "before div"
   • Actual: "div"

Still persists in Internet Explorer Version: 11.0.16251.0, Update Versions: 11.0.41(KB4014661)

Still reproducible in NVDA 2019.1.1. I wonder if someone can test in the IE mode of Edge chromium if this issue occurs there as well?

If I"m correct, this requires a change both in the MSHTML virtual buffer and on the MSHTML object level.

While I know that IE is still used in some corporate environments, IE is considered legacy by Microsoft. Given this is an issue that requires a lot of effort to implement, I'm tempted to close this as a wont fix. We can always reopen and remove the label if someone provides a pr.

@LeonarddeR I have no interest in this particular issue, however my impression is that when issue is closed the PR for it wouldn't be accepted. Leaving it open as a P4 seems more reasonable.

Support for IE ended completely in 2022 and is being automatically removed from machines that still have it after an Edge update in February 2023. Even though MSHTML will still be active until 2029 especially for backwards compatibility in IE mode in Edge, I don't expect any accessibility updates to IE or to IE mode in Edge. Closing as abandoned.