RE: Review of Section 7.1 by ARIA working group in PF

Maciej Stachowiak wrote:
> 
> 
> Are any of these different from the implied automatic consequences of
> hidden elements having display: none style?
> 
>  - Maciej

Hi Maciej,

As I have already noted (asked?) elsewhere, with the proposed changes to
@hidden, and its ability to now expose some rich content to ARIA, would the
default Browser CSS will also likely have to be re-worked, as currently all
screen readers respect {display:none} as content that is not there, and thus
not read aloud. 

I had previously asked
(https://www.w3.org/Bugs/Public/show_bug.cgi?id=19277) if instead it would
thus now be closer to {visibility:hidden; height:0; width:0;
overflow:hidden} (conceptually a "black-hole" that could still contain
content).

I have only heard from Henri, who if I am to understand his response, also
notes that the default CSS rendering rules (with regard to the visual
viewport versus outside of that viewport) would also need to be redefined
with regard to ARIA mapping/exposure. 

Finally, his suggestion of: 

	"<div hidden style="display: block !important;">This should render
in a CSS view port.</div>" 

...would also remove the restrictions that are currently staking up against
this technique: if it is rendered on screen, then all of the previously
disabled 'focusable' elements could now take focus.

I will note in passing here that this is also significantly related to my
current Formal Objection to Issue 204 (the tab focusable content problem),
and if we can get this resolved in a timely manner, it would allow me to
withdraw my Formal Objection in advance of TPAC. I am mindful however of not
getting that cart before the horse, and so any effort that the Chairs can
apply to a speedy resolution here will also unblock other efforts elsewhere.

JF

Received on Saturday, 13 October 2012 01:30:57 UTC