W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 2009

RE: Linking to WAI Guidelines & WAI Resources

From: <Anna.Zhuang@nokia.com>
Date: Tue, 17 Feb 2009 14:40:35 +0100
To: <shawn@w3.org>
CC: <w3c-wai-eo@w3.org>
Message-ID: <D1E1C1C072023846AC4A55088BAA4B0330948DF50B@NOK-EUMSG-04.mgdnok.nokia.com>

 Hello Shawn,

The purpose and the audience from requirements should be folded into resourse page itself as an intro.

More text is needed around what should be referenced when and how. Can also be part of the intro.

Now I don't see the need in the table at all. You have all the links in the text above. The text from the table should be put into subcequent sections and it will refere to all the guidelines' links that are collected in each section.

I now agree with William, the doc needs to be more extensive. Need to add referencing working groups as well.

Additionally can have one or two links to WAI EO resoruces.

Anna



>-----Original Message-----
>From: w3c-wai-eo-request@w3.org
>[mailto:w3c-wai-eo-request@w3.org] On Behalf Of ext Shawn Henry
>Sent: Tuesday, February 17, 2009 3:04 PM
>To: Zhuang Anna (Nokia-D-MSW/Tampere)
>Cc: w3c-wai-eo@w3.org
>Subject: Re: Linking to WAI Guidelines & WAI Resources
>
>Hello all,
>
>Thank you for taking the time to write up your thoughts, Anna.
>A few replies for now:
>
>> I assume the target audience of the document is largely
>internal WAI or W3C people. I don't expect developers needing
>such guidance nor I expect them to care.
>
>Actually, the primary audience is external people who are
>linking to WAI guidelines, such as evaluation tool developers.
>I made this more clear in the requirements/analysis at:
>http://www.w3.org/WAI/EO/changelogs/cl-linking
>
>> I don't see the need in the last row of the table
>
>There is at least one evaluation tool that points to this URI
>and we would like them the change it. That is the reason for
>that last row.
>
>> Question: Are URIs we are discussing here supposed to point
>to the document itself or to specific part of a page?
>
>We are talking in general about URIs for the documents;
>however, one of the main issues that we are addressing is
>broken fragments/targets/anchors. I've added that to the
>requirements/analysis page.
>
>Regards,
>~Shawn
>
>
>Anna.Zhuang@nokia.com wrote:
>>  Hello EOWG,
>>
>> Here are my comments. They go a bit beyond the tast -:)
>>
>> I assume the target audience of the document is largely
>internal WAI or W3C people. I don't expect developers needing
>such guidance nor I expect them to care.
>>
>> So if the purpose of the document is to keep referencing WAI
>docs consistently across all WAI guidelines then my suggestions:
>>
>> 1. Swap the columns: first "what", then "URI" followed by
>"use" and then "content change". IMO the table as it is now is
>hard to read.
>>
>> 2. Rename the column titles: "what" should be "referenced
>document", "use" explains the rules of what to reference with
>this particular URI, it extends the column "referenced
>document", I would rename "use" into "referencing
>guidance/instruction".
>>
>> 3. "Content change" is not absolutely necessary it merely
>repeats what is stated in "use"
>>
>> 4. There is too much text in the current "use". My proposal
>for each row of the table:
>> =====
>> WCAG Overview --> URL --> The URL always points to the Guidelines
>> Overview page. Page content changes over time ===== Latest
>version of
>> the guidelines (draft or approved) --> URI --> The URL
>always points to the latest available version of the guideline.
>> =====
>> Latest approved version of the guidelines ---> URI ---> The
>URL always points to the latest approved version of the
>guideline. The content of the page remains unchanged untill
>the guidelines are superceeded by the new approved version.
>> =====
>> Old approved version of the guideline ---> URI ---> The URL
>always points to old approved versions of the guideline. The
>content of the page remains unchanged untill more guidelines
>are superceeded by the new approved version and added to this page.
>> =====
>> I don't see the need in the last row of the table
>>
>> 5. It would be good to have Overview page as Overview only,
>i.e. what guideline is about and who develops it. Current
>Overview pages are not Overview at all. (Looking at WCAG
>Overview): If we keep the following headings in one single
>overview doc (removing those headings): Web Content
>Accessibility Guidelines (WCAG), Who WCAG is for, Who develops
>WCAG and more the rest to another page. Overview page should
>have a link to technical documentation and supporting
>material. Then technical documentation and supporting material
>page should contain:
>> * Working draft(s)
>> * Latest approved version
>> * Older approved versions
>> * EO material
>> * Any other related material and presentations
>>
>>
>> Question: Are URIs we are discussing here supposed to point
>to the document itself or to specific part of a page?
>>
>> Anna
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: w3c-wai-eo-request@w3.org
>>> [mailto:w3c-wai-eo-request@w3.org] On Behalf Of ext Shawn Henry
>>> Sent: Sunday, February 15, 2009 3:56 AM
>>> To: EOWG (E-mail)
>>> Subject: Re: Linking to WAI Guidelines & WAI Resources
>>>
>>> EOWG,
>>>
>>> I have updated the page at:
>>>        http://www.w3.org/WAI/EO/Drafts/linking
>>> along with the requirements/analysis and changelog at:
>>>        http://www.w3.org/WAI/EO/changelogs/cl-linking
>>>
>>> Please send comments in e-mail by Friday 20 February.
>>>
>>> Thanks,
>>> ~Shawn
>>>
>>>
>>> Shawn Henry wrote:
>>>> EOWG,
>>>>
>>>> At today's teleconference we decided to look at improving the
>>>> usability and visibility of the following resources:
>>>> * Linking to WAI Guidelines and Technical Reports
>>>> <http://www.w3.org/WAI/EO/Drafts/linking>
>>>> * WAI Resources annotated list <http://www.w3.org/WAI/Resources/>
>>>>
>>>> Please send your ideas via e-mail for now.
>>>>
>>>> Thanks,
>>>> ~Shawn
>>>>
>>>> -------
>>>>
>>>> Shawn Lawton Henry
>>>> W3C Web Accessibility Initiative (WAI)
>>>> e-mail: shawn@w3.org
>>>> phone: +1.617.395.7664
>>>> about: http://www.w3.org/People/Shawn/
>>>>
>>>>
>>>
>>
>>
>
>
Received on Tuesday, 17 February 2009 13:42:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:57 UTC