- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Thu, 12 Nov 2015 10:36:17 -0600
- To: Matt King <a11ythinker@gmail.com>
- Cc: "'PF'" <public-pfwg@w3.org>
- Message-ID: <OFA7F4D0C8.E7874677-ON86257EFB.005AF803-86257EFB.005B3686@us.ibm.com>
Hi Matt, I am happy with the changes to document and application roles. We still need to discuss them on the call. I am not sure whether you changed it since TPAC but I like the change for "document". As I said, I was mentally out of gas due to lack of sleep when we discussed it at TPAC. There is an editorial change, nit, where you say tabindex of 0 and I thin the 0 should be in quotes like "0". Cheers, Rich Rich Schwerdtfeger From: Matt King <a11ythinker@gmail.com> To: "'PF'" <public-pfwg@w3.org>, Richard Schwerdtfeger/Austin/IBM@IBMUS Date: 11/12/2015 06:28 AM Subject: ACTION 1361 Updates to application and document roles ready for final review Here is a summary of the changes to the application and document roles for action 1361 that are ready for review in the mck_applicationRole branch[1]. Note that these changes to not "invalidate" any prior art with respect to how these roles are used. The new language is primarily intended to prevent unnecessary use of these roles and clarify what assistive technologies should be doing. 1. State that application is intended to be used only when a sufficient widget role is not available. 2. Add language that helps authors understand it is unnecessary to wrap standard widgets in an application element. 3. Change application elements from landmarks to structures. 4. Remove text that encourages applying application to the root node, but do not add a normative requirement that prohibits using application on the body element or root node. 5. Provide a realistic example that justifies use of the application role. 6. State that the document role is only useful when applied to focusable children of widgets or applications, but do not add a normative requirement that documents have a required context of widget or application. 7. Remove text that encourages applying document to the root node, but do not add a normative requirement that prohibits using document on the root node. 8. Remove the requirement that a document element have a label. Editorial changes: 1. Remove use of the word "application" from the definition of application. 2. Remove the word "document" from the definition of document. [1] http://rawgit.com/w3c/aria/mck_applicationRole/aria/aria.html#application Matt King
Attachments
- image/gif attachment: graycol.gif
Received on Thursday, 12 November 2015 16:36:52 UTC