Re: Re[2]: Should we require labels to be always visible?

I think the construct is sufficiently comprehensible visually. The
instructions/label are 10 years of math classes ...

the aria-label should have numerator and denominator in them.

David MacDonald

*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902


GitHub <> <>

*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy

On Fri, Jan 13, 2017 at 3:37 PM, White, Jason J <> wrote:

> *From:* Glenda Sims []
> *Sent:* Friday, January 6, 2017 1:54 PM
> In my book, the label can be an icon (or text).  Here is how I have our
> experts consistently call this for 3.3.2 (with some thoughts related to
> 1.3.1 and 4.1.2)
>    - Label or Instructions MUST be visible at all times to sighted users.
>    - An icon (with appropriate alternative text) can serve as a label.
>    Examples of common icons that label form fields (or user controls) include:
>    magnifying glass (for search), 3 horizontal lines on top of each other
>    (hamburger menu), gear (preferences or settings), trash can (delete or view
>    trash depending on context). Remember, these are just a few examples.
>    - A placeholder alone in a form field does not qualify as a label for
>    sighted users because it is not always present. Note: A placeholder, then
>    supplemented by a label (even if the label does not visually appear until
>    after the user focuses on the field) is enough to pass - so long as a label
>    is always programmatically associated.
> *[Jason] An interesting example that occurs here at ETS is a pair of
> fields for entering the numerical numerator and denominator of a fraction,
> arranged vertically and separated by a visible fraction line.*
> *I assume that label elements or aria-label attributes are used correctly
> to provide explicit labels for assistive technologies. The spatial layout
> of the fields and the fraction line (in an educational setting) should be
> clear to visual readers without the need for textual labels. This example
> arguably doesn’t fall into your first category (icons), although the intent
> is similar. My inclination is to regard such examples as sufficiently
> unambiguous to be worthy of satisfying any proposed success criterion in
> this area.*
> ------------------------------
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
> Thank you for your compliance.
> ------------------------------

Received on Friday, 13 January 2017 21:04:02 UTC