Re: More comments on Mobile examples

On Nov 8, 2012, at 12:44 AM, Greg Lowney <gcl-0039@access-research.org> wrote:

Hi! Per our last call, here are a few more comments on the mobile examples marked with $$ in ED-IMPLEMENTING-UAAG20-20121012:


1. Re 2.7.4 Change preference settings outside the user interface, "$$ Jan is easily confused by new interfaces. She tries out the voiceover capabilities on her mobile phone, but then can't figure out how to turn them off. She connects the device to her computer and restores the default settings.":

this seems not to be a good example because voiceover can be dismissed with a triple click of the home key if it is "voiceover on iOs to which is being referred.

    If "voiceover" is supposed to mean the specific feature on iOS it should be capitalized appropriately and called a feature instead of capabilities, but if it’s meant to be a generic self-voicing feature then we should use a more genetic term. 


2. Re 2.11.1 Background Image Toggle, "$$ Betty is a low vision user and has difficulty reading text on her mobile device when it is displayed over a background image. Using her user-defined style sheet, she can disable all background images from being rendered in her browser.":

    There’s no reason examples like this don’t apply equally to desktop and mobile, so perhaps rephrase as "Betty is a low vision user and has difficulty reading text when it is displayed over a background image. Using her user-defined style sheet, she can disable all background images from being rendered in the browsers on her desktop and her phone."


3. Re 2.11.3 Execution Placeholder, "$$ Evan has configured his mobile phone to so that any audio or video file displays a placeholder with a triangle "play" icon, so that he can control when the audio or video starts.": 

    This would be stronger if it said why this affects his disbility. For example, "Evan has seizures that can be triggered by some types of sounds. To avoid those sounds, he has configured his mobile phone to so that any audio or video file displays a placeholder with a triangle 'play' icon, letting him control when the audio or video starts."


4. Re 3.3.2 Document Accessibility Features, "$$ Neta has a repetitive strain injury. She relies on gestures and shortcuts to complete tasks. Using a specialize command, she can pull up a list of all the gestures commands available with descriptions on how they function.":

    a. The word "specialize" should be "specialized", but since this command isn’t really more specialized than most others, you could drop that to make it simply "She can use a command to pull up a list of all the gestures commands available with descriptions on how they function." or a more specific example such as "A command is available through the browser's help system that displays list of available command gestures with descriptions of how they function. She can also use a three-finger swipe from the top of the screen to display this same list."?

    b. In truth, on mobile devices that only support touchscreen input, don't all users (not just those with motion impairments) rely on gestures and shortcuts? Or is "gestures and shortcuts" meant to imply that she can’t use the normal touchscreen commands such as tapping on an icon to bring up Help or Settings screens?  


    Thanks,
    Greg

-- 
Jonnie Appleseed
With His
Hands-On Technolog(eye)s
touching the internet
Reducing Technology's disabilities
One Byte At a time

Received on Thursday, 8 November 2012 12:44:40 UTC