WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Augmentative and alternative communication

for

Number of posts in this thread: 4 (In chronological order)

From: Michael Ausbun
Date: Fri, May 22 2020 1:42PM
Subject: Augmentative and alternative communication
No previous message | Next message →

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

From: Michael Ausbun
Date: Fri, May 22 2020 2:03PM
Subject: Re: Augmentative and alternative communication
← Previous message | Next message →

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 ADDRESS REMOVED = > On Behalf Of Michael Ausbun
Sent: Friday, May 22, 2020 2:42 PM
To: WebAIM Discussion List < = EMAIL ADDRESS 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

From: Marissa Goldsmith
Date: Fri, May 22 2020 7:18PM
Subject: Re: Augmentative and alternative communication
← Previous message | Next message →

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 ADDRESS 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 ADDRESS REMOVED = > On Behalf Of
> Michael Ausbun
> Sent: Friday, May 22, 2020 2:42 PM
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> > > > >

From: Jonathan Avila
Date: Tue, May 26 2020 4:47PM
Subject: Re: Augmentative and alternative communication
← Previous message | No next message

I believe people who use AAC might benefit from familiar icons being used on the site they are accessing. Also the software that takes icon based input from the user may need to convert that into text or numeric input on the website. So I'd imagine correct and specific input type as well as input purpose (WCAG 2.1 SC 1.3.5) would be important for compatibility with such assistive technology.

Jonathan

-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Michael Ausbun
Sent: Friday, May 22, 2020 3:42 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] Augmentative and alternative communication

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.


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