W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2012

RE: additional sentence for 204

From: David MacDonald <david100@sympatico.ca>
Date: Fri, 14 Sep 2012 13:34:44 -0400
Message-ID: <BLU0-SMTP83110078C7EB00AD68BD3DFE900@phx.gbl>
To: "'Leif Halvard Silli'" <xn--mlform-iua@xn--mlform-iua.no>
CC: "'Janina Sajka'" <janina@rednote.net>, "'James Craig'" <jcraig@apple.com>, "'Cynthia Shelly'" <cyns@microsoft.com>, "'HTML Accessibility Task Force'" <public-html-a11y@w3.org>, "'Ted O'Connor'" <eoconnor@apple.com>
Hi Leif

... it's a follow up to a discussion we had on the call... no time to get
into it during my work day... but parts of it should be in the thread...

Cheers
David MacDonald

CanAdapt Solutions Inc.
  "Enabling the Web"
www.Can-Adapt.com


-----Original Message-----
From: Leif Halvard Silli [mailto:xn--mlform-iua@målform.no] 
Sent: September-14-12 7:27 AM
To: David MacDonald
Cc: 'Janina Sajka'; 'James Craig'; 'Cynthia Shelly'; 'HTML Accessibility
Task Force'; 'Ted O'Connor'
Subject: RE: additional sentence for 204

Hi David,

May be I have misunderstood something very fundamental her, but to include
@usemap on an <img> is not a special signal to AT. It is an attribute that
changes the <img> from non-interactive to interactive. 

Leif H Silli

David MacDonald, Fri, 14 Sep 2012 00:41:21 -0400:
> I very much support this approach to exposing hidden content to 
> assistive technologies ... an id reference (or hash tag reference) to 
> the hidden content indicates an intent by the author to expose it to 
> Assistive Technology or other user agents...
> 
> Cheers
> David MacDonald
> 
> CanAdapt Solutions Inc.
>   "Enabling the Web"
> www.Can-Adapt.com
> 
> 
> -----Original Message-----
> From: Janina Sajka [mailto:janina@rednote.net]
> Sent: September-13-12 8:10 PM
> To: James Craig
> Cc: Cynthia Shelly; HTML Accessibility Task Force; Ted O'Connor
> Subject: Re: additional sentence for 204
> 
> Works for me, James. Much cleaner and yet clearly indicates that there 
> are two kinds of use cases covered.
> 
> Janina
> 
> James Craig writes:
>> How about this take?
>> 
>> Note: Only hidden="" elements that are referenced indirectly by a 
>> unique
> identifier (ID) reference or valid hash-name reference may have their 
> structure and content exposed upon user request. Authors desiring to 
> prevent user-initiated viewing of hidden="" elements should remove 
> identifier (ID) or hash-name references to the element.
>> 
>> 
>> On Sep 13, 2012, at 2:51 PM, James Craig <jcraig@apple.com> wrote:
>> 
>>> Janina,
>>> 
>>> I don't have substantive objections with either of these, and only 
>>> minor
> editorial objections to tense and style.
>>> 
>>> James
>>> 
>>> 
>>> Cynthia's
>>>>> Note: Authors have control over whether elements with the @hidden
> attribute will be exposed in this manner.  Only elements that are is 
> referenced indirectly by a unique identifier (ID) reference or valid 
> hash-name reference will be exposed.  If an author does not wish to 
> have a @hidden element exposed, he may achieve this by not referencing the
element.
>>> 
>>> Janina's:
>>> 
>>>> Author  control, as opposed to user control  over whether elements 
>>>> with
> the @hidden attribute may be exposed to users will be delineated in 
> this manner.  Only elements that are referenced indirectly by a unique 
> identifier
> (ID) reference or valid hash-name reference may be exposed at user
request.
> An author desiring to keep a @hidden element hidden from any and all 
> user initiated viewing scenarios may achieve this by simply not 
> referencing the element.
>>> 
>>> 
> 
> --
> 
> Janina Sajka,	Phone:	+1.443.300.2200
> 			sip:janina@asterisk.rednote.net
> 		Email:	janina@rednote.net
> 
> The Linux Foundation
> Chair, Open Accessibility:	http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair,	Protocols & Formats	http://www.w3.org/wai/pf
> 	Indie UI			http://www.w3.org/WAI/IndieUI/
> 
> 
> 
> 
Received on Friday, 14 September 2012 17:35:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 14 September 2012 17:35:25 GMT