E-mail List Archives
Re: Web Accessibility For Notetakers
From: Cliff Tyllick
Date: Nov 19, 2015 10:34AM
- Next message: Cliff Tyllick: "Re: Web Accessibility For Notetakers"
- Previous message: Paul Adam: "Re: Does WCAG require that when you click a label it checks the checkbox or radio button?"
- Next message in Thread: Cliff Tyllick: "Re: Web Accessibility For Notetakers"
- Previous message in Thread: _mallory: "Re: Web Accessibility For Notetakers"
- View all messages in this Thread
You made no mistakes, Ella. I apologize for forgetting that not all forms of humor are easy to understand online.
Actually, I was strongly agreeing with you.
If an interface causes you to stop and think about how it is supposed to work, then it is not as usable as it should be. So even a little weird is too weird, as I consider it.
Thanks for participating!
Cliff
Sent from my iPhone
Although its spellcheck often saves me, all goofs in sent messages are its fault.
> On Nov 19, 2015, at 9:55 AM, Ella Yu < <EMAIL REMOVED> > wrote:
>
> Sorry for my mistakes. What I mean is some of the elements are a little weird, but nothing terrifying.
>
> ----- Original Message -----
> From: Cliff Tyllick < <EMAIL REMOVED>
> To: WebAIM Discussion List < <EMAIL REMOVED>
> Date sent: Thu, 19 Nov 2015 01:10:37 -0600
> Subject: Re: [WebAIM] Web Accessibility For Notetakers
>
> "Ever so slightly too complicated"?
>
> Ella, in many cases that's an extreme understatement. Whenever I have given a presentation, I have found myself showing one example of an interface that is too complicated for everyone. (It's never the same example. Often, I find an example that is actually easier to figure out if you rely on a screen reader but can't see the screen.)
>
> Many who read your message will infer that you mean these sites should regress to a plain format. I'm sure you aren't suggesting that. What you mean is that the available features should be easy for everyone to discover and useâor, in the parlance of WCAG 2.0, "perceive" and "operate."
>
> There are two solutions to that problem that we haven't pursued enough:
>
> 1. Site owners, content managers, designers, and developers should conduct more usability testing of their designs, and they should include people with disabilities among the participants. Those who do will make it easier for all people to use the Web.
>
> 2. The accessibility community should build and maintain an application any Web professional can use to discover known techniques for producing usable and accessible interactions in the presentation technology they are using. The same application would allow developers to submit new techniques they have used to solve a previously unsolved problem or to improve upon an existing solution. Each technique submitted should be specific; include appropriate examples of its implementation; be tagged according to the interface or interaction (form, text input, error checking, labels for fieldsets, navigation menus, and so on), the presentation technology (HTML, PDF, XHTML, Word for Windows, Open Office, Drupal, WordPress, Plone, Bootstrap.js, and so on), the presentation environments in which it works (video, audio, wearables, smart phones, large monitors, haptic interfaces, and others), the disability addressed, the relevant WCAG success criteria, and other relevant features if I've missed any; and be linked to closely related solutions, relevant tutorials, explanations of the underlying principles, and the like.
>
> This application would make it easier for all authors, content managers, designers, and developers to build a highly usable and accessible Web. It would also help us win over people who fear that it's difficult, expensive, or time consuming to build accessible, usable interactionsâbecause instead of having to stop everything to take a tutorial or figure out a checklist and its results, they could get a quick solution to their specific problem in their first experience with making their product accessible. (If there is no solution, or at least no ideal solution, they could find that out quickly and revise their plans accordingly. Maybe that means they would give this phase of their project more time. Maybe it means they would scrap the original approach and use another instead.)
>
> If the W3C won't coordinate the building of this application and then host it, the IAAP should. Rob Sinclair, the first president of the IAAP, lamented in an interview that he had once had to let a group of developers know that the solution they had worked so hard to develop was a duplicate of a solution others had developed two years earlier. With this application in place, it would be highly unlikely for that circumstance to arise again.
>
> Because even the most seasoned developer could quickly discover whether someone has finally figured out how to build a carrousel that will thrill users with its accessibility, usability, and relevance every bit as much as it thrills marketers and executives with whatever it is that thrills them about carrousels.
>
> Best regards,
>
> Cliff Tyllick
> Accessibility curmudgeon on my own time.
> In my day job, accessibility specialist for the Texas Department of Assistive and Rehabilitative Services.
>
> Sent from my iPhone
> Although its spellcheck often saves me, all goofs in sent messages are its fault.
>
> On Nov 18, 2015, at 11:38 PM, Ella Yu < <EMAIL REMOVED> > wrote:
>
> I totally agree with you, but some sites could be made somewhat simpler but still have the same features. Some sites are just ever so slightly too complicated.
>
> ----- Original Message -----
> From: "Harrison, Rita L" < <EMAIL REMOVED>
> To: WebAIM Discussion List < <EMAIL REMOVED>
> Date sent: Wed, 18 Nov 2015 21:49:22 +0000
> Subject: Re: [WebAIM] Web Accessibility For Notetakers
>
> Good Afternoon List,
>
> After reading some of the comments, I would like to share my observation and personal opinion as follows, for those who may not be familiar with Notetaking Devices.
>
> First, I absolutely agree that there is no need to make sites simpler, if they are coded correctly. Individuals using Assistive Technology (AT), should be able to navigate without a problem, provided there is proper structure and all elements are labeled.
>
> Braille Notetakers serve many other purposes than just surfing the web. Having and using a braille display is an important piece in braille literacy, which allows someone the ability to read and write with ease, as those who have vision read and write print.
>
> I personally use and have done so for years, a Braille Notetaker and find it much more portable to use when I lead and/or attend meetings, when I'm doing a formal Presentation and for taking notes on the fly.
>
> Rather than discourage someone from purchasing and using a Braille Notetaker, perhaps the focus should be on those who manufacture and sell these devices, to use a more current browser, so everyone using these wonderful devices, are able to access the information they need when they need it, because the cost of these devices is high and we should expect to be able to access information online using a current browser.
>
> I absolutely understand some of the frustration voiced here and I thank you for affording me the opportunity to share my view.
>
> I hope everyone is having a great Wednesday!
>
> Rita L. Harrison, FDA 508 Coordinator
> Lead, 508 Web Task Force
> Chairperson, Advisory Committee for Employees with Disabilities (ACED)
> OO/OIMT/DBPS/IIB
> Web Support Team (WST)
> Phone: 805-620-0203
> <EMAIL REMOVED>
>
>
- Next message: Cliff Tyllick: "Re: Web Accessibility For Notetakers"
- Previous message: Paul Adam: "Re: Does WCAG require that when you click a label it checks the checkbox or radio button?"
- Next message in Thread: Cliff Tyllick: "Re: Web Accessibility For Notetakers"
- Previous message in Thread: _mallory: "Re: Web Accessibility For Notetakers"
- View all messages in this Thread