Having done some further reading, according to the spec (http://www.w3.org/TR/wai-aria/roles#textalternativecomputation point 3) JAWS is actually doing the right thing here. Font awesome claims to be screen reader accessible, but it appears this accessibility is based on screen readers not rendering text ::pseudo elements, which practically has been true for a while but isn't what the spec dictates (and isn't what JAWS is now doing).
Adding role=presentation or aria=hidden (or both) might be the only way to consistently alleviate the issue (see http://john.foliot.ca/aria-hidden/) for a discussion of which of those would be appropriate.
Having done some further reading, according to the spec (http:// www.w3. org/TR/ wai-aria/ roles#textalter nativecomputati on point 3) JAWS is actually doing the right thing here. Font awesome claims to be screen reader accessible, but it appears this accessibility is based on screen readers not rendering text ::pseudo elements, which practically has been true for a while but isn't what the spec dictates (and isn't what JAWS is now doing).
Adding role=presentation or aria=hidden (or both) might be the only way to consistently alleviate the issue (see http:// john.foliot. ca/aria- hidden/) for a discussion of which of those would be appropriate.