Re: Essential Controls

Jon,

I believe the intent of this SC was that scrolling of any kind, including
auto-scrolling, would not be needed.  That makes designing long forms with
numerous optional fields more difficult to design for but other techniques
such as pagination, collapsible, and thoughtful placement of required
fields within the process can be used to address this SC.

Regards,

Rachael

On Thu, Jul 18, 2019 at 3:31 PM Jonathan Avila <jon.avila@levelaccess.com>
wrote:

> Rachael, Interesting, thanks for sharing.   Do you expect that this might
> require some auto scrolling?  For example, once the user fills out all
> fields the submit button has to scroll into view?  How might auto-scrolling
> be problematic for other user groups such as users with low vision or
> people sensitive to movement?
>
>
>
> Jon
>
>
>
> *From:* Rachael Bradley Montgomery <rachael@accessiblecommunity.org>
> *Sent:* Thursday, July 18, 2019 2:52 PM
> *To:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* Essential Controls
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
> Hello,
>
>
>
> Based on feedback from the AG working group and the COGA task force, I
> revised the 2.2 SC Proposal for Essential Controls
> <https://docs.google.com/document/d/1DPtCqWHjrhj3QZ4afsqzmWDd-zMSf39RsMqSpR2QGCg/edit#heading=h.4vsa10j1zo6f>.
> If you have time, I'd appreciate further comments and suggestions from the
> group.
>
>
>
> Best regards,
>
>
>
> Rachael
>
>
>
> --
>
> Rachael Montgomery, PhD
>
> Director, Accessible Community
>
> rachael@accessiblecommunity.org
>
>
>
>
>


-- 
Rachael Montgomery, PhD
Director, Accessible Community
rachael@accessiblecommunity.org