<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19019">
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal-compose
}
.MsoChpDefault {
mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US link=blue vLink=purple>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><SPAN class=153424515-30032011></SPAN><FONT
face=Arial><FONT color=#0000ff><FONT size=2>H<SPAN
class=153424515-30032011>i <SPAN
class=128191718-30032011>Wink,</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011><SPAN
class=128191718-30032011></SPAN></SPAN></FONT></FONT></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011><SPAN class=128191718-30032011>I responded to this
topic earlier at one of our local mailing list. See below and hope it
helps.</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011><SPAN
class=128191718-30032011></SPAN></SPAN></FONT></FONT></FONT> </DIV>
<DIV><SPAN class=153424515-30032011><FONT color=#0000ff size=2 face=Arial>There
are a few fact that we need to know about access keys:</FONT></SPAN></DIV>
<DIV><SPAN class=153424515-30032011><FONT color=#0000ff size=2
face=Arial>1. A</FONT></SPAN><SPAN class=153424515-30032011><FONT
color=#0000ff size=2 face=Arial>ccess keys are useful as long as there
are only a limited numbers of them and are used consistently across the
domain.</FONT></SPAN></DIV>
<DIV><SPAN class=153424515-30032011><FONT color=#0000ff size=2 face=Arial>2.
Access keys frequently overlap with OS, browser, and assistive technology
shortcut keys. As long as the end-user can specify the access keys to desired
functions in an application, then it makes sense but according to the
article</FONT></SPAN></DIV>
<DIV><SPAN class=153424515-30032011><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011>"</SPAN>One of these Omeka plugins, called Access Keys,
allows site administrators to specify <BR>access keys<BR> (or keyboard
shortcuts) for navigating around Omeka. People who are blind do not navigate Web
sites through a graphical user interface; they usually rely<BR>exclusively on
their keyboard. Access keys are time-saving shortcuts that allow them to
navigate quickly and easily. For instance, an administrator could<BR>specify
that the access key “s” would be reserved for loading the “Search” page, the “h”
key could be reserved for the “Home” page, the “a” key for the<BR>“About” page,
and so on.<SPAN class=153424515-30032011>"</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011>the administrator assigns the access keys. And this is
the problem. how the admin knows what access keys doesn't interfere with my
OS/browser/assistive technology shortcut keys.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011>This is similar to that an admin choose the best color
setting for the users. I believe we all do have our color preferences and
administrators should not impose their color preferences to the end
users.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011>The optimal option is to provide the mechanism that
end-user specifies his/her access keys within a domain depending on his/her
OS/browser/AT settings.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011>I personally think access keys cause more problems for
AT users than helping them. We really don't need to invest too much energy into
access keys solution. An application with logical heading structures/landmarks
doesn't need access keys very much. They are helpful if we are dealing with
pages/forms that we access repetitively.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011>Thanks,</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011>Hadi</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=153424515-30032011></SPAN></FONT></FONT></FONT> </DIV></DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> athen-bounces@athenpro.org
[mailto:athen-bounces@athenpro.org] <B>On Behalf Of </B>Wink
Harner<BR><B>Sent:</B> Wednesday, March 30, 2011 12:29 PM<BR><B>To:</B>
DSSHE-L@LISTSERV.BUFFALO.EDU; 'Access Technology Higher Education
Network'<BR><B>Subject:</B> [Athen] Worpress/accessibility
question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN lang=PT-BR>Hi all,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=PT-BR><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=PT-BR>Forgive cross-posting.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=PT-BR><o:p> </o:p></SPAN></P>
<P class=MsoNormal>Received this from a colleague today and am curious as to
your collective (wise!) thoughts about Wordpress and accessibility for Blind
users. <o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Here is the <SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt">link to the
higher ed article about a plugin for wordpress to help blind
people.<BR><BR><o:p></o:p></SPAN></P>
<P class=MsoNormal><A
href="http://chronicle.com/blogs/profhacker/access-keys-a-wordpress-plugin-to-improve-accessibility/32181?sid=at&utm_source=at&utm_medium=en">http://chronicle.com/blogs/profhacker/access-keys-a-wordpress-plugin-to-improve-accessibility/32181?sid=at&utm_source=at&utm_medium=en</A><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Your input, as always, is welcome.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Wink<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BODY></HTML>