PF/XTech/HTML5

HTML5 Accessibility

This section of the ESW wiki is dedicated to HTML5 from an accessibility standpoint.

It is a directory to HTML5 accessibility meetings, reviews, processes, bugs, issues, proposals, and related resources from 2007 to date.

Much of this content is expected to be migrated to the HTML Accessibility Task Force Wiki Space over time.

Meetings

• HTML Accessibility Task Force Meeting Minutes, November 2009 to Present
  • HTML Accessibility Task Force Teleconference Logistics
• Video TPAC breakout session Minutes, November 6, 2009
• ARIA/HTML5 TPAC breakout session, November 5, 2009
• PFWG Open TPAC Meeting on Accessibility in HTML5 Minutes, November 3, 2009
• Accessibility of Media Elements in HTML 5 Gathering Minutes, November 1, 2009
  • Accessibility of Media Elements in HTML 5 Gathering, Logistics
• Ad Hoc PF HTML Issues Caucus, August 2008 to October 2009

---

Reviews

• PFWG spec review Q3 2009
• HTMLWG Requests and PFWG Responses

---

Surveys

• HTML Accessibility Surveys

---

Process for Bugs and Issues

The HTML Working Group Decision Policy Document explains the process of submitting HTML Bugs and escalating Bugs to Issues. The deadline to comment on the decision making process proposal was Tuesday, November 10, 2009.

Bug Process

Bugs initially record a problem, and are given an initial disposition by the editor of the spec.

• General process to submit HTML5 Bugzilla bugs
• Process to submit HTML accessibility Bugzilla bugs
• Setting up, Using, and Subscribing to Bugzilla

Escalating a Bug to an Issue

According to the HTML Working Group Decision Policy, bugs that are not satisfactory resolved can be escalated to the HTML WG Issue Tracker. Tracker Issues "record that an editor's resolution was not satisfactory, and so the full Working Group must address the issue."

Recourse For a Dissatisfied Bug Reporter

If a bug reporter is dissatisfied with the bug resolution and does not believe it is productive to ask the editor to reconsider, he or she may ask to escalate the issue to the issue tracker.

A dissatisfied bug reporter:

• With Tracker access can raise an Issue directly.
• Without Tracker access should:
  1. Add the keyword [[TrackerRequest]] to the bug.
  2. Suggest an issue title.
  3. Suggest an issue description.
  4. As previously explained in the process to submit HTML accessibility Bugzilla bugs, if it is an accessibility bug make sure you have:
     1. Added the Keyword a11y .
     2. Added the address public-html-a11y@w3.org to the cc field.

---

Bugs

• Search for Accessibility Bugs with Keyword "a11y"
• Search for Accessibility Bugs with Keyword "a11ytf"
• Search for Accessibility Bugs with Keyword "PFWG"
• HTML WG Bugzilla Login Page

---

Issues by State

Tracker issues have various states and actions.

• Open Tracker HTML Accessibility Issues
• Raised Tracker HTML Accessibility Issues
• Closed Tracker HTML Accessibility Issues
• All Tracker HTML Accessibility Issues
  • All Tracker HTML Accessibility Actions

A raised issue means that a working group member suggests this is worth a WG discussion and potentially a decision, but to date no concrete proposal has been created that enjoys a consensus of at least one.

An open issue means that least one concrete proposal is being made to resolve the problem, but one on which consensus has either not been evaluated, or has not yet been reached; a working group member is assigned an ACTION to follow up (similar to ASSIGNED). An action is the process of doing something in order to resolve or help resolve an ISSUE. (An ACTION generates a potential resolution to an ISSUE, or helps solve it e.g. by writing a change proposal.)

Change Proposals

According to the HTML Working Group Decision Policy, Open Tracker Issues are issues with someone working on a change proposal. If the change proposal is not done by the deadline, the issue will be closed without prejudice and deferred to the next version of HTML. The default deadline to complete a Change Proposal is one month from the time someone volunteers. The chairs may grant a longer deadline for complex issues on request."

• Writing a Change Proposal (Instructions)
• Change Proposal Template

