CSS-generated-text bugs

Hey all.

Given that this group was talking about accessibility issues of
CSS-generated-text....

Issues not tied to accessibility APIs, but which are related to
accessibility (e.g. ability to search for generated content):

1. https://bugzilla.mozilla.org/show_bug.cgi?id=12460
   Cannot select or edit or search generated content and alt text
   (This one is really old. <insert sigh here>)

2. https://code.google.com/p/chromium/issues/detail?id=383920
   Find function (Ctrl+F) is ignoring CSS generated content

3. https://code.google.com/p/chromium/issues/detail?id=431588
   CSS-generated text content is not selectable

4. https://bugs.webkit.org/show_bug.cgi?id=138545
   Find in page fails to find css-generated content

5. https://bugs.webkit.org/show_bug.cgi?id=138546
   CSS-generated text content is not selectable

Accessibility-API issues:

6. https://bugzilla.mozilla.org/show_bug.cgi?id=1096071
   atk_text_get_text_at_offset is broken for CSS-generated content
   (I'm guessing it's also broken for IA2.)

7. https://bugs.webkit.org/show_bug.cgi?id=137672
   AX: [ATK] atk_text_get_text_at_offset is broken for elements with
   CSS-generated text content
   (Does VoiceOver have any need to get text for a given boundary type
   like the current line? And if so, does this work as expected?)

--joanie, who is really starting to dislike CSS-generated content. ;)

Received on Sunday, 9 November 2014 20:13:20 UTC