Edit comment LC-625 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-838 Next: LC-626

Comment LC-625: Comment Shortname:; Commenter: Lisa Seeman 2 <lisa@ubaccess.com> on behalf of Invited expert at W3C, UB access; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
http://lists.w3.org/Archives/Public/public-comments-wcag20/2006May/0137.html
http://lists.w3.org/Archives/Public/public-comments-wcag20/2006May/att-0137/wcagform_ch2_.html

Comment (including rationale for proposed change):

Web units have titles, what is the advantage if the titles are not descriptive?

Proposed Change:

change to Web units have descriptive titles; Related issues: 626 838 839 1052 1141 1289 1291
(space separated ids); WG Notes: [TEAMB] @@ MU: I agree with this comment. 2.4.3 requires just the page title and 2.4.5 requires the descriptive page title. Why don't we require the descriptive page title at L2 SC(2.4.3)? In my opinion, the non-descriptive page title means nothing. Additionally I'd like to put the descriptive page title to L1 SC. See also LC-626. LGR: Background: the June 2005 WCAG2 draft had "Delivery units have descriptive titles". This was changed as a result of the 13 October 2005 Team B Survey, http://www.w3.org/2002/09/wbs/35422/20051012teamb/results#xdestitle which was primarily focused on issues of what to say about document structure and making headings descriptive. Discussed in the 24 August 2006 telecon: Resolution: Team B Take back LC-625, LC-626: descriptive titles (look at G88) http://www.w3.org/WAI/GL/2006/08/24-wai-wcag-minutes.htm LGR: are there security issues with exposing sensitive personal information in Web unit titles? Discussed in the 31 August 2006 telecon: resolution: accept LC-625, LC-626, LC-1105, LC-1141, LC-1291: Descriptive titles as amended action: Loretta to add language to the appropriate responses that explains why we are not adding "unique" http://www.w3.org/WAI/GL/2006/08/31-wai-wcag-minutes.html {accept} DONE Change SC 2.4.3 to "Web units have descriptive titles." DONE In the first sentence of the Intent section of SC 2.4.3, change "title" to "descriptive title". DONE Delete technique G7: Associating a title with a Web page DONE Remove from advisory techniques for SC 2.4.3: G88: Providing descriptive titles for Web units DONE Change sufficient technique for Addressing Success Criterion 2.4.3 to "G88: Providing descriptive titles for Web units and associating a title with a Web unit USING a technology-specific technique below (for a technology in your baseline) DONE Remove from SC 2.4.3 Examples: #An audio file. A podcast is associated with the title "Today's Tech Tips" by setting the id3 property of the .mp3 file. #A video clip. A video clip is associated with a title using the meta element in SMIL 1.0 or SMIL 2.0, plus the title attribute of the main par element in the SMIL file. #An image. A .JPEG image is associated with a title using EXIF metadata stored in the image file. (Note: Current user agents do not read this metadata.) DONE Add example to How to Meet SC 2.4.3: *A web application. A banking application lets a user inspect his bank accounts, view past statements, and perform transactions. The web application dynamically generates titles for each Web unit, e.g., "Bank XYZ, accounts for John Smith" "Bank XYZ, December 2005 statement for Account 1234-5678". DONE Change SC 2.4.5 to "Headings and labels are descriptive." DONE Change SC 2.4.5 Intent section from "When titles and headings are clear and descriptive" to "When headings are clear and descriptive" DONE Remove G88: Providing descriptive titles for Web units from sufficient techniques for SC 2.4.5 DONE Change Note on SC 2.4.5 to "Note: Headings and labels must be programmatically determined, per success criterion 1.3.1." DONE Change Benefits of SC 2.4.5 to "Descriptive headings and labels are especially helpful for users who have disabilities that make reading slow and for people with limited short-term memory. These people benefit when section headings make it possible to predict what each section contains. This success criterion helps people who use screen readers by ensuring that labels and headings are meaningful when read out of context, for example, in a Table of Contents, or when jumping from heading to heading within a page. This success criterion may also help users with low vision who can see only a few words at a time." DONE Remove from SC 2.4.5: Technology-Specific Techniques HTML Techniques * H64: Using the title attribute of the frame element DONE Move the following resources from SC 2.4.5 to SC 2.4.3: #Guidelines for Accessible and Usable Web Sites: Observing Users Who Work With Screen Readers. Theofanos, M.F., and Redish, J. (2003). Interactions, Volume X, Issue 6, November-December 2003, pages 38-51, http://doi.acm.org/10.1145/947226.947227. #Writing Better Web Page Titles How to write titles for Web pages that will enhance search engine effectiveness. Internal WD updated 1 September 2006.; Resolution: We have changed SC 2.4.3 to "Web pages have descriptive titles" and have also reflected this change in success criterion 2.4.5 and the support documents for both success criteria.; (Please make sure the resolution is adapted for public consumption)