Re: Response to: ChangeProposals/DeprecateLongdesc

Silvia Pfeiffer, Tue, 23 Aug 2011 09:34:44 +1000:
> Actually, something that just dawned on me: we have to fix
> aria-describedby no matter whether it is a valid replacement for
> @longdesc. Since browser APIs all deal with @aria-describedby
> differently, it's obviously underspecified and for that reason not
> quite as useful as it could be. Is that being worked on? Should I
> provide input somewhere?

I only have a cliche answer: If you see a need and perhaps a solution, 
then should file a bug ... It seems to me that a bug to specify how 
@hidden interacts with ARIA would at least be good to file - against 
HTMl5. Else, the are so many ARIA related specs ... so for the 
interoperatbilitiy feature you have in ind mind, it perhaps requires 
more thinking to find the right place to file the bug ...

For that matter: even a @longdesc could point to a @hidden section - 
except that there would perhaps be no result ... 

Leif H Silli


> Cheers,
> Silvia.
> 
> On Tue, Aug 23, 2011 at 9:25 AM, Leif Halvard Silli
> <xn--mlform-iua@xn--mlform-iua.no> wrote:
>> Silvia Pfeiffer, Tue, 23 Aug 2011 09:06:41 +1000:
>>  [ … snip … ]
>>> Also, maybe we should propose a change to the HTML spec:
>>> "The hidden attribute is a boolean attribute. When specified on an
>>> element, it indicates that the element is not yet, or is no longer,
>>> relevant. User agents should not render elements that have the hidden
>>> attribute specified."
>>> 
>>> should become
>>> 
>>> "The hidden attribute is a boolean attribute. When specified on an
>>> element, it indicates that the element is not yet, or is no longer,
>>> *visually* relevant. User agents should not render elements that have
>>> the hidden attribute specified."
>> 
>> This does not sound smart.
>> 
>>> Also, the further text would need a change, too - in particular this
>>> cannot stay as is:
>>> "if something is marked hidden, it is hidden from all presentations,
>>> including, for instance, screen readers."
>>> Something would need to be added about hiding it from screen readers
>>> in their normal page progression, which is indeed necessary, but not
>>> hiding it from @aria-describedby.
>> 
>> This sounds smarter. One coudl simply add that ARIA is not bound by
>> this rule.
>> 
>> Btw - and from another POV: while @hidden currently hides the element
>> (or as the spec says "not yet" sees it as relevant), it doesn't follow
>> that, when made "un-hidden", it becomes un-hidden for *all*
>> presentations - does it?
>> 
>>> Maybe @aria-describedby would create
>>> a temporally restricted unhiding and focus for tabbing, similar to how
>>> modal dialogs work.
>> 
>> +1
>> --
>> Leif H Silli
>

Received on Monday, 22 August 2011 23:49:20 UTC