RE: Understanding SC 2.4.8 ( LC-2798)

Devarshi,
I think that the working group agrees that a possible technique exists which can help meet SC 2.4.8, but it does not believe that G88 is that technique.  Our response was that we intend to develop this technique in the future (and we would welcome submission of such a technique also). Does this seem reasonable?

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe Systems

akirkpat@adobe.com<mailto:akirkpatrick@adobe.com>
http://twitter.com/awkawk
http://blogs.adobe.com/accessibility

From: Devarshi Pant [mailto:devarshipant@gmail.com]
Sent: Tuesday, August 20, 2013 7:54 PM
To: Andrew Kirkpatrick
Cc: public-comments-wcag20@w3.org
Subject: Re: Understanding SC 2.4.8 ( LC-2798)


In G88, under Description, please refer to the text towards the end that reads:
<quote>
It may also be helpful for the title to -
>Identify the site or other resource to which the Web page belongs
>Be unique within the site or other resource to which the Web page belongs.
</quote>
Now compare this, especially the first bullet above, with the Intent under SC 2.4.8 that says:
"The intent of this Success Criterion is to provide a way for the user to orient herself within a set of Web pages, a Web site, or a Web application and find related information."

*** It seems that the title on a specific webpage can convey the larger context (series of steps, drill down navigational scheme, etc.) using G88, and therefore it can be considered as a sufficient technique to satisfy SC 2.4.8.

Devarshi
On Aug 20, 2013 2:40 PM, <akirkpat@adobe.com<mailto:akirkpat@adobe.com>> wrote:
 Dear Devarshi Pant ,

The Web Content Accessibility Guidelines Working Group has reviewed the
comments you sent [1] on the Last Call Working Draft [2] of the
Understanding WCAG 2.0 (Public Review Draft) published on 11 Jul 2013.
Thank you for having taken the time to review the document and to send us
comments!

The Working Group's response to your comment is included below.

Please review it carefully and let us know by email at
public-comments-wcag20@w3.org<mailto:public-comments-wcag20@w3.org> if you agree with it or not before 25 August
2013. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track.

Thanks,

For the Web Content Accessibility Guidelines Working Group,
Michael Cooper
W3C Staff Contact

 1.
http://www.w3.org/mid/CAJGQbjvU6dHvCbnGYK2_vbCMY-aAWXNckN4S0pUuYfr8pUEusA@mail.gmail.com
 2. http://www.w3.org/WAI/GL/2013/WD-UNDERSTANDING-WCAG20-20130711/


=====

Your comment on :
> Understanding SC 2.4.8 at
>
http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-location.html
>
> Problem:
> The existing set of techniques could include the page title (G88) as a
> sufficient / advisory technique.
>
> Proposed Change:
> Using page title also serves to orient users on their location. Use
> G88:
> Providing descriptive titles for Web pages
> http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/G88 as a
> sufficient
> technique under SC 2.4.8. If the editors feel that the length of the
> page
> title string cannot be accommodated in the title bar, consider using
> this
> as an advisory.
>
> -Devarshi


Working Group Resolution (LC-2798):
The WG thanks you for your comment.  Technique G88 applies to a single web
page, whereas the intent of SC2.4.8 is to allow the user to determine
location within a larger context than a single web page (for example, a
series of web pages).  Therefore, the inclusion of G88 as a
sufficient/advisory technique for SC2.4.8 does not seem warranted, because
title contents themselves may not give location information to a user
within a larger website or web application.  However, we intend to develop
a future technique which suggests how to implement page titles in a way
which can address SC2.4.8.

----

Received on Wednesday, 21 August 2013 01:31:40 UTC