RE: Finalizing an Issue-204 CP

Cynthia Shelly, Thu, 19 Apr 2012 23:25:41 +0000:
> OK, I think I'm close.  
> 
http://www.w3.org/html/wg/wiki/Correct_Hidden_Attribute_Section_v2#Accessibility_API_mappings
> 
> 1) rewrote summary to talk more about @hidden being simpler than CSS, 
> rather than @aria-describedby being simpler than something else

I would like to have more clarity here. Firstly, I don't consider 
@hidden simpler than CSS:

* What if one does p[hidden]{display:block;visibility:visible} ?
  Do AT users then get to see it too, or do they not? I suppose they
  don't. And so one must use JavaScript to interactively show it to
  AT users.

* For contrast, if one does p.hidden{display:block;visibility:visible}
  (and the element does not have the @hidden attribute), then there is
  no doubt that all audiences will see it. This seems simpler

OTOH: What "complicates" the matter is that *ARIA* says that, in the 
case of p{display:none}, then one MUST *also* use <p 
aria-hidden="true"> in the HTML:

   ]] Authors MUST set aria-hidden="true" on content that is not
      displayed, regardless of the mechanism used to hide it. [[
      http://www.w3.org/TR/wai-aria/complete#aria-hidden

So, if @hidden simplifies something, then it isn't, in my opinion, 
related to CSS but to ARIA: It appears simpler to just operate with a 
single @hidden attribute, compared with the alternative - which is to 
use aria-hidden="true" in combination with another hiding method - such 
as CSS.

(Btw, when I look at that CP now, then it doesn't even mention 
aria-hidden="true".)

Could you change this - along the above lines - so that it says that 
@hidden is simpler than the alternative - which - to put it as brief as 
possible - is  
    [aria-hidden="true"]{display:none}
-- 
Leif H Silli

Received on Friday, 20 April 2012 09:07:55 UTC