Re: WAI needs to address email explicitly

Dear Anna and George,
You have already identified problem areas I hadn't listed. When I was a
member of WAI EOWG and then AGWG I found it was hard to notify the groups
of problems because the groups would immediately jump to the feasibility of
solving the problem.
I am envisioning a Community Group that identifies and classifies problems
with technology, specifically software. This group would probably be
overwhelmed quickly, because there are lots of bottlenecks. Also, people do
report problems that cannot be solved by IT policy.

I've just come to the conclusion that identifying and solving software
issues are different jobs. We need a way to clear issues for ultimate
solutions by some other group.

Best, Wayne


On Wed, May 26, 2021 at 8:15 AM <kerscher@montana.com> wrote:

> Hello,
>
>
>
> I am not sure of the scope of this thread, but as a screen reader user, I
> struggle with highly formatted emails. Delta, Alaska, Costco, etc. are most
> difficult to navigate and use. I expect is because of the heavy use of
> tables for layout in the emails.
>
>
>
> Best
>
> George
>
>
>
>
>
> *From:* Anna Somos-Feliz <anna.somosfeliz@gmail.com>
> *Sent:* Monday, May 24, 2021 4:21 PM
> *To:* Wayne Dick <wayneedick@gmail.com>
> *Cc:* W3C WAI ig <w3c-wai-ig@w3.org>
> *Subject:* Re: WAI needs to address email explicitly
>
>
>
> I'd like to see some talk about immersable reader. The fact that the
> formats now available to adjust are not printable or shareable in the way
> that you set them up to assist. I think the whole lot of the systems, like
> you've pointed out need to be consistent. Young people worry that they are
> not going to have the diverse skills to use a majority of systems so they
> aren't utilising accessibility options, which would see them have less
> cognitive load and increase, for our case language use (DLD).
>
>
>
> Regards,  Anna.
>
>
>
>
>
> .
>
>
>
>
>
>
>
>
>
>
>
>
>
> .
>
>
>
>
>
>
>
>
>
> On Tue, 25 May 2021, 4:06 am Wayne Dick, <wayneedick@gmail.com> wrote:
>
>
>
> 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
>
>