Monday, November 25, 2013
Thursday, November 7, 2013
Tuesday, October 8, 2013
Thursday, October 3, 2013
This leaves me with enough "free time" to keep our home a 1/4th clean, to cook dinner 2 or 3 times a week, to barely keep up with the class that I'm taking this semester, and to keep arguing with the DOE and office of transportation about busing. I didn't even manage to bill a single hour for my job in the month of September. Much like my over-used car, I am running on fumes.
But it's worth it, because Maya's school is good. We're still settling in, but they understand communication devices and jumped right in with the talker. They are firm and consistent with the I'm-going-to-test-every-single-situation-and-person-here Maya that emerges in new settings. They see her strengths.
Speaking of strengths . . .at back-to-school night I listened to curriculum discussions and then wondered where Maya's literacy level (letter recognition, etc) is. I picked up a book and asked her about a few words, and she surprised me. Yesterday I wrote a few sentences, and she actually was able to read them with the talker. I tried again at breakfast this morning (because nothing counts until it's video documented, right?), check it out:
Literacy is so, so, so important for Maya, and other AAC users. Once you can spell, you can say anything---even if you don't have a button for a particular word. Just a few weeks ago she was using the starting letter sound to try to tip me off as to the new button she wanted me to add to her talker . . . once she can read and approximate spelling, she can learn how to do the programming herself! (Oh boy. I can only imagine what will end up in there.)
This is where I would typically sum things up, but I'm too tired to even come up with an ending. Today was kind of a lousy day, and this video was my silver lining. There you go.
Friday, August 23, 2013
(cue the laughter)
Yeah, it didn't work . . . not initially, anyway. But I did learn a few things, create something decent on the second try, and figure out some tips and tricks that I think would be helpful to any parents/professionals who decide to do something similar on a tablet/phone/iPod.
Maya is using a full communication app called Speak for Yourself. Her talker is an original iPad in an iAdapter case, outfitted with a durable keyguard. The keyguard is a gamechanger for her----preventing a large number of mishits, allowing her to communicate rapidly and accurately. Here's the problem: the iPad + iAdapter are big. She's a little girl. It's challenging for her to carry the device, to set it up on a table, etc. As soon as I saw the mini iPad and mini iAdapter I knew they would be a much better fit for her----but there was a big problem. Due to the large number (120) of cells in the SFY app, there is just no way for any company to make a plastic keyguard for it---the strips of plastic would be slivers, bound to splinter off. We waited for a different keyguard to hit the market (sure that someone would design one) . . . but no luck (yet). Finally, I decided to see what I could figure out on my own, and this is the best that I've been able to do (so far).
What I used: screen protector (any old screen protector is just fine), Viva Decor Glass Effect Gel Pen (transparent color), pointy q-tips
This glass effects pen was undoubtedly the perfect choice---it goes on slightly opaque, which allows you to see what you're doing. It dries clear, hard, and without heat . . . so you don't have to be concerned about heating the iPad screen, as you would if you were to use hot glue. It comes in a squeeze bottle and it's not challenging to make lines that vary from fairly thin to pretty thick. It's also very forgiving---easy to wipe up with a fingernail or pointy q-tip if you happen to make a mistake. (Or many mistakes. Not that I would know anything about that.)
Important tip: If you're going to create a keyguard on a screen protector, you must do it after the screen protector has been applied, otherwise you won't be able to smooth out the air bubbles. First apply the screen protector, then you make the keyguard on top of the already applied screen protector.
Even thought this draft has a few key design flaws, I think the pictures do a good job of illustrating what the keyguard looks and feels like:
The Stuff That I Messed Up
Crucial Mistake #1: Think about every screen configuration, and account for it as best as you can. I tried to do this, but didn't fully succeed. Have a look:
1. If applicable, make sure to leave space open for the slide-to-unlock bar! (I remembered to do that!)
Here was the first draft. Oops:
To correct this I had to get a little bit crazy. I ended up building something that slightly resembles a maze, with small openings to account for the letter labels. There was much squinting and muttering during this process.
I did the easy, non-keyboard-involved part first:
And then switched back and forth between the screens to figure out the gaps. I also took a screen shot of the keyguard screen and had it open on my laptop when I was working on the main screen, to make things a bit easier.
4. Think outside the app---what about the main settings page for the iPad? Luckily since the gel is directly on the screen, if you accidentally cover a button that you need to push, you can just push on the gel and it will activate the button (that worked in the first draft picture below). However, if anyone else will need to do any programming or work controls on the device, you might want to keep things as clear, readable, and accessible as possible.
First draft, not very accessible:
Second try, with the "Enable Programming" row cleaned up:
Crucial Mistake #2: If you need to obscure something, obscure pictures---not text. Literacy is the big goal---don't take the words away. In my first draft I tried to follow the lines between the buttons perfectly, but as I added (more aggressive) layers and the lines thickened, some of the text was obscured:
In the second draft I made the horizontal gel lines just slightly above the divide between the buttons. It's hardly noticeable that small amounts of the picture bottoms are missing.
Crucial Mistake #3: Leave space for extra layers. And apply extra layers carefully. Don't get all the-first-one-went-on-so-thin-and-easy-that-I-can-put-this-next-one-on-more-thickly-and-save-time. The time you save in layer application won't seem so sweet when you've accidentally obscured text or buttons and realize you need to start over.
What We've Ended Up With:
I've corrected the mistakes above. It's helpful, but not amazing---Maya would still benefit from something that would prevent more mishits. (She hits buttons with her knuckles while she's reaching for something else with her pointer finger.) That being said, it's only been a week, and we're going to sit tight and see how much she's able to refine her movements and increase her accuracy. And I'm probably going to add a few more layers.
Happy keyguarding :)
Monday, August 12, 2013
I would like to believe this is true.
She is limited, still. She thinks things that she can't communicate. We play guessing games and I think that we often are able to figure out what she is trying to say, but not always.
The first time we couldn't figure out her mystery word, she gave up. This time she gave up, but only for a few seconds and then she came back. And this time she tried to spell, too! The fact that she thought enough to figure out the first letter of Super Why, and gave it to me as a hint---well, that's pretty big. (That's also indicative of why I'm so obsessed with finding an academic placement for her that will have high expectations, like literacy now-not later.)
Saturday, August 3, 2013
Friday, July 19, 2013
Monday, July 15, 2013
*We have tried many methods of communicating with Maya before settling in with her communication app, Speak for Yourself. Many of those methods are outlined here. This is definitely not a comprehensive list of AAC options, it's just the stuff that we've tried.