Re: Focus indicators for large editing areas #2017

>  Is a multi-line editing area a “user interface component”?

I would say yes. I think for simplicity that we would just require the same
focus requirements on that large component, understanding that it might or
might not be useful... users of magnifiers might not get much valu out of
it, but there are controls to bump up the caret in most magnifying AT.

I'm not keen on making the SC more complicated for an edge case... I
would say it's already the most complicated SC in the history of WCAG since
1998.

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*
Mobile:  613.806.9005

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



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

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>


On Wed, Sep 15, 2021 at 7:23 PM Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi everyone,
>
>
>
> I’m looking for some ideas on this issue which Michael Gower raised:
>
> https://github.com/w3c/wcag/issues/2017
>
>
>
> Consider a large editing area, e.g. a blog post or code editor which has a
> caret (indicator of where the text-entry is). Should that be required to
> have a focus indicator proportional to the entire editing area?
>
>
>
> For small text inputs we have text in the understanding which say
> (paraphrasing) that a caret is not a sufficient indicator. That is a good
> thing for a user filling in multiple small inputs.
>
>
>
> However, a large editing area seems like a different scenario, a bit like
> the note we added for target size about spatially based targets.
>
>
>
> Is a multi-line editing area a “user interface component”? (I think yes,
> but perhaps we need to separate it for multi-line editors?)
>
>
>
> Kind regards,
>
>
>
> -Alastair
>
>
>
> --
>
>
>
> @alastc / www.nomensa.com
>
>
>