ISSUE-182: Advice in spec about annotations promotes inaccessible content

footnote-recommendation

Advice in spec about annotations promotes inaccessible content

State:
CLOSED
Product:
pre-LC1 HTML 5 spec
Raised by:
Steve Faulkner
Opened on:
2011-11-22
Description:
The section 4.13.5 Footnotes http://dev.w3.org/html5/spec/Overview.html#footnotes of the HTML5 specification recommends the use of a markup antipattern that makes it impossible for some user groups and very difficult for some other user groups to access footnote content. It advocates the use of the title attribute, yet historically and currently title attribute content is not available to a range of users. there is no indication from implementors that this is likely to change.

The spec text in question needs to be modified or removed:

"For short inline annotations, the title attribute should be used.

In this example, two parts of a dialogue are annotated with footnote-like content using the title attribute.

<p> <b>Customer</b>: Hello! I wish to register a complaint. Hello. Miss?
<p> <b>Shopkeeper</b>: <span title="Colloquial pronunciation of 'What do you'"
>Watcha</span> mean, miss?
<p> <b>Customer</b>: Uh, I'm sorry, I have a cold. I wish to make a complaint.
<p> <b>Shopkeeper</b>: Sorry, <span title="This is, of course, a lie.">we're
closing for lunch</span>."

escalated from Bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=13650
Related Actions Items:
No related actions
Related emails:
  1. RE: CfC: Publish ten heartbeat drafts as WDs (from Paul.Cotton@microsoft.com on 2012-03-29)
  2. RE: CfC: Publish ten heartbeat drafts as WDs (from Paul.Cotton@microsoft.com on 2012-03-27)
  3. Re: CfC: Publish ten heartbeat drafts as WDs (from rubys@intertwingly.net on 2012-03-22)
  4. Re: {minutes} HTML WG telecon 2012-03-22 (from glenn@skynav.com on 2012-03-22)
  5. {minutes} HTML WG telecon 2012-03-22 (from glenn@skynav.com on 2012-03-22)
  6. {agenda} HTML WG telecon 2012-03-22: issue progress, heartbeat drafts, revert request, F2F registration, task force reports (from rubys@intertwingly.net on 2012-03-21)
  7. Working Group Decision: Close ISSUE-182 footnote-recommendation by Amicable Resolution (from rubys@intertwingly.net on 2012-03-20)
  8. {minutes} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, F2F meeting plans, task force reports (from glenn@skynav.com on 2012-03-08)
  9. Re: {agenda} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, F2F meeting plans, task force reports (from glenn@skynav.com on 2012-03-08)
  10. {agenda} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, F2F meeting plans, task force reports (from Paul.Cotton@microsoft.com on 2012-03-08)
  11. {agenda} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, F2F meeting plans, task force reports (from Paul.Cotton@microsoft.com on 2012-03-07)
  12. {minutes} HTML WG telecon 2012-03-01: issue progress and heartbeat drafts (from eoconnor@apple.com on 2012-03-01)
  13. {agenda} HTML WG telecon 2012-03-01: issue progress and heartbeat drafts (from rubys@intertwingly.net on 2012-02-29)
  14. [Minutes] (HTML WG telecon 2012-02-23: issue progress, heartbeat drafts, task force reports) (from glenn@skynav.com on 2012-02-23)
  15. [Minutes] (HTML WG telecon 2012-02-23: issue progress, heartbeat drafts, task force reports) (from glenn@skynav.com on 2012-02-23)
  16. FW: counter proposal for issue 185 (from Paul.Cotton@microsoft.com on 2012-02-22)
  17. Re: HTML WG telecon 2012-02-16: issue progress, heartbeat drafts, task force reports (from ian@iandevlin.com on 2012-02-22)
  18. HTML WG telecon 2012-02-16: issue progress, heartbeat drafts, task force reports (from mjs@apple.com on 2012-02-21)
  19. CfC: Close ISSUE-182 footnote-recommendation by Amicable Resolution (from rubys@intertwingly.net on 2012-02-20)
  20. [minutes] HTML WG telecon 2012-02-16: issue progress (from rubys@intertwingly.net on 2012-02-16)
  21. HTML WG telecon 2012-02-16: issue progress (from Paul.Cotton@microsoft.com on 2012-02-15)
  22. RE: {minutes} HTML WG telecon 2012-02-09: issue progress, task force reports, revert request, new information deadline, F2F (from adrianba@microsoft.com on 2012-02-09)
  23. HTML WG telecon 2012-02-09: issue progress, task force reports, revert request, new information deadline, F2F (from rubys@intertwingly.net on 2012-02-07)
  24. ISSUE-182: footnote-recommendation - Chairs Solicit Alternate Proposals or Counter-Proposals (from Paul.Cotton@microsoft.com on 2012-01-17)
  25. RE: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals (from Paul.Cotton@microsoft.com on 2012-01-17)
  26. Re: HTML5 design philosophy disconnect (from faulkner.steve@gmail.com on 2012-01-13)
  27. Re: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals (from faulkner.steve@gmail.com on 2012-01-12)
  28. Re: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals (from mjs@apple.com on 2012-01-12)
  29. HTML WG minutes (Re: {agenda} HTML WG telecon 2012-01-12: issue progress, other business) (from mjs@apple.com on 2012-01-12)
  30. {agenda} HTML WG telecon 2012-01-12: issue progress, other business (from mjs@apple.com on 2012-01-12)
  31. Re: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals (from faulkner.steve@gmail.com on 2012-01-12)
  32. Re: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals (from faulkner.steve@gmail.com on 2012-01-12)
  33. Re: ISSUE-172: restore-rb - Chairs Solicit Alternate Proposals or Counter-Proposals (from xn--mlform-iua@xn--mlform-iua.no on 2012-01-12)
  34. Re: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals (from mjs@apple.com on 2012-01-11)
  35. Re: ISSUE-172: restore-rb - Chairs Solicit Alternate Proposals or Counter-Proposals (from mjs@apple.com on 2012-01-11)
  36. ISSUE-172: restore-rb - Chairs Solicit Alternate Proposals or Counter-Proposals (from mjs@apple.com on 2012-01-11)
  37. Re: HTML5 implementor feedback requested - title attribute recommendations and requirements (from faulkner.steve@gmail.com on 2011-12-18)
  38. RE: HTML5 implementor feedback requested - title attribute recommendations and requirements (from Paul.Cotton@microsoft.com on 2011-12-17)
  39. HTML5 implementor feedback requested - title attribute recommendations and requirements (from faulkner.steve@gmail.com on 2011-12-12)
  40. {minutes} HTML WG telecon 2011-12-01: actions and issues (from eoconnor@apple.com on 2011-12-01)
  41. {agenda} HTML WG telecon 2011-12-01: actions and issues (from Paul.Cotton@microsoft.com on 2011-11-29)
  42. ISSUE-182: footnote-recommendation - Chairs Solicit Proposals (from Paul.Cotton@microsoft.com on 2011-11-29)
  43. HTML-ISSUE-182: Advice in spec about annotations promotes inaccessible content [HTML 5 spec] (from sysbot+tracker@w3.org on 2011-11-22)

Related notes:

It appears that the following is the bug that is the one being escallated:

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13650

Sam Ruby, 22 Nov 2011, 16:32:08

Closed without prejudice for lack of a Change Proposal.

Maciej Stachowiak, 12 Jan 2012, 07:47:18

had wrong bug link in there

Steve Faulkner, 13 Jan 2012, 14:27:22

[glenn]: footnote-recommendation call for Alternate or Counter Proposals closed Feb 16

23 Feb 2012, 17:04:12

[glenn]: footnote-recommendation, Call for Consensus closes Feb 29

23 Feb 2012, 17:07:29

http://html5.org/tools/web-apps-tracker?from=7055&to=7056

Sam Ruby, 25 Apr 2012, 11:48:13

Changelog:

Created issue 'Advice in spec about annotations promotes inaccessible content' nickname owned by Steve Faulkner on product HTML 5 spec, description 'The section 4.13.5 Footnotes http://dev.w3.org/html5/spec/Overview.html#footnotes of the HTML5 specification recommends the use of a markup antipattern that makes it impossible for some user groups and very difficult for some other user groups to access footnote content. It advocates the use of the title attribute, yet historically and currently title attribute content is not available to a range of users. there is no indication from implementors that this is likely to change.

The spec text in question needs to be modified or removed:

"For short inline annotations, the title attribute should be used.

In this example, two parts of a dialogue are annotated with footnote-like content using the title attribute.

<p> <b>Customer</b>: Hello! I wish to register a complaint. Hello. Miss?
<p> <b>Shopkeeper</b>: <span title="Colloquial pronunciation of 'What do you'"
>Watcha</span> mean, miss?
<p> <b>Customer</b>: Uh, I'm sorry, I have a cold. I wish to make a complaint.
<p> <b>Shopkeeper</b>: Sorry, <span title="This is, of course, a lie.">we're
closing for lunch</span>."

escalated from Bug 704416 - HTML acronym and abbr names should be provided by @title https://bugzilla.mozilla.org/show_bug.cgi?id=704416
' non-public

Steve Faulkner, 22 Nov 2011, 15:27:45

nickname changed to 'footnote-recommendation'

Sam Ruby, 22 Nov 2011, 16:32:08

Product changed to pre-LC1 HTML 5 spec

Steve Faulkner, 1 Dec 2011, 15:40:00

Status changed to 'closed'

Maciej Stachowiak, 12 Jan 2012, 07:47:18

Description changed to 'The section 4.13.5 Footnotes http://dev.w3.org/html5/spec/Overview.html#footnotes of the HTML5 specification recommends the use of a markup antipattern that makes it impossible for some user groups and very difficult for some other user groups to access footnote content. It advocates the use of the title attribute, yet historically and currently title attribute content is not available to a range of users. there is no indication from implementors that this is likely to change.

The spec text in question needs to be modified or removed:

"For short inline annotations, the title attribute should be used.

In this example, two parts of a dialogue are annotated with footnote-like content using the title attribute.

<p> <b>Customer</b>: Hello! I wish to register a complaint. Hello. Miss?
<p> <b>Shopkeeper</b>: <span title="Colloquial pronunciation of 'What do you'"
>Watcha</span> mean, miss?
<p> <b>Customer</b>: Uh, I'm sorry, I have a cold. I wish to make a complaint.
<p> <b>Shopkeeper</b>: Sorry, <span title="This is, of course, a lie.">we're
closing for lunch</span>."

escalated from Bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=13650
'

Steve Faulkner, 13 Jan 2012, 14:27:22

Status changed to 'open'

Sam Ruby, 18 Jan 2012, 01:34:32

Status changed to 'closed'

Sam Ruby, 25 Apr 2012, 11:48:13


Paul Cotton <Paul.Cotton@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Sam Ruby <rubys@intertwingly.net>, Chairs, Michael[tm] Smith <mike@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $