WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: resources on writing accessible user guides

for

From: Karen McCall
Date: Apr 18, 2021 3:54AM

I'd also consider plain language and Easy Read guidance. One of the compliments I often get is that those who read by books and tutorials can understand what I'm talking about and guiding them through, especially technical processes.

I also use activate this or activate that as a more generic way of wording.

In terms of what I avoid. I avoid using ableist language like "enabled" and "disabled" when describing things. That is the only terminology that "grates on my nerves". 😊

I use available or not available. I can then describe why something is available or not available at a particular point in time.

Cheers, Karen

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Mallory
Sent: Sunday, April 18, 2021 3:32 AM
To: Steve Green < <EMAIL REMOVED> >; WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] resources on writing accessible user guides

In tickets to developers (I know, they think and speak different than regular users), I use the word "actived" and "activated" a lot.

However if I didn't use words like "click", none of my non-technical family members would really follow instructions very well. My family thinks they're "clicking" on buttons when they smoosh their fingers against their phone screens.

As far as "look" and "see", I haven't met a blind person yet who doesn't "watch" movies or "sees" a TV show. I'm sure they're out there, and my personal bubble is definitely more the nerds than people like my family, but I'm just piling on to agree with Pat.

cheers,
_mallory