- From: timeless <timeless@gmail.com>
- Date: Sun, 7 Jun 2015 11:56:54 -0400
- To: public-pfwg-comments@w3.org
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#button > A common convention for informing users that a button launches a dialog is to append "…" (ellipsis) to the button label, e.g., ."Save as …". * You have a stray period before `"Save as …` * The convention is that if there's a dialog that will interfere with an activity, show `…` -- the `…` aren't to be shown if the dialog is the final state. A simple example is that "About" is often a dialog, it won't have `…`. > In this example, when the pressed state is true, the label should not change to "Unmute"" or "Muted." There's a stray `"` after `"Unmute"` > If activating the button does not dismiss the current context, then focus should typically remain on the button after activation, e.g., an Apply or Recalculate button. Typically `Apply` should be disabled after use, since there are no changes to be Applied once it's triggered. It's generally poor form to focus a disabled button. > However, it can also be provided with aria-labelledby" or aria-label. there's a stray `"` here > When the action associated with a button is unavailable, the button displays in a aria-disabled state. `in a` => `in an` > If all options in the group are checked, the overall state is represented by the tri-state checkbox displaying as checked . Stray ` ` before `.`
Received on Sunday, 7 June 2015 15:57:22 UTC