WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Insertion Point while editing

for

From: Sowmya D C
Date: Dec 1, 2022 10:34PM

Yes Patrick,

This is infact a mobile bsoftware application. Are you saying that its not
a WCAG violation but would be a Section 508 violation? Also, I couldn't
find much on the Section 502.3 except for few lines over internet, do you
have a mirror link or something where I can read it in detail?

Thanks.

On Thursday, December 1, 2022, Patrick H. Lauke < <EMAIL REMOVED> >
wrote:

> On 01/12/2022 13:05, Sowmya D C wrote:
>
>> Hello everyone,
>>
>> First time post here.
>>
>> Would it fail under WCAG or Section 508 if the insertion cursor point is
>> not announced by screen reader ( such as insertion point at start,
>> insertion point at end etc ) while on editing? If so, which is the
>> suitable
>> guideline to fail it under? Additionally, are there some screen reader
>> features that helps screen reader users place cursor at different
>> positions
>> other than charcter key method.
>>
>> Any comments and thoughts would be greatly appreciated!
>>
>
> For web content, there's definitely nothing applicable (as how this sort
> of thing is announced is dependent on the browser/OS/AT).
>
> However, if this is about an actual piece of software, there's various
> bits under Section 508 Chapter 5: Software (e.g. 502.3 Accessibility
> Services) that I believe touch on this sort of thing (how things like
> cursor/editing is conveyed)
>
> P
> --
> Patrick H. Lauke
>
> https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
> > > > >