<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Hi Eric,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
I'd be happy to provide some information to you about all of those topics. I was hired as the University of Oregon's Digital Accessibility Architect a few months ago, and prior to that, I spent over a decade involved in digital accessibility work at Michigan
State University (and consulted for a variety of other organizations). Feel free to send me an email if you'd like to find a time to meet (<span style="background-color:rgb(255, 255, 255);display:inline !important">due to dexterity disabilities, </span>I'm
limited in how much I can type, and the answers to some of your questions are a bit long).</div>
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
--
<div>Grey L. Pierce (they/them)</div>
<div>Digital Accessibility Architect</div>
<div>University of Oregon</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<div id="signature_bookmark"></div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr" class="elementToProof">Date: Thu, 7 Jul 2022 18:50:07 +0000<br>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText elementToProof">From: "Matson, Eric (ecmatson@uidaho.edu)" <ecmatson@uidaho.edu><br>
To: Access Technology Higher Education Network<br>
<athen-list@u.washington.edu><br>
Subject: [Athen] EIT Accessibility - Position Description / Policy<br>
Message-ID:<br>
<CO1PR04MB82651CC5FE5D66EF86215130B2839@CO1PR04MB8265.namprd04.prod.outlook.com><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hey all,<br>
<br>
After a couple years of nagging and a some major accessibility issues, I finally got my administration to at least talk about the need for an Electronic Information Technology Accessibility position. Figured I'd see if any ATHENites have gone through the process
of getting an EIT position at their institution and have some pointers. More specifically is anyone is willing to share some or all the things below:<br>
<br>
<br>
1. Position Description w/ pay range. The few I've found just say salary dependent on experience, so would like to get a better idea of pay scale. And figure once I get to job description stage would be easier to pull language from existing positions rather
than reinvent the wheel.<br>
2. EIT Accessibility Policy - UIdaho is pretty late to the game. Currently no University wide policy, with accessibility left to each department. Again, hoping to use other schools' policy as a starting point to write ours.<br>
3. Policy Enforcement - specifically around EIT used in classes. I assume some of that is in the policy, but wondering how it works in practice. I've had faculty voice concerns that this position would take away their freedom to structure courses as they
see fit. As opposed to currently, where any barriers are brought to my director and I to come up with an alternative format or accommodation, but the issue doesn't actually get fixed.<br>
4. Proposal / Presentation around the need for an EIT Accessibilitity Position - I have a communication disability, so in my brain it all just makes sense, but when I try to explain, it comes out as a rambling list of disjointed facts. If anyone is willing
to share any proposals or presentations they've done relating to an EIT accessibility position, I would be forever grateful.<br>
<br>
For those of you without an EIT Accessibility position, who handles digital accessibility at your school? In the past I've helped different departments and done accessibility reviews, but my case load has gotten to the point where I don't have time for that.<br>
<br>
<br>
Eric Matson | Assistive Technology Specialist<br>
Center for Disability Access and Resources<br>
Division of Student Affairs<br>
The University of Idaho<br>
Phone: 208.885.6307 | ecmatson@uidaho.edu|<mailto:ecmatson@uidaho.edu%7C> Bruce M. Pitman Center 127<br>
Fax: 208.885.9404<br>
Campus Zip: 4257<br>
<br>
Pronouns: He / Him / His<br>
<br>
This communication may contain privileged, non-public or other confidential information. If you have received it in error, please advise the sender by reply e-mail and immediately delete the message and any attachments without copying or disclosing the contents.
Thank you.<br>
</div>
</span></font></div>
</body>
</html>