Re: WAI needs to address email explicitly

Now that AG addresses accessibility in general, it may be time to address
as Patrick points out platform applications in a small screen framework.
Web applications are actually special cases of these programs where the
platform is not a machine but web servers.
Aside from email, there are many program app categories that are
bottlenecks: IDEs, CAD programs, Photo Editors, Version Controlers, ebooks,
ebook players, Content Management Systems, and Learning Management
Systems... There are certainly more.
Also, we also need not forget original WCAG 1 and 2 issues plus cognitive
issues. How do specific functional categories interact with these issues?

People's employment depends on operating these programs. I am retired, so I
just get a little miffed at email. Young people's professional careers
depend on being able to use this software. Most users don't have the skills
of the disability representatives on the W3C. We need a mechanism to hear
from people who cannot creat work arounds.

Best, Wayne


On Mon, May 24, 2021 at 10:17 AM Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> On 24/05/2021 17:20, Wayne Dick wrote:
> > None of the major email clients are accessible to people with low
> > vision. The Apple Client, Google GMail client, and MS Outlook all fail
> > to provide access. I think everyone has their own work arounds, but this
> > is a bottleneck issue. It shuts people out of meaningful discussion.
>
> To add to this/avoid the same confusion I had at the time this was first
> mentioned: this would be about actual *native* email client
> applications, and having them adapt to small viewports/allow for user
> interface etc of the application allowing zooming. So conceptually, UAAG
> 2.0 related / WCAG 3.0 related.
>
> 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
>
>