A closed issue means that the chairs believe either the WG has resolved the issue (via spec editing) or the issue has been withdrawn. Only the chairs should move issues to 'closed'. Typically moving issues from PENDINGREVIEW to CLOSED will involve review in the weekly telecon. According to the HTML Working Group Decision Policy, Tracker Issues that are Closed without Prejudice become an endpoint for the escalation process.

Visit the HTML Working Group Issues page for more information definitions of tracker states.

---

Issues by Topic

ARIA

• @aria in the HTML WG's tracker:
  1. HTML WG ISSUE-14: aria-role: Integration of WAI-ARIA roles into HTML5.
     • HTML WG ACTION-9: Discuss UML tools with DanC
     • HTML WG ACTION-8: Discuss with PFWG role attribute vs aria attribute
     • HTML WG ACTION-11: Show how
       works with URI based extensibility
     • HTML WG ACTION-23: coordinate tests using ARIA
     • HTML WG ACTION-30: Report back after 11-30 meeting on ARIA syntax
• HTML WG ISSUE-35: aria-processing: Need to define processing requirements for aria states and properties when used in html.
  • HTML WG ACTION-73: Follow up on WAI-ARIA markup thread, emphasizing the conformance point
  • HTML WG ACTION-107: recruit ARIA joint-TF members
  • HTML WG ACTION-114: Report progress on ARIA TF
  • HTML WG ACTION-138: Produce a matrix based on Henri's work
  • HTML WG ACTION-158: Bring question to group: Do we want changing of element handler and role semantics via attributes to be deprecated?
• HTML WG ISSUE-51: aria-curie - WAI-ARIA dependency on Role Attribute Module, which takes Curie values. problem for implementations?
  1. HTML WG ISSUE-85: ARIA roles added to the a element should be conforming
• aria in the HTML WG's Bugzilla:
  1. HTML Bug 6496: Allow <img aria-labelledby> to act as a caption.

---

AUDIO and VIDEO (Multimedia)

• <Audio> <Video> in the HTML WG's wiki:
  • Multimedia Accessibility <Audio> <Video> Issue Page
• <Audio> <Video> in the PFWG's wiki:
  • Multi-Media "Matters": Coordination, Collaboration, Issues & Reviews
  • Towards A Unified Approach to HTML5's Media Specific Elements, version 0.1
• Video in the HTML WG's tracker:
  1. HTML WG ISSUE-9: Video - How accessibility works for <video> is unclear.
• Video in the HTML WG's Bugzilla:
  1. HTML Bug 5758: Insufficient accessibility fallback for <audio> or <video>.
  2. HTML5 Bug 8187: Section 4.8.7 on video makes no reference to audio description

---

CANVAS

• canvas in the HTML WG's wiki:
  • canvas Element Accessibility Issue Page
• canvas in the HTML WG's tracker:
  1. HTML WG ISSUE-74: canvas-accessibility: How accessibility works for <canvas> is unclear.
     • HTML WG ACTION-133: Develop an accessibility API and model for canvas as well as attributes to specify alternative content.
• canvas in the HTML WG's Bugzilla:
  1. HTML Bug 7011: Canvas accessible fallback provision is under specified.
  2. HTML Bug 7404: But only if the element is being rendered needs to take into account <canvas> descendants...

---

Drag and Drop

• Drag and Drop in the HTML WG's Bugzilla:
  1. HTML WG Bug 7721: Drag and Drop is not keyboard accessible

---

Equivalent Content for Static Images (@alt, Longdesc, etc.)

