This Wiki page is edited by participants of the HTML Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.

Wishlist for HTML5.1

From HTML accessibility task force Wiki
(Redirected from 51wishlist)
Jump to: navigation, search

The following is a list of areas and issues that the Task Force may consider taking up in HTML5.1. Each links to a dedicated wikipage where individuals and/or groups are encouraged to research and possibly demonstrate a need to formally address any of the individual issues.

Keyboard Interaction

Ensure interactions, such as focus navigation (e.g. fixing tabindex, accesskeys, etc) and activating elements can be done with keyboards, while working for Touch, Voice etc. (This is a large set of problems, and we deal with it in chunks). Includes keyboard text input issues

Chaals, John Foliot
September 4 2014 meeting
November 13 2014 meeting

Full Transcript

John Foliot, Media Subteam

There is now a draft transcript extension for HTML

Panels and Panel Sets

Léonie Watson, chaals, Brian Kardell
December 18 2014 meeting
January 22 2015 meeting

Brian has a personal draft spec - (github repository)

Date pickers

Léonie Watson, Janina Sajka, Joanie Diggs, chaals
July 17 2014 meeting
January 29 2015 meeting

Web Payments

ShaneM, Chaals

ACTION-260 for Shane to present web payments in tf meeting due ASAP

Media Descriptions

chaals, John Foliot, Media Subteam

ACTION-329 chaals hopes we can discover that this is mostly dealt with, or being fixed, for HTML.

Looking for owners…


Discussed in july 2014 teleconf

Emotion Markup

Lisa Seeman? Media Subteam?, Léonie? MarkS?

Haptic Output

Léonie, chaals, Markku Hakinen?

stuff not happening here much


Jeanne Spellman?  Kwasi Mensa? (Mark to follow-up) BBC (Ian Pouncey to follow-up: Update (2014-07-29): Gareth Ford Williams and Jon Howard from the BBC are interested in this)

This is probably a far larger topic than the HTML accessibility Task Force should be taking on


Lisa Seeman, Rich?

This is generally being done in a WCAG task force

Referencing UAAG

Figure out where HTML should point to UAAG

    • Jeanne Spellman


    • Media Sub-Team

Footnotes, End notes, Annotations, Definitions