Re: Request for PFWG WAI review of summary for tabular data

Hi Janina,

I noticed a broken link in my email [1] to you.

The correct link for "Steps to Implement PFWG Recommendations"  is:

http://esw.w3.org/topic/HTML/SummaryForTABLE#head-14806556967e604b22000d3c09ae7dd5a0ac2e23

Best Regards,
Laura

[1] http://lists.w3.org/Archives/Public/public-html/2009May/0033.html

On Wed, May 20, 2009 at 12:58 PM, Laura Carlson
<laura.lee.carlson@gmail.com> wrote:

> Hi Janina,
>
> From Sam Ruby:
>
>> We specifically need people to put forward suggestions for @profile
>> and @summary. If no such proposals are produced, such issues will be
>> summarily closed. [1]
>
> My HTML WG Action 111 [2] on the summary issue is due May 29. Do you
> think it would be possible for PF to respond to my message [3] by
> then?
>
> [1] http://lists.w3.org/Archives/Public/public-html/2009May/0161.html
> [2] http://www.w3.org/html/wg/tracker/actions/111
> [3] http://lists.w3.org/Archives/Public/public-html/2009May/0033.html
>
> Thank you very much.
>
> Best Regards,
> Laura
>
> On Thu, May 7, 2009 at 7:18 PM, Janina Sajka <janina@rednote.net> wrote:
>> HTML Caucus:
>>
>> I'm forwarding the following from Laura for our consideration re
>> @summary.
>>
>> Laura Carlson writes:
>>> Hi Janina,
>>>
>>> The HTML working group has continued debating the table summary issue.
>>> To move the issue toward resolution, PFWG's comments and guidance on
>>> the following would be greatly appreciated.
>>>
>>> On August 6 2008, Al Gilman wrote:
>>>
>>> > Here is a summary of how PFWG sees the situation as regards
>>> > @summary on <table> in HTML:
>>> >
>>> > 1. @summary should stay
>>> > 2. It provides a needed service
>>> > 3. element content providing this info, *if linked by markup to the
>>> > table* offers growth to even better practice
>>> > 4. Don't have the linking markup yet; is a developmental item
>>> > 5. evolution not revolution says: keep @summary at least until
>>> > alternatives are deployed and stable
>>> >
>>> > There are lots of details to be worked out, and we would like
>>> > to continue discussing those with you. But the above summarizes
>>> > how we see and approach the matter.
>>> http://lists.w3.org/Archives/Public/public-html/2008Aug/0213.html
>>>
>>> 1. Does PFWG continue to see the situation as Al Gilman described in
>>> his August 6, 2008 message to the HTML working group?
>>>
>>> 2. Does the "Steps to Implement PFWG Recommendations" approach
>>> continue to meet WAI's needs? In particular, does PFWG recommend
>>> adding a <summary> element or equivalent to HTML5 and removing
>>> @summary once its replacement is accessibility supported?
>>> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-a824aba06e202785923a97575ed943a8ae355135
>>>
>>> 3. Do you have any comments, suggestions, or guidance on the short
>>> term, mid-term, and long term solutions? Are they in line with WAI's
>>> needs?
>>> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-ce93d0f2d659cc23cd00b5c5353a7a29576a3ceb
>>>
>>> 4. Would PF have any objections to allowing a <summary> element or
>>> equivalent to have an "open" display attribute similar to the one on
>>> the <details> element [1] which would allow it to be available not
>>> only for the blind/non-visual use case but for a sighted use case?
>>> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-4fd8f8462033b251ea8328b598d9482140ff3f1f
>>>
>>> 5. To help fulfill step one of the "Steps to Implement PFWG
>>> Recommendations" members of HTML working group composed spec language.
>>> Several versions of RFC 2119 compatible @summary definition text for
>>> HTML 5 have been drafted and are in the Wiki.
>>> http://esw.w3.org/topic/HTML/SummaryForTABLE/SummarySpecification
>>> We are trying to eliminate ones that won't work for one reason or
>>> another [2].  Are any of the versions not acceptable? Which would best
>>> fulfill the needed accessibility functionality? Are there any
>>> improvements that PFWG would suggest? Additional options have also
>>> been discussed on public-html [3].
>>>
>>> The latest published HTML draft does not yet incorporate a summary
>>> attribute or element.
>>> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-8ee232b5eb01c32d41feddf1ce0e9129871331e0
>>>
>>> For reference, the "Mechanism to Summarize a Table" issue is detailed at:
>>> http://esw.w3.org/topic/HTML/SummaryForTABLE
>>>
>>> Thank you. Looking forward to your input.
>>>
>>> Best Regards,
>>> Laura
>>> [1] http://www.w3.org/TR/html5/interactive-elements.html#the-details-element
>>> [2] http://lists.w3.org/Archives/Public/public-html/2009Mar/0084.html
>>> [3]  http://esw.w3.org/topic/HTML/SummaryForTABLE#head-6fcfaa26f41088d2cf13b4dd3247225a49ee7be1
>>>
>>> HTMLWG Tracker ACTION-111, ISSUE-32
>>> --
>>> Laura L. Carlson
>>
>> --
>>
>> Janina Sajka,   Phone:  +1.202.595.7777;
>>                sip:janina@CapitalAccessibility.Com
>> Partner, Capital Accessibility LLC      http://CapitalAccessibility.Com
>>
>> Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada
>> Learn more at http://ScreenlessPhone.Com
>>
>> Chair, Open Accessibility       janina@a11y.org
>> Linux Foundation                http://a11y.org
>>
>> Chair, Protocols & Formats
>> Web Accessibility Initiative    http://www.w3.org/wai/pf
>> World Wide Web Consortium (W3C)
>
> --
> Laura L. Carlson

-- 
Laura L. Carlson

Received on Wednesday, 27 May 2009 14:22:58 UTC