• Omitting Text Alternatives on <img> Issue Page
• Equivalent Content for Static Images
• WAI CG's Consensus Resolutions on Text alternatives in HTML 5
  • Requirements for Descriptions for Static Images (obsoleted by WAI CG's Consensus doc)
• @alt in the HTML WG's wiki:
  • Action 54 Deliverable: alt attribute authoring guidelines and examples (First Draft)
    • Action 54 Discussion of First Draft
• Action 54 Deliverable: alt attribute authoring guidelines and examples (Second Draft)
  • Action 54 Deliverable: alt attribute authoring guidelines and examples (Third Draft)
  • Start of "Best practice techniques: Providing text alternatives for images" (Based on ACTION 54) - Steve Faulkner
• @alt in the HTML WG's tracker:
  1. HTML WG ISSUE-31: What to do when a reasonable text equivalent is unknown/unavailable?
     • HTML WG ACTION-54: @alt authoring guidelines and examples
     • HTML WG ACTION-61: Ensure HTML WG responds to PF WG on Omitting alt Attribute.
     • HTML WG ACTION-98: Discuss missing-alt with the WAI CG and report back
     • HTML WG ACTION-131: (draft ALT spec).
       • Action 54 Deliverable: Spec text (First Draft)
• HTML WG ISSUE-58: Use of "curly brackets" to identify a graphical image by its use or type by inserting a generic identifier / descriptor in curly braces as the @alt value for an IMG - State: CLOSED (Dup of ISSUE-31)
  1. ISSUE-66: Image analysis heuristics.
• alt in the HTML WG's Bugzilla:
  1. HTML Bug 6494: Make the requiredness about alt more obvious.
  2. HTML Bug 7144: I am not sure if we are ditching ALT in favour of legend. You don't make this clear.
  3. HTML WG 8171: Bug Implement the text alternatives proposal from WAI
• NOTE DEPENDENCIES: title attribute method to provide text alternatives on <img> (Issue 80 and Bugs 7362 and 5807).
• @alt issues on the PF WG's radar:
  • Use of Machine Language as alt text
• @longdesc in the HTML WG's tracker:
  1. HTML WG ISSUE-30 longdesc: Should HTML 5 include a longdesc attribute for images?
     • Change Proposal for longdesc ISSUE 30 by Charles McCathieNevile

---

FORMS

Please also consult PF's Forms in HTML5: Issues & Requirements Index

Forms Possibilities/Competing Drafts

• XForms, 1.1 (Candidate Rec Draft)
• XForms Transitional
• XForms Transitional, 1.2 (available only as a zipped source bundle)
  • XForms for HTML Authors
  • XForms FAQ
• Web Forms, 2.0

Forms Feedback, Requirements, and Issues

• Forms in HTML5: Issues & Requirements Index
  • Forms Requirements for HTML5
    • GJR's Formal Forms Feedback for HTML5 WG

---

MathML

• MathML in HTML5: Issues and Requirements

---

SVG

• SVG in HTML5

---

TABLES

@axis and @abbr

• @axis and @abbr (dropped attributes)

@headers

• @headers in the PF WG's wiki:
  • headers Attribute for TABLE
• @headers in the HTML WG's wiki:
  • headers Attribute Issue Page
  • headers Spec Text Rewrite (Deliverable for Action 72)
  • Table Headers Testing for Bug 5822
  • Cyclic Header Chains
  • Table Headers HTMLWG/PFWG Joint Discussion
• @headers in the HTML WG's tracker:
  1. HTML WG ISSUE-20: Improvements to the table-headers algorithm in the HTML 5 spec. Note: HTML WG ISSUE-57: @headers is a duplicate of Issue 20.
     • HTML WG ACTION-72: @headers rewrite of Spec text
     • HTML WG ACTION-84: Prepare status report on @headers
     • HTML WG ACTION-85: compare "Smart Headers" with HTML5 algorithm
     • HTML WG ACTION-87: Ensure Ian Hickson follows up on semantics-tables messages
• @headers in the HTML WG's Bugzilla:
  1. HTML Bug 5822: The headers attribute should be able to reference a td.
  2. HTML Bug 6181: Process table feedback (including headers='" issue).
  3. HTML Bug 6462: Self-reference and cyclic references in headers=
  4. HTML Bug 7260: Create testsuite for table headers association.

@summary

• @summary in the PF's wiki:
  • Summary for TABLE (PF Feedback)
• @summary in the HTML WG's wiki:
  • Mechanism to Summarize a Table Issue Page
  • Proposed approaches in defining the summary attribute
  • TABLE Accessibility (Testing)
• @summary in the HTML WG's tracker:
  1. HTML WG ISSUE-32 (@summary)
     • HTML WG ACTION-66: Collate information on what spec status is with respect to table@summary
     • HTML WG ACTION-76: Create poll on issue-32, based on Joshue's page from action-66
     • HTML WG ACTION-104: Inquire about table summary and headers status at PFWG caucus on 2009-02-06
     • HTML WG ACTION-111: Send call to working group on summary to update wiki in preparation for vote
     • HTML WG ACTION-126 Send a call to the WG to update the Wiki page to adequately reflect both (all) viewpoints on summary, in prep. for a vote
     • HTML WG ACTION-128: Work with PF to find an owner for drafting @summary text proposal
     • HTML WG ACTION-136: Send draft to the list
       • ACTION-136 Deliverable Spec Text Draft.
         • Related email
  2. HTML WG ACTION-145: Write a Change Proposal for summary.
• @summary in the HTML WG's Bugzilla:
  1. HTML Bug 6181: Process table feedback (including headers='" issue)
  2. HTML Bug 7539 Since @summary is an official part of the table element, it is no longer obsolete...
  3. HTML Bug 7633: The use of @summary should be encouraged when circumstances warrant

@scope

• @scope in the HTML WG's Bugzilla:
  1. HTML Bug 5823: Scope Allowable on TD?

Layout Tables

• Deprecation of TABLE for layout/stylistic purposes

---

title Attribute

• title in the HTML WG's tracker:
  1. HTML WG ISSUE-80: Title alternative- Document conformance and device dependent display of title attribute content.
• title in the HTML WG's Bugzilla
  1. HTML Bug 7362: Inclusion of the title as a case where the alt may be omitted is problematic.
  2. HTML Bug 5807: UA display of @title if content not defined

---

General and Meta-Issues

• Accessibility Dependencies of HTML5
• Support for ARIA in HTML5
  • Explicit Association Patterns (and Points of Conflict)
• Access Key Requirements for HTML5
  • Dropped Attribute "accesskey"
• Tabindex (changed attribute)
• Abbreviated Forms in HTML5
  • More Considerations About Abbreviations

---

Added, Changed, and Deprecated Attributes

Added Attributes

• required (added attribute)

Changed Attributes

• lang (changed attribute)
• tabindex (changed attribute)

Dropped Attributes

• accesskey (attribute removed without replacement)
  • Access Key Requirements (Replacing HTML5's Dropped Attribute, "accesskey"

---

Related Issue Information

• August 2008 Snapshot of HTML5 Accessibility Issues
• Openness of W3C Working Groups

---

Proposals

• Writing a HTML5 Change Proposal (Instructions)
• Change Proposal Template

HTML Accessibility Task Force Change Proposals

• To be determined.

PFWG Proposals

• WAI CG's Consensus Resolutions on Text alternatives in HTML 5

Note: The following Proposals Are Under Consideration by the PFWG, but carry no endorsement by the PFWG

• Access Key Requirements (replacing HTML5's dropped attribute, "accesskey"
• Towards A Unified Approach to HTML5's Media Specific Elements
• A Role Attribute for HTML5
• Layout TABLE Deprecation Proposal

HTML WG Proposals Related to WAI Issues

General Accessibility Proposals

• Request to Strengthen the HTML5 Accessibility Design Principle
• (Proposal) Procedure to Promote Progress With Accessibility Issues in HTML5
  • Discussion Page for Accessibility Issues Procedure

alt Attribute Authoring Guidelines and Examples

• For corresponding ISSUE-31: missing-alt
  • alt attribute authoring guidelines and examples First Draft Action 54 Deliverable
    • alt attribute usage discussion based on First Draft Action 54 Deliverable
• alt attribute usage second draft Action 54 Deliverable
  • alt attribute usage third draft Action 54 Deliverable
  • Best practice techniques: Providing text alternatives for images"
  • A Better @alt

IMG Spec Text

• For corresponding ISSUE-31: missing-alt
  • First Draft Deliverable (Spec text) for Action 131

Longdesc

• For corresponding ISSUE-30: Longdesc
  • Longdesc Change Proposal.

Table headers

• For corresponding ISSUE-20 table-headers ISSUE State: CLOSED
  • Table headers Spec Text Rewrite (Deliverable for Action 72)

Table summary

• For corresponding ISSUE-32 table-summary
  • Proposed approaches in defining the summary attribute
  • ACTION-136 Deliverable Spec Text Draft

Q

• An Argument for the Preservation & Strengthening of Q
• Quotations: Block versus Inline
• Associating attributions, citations, quotations and references
  • Corresponding Issue #50

---

HTML5-Specific Resources

• HTML Working Group Home Page
• The HTML5 Draft:
  • Latest Editor's Draft of HTML5
  • Latest Published Draft of HTML5
  • Tools To Assist Tracking HTML5 Draft Changes:
    • Interactive W3C Draft Tracker
    • CVS Web View
• HTML5: The Markup Language: a version of HTML5 produced at the request of the TAG to provide a collaborative basis for HTML5 from a purely declarative markup point of view
  • Abstract of HTML5: The Markup Language: This specification defines the fifth major version of the HTML vocabulary. It provides the details necessary for producers of HTML content to create conformant documents. By design, it does not define related APIs nor attempt to specify how consumers of HTML content are meant to process documents.
• HTML WG Related Resources
  • Accessibility Dependencies of HTML5
  • HTML Working Group Teleconferences
  • HTML Working Group Minutes
  • HTML Working Group Email Lists
  • HTML Working Group Surveys
  • HTML Working Group Accessibility Consensus (2007)
• Associated HTML WG Drafts and Documents:
  • HTML5 Design Principles (Public Draft)
  • HTML 5 Differences from HTML 4 (Editor's Draft)
  • Web Developers' Guide to HTML5 (Editor's Draft)
    • Abstract of Web Developers' Guide to HTML5: "This document illustrates how to write HTML 5 documents, focusing on simplicity and practical applications for beginners while also providing in depth information for more advanced web developers"
    • Web Developers' Guide to HTML5 (ESW Wiki Page)
• Offline Web Applications (W3C Note)
  • Abstract of Offline Web Applications: "HTML 5 contains several features that address the challenge of building Web applications that work while offline. This document highlights these features (SQL, offline application caching APIs as well as online/offline events, status, and the localStorage API) from HTML 5 and provides brief tutorials on how these features might be used to create Web applications that work offline"
• Web Workers: An accompaniment specification for HTML5
  • Abstract of Web Workers: "This specification defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page. This allows for thread-like operation with message-passing as the coordination mechanism."
• HTML5 Tracker
  • HTML WG Tracker Start Page
  • HTML WG Agenda Planning Page
  • All Open Issues
    • All Closed Issues
• All Open Actions
  • All Closed Actions

---

Task Forces (Accessibility Specific and Related)

Accessibility Task Force

• Accessibility Task Force Proposal, August 2009.
• Accessibility Task Force Work Statement, August/September 2009.
• Call For Consensus (CFC): Create HTML Accessibility Task Force, September 2009.
• Accessibility Task Force Participants
• Accessibility Task Force Email Archive (Posting is restricted to task force members. People not in the task force may bring issues for consideration by emailing the WAI-XTech mailing list at wai-xtech@w3.org.WAI-XTech mailing list archives are available.)
• Facilitation
• Accessibility Task Force Home Page
  • Process to submit HTML spec Accessibility Bugs So Accessibility Task Force will see them.

ARIA User Agent Implementation Task Force

• Survey: Request for Input on organizing accessibility API binding work in PFWG and HTML WG, November 2008.
• Joint task force on ARIA user agent implementation proposal, February 2009.
• ARIA Task Force Work Statement, February 2009.
• ARIA Task Force Participants
• The ARIA Task Force has no dedicated mailing list. Email discussion takes place on the WAI-XTech mailing list at wai-xtech@w3.org. Add the prefix "[AAPI]" to your messages to separate threads from other topics on the list. WAI-XTech mailing list archives are available.
• Facilitation
• ARIA Task Force Home Page

Forms Task Force

• Forms Task Force Charter Proposal
• Forms Task Force Members
• Forms Task Force Email Archive (Posting restricted to task force members.)
• Survey: Web Forms Features
• Forms Task Force Home Page

Testing Task Force

• Development of test suites for HTML-related specifications list proposal, November 2007.
• Call For Consensus (CFC): Create HTML Testing Task Force, September 2009
• Testing Task Force Email Archive
  • Subscribe to public-html-testsuite
  • Unsubscribe from public-html-testsuite
  • mail a new topic to public-html-testsuite

---

• XTech Wiki: Issues Which Cut Across Specific Working Groups & Domains
• PF Working Group Member-Confidential Space
• PF Working Group Public Web Space