Re: finishing up MS04 - Spell Check

Here is the revised text for *3.2.3 Spell Check* that we approved on today's call, and suggested expansion of its Intent section (the first paragraph being untouched, everything after that being new):

    *3.2.3 Spell Check:* The user can have spelling assistance for editable text in rendered content. (Level AA)
    *
    **Intent of Success Criterion 3.2.3:*

        Users with various disabilities benefit from spell checkers. The ability to check spelling is particularly important for users with disabilities such as dyslexia that significantly increase the likelihood of misspelled words. Spellcheckers also alert blind and low vision users to errors in text entry.

        Spell checking is only expected in editable text in content, most commonly text input controls and form fields. It is not required on text input fields that are part of the UA user interface, such as an address bar or File Open dialog box. Spell checking is also not required on static, read-only, or disabled text elements, controls, and fields in content, except when they display text the user can edit indirectly (e.g. static text that the user can alter using nearby buttons), or when the user agent is in an authoring mode that allows the user to edit text that would otherwise be static.

        Spell checking should be available regardless of how the text was entered. For example, text may be entered by the user typing, pasted from the clipboard, initialized by the content (e.g. the HTML value attribute), set programmatically by scripts or assistive technology, or filled in by a feature of the user agent itself (e.g. auto-complete).

        Spell checking which highlights unrecognized words as they are entered is preferred over requiring the user to use a separate tool or editing pass.

        Spell checking should be optional, so that it can be avoided by users who find it too distracting, or for whom the highlighting makes the text less legible.

        Note: It is recommended that user agents also provide assistance with grammar, as well as spelling. Grammar can pose more difficulty than spelling for people with some cognitive disabilities or whose native language is signed.


     Thanks,
     Greg

-------- Original Message --------
Subject: Re: finishing up MS04 - Spell Check
From: Greg Lowney <gcl-0039@access-research.org>
To: Jeanne Spellman <jeanne@w3.org>, UAWG <w3c-wai-ua@w3.org>
Date: 9/3/2014 10:43 PM
> Re 3.2.3 Spell Check, on a purely editorial level we changed all the other SC to no longer use the wording "User agents provide"; instead, almost all use variations on "The user can". I definitely don't think it's appropriate to say "UA user interface provides" the spell checking, given that it's provided by the UA but in content, rather than in the UA UI, and while everything is ultimately implemented by the UA, it's no more specific to the UA UI than any other feature.
>
> Also, I’m leery of the phrase "text created inside the user agent". Ideally spell checking would be available on any recognized text input field/control, regardless of whether the text was "created" by the user typing, or by pasting text that was created and copied from elsewhere, by assistive technology that changed the control's value programmatically, or by a feature of the user agent itself (such as auto-complete). Especially in this last case, it doesn't matter if the text were created by the user or by the user agent, as long as it ends up in a text input control in content. In contrast, we don't expect spell checking on every text input field in the UA user interface, such as the address bar or the File Open dialog box. Similarly, we don't expect spell checking on static text controls in content, regardless of whether the text is created by the user agent or by the content (e.g. scripts), except when it's showing text the user can still edit directly or indirectly 
> (e.g. static text that's part of a composite control, showing text that the user cannot edit directly but can edit using nearby buttons).
>
> Also, could we at least recommend that user agents also provide assistance with grammar, in addition to the assistance with spelling? For many people with cognitive disabilities or whose native language is signed, written grammar is at least as difficult as spelling.
>
>     Thanks,
>     Greg
>
> -------- Original Message --------
> Subject: finishing up MS04
> From: Jeanne Spellman <jeanne@w3.org>
> To: UAWG <w3c-wai-ua@w3.org>
> Date: 9/2/2014 12:25 PM
>> MS04 (be clear what is user interface and what is rendered content)
>> We fixed our definitions, but MS04 also pointed out SC where we were not specific which applied.  I propose the following:
>>
>> 3.2.2 Back button.  Added sentence to Intent "The Back feature is a part of the user agent user interface instead of the rendered content, however, authors should not "break" the Back button by disabling it, or creating sequences of web pages that would cause an error if the Back button were used. "
>>
>> 3.2.3 Spell Check: User agents provide spell checking functionality for text created inside the user agent.
>> Changed to: "UA user interface provides... "  [UA user interface is linked to the definition]
>>
>> 2.2.1 Sequential Navigation Between Elements: The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the current viewport. (Level A)
>> Change to "...all recognized enabled elements in the rendered content of the current viewport."  [rendered content is linked to definition]
>>
>>
>>
>