WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Augmentative and alternative communication

for

From: Marissa Goldsmith
Date: May 22, 2020 7:18PM

One thing that's less a professional experience and more personal. My
daughter occasionally uses switch control to navigate on various
technologies. Probably 95% of the time, the things you concern yourself
with for keyboard navigation apply to switch navigation. But there are a
few exceptions, so may be worth considering.



Marissa Goldsmith
www.marissagoldsmith.com
<https://www.marissagoldsmith.com?utm_medium=email&utm_source=sigfile>
571-354-7746
@mjgoldsmith



On Fri, May 22, 2020 at 4:03 PM Michael Ausbun < <EMAIL REMOVED> >
wrote:

> Hi again,
> To add:
> I realize (now) I forgot to include eye-tracking software in my ask;
> which, I believe relies on mouse-esk input.
> To clarify my question:
> Are there any considerations that need to be made by developers, outside
> of the standard considerations, to ensure AAC can cross-functionally
> interact with a site/application, or, is that handle by general
> best-practices?
> Thanks again; it's been a fun but long week! Sorry for the confusion!
> Respectfully,
> Michael
>
>
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Michael Ausbun
> Sent: Friday, May 22, 2020 2:42 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: [WebAIM] Augmentative and alternative communication
>
> Good afternoon,
> I have a question regarding Augmentative and alternative communication
> devices and how people using these tools interact with web content.
> As I understand it, AAC used to interact with user interfaces rely
> programmatically on the same technology which allows for keyboard access.
> Thus, if keyboard access exists, then AAC should be able to work as well.
> Is this assumption incorrect? If so, what am I not thinking about?
> Thanks in advance!
> Respectfully,
> Michael
> > > http://list.webaim.org>;
> > http://webaim.org/discussion/archives>;
> > <EMAIL REMOVED> >
> > > > >