Hmm.. well the reason we avoid setting a "top" value for this is
because when an item within that hidden element gains focus, the page
will scroll to the element. In other words, if we used a negative top
position, the page would jump to top when that element is focused.
It may seem odd to give focus to an element that's visually hidden,
but we sometimes do it with form elements, and provide a focused
appearance on a related control on the visible portion of the page.
Maggie actually ran into this issue while developing this technique,
which is why it's pretty fresh in my mind:
http://www.filamentgroup.com/lab/accessible_custom_designed_checkbox_radio_button_inputs_styled_css_jquery/Maybe we should experiment with different hiding methods for this
class, like perhaps "width: 0; height: 0; overflow: hidden;" (though I
think I read somewhere that you need at least 1px dimension for some
AT software to read it..).
Another option is to suggest that this particular person just
overrides the .ui-helper-hidden-accessible rules with something that
works for their particular case, since our styles do work for most
situations.
Thoughts?
