Re: additional sentence for 204

As requested in the 20 September HTML-WG teleconference:
http://www.w3.org/2012/09/20-html-wg-minutes.html

I have now captured the topic of this thread in bug 18952:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18952

Janina


Laura Carlson writes:
> Hi Maciej,
> 
> On Tue, Sep 18, 2012 at 11:57 AM, Maciej Stachowiak <mjs@apple.com> wrote:
> >
> > On Sep 18, 2012, at 9:28 AM, Laura Carlson <laura.lee.carlson@gmail.com> wrote:
> >
> >> Hi Janina,
> >>
> >> On Tue, Sep 18, 2012 at 9:36 AM, Janina Sajka <janina@rednote.net> wrote:
> >>
> >>> The intention of the language we're looking for is to allow software to
> >>> identify which hidden conten can be revealed to users at their request,
> >>> and which content cannot. If the id and href approach is insufficient
> >>> for that, then we would need a different approach. But, the approach
> >>> must be one that software can reliably use to distinguish between the
> >>> two use cases of hidden content.
> >>
> >> Here is an idea: add a discoverable attribute. @discoverable or @nothiddenfromAT
> >
> > Would it mean something different than aria-hidden=false?
> 
> It could natively mean: this is element is hidden but discoverable. So
> browsers would make it discoverable to users who wanted access to it.
> 
> Best Regards,
> Laura
> 
> -- 
> Laura L. Carlson

-- 

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, 21 September 2012 15:56:07 UTC