- From: Janina Sajka <janina@rednote.net>
- Date: Mon, 09 Dec 2013 15:01:49 +0000
- To: Joanmarie Diggs <jdiggs@igalia.com>
- CC: PFWG Public Comments <public-pfwg-comments@w3.org>
Dear Joanmarie Diggs:
Thank you for your comments on the 5 November 2013 Last Call Working Draft
of WAI-ARIA 1.0 User Agent Implementation Guide
(http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/). The
Protocols and Formats Working Group has reviewed all comments received on
the draft. We would like to know whether we have understood your comments
correctly and whether you are satisfied with our resolutions.
Please review our resolutions for the following comments, and reply to us
by 13 December 2013 to say whether you accept them or to discuss additional
concerns you have with our response. If we do not hear from you by that
date, we will mark your comment as "no response" and close it. If you need
more time to consider your acknowledgement, please let us know. You can
respond by email to public-pfwg-comments@w3.org (be sure to reference our
comment ID so we can track your response). Note that this list is publicly
archived.
Please see below for the text of comments that you submitted and our
resolutions to your comments. Each comment includes a link to the archived
copy of your original comment on
http://lists.w3.org/Archives/Public/public-pfwg-comments/.
Note that if you still strongly disagree with our resolution on an issue,
you have the opportunity to file a formal objection (according to 3.3.2 of
the W3C Process, at
http://www.w3.org/2005/10/Process-20051014/policies.html#WGArchiveMinorityViews)
to public-pfwg-comments@w3.org. Formal objections will be reviewed during
the candidate recommendation transition meeting with the W3C Director,
unless we can come to agreement with you on a resolution in advance of the
meeting.
Thank you for your time reviewing and sending comments. Though we cannot
always do exactly what each commenter requests, all of the comments are
valuable to the development of WAI-ARIA 1.0 User Agent Implementation
Guide.
Regards,
Janina Sajka, PFWG Chair
Michael Cooper, PFWG Staff Contact
Comment 428: 4.1. Focus States and Events Table - focus mapping
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 4.1. Focus States and Events Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#focus_state_event_table>
Status: Accepted proposal
-------------
Your comment:
-------------
The draft text for ATK/AT-SPI "focus event" currently states:
object:state-changed:focused or object:focus
Nit: It's focus: not object:focus.
--------------------------------
Response from the Working Group:
--------------------------------
We agree, and since this is an editorial modification only, it will be made
in time for the proposed recommendation status of the document.
----------------------------------------------------------------------
Comment 429: 4.1. Focus States and Events Table - focus event
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 4.1. Focus States and Events Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#focus_state_event_table>
Status: Alternate action taken
-------------
Your comment:
-------------
The focus: event is deprecated. If user agents wish to continue emitting
this event for older screen readers, fine. However:
The object:state-changed:focused event is required regardless of what
decision is made with respect to focus: events.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 430: 5.4.1 Role Mapping Table
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role article should not be exposed as ROLE_DOCUMENT_FRAME. A document frame
is not a section of a page. Moreover, as the ATK documentation states for
this role:
ATK_ROLE_DOCUMENT_FRAME
The object is a visual frame or container which contains a view of document
content. Document frames may occur within another Document instance, in
which case the second document may be said to be embedded in the containing
instance. HTML frames are often ROLE_DOCUMENT_FRAME. Either this object, or
a singleton descendant, should implement the Document interface. Since:
ATK-1.11.
It would not be appropriate for an article to implement the Document
interface.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 431: 5.4.1 Role Mapping Table - landmark
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role banner can be mapped to the new ROLE_LANDMARK that has been added to
both ATK and AT-SPI2. The xml-roles:banner object attribute should remain
so that the type of landmark can be identified.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 432: 5.4.1 Role Mapping Table - checkbox
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role checkbox: The use of an object attribute to expose a state (checkable)
is not ideal. In the case of checkboxes, it is not needed because ATs
assume that checkboxes are checkable. Having said that, because there are
other objects that are checkable but which lack a role suggesting that, we
have added a new state to both ATK and AT-SPI2: STATE_CHECKABLE.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 433: 5.4.1 Role Mapping Table - combobox
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role combobox: As with checkbox, we have added a new state to both ATK and
AT-SPI2: STATE_HAS_POPUP.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 434: 5.4.1 Role Mapping Table - heading
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Accepted proposal
-------------
Your comment:
-------------
Role heading: lacks documentation as to how to expose the level. (object
attribute, level:<value>)
--------------------------------
Response from the Working Group:
--------------------------------
The heading role is documented as supporting the aria-level property [1].
The UAIG defines the mapping of aria-level in 5.5.1 State and Property
Mapping table [2], where aria-level is mapped as:
"Expose as object attribute level:<value>".
We propose to add link text to the heading role mappings to provide access
to the aria-level mappings, for example:
"The heading level is specified by the <a href="#ariaLevel">aria-level</a>
property.
[1] http://www.w3.org/WAI/PF/aria/roles#heading
[2]
http://www.w3.org/TR/wai-aria-implementation/#mapping_state-property_table
----------------------------------------------------------------------
Comment 435: 5.4.1 Role Mapping Table - listbox
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role listbox: Should be ROLE_LIST_BOX. This role is not new; it is already
in ATK and AT-SPI2 stable.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 436: 5.4.1 Role Mapping Table - log
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role log: We have added ROLE_LOG to both ATK and AT-SPI2.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 437: 5.4.1 Role Mapping Table - marquee
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role marquee: ROLE_ANIMATION does not seem like a good fit. According to
the ATK documentation:
ATK_ROLE_ANIMATION
An object which is an animated image
But according to the current draft docs for the marquee role, this is
a live region which can include textual content (e.g. stock tickers).
So while it's animation-like; a marquee is not really an animation.
There isn't a great alternative to ROLE_ANIMATION, so we added a new
ROLE_MARQUEE to ATK and AT-SPI2.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 438: 5.4.1 Role Mapping Table - math
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role math: Currently mapped to ROLE_UNKNOWN with no way for an AT to
identify that it is math. User agents should expose something. Those
sticking with stable could presumably do so via an object attribute.
But we have added ROLE_MATH to ATK and AT-SPI2.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 439: 5.4.1 Role Mapping Table - menus
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role menu item, menuitemcheckbox, and menuitemradio. Prefer the new
STATE_CHECKABLE over the object attribute.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 440: 5.4.1 Role Mapping Table - navigation
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role navigation. Prefer the new ROLE_LANDMARK. Continue exposing the
xml-roles:navigation so ATs know what kind of landmark it is.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 441: 5.4.1 Role Mapping Table - note
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role note. Should be ROLE_COMMENT:
ATK_ROLE_COMMENT
An object found within a document and designed to present a
comment, note, or other annotation. In some cases, this object
might not be visible until activated. Since: ATK-2.1.0
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 442: 5.4.1 Role Mapping Table - radiogroup
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role radiogroup. Should be ROLE_GROUPING; not ROLE_PANEL:
ATK_ROLE_GROUPING
A group of related widgets. This group typically has a label.
Since: ATK-2.1.0
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 443: 5.4.1 Role Mapping Table - row
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role row. Should be ROLE_TABLE_ROW; not ROLE_LIST_ITEM:
ATK_ROLE_TABLE_ROW
A row in a table. Since: ATK-2.1.0
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 444: 5.4.1 Role Mapping Table - timer
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role timer. We added ROLE_TIMER to ATK and AT-SPI2.
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
----------------------------------------------------------------------
Comment 445: 5.4.1 Role Mapping Table - treeitem
Date: 2013-12-02
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0001.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4.1. Role Mapping Table <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/#mapping_role_table>
Status: Alternate action taken
-------------
Your comment:
-------------
Role treeitem. Should be ROLE_TREE_ITEM; not ROLE_LIST_ITEM:
ATK_ROLE_TREE_ITEM
An object that represents an element of a tree.
Since: ATK-2.1.0
--------------------------------
Response from the Working Group:
--------------------------------
This comment requires a substantive change that, according to W3C Process,
would require us to return the document for further work. Doing so would
delay the finalization of this document by several months, which would in
turn delay the preparation of ARIA 1.1 which is currently where the Working
Group plans to address newer issues. In order to avoid these delays, we
will not make this change now but will address it in a 1.1 draft in early
2014.
Received on Monday, 9 December 2013 15:01:55 UTC