Category Archives: Adaptability

A part of my thinking towards using and assessing technology has come from the idea users must do their part adapt to its use. You know, because most technology sucks. It’s required. Admittedly, this thinking largely stems from a narcissistic pride in my own ability to adapt. But, of course, there are limits. What happens when users can’t adapt? Well, The Hardest Lessons Earned represents exactly what happens. It can have very harmful consequences.

Defining focus

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

Regaining focus

During the latter part of this past week, I performed an accessibility “audit” for an organization I’ve done this type of work for in the past and unfortunately haven’t done much for in recent months. It feels good to be at it again.

And the web developer’s work I was evaluating was missing one of the most basic concepts of accessible web design. They removed the focus indicator from their links. I thought I’d share how I got around this potential show stopper with a little browser feature I’ve had to use possibly a couple other times for situations not quite as serious as this proved to be, but I think this will be worth the effort.

But before I drone on, it seems this needs to be said at least one more time. You really should avoid removing the focus indicator from web sites. Now I understand why one would do it. In some browsers the outline shows when you click on a link and that complicates certain aesthetic goals. And there are ways around this (largely).

But, as the link above demonstrates, this isn’t a new concern. This is merely me taking my sweet ass time at getting to a point. Which isn’t my main point, bear with me, I’ll get there. Revisiting practices that have since passed “pressing” relevancy can sometimes help your current processes. Take my “audit” this past week as a perfect example. Read “Regaining focus” in its entirety

My life with a Screen Reader

So for quite some time now, much longer than is even remotely justifiable in fact, I’ve been having my share of difficulty both with using and understanding how to use Screen Reader Technology. Or more to the point, I just don’t get how this particular technology is usable to Blind and Low-Vision users.

Just to be crystal clear, I’m not knocking the technology or anyone who uses it, I’m only speaking towards my experience with it. And since my experience is limited, take this for what it’s worth, which isn’t a hellva lot.

Using said technology is an almost maddening endeavour each and every time I try to use it. I cannot wrap my head around making personal, productive use of it — and when I refer to “it,” in the interests of full disclosure, since I design and develop on a Mac, I mean VoiceOver. Read “My life with a Screen Reader” in its entirety

Adaptive web design

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

The gamut of ever changing ability

I’ve been away from here for quite sometime attending to a whole host of issues. So in an effort to get back into gear I’ll continue my series of posts describing my computing career. This is the second post in what will be three relating the story of what brought me here. Be sure to see my post the origins of interest for the first bit of my story…

… So by April of ’97, soon after transferring to a third “rehab” hospital (which was everything but a rehabilitation facility, hence the quotes), I was no longer “locked-in” — which as I understand it calls into question my original diagnosis, seeing how it wasn’t permanent (semantics, eh?). I started to regain enough mobility in my right arm and hand to be able to use a keyboard to type and use mouse keys.

Ahhh, mouse keys. I should probably provide you some context. Picture the ways in which any computer pointing device, like a mouse, can move. Limitless, right (speaking 2 dimensionally of course)? Forward, left, right and back. Plus every direction in between. Now imagine the representation of those basic movements on a flat surface, on a keyboard say, and using the numeric keypad to represent 8 directions that device can move. The number “2” key, when pressed, moved the mouse cursor up on the screen. Number “4” moved it left. Number “6” moved it right. And number “8” moved it down. Then the number “1” key moved the cursor up and left diagonally on the screen. Number “3” moved it up and right diagonally. The “7” key down and left diagonally. And “9” down and right diagonally. The number “5” key is the mouse button. Honestly what the rest of the buttons did is pretty fuzzy. Rather than guess I should simply refer you to the Wikipedia entry concerning mouse keys for more accurate context.

And that solution served me remarkably well for probably close to, if not exceeding, two years. Mouse keys are still simple to understand and most importantly easy to use. And it got completely out of the way and let me “master” elements where mouse keys reached their limit and other solutions picked up the slack — keep in mind I’m speaking wholly as a differently-abled creative individual whose primary creative canvas has been a computer monitor for well over a decade. It’s just the nature of the beast. 8 linear directions will only get you so far. It’s much like an Etch A Sketch™, in theory, as it’s movement is rigid and limited. And must like said Etch A Sketch™ there are ways around it’s operation. Read “The gamut of ever changing ability” in its entirety