- From: Matthew King <mattking@us.ibm.com>
- Date: Thu, 19 Feb 2015 10:30:52 -0800
- To: WAI Protocols & Formats <public-pfwg@w3.org>
- Message-Id: <OF824025E5.EA2AE48E-ON88257DF1.00659C53-88257DF1.0065B4A7@notes.na.collabserv.c>
Current note: The aria-current attribute is similar to the aria-selected attribute, but there are important differences. For example in a listbox widget for choosing between pages of search results, aria-current would be used to indicate the option representing the currently displayed page of results, whereas aria-selected would be used to indicate the page of results the user had selected to be displayed next. Propose replacing the above with the following 3 notes. Note: Only one element in a set of elements should be marked as current with aria-current. Note: The aria-current attribute should not be used as a substitute for aria-selected in widgets where aria-selected has the same meaning. For example, in a tablist, aria-selected is used on a tab to indicate the currently displayed tabpanel. Note: In some use cases for widgets that support aria-selected, current and selected can have different meanings and may both be used within the same set of elements. For example, aria-current="page" may be used in a navigation tree to indicate which page is currently displayed while aria-selected="true" indicates which page will be displayed if the user activates the treeitem. Further, the same tree may support operating on one or more selected pages (treeitems) by way of a context menu containing options such as delete and move. Matt King IBM Senior Technical Staff Member I/T Chief Accessibility Strategist IBM BT/CIO - Global Workforce and Web Process Enablement Phone: (503) 578-2329, Tie line: 731-7398 mattking@us.ibm.com
Received on Thursday, 19 February 2015 18:31:39 UTC