Can you clarify what accessibility is doing today and what you'd like it to do?

For example, I'm pretty sure that when you use text-transform: upper, the transformed text is what appears in the accessibility tree, and overall that's the desired behavior.

I haven't checked the others but I thought we were generally exposing rendered text.

Currently we don't have a way to expose both the logical and rendered text separately on any platform. If there was a platform that did something interesting with access to both that'd be good motivation to do more.

When AX specify selection location based on AXInlineTextBox, text-tansform:upper specify wrong DOM offset.

AX: SSx
DOM: ßx

Selection painting and TextItertor also don't handle this case.

For text-overflow:ellipsis, AXInlineText holds characters before ellipsis. I'm not sure what happen when script specified offset after ellipsis.

Sorry, I'm not sure hyphen case, but AXInlineText split before and after hyphen. 

This issue is just a notice or hit my head during chatting with nektar@ when I visited NYC office.

Thanks, that makes sense. We can try to write some failing tests based on that. Leaving as available.