E-mail List Archives
Thread: disabilities and accessibility
Number of posts in this thread: 9 (In chronological order)
From: Nathan Clark
Date: Wed, Feb 09 2022 11:57AM
Subject: disabilities and accessibility
No previous message | Next message →
Dear list,
My company and I are trying to create an accessible training program
for screen reader users to use our unstoppable plug in for confluence
and Jira. We are in the brainstorming portion of this project. One of
my developers posed this question to me and I was kind of stumped on
to answer him. He asked me the following:
question: Is there a specific disability that should be focused on
first or do we need to approach this as an all or nothing accessible
training? Basically, should we focus on making our training accessible
for a specific disability or should we try and focus on all of them?
The way I look at this and I may be wrong is that it is hard to
accommodate all disabilities and all user capabilities therefore you
should try and pick what disabilities that you think would more likely
to use the product? Can someone please tell me what the best approach
is? Thanks.
Sincerely,
Nathan Clark
--
Nathan Clark
QA Automation Analyst Tech team
Accessibility assistant
CPACC
cell: 410-446-7259
email: = EMAIL ADDRESS REMOVED =
101 Village Blvd
Princeton, NJ 08540
SMBE & Minority Owned Business
--
<https://www.eventbrite.com/e/discover-the-secret-of-high-performing-software-teams-tickets-22539850299>
--
From: Lucy GRECO
Date: Wed, Feb 09 2022 12:02PM
Subject: Re: disabilities and accessibility
← Previous message | Next message →
NOVER FOCUS ON ONE DISABILITY
Berkeley IT <https://technology.berkeley.edu/home>
Lucy Greco, Web Accessibility Evangelist
Campus IT Experience
Phone: (510) 289-6008 | Email: = EMAIL ADDRESS REMOVED = |
https://webaccess.berkeley.edu Follow me on twitter @accessaces
We champion diversity. We act with integrity. We deliver. We innovate.
On Wed, Feb 9, 2022 at 10:57 AM Nathan Clark < = EMAIL ADDRESS REMOVED = >
wrote:
> Dear list,
>
> My company and I are trying to create an accessible training program
> for screen reader users to use our unstoppable plug in for confluence
> and Jira. We are in the brainstorming portion of this project. One of
> my developers posed this question to me and I was kind of stumped on
> to answer him. He asked me the following:
>
> question: Is there a specific disability that should be focused on
> first or do we need to approach this as an all or nothing accessible
> training? Basically, should we focus on making our training accessible
> for a specific disability or should we try and focus on all of them?
>
> The way I look at this and I may be wrong is that it is hard to
> accommodate all disabilities and all user capabilities therefore you
> should try and pick what disabilities that you think would more likely
> to use the product? Can someone please tell me what the best approach
> is? Thanks.
>
> Sincerely,
> Nathan Clark
>
>
>
> --
> Nathan Clark
> QA Automation Analyst Tech team
> Accessibility assistant
> CPACC
> cell: 410-446-7259
> email: = EMAIL ADDRESS REMOVED =
> 101 Village Blvd
> Princeton, NJ 08540
> SMBE & Minority Owned Business
>
> --
>
> <
> https://www.eventbrite.com/e/discover-the-secret-of-high-performing-software-teams-tickets-22539850299
> >
>
> --
>
>
> > > > >
From: Karen McCall
Date: Wed, Feb 09 2022 12:08PM
Subject: Re: disabilities and accessibility
← Previous message | Next message →
I agree with Lucy...my training and teaching has always been to optimize accessibility for the broadest range of people. You never know when someone with a disability is in your audience. Trying to prioritize access to digital content for a specific group of people is never a winning scenario.
Cheers, Karen
From: L Snider
Date: Wed, Feb 09 2022 12:25PM
Subject: Re: disabilities and accessibility
← Previous message | Next message →
Totally agree with Lucy and Karen! I cover a wide range and even ones that
are rare or that others wouldn't consider a disability....remember many
people have multiple disabilities...
I am trying to find the source, but a few years ago, I read that 60-70% of
people who answered a survey identified with multiple disabilities. Also
some people have them and don't identify with disabilities they may
have...complex thing is the human!
Cheers
Lisa
On Wed, Feb 9, 2022 at 3:08 PM Karen McCall < = EMAIL ADDRESS REMOVED = > wrote:
> I agree with Lucy...my training and teaching has always been to optimize
> accessibility for the broadest range of people. You never know when someone
> with a disability is in your audience. Trying to prioritize access to
> digital content for a specific group of people is never a winning scenario.
>
> Cheers, Karen
>
>
From: Nathan Clark
Date: Wed, Feb 09 2022 12:29PM
Subject: Re: disabilities and accessibility
← Previous message | Next message →
thanks for the comments. I thought everyone would say this. I just
wanted confirmation before I go down the phase of design and
development.
On 2/9/22, L Snider < = EMAIL ADDRESS REMOVED = > wrote:
> Totally agree with Lucy and Karen! I cover a wide range and even ones that
> are rare or that others wouldn't consider a disability....remember many
> people have multiple disabilities...
>
> I am trying to find the source, but a few years ago, I read that 60-70% of
> people who answered a survey identified with multiple disabilities. Also
> some people have them and don't identify with disabilities they may
> have...complex thing is the human!
>
> Cheers
>
> Lisa
>
> On Wed, Feb 9, 2022 at 3:08 PM Karen McCall < = EMAIL ADDRESS REMOVED = > wrote:
>
>> I agree with Lucy...my training and teaching has always been to optimize
>> accessibility for the broadest range of people. You never know when
>> someone
>> with a disability is in your audience. Trying to prioritize access to
>> digital content for a specific group of people is never a winning
>> scenario.
>>
>> Cheers, Karen
>>
>>
From: David Engebretson Jr.
Date: Wed, Feb 09 2022 7:49PM
Subject: Re: disabilities and accessibility
← Previous message | Next message →
Cool thing is that the WCAG WAI interest group defines this for us. It tries to evaluate web accessibility issues from a disability agnostic perspective. At least that is how I see it.
I think that if we all follow, implement recommendations of, and contribute to the WAI then we can change how the WCAG standards are applied; we can help people with disabilities who have undefined disabilities, we can help those who have known disabilities, and we can even help those who don't have or are unwilling to admit they have a disability.
When designing a digital technology I say, follow the WAI work... WCAG, ARIA, and ATAG (https://www.w3.org/WAI/standards-guidelines/).
Then, at the very least, you are working with an official source of experts in accessible digital technologies.
Thanks!
David
From: Mark Magennis
Date: Thu, Feb 10 2022 4:23AM
Subject: Re: disabilities and accessibility
← Previous message | Next message →
I would add that focussing on a solution that works for one type of disability can actually make things worse for other types. For example, aspects of the visual presentation that aren't accessible to some blind user may be essential for some users with cognitive disabilities.
From: Morin, Gary (NIH/NCI) [E]
Date: Thu, Feb 10 2022 12:11PM
Subject: Re: disabilities and accessibility
← Previous message | Next message →
Couldn't agree more - not to dismiss one group in favor of another. There is a paradigm that if websites are made compatible with ScreenReaders then they're compatible with and accessible to speech recognition software, used by persons with dexterity impairments. It's a false paradigm and one that clearly fails in reality. To this day, I'm finding websites and applications that may or allegedly work with ScreenReaders that are NOT accessible to speech input or speech recognition software (such as Dragon NaturallySpeaking).
ScreenReader users may be more vocal or organized but that may or may not mean that the numbers of ScreenReader users versus speech input users are greater one way or the other.
No one individual or group should take precedence or priority over another.
Gary
From: Schulz, Leslie
Date: Fri, Feb 11 2022 12:17PM
Subject: Re: disabilities and accessibility
← Previous message | No next message
The problem with pages coded for screen readers not working for speech recognition has to do with understanding how speech recognition works.
A screen reader user can navigate to a link with an aria-label that states: "Additional Information about product x". But if the link text reads, "Read More" under a photo of the product, the speech recognition user will not be able to activate the link. The aria-label must include the text from the visible link, although the aria-label can, and probably should, include more.
A better match would be
<a href="product-x.html" aria-label="More information about product X">More information</a>
That being said, if developers are unaware of the way speech recognition works, their efforts to please both screen reader users and speech recognition users will always be hit or miss.
Just some thoughts.
Leslie