Tag Archives: Inclusivity

Automatic audio text transcriptions

Categorized Under: Adaptability, Technology Published on Authored by Leave a comment

In honour of Global Accessibility Awareness Day (GAAD) today I’m throwing this method out in to the ether that is the web. However, it’s not the quote/ unquote “technique” I’m offering — in the sense I really expect anyone will use it. Rather it’s my aim to try and get people thinking about the content they consume and produce on and for the web, period. And thinking a little differently about said web content.

After all, that’s the point of going through the effort of raising awareness. To think about anything in a manner which you aren’t typically conditioned to think about them. Or in other words, it’s not so much the result I’m most interested in here, it’s the reasons for and process that give us that result. It’s my hope to draw some attention towards automatic text transcriptions of audio only podcasts, specifically.

And I’m aware such a solution is still a ways off from being practical — as in reliably useable. But it’s never too early to entertain prospects. And experiment. Read “Automatic audio text transcriptions” in its entirety

Defining focus

Categorized Under: Adaptability, CSS Published on Authored by Leave a comment

When I wrote Regaining focus I figured, from my past experience using user defined style sheets, things would be as straight forward as I remembered them being. Why isn’t anything as simple as the utility demands? And for the record, I know relying on memory alone is largely a sloppy move to make. And I hope to correct myself with this post today.

But I didn’t fully realize my error until I went to write up the README for a Github repository I wrote for a solution for such a problem. Using the bit of code I provided in my post I linked to above, I wrote a style sheet (FOCUS.css) that would provide a user the same experience in the same browser from one site to another.

The problem being the ways to implement user defined focus styles vary quite a bit from browser to browser. From easy to complicated. Read “Defining focus” in its entirety

The Applicability of Keyboard Access

Categorized Under: About, Usability Published on Authored by Leave a comment

Back in December of 2011 I wrote (which is almost impossible for me to believe);

“[I]n searching for alternative methods of access — which essentially means [the] ways [in which] I input my intentions into a computer, and I’ve also begun to experiment with a trackpad, too — I discovered the keyboard is my ideal method of access. I had to change a few [Operating System] OS specific key commands, for usability’s sake, but using the keyboard to control a computer cut way down on the time I used to fumble with the mouse.”

Habit is powerful thing. I’ve spent virtually the entire time on my computer “fumbling” around with various input devices. Specialty mice (specifically programmable mice), not so special mice (the Apple hockey puck comes to mind), trackballs (I hated using a trackball), Wacom tablets and most recently an Apple Track Pad. All had their pro’s but each had a lot of con’s. Mainly in terms of my ability to use them. More often than not, the trackball especially, they were just awkward for me to use in any productive fashion.

The irony of it all is the most productive means of access was sitting right there in front of my face, the whole time. The keyboard. And as time lapsed I was gravitating my use increasingly away from those various input devices I was trying to use to the keyboard without realizing it. Not because it was more natural feeling, rather it was just easier for me. Read “The Applicability of Keyboard Access” in its entirety

Keyboard accessibility

Categorized Under: About, Technology Published on Authored by Leave a comment

Not that long ago I wrote about my initial experiences with Assistive Technology. And even though those experiences happened quite some years ago and I’ve undergone a lot of healing and a number of behaviour alterations since, I still use a handful of alternative means to access a computer.

But by far the most important one I use, that makes the time I spend on a computer much more productive and enjoyable, is the manner in which I use a keyboard.

As my physical ability has progressively changed, my needs — in the sense the solutions I use — have not. Well that’s not entirely true. I no longer need switch access scanning or mouse keys, but I still heavily rely on the keyboard, and sticky keys especially, to interface a computer. I can use two hands to type, but that can be challenging (working in Photoshop is the exception) so I don’t typically use both hands. But in an effort to speed up my productivity I don’t so much require said solution, as I much prefer to use it.

Which gets to my point, my most productive use of time, in terms of my access, is the keyboard. Most of the solutions I currently use involve these 90 keys that lay before me. Read “Keyboard accessibility” in its entirety

Adaptive web design

Categorized Under: Adaptability, Design Published on Authored by Leave a comment

I’ve thought, for quite sometime honestly, that most of a persons success in using technology, and the internet specifically, is directly related to both a person’s willingness and ability to adapt. And while parts of my thinking still reflect this belief, large parts of those thoughts are not so much changing (in the sense my opinion is flipping), as they are evolving.

Before I proceed I’d like to define what it is that I meant by “success in using technology” above. Just for the record, I’ve never thought a persons perceived (whether it’s an internal or external perception) failure to interact with any given piece of technology was the fault of the user. It’s not. It most definitely is the fault, or better still, a short-sightedness of the creator. Nor do I think the word “failure” is valid in this context either. Failure and it’s implications would suggest this is a black and white issue. And it’s not. Not by any stretch of the imagination. As with anything there are shades of grey. As there are varying degrees of success.

That said, I’d very much like to alter what it is that I meant when using the word “adapt.” How I was using the word wasn’t entirely fair. It placed too much of an expectation on the user. It’s not any users job to adapt to technology. It’s technology’s need to be used by us. Otherwise why was it thought of and built? I’d simply like to swap “adapt” for “learn.” Most of a persons success in using technology is directly related to both a person’s willingness and ability to learn how to use it. The trick is to make that initial learning curve as inviting as possible. Easier said than done. Read “Adaptive web design” in its entirety