On 28/12/08 22:36, Alex Jurgensen wrote:
This is because VO
won't read items inside containers that use CSS "Padding: 4px;", or
greater.

Please link to an example which demonstrates this.

http://www.webdevout.net/test?0c&raw is a reduced test case. "Hello world" is in DIV with padding 4px, but VoiceOver reads it with current Safari, so you haven't provided enough information to reproduce the problem.

Also, on another note: Voiceover does not obey oral CSS, which is really
frustrating.

WebKit ignores speech and braille CSS as far as I know.

Is it frustrating for VoiceOver users? If so, why?

(The reason I ask is it's generally believed that screen reader users do not want web authors changing how different elements are pronounced from what the screen reader is used to. Witness all popular screen readers ignoring speech CSS.)

Out of interest, is what you're actually trying to do hide content from screen reader users?

Can someone file these bugs, plese, as I have no experiance filing bugs.

The first item might be a bug, if reproducible, but the second item is a feature request.

The hard bit about filing software tickets is providing the information required to understand the issue, and - in the case of bugs - the information required to reproduce the problem. See:

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

If you can communicate those things to a person on this list, then you can communicate them via a bug tracker. It's purely a matter of becoming familiar with any local conventions and the bug tracker for the software in question. For WebKit, that information can be found at:

http://webkit.org/quality/reporting.html

http://webkit.org/quality/bugwriting.html

In essence a bug tracker ticket is little more than a well-written email with some additional form fields.

Conversely, if you can't communicate those things to a person on this list, then they wouldn't be able to file an effective ticket for you on your behalf.

--
Benjamin Hawkes-Lewis

Reply via email to