View source for PF/XTech/HTML5/A11ySnapshot2008-08

__NOTOC__
= Shapshot of HTML5 Accessibility Issues Currently "in play", August 2008 =

''Note: this page is based on information originally compiled by Laura Carlson on 14 August 2008''

In response to a query about the direction of HTML5 and the possible positive and negative effects on accessibility of changes in the specification, Laura Carlson, an HTML WG member, prepared the following summation:

== Issues Relating to the alt Attribute ==

=== Optional alt Issue ===

* [http://esw.w3.org/topic/HTML/IssueAltAttribute Thorough details and history from September 2007 to date]
* [http://www.w3.org/html/wg/tracker/issues/31 alt: Optional or Required? (HTML Issue 31)]
** [http://www.w3.org/html/wg/tracker/actions/54 draft text requiring producers/authors to include @alt on img elements (HTML Action 54)]
*** [http://esw.w3.org/topic/HTML/Action54AltAttribute Action 54: First Draft]
*** [http://esw.w3.org/topic/HTML/Action54AltAttributeDiscussion Discussion Page for HTML WG Action 54 First Draft]
*** [http://esw.w3.org/topic/HTML/Action54AltAttributeSecondDraft Start of second draft for HTML WG Action 54]
*** [http://lists.w3.org/Archives/Public/public-html/2008Apr/0408.html Request for PF review of Action 54 (March 2008]
*** [http://lists.w3.org/Archives/Public/public-html/2008Mar/0234.html Second Request for PF Review of Action 54 (April 2008)]

=== Proper Usage of the alt Attribute ===

One of the biggest change between the first draft and the second draft of HTML5, was that the majority of the usage examples and code samples were removed. Usage examples and code samples from [[HTML/Action54AltAttribute| HTML WG Action 54 first draft]] are being refined and most have now been submitted as Techniques for WCAG 2.0. If they are accepted, the action 54 document will link to them there.

Since a format specification is not a tutorial. Including detailed guidance in <code><nowiki>alt</nowiki></code> attribute techniques could be seen as usurping the role of WCAG 2.0 and its techniques documents. PF has also pointed out, "[http://lists.w3.org/Archives/Public/public-html/2008Feb/0082.html WCAG WG is chartered to set Accessibility guidelines and HTML WG is not]".  The [http://www.w3.org/WAI/ W3C Web Accessibility Initiative (WAI)] is the accessibility authority.

=== Use/Misuse of alt to Convey Machine-Parseable Generic Type Values ===

[http://www.w3.org/html/wg/tracker/issues/58 HTML WG Issue 58] has been raised regarding the editor's [http://www.w3.org/html/wg/html5/#alt0 curly brace proposal for the alt attribute]. Curly braces are but one of [[HTML/IssueAltAttribute#head-27468e7ee9afd1f9e07186c8d74f0b0168b3975a| many potential solutions for improving, extending and replacing alt]] have been discussed. The HTML 5 editor imposing a particular solution and adding it to the draft could be seen as usurping the role of WAI. PF has previously pointed out, "[http://lists.w3.org/Archives/Public/public-html/2008Feb/0082.html WCAG WG is chartered to set Accessibility guidelines and HTML WG is not]".

The W3C Web Accessibility Initiative (WAI) is the accessibility authority.

The curly braces proposal in the editor's draft doesn't appear to be a text equivalent per WCAG. The HTML WG needs to be sure deliverables satisfy accessibility requirements. PF are the go-to-guys for guidance in accessibility matters. PF's counsel is needed BEFORE any particular solution is chosen to be added to the next published draft. The curly braces proposal should not be published outside of an editor's draft without consultation and collaboration with PF.

The issue of [[PF/XTech/HTML5/AltCurlyBraces| curly braces used to contain generic type values for alt]] is actively being investigated by the PFWG, as are alternatives, such as the use of a [[PF/XTech/HTML5/RoleAttribute| role attribute to convey generic type values for elements]] is also under active consideration and development.

----
== TABLE Accessibility Issues ==

=== summary Attribute for Tables ===

Thorough details and history of the [[HTML/SummaryForTABLE| discussion over the summary attribute for TABLE, from May 2007 to date]] is captured in a HTML WG wiki page, entitled: "Mechanism to Summarize a Table"

In March [http://www.w3.org/html/wg/tracker/issues/32 Issue 32] was closed by the editor: "Rejected by editor due to unclear problem description".  But on June 12 it was reopened. The [http://www.w3.org/2008/06/12-html-wg-minutes.html#item01 minutes of the meeting where the issue was reopened] read: "reopened issue 32 and will remain open until have a resolution that allows it to be closed; not resolved now -- needs more discussion".  As a result, [http://www.w3.org/html/wg/tracker/actions/66 HTML WG Action item 66 was opened].

=== Advice From PFWG on @summary ===

In a formal response as chair of PFWG, Al Gilman {http://lists.w3.org/Archives/Public/public-html/2008Aug/0213.html informed the HTML WG of the PF's stance on @summary]:

# @summary should stay.
# It provides a needed service.
# element content providing this info, '''if linked by markup to the table''' offers growth to even better practice.
# Don't have the linking markup yet; is a developmental item.
# evolution not revolution says: keep @summary at least until alternatives are deployed and stable."

=== headers for TABLE ===

Thorough details and history of [[HTML/IssueTableHeaders| discussion of the headers attribute from May 2007 to date]] are availble from the HTML WG's portion of the ESW wiki.

The HTML5 editor added <code><nowiki>headers</nowiki></code> to the draft specification. HTML 5 now says that "The <code><nowiki>td</nowiki></code> element may have a <code><nowiki>headers</nowiki></code> content attribute specified". However, the [[HTML/IssueTableHeaders#head-85e22b44113d468a06de687ce426b4d3135b0834| summary issue isn't solved by the current specification's language]].

''Follow-up and Continued Issues and Actions pertaining to @summary''
* [http://www.w3.org/Bugs/Public/show_bug.cgi?id=5822 Gez Lemon has filed a bug report on summary]
* [http://www.w3.org/html/wg/tracker/issues/57 HTML ISSUE-57: @headers]
** [http://www.w3.org/html/wg/tracker/actions/72 Action 72]
** [[HTML/Action72Headers| Deliverable for Action 72]]

----
== title attribute issue ==

Steve Faulkner raised bug 5807: [http://www.w3.org/Bugs/Public/show_bug.cgi?id=5807 User Agent display of title attribute content not defined]. Steve continues to [http://lists.w3.org/Archives/Public/www-archive/2008Jul/0017.html work on addressing the issue of the exposition of title (along with many others) from within PF.

----
== longdesc issue ==

Chaals [[McCathieNevile]] raised [http://www.w3.org/html/wg/tracker/issues/30 HTML WG ISSUE-30: longdesc]. No Action has been assigned to address this issue yet from within the HTML WG, although there has been much dialog about the [http://esw.w3.org/topic/HTML/LongdescRetention provision of a terse and long descriptor mechanism in HTML5].

----
== Support for WAI-ARIA in HTML5 ==

PF has been actively pursuing the issue of [http://esw.w3.org/topic/HTML/ARIAIntegration support for WAI-ARIA in HTML5].

----
* [[PF/XTech/HTML5| HTML5 Issue Collection and Requirements Drafting Index]]
* [[PF/XTech| XTech Wiki: Issues Which Cut Across Specific Working Groups & Domains]]
* [http://www.w3.org/WAI/PF/group PF Working Group Member-Confidential Space]
* [http://www.w3.org/WAI/PF/ PF Working Group Public Web Space]