<html 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" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Book Antiqua";
panose-1:2 4 6 2 5 3 5 3 3 4;}
@font-face
{font-family:"Arial Narrow";
panose-1:2 11 6 6 2 2 2 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:618999476;
mso-list-template-ids:-476669682;}
@list l1
{mso-list-id:1626040983;
mso-list-template-ids:-788787516;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">I totally agree with this sentiment. The WCAG technical criteria are adopted by 508 so that we have consistent design that is as accessible as possible. An unlabeled button violates the technical
criteria and is a violation even if the form is usable with a JAWS double twist backflip.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">On Ronza’s observations about destination elevators below, we really need the Access Board to adopt a standard. I’ve also noticed that some of these systems have a universal accessibility mode
that creates a major delay with doors slowly opening and closing to allow wheelchair access and flashing lights for those who cannot hear. Thus a blind person might greatly slow down everyone else in the elevator car and create a light show without need.
While well-meaning, there needs to be some serious thought about best practices for destination elevator accessible design. An Access Board regulation on this point would be ideal.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial Narrow",sans-serif;color:black">Timothy Elder</span><span style="font-family:"Aptos",sans-serif;color:#1F497D"> <br>
</span><span style="font-family:"Arial Narrow",sans-serif;color:black">Attorney</span><span style="font-family:"Aptos",sans-serif;color:#1F497D"> <br>
</span><span style="font-family:"Arial Narrow",sans-serif;color:black">TRE Legal Practice</span><span style="font-family:"Aptos",sans-serif;color:#1F497D"> <br>
</span><span style="font-family:"Arial Narrow",sans-serif;color:black">1155 Market Street, Tenth Floor</span><span style="font-family:"Aptos",sans-serif;color:#1F497D"> <br>
</span><span style="font-family:"Arial Narrow",sans-serif;color:black">San Francisco, CA 94103</span><span style="font-family:"Aptos",sans-serif;color:#1F497D"> <br>
</span><span style="font-family:"Arial Narrow",sans-serif;color:black">Phone: (415) 873-9199</span><span style="font-family:"Aptos",sans-serif;color:#1F497D"><br>
</span><span style="font-family:"Arial Narrow",sans-serif;color:black">Fax: (415) 952-9898<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif;color:#1F497D"> <br>
</span><span style="font-family:"Arial Narrow",sans-serif;color:black">E-mail: </span><span style="font-family:"Aptos",sans-serif"><a href="mailto:telder@trelegal.com"><span style="color:blue">telder@trelegal.com</span></a><span style="color:#1F497D"> <br>
</span><a href="http://www.trelegal.com/"><span style="color:blue">www.trelegal.com</span></a><span style="color:#1F497D"> </span></span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif;color:#1F497D">Twitter:
</span><span style="font-family:"Aptos",sans-serif"><a href="https://twitter.com/TRELegal"><span style="color:blue">@trelegal</span></a><span style="color:#1F497D"><br>
</span></span><b><i><span style="font-family:"Arial Narrow",sans-serif;color:green">Please consider the environment before printing this email.</span></i></b><span style="font-family:"Aptos",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-family:"Arial Narrow",sans-serif;color:black">Confidentiality Notice</span><span style="font-family:"Aptos",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial Narrow",sans-serif;color:black">This e-mail may contain confidential information that may also be legally privileged and that is intended only for the use of the Addressee(s) named above. If you are not the
intended recipient or an authorized agent of the recipient, please be advised that any dissemination or copying of this e-mail, or taking of any action in reliance on the information contained herein, is strictly prohibited. If you have received this e-mail
in error, please notify me immediately by use of the Reply button, and then delete the e-mail from your system. Thank you!</span><span style="font-family:"Aptos",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Blind-Gov <blind-gov-bounces@nfbnet.org> <b>On Behalf Of
</b>Othman (She/her), Ronza (CMS/OEOCR) via Blind-Gov<br>
<b>Sent:</b> Friday, June 14, 2024 10:08 AM<br>
<b>To:</b> kaye.j.zimpher@gmail.com; List for blind government employees <blind-gov@nfbnet.org><br>
<b>Cc:</b> Othman (She/her), Ronza (CMS/OEOCR) <Ronza.Othman@cms.hhs.gov><br>
<b>Subject:</b> Re: [Blind-Gov] Action Alert: Federal Employee ViewPoint SSurvey (FEVS) Accessibility Issues<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">This is what we call technically accessible but functionally inaccessible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">I recently encountered an elevator with a touch screen keypad inside the car. There is a single button you press for accessibility, which activates an audio menu. It verbalizes all of the floors,
and says, “Press the accessibility button when you hear your floor. [30 second pause] For floors 1 – 10, press the accessibility button. [30 second pause] For floors 11 – 20, press the accessibility button. [30 second pause] For floors 21 – 30, press the
accessibility button. [30 second pause] For floors 31 – 40, press the accessibility button. [30 second pause].<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">So let’s say I’m going to floor 39. I press the button when they read the 31 – 40 one. Then, here’s what happened.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">For floor 31, press the accessibility button. [30 second pause] For floor 32, press the accessibility button. [30 second pause] and so on.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">It took me 6 full minutes to get to floor 15. Imagine if I was trying to go to 39 or 40.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">Is it technically accessible? Yes. Is it functionally accessible? Absolutely not. It shouldn’t take 6 or 16 minutes to do something that it’d take a sighted person half a literal second to
do.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Book Antiqua",serif;color:black">Ronza M. Othman (she/her/hers),
</span></b><span style="font-size:9.0pt;font-family:"Aptos",sans-serif;color:black">Director, EEO Compliance Group, Office of Equal Opportunity and Civil Rights, Centers for Medicare & Medicaid Services – 7500 Security Blvd, N3-22-16, Baltimore, MD 21244 -
410-786-3274 (o); 443-380-5044 (f)</span><span style="font-family:"Aptos",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Aptos",sans-serif">CMS aspires to create: a culture that values and recognizes our employees’ unique identities and perspectives; an environment that provides all employees with equitable
access to opportunities for growth and development; and a workforce that reflects the communities we serve.</span></i></b><span style="font-size:10.0pt;font-family:"Aptos",sans-serif"> </span><span style="font-family:"Aptos",sans-serif"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Blind-Gov <<a href="mailto:blind-gov-bounces@nfbnet.org">blind-gov-bounces@nfbnet.org</a>>
<b>On Behalf Of </b>Kaye Baker via Blind-Gov<br>
<b>Sent:</b> Friday, June 14, 2024 12:41 PM<br>
<b>To:</b> 'List for blind government employees' <<a href="mailto:blind-gov@nfbnet.org">blind-gov@nfbnet.org</a>><br>
<b>Cc:</b> Kaye Baker <<a href="mailto:kaye.j.zimpher@gmail.com">kaye.j.zimpher@gmail.com</a>><br>
<b>Subject:</b> Re: [Blind-Gov] Action Alert: Federal Employee ViewPoint SSurvey (FEVS) Accessibility Issues<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">Wow, I just did not have any of these issues. I did happen to notice that after each question, there are radio buttons for the choices, and then the choices such as strongly agree, agree, neither
agree or disagree or agree were written out without buttons. While that is odd and one has to arrow through it, I did not find it inaccessible. My agency specific questions were choices with radio buttons just like the rest of the survey. I wonder then,
since there have been issues among other agency employees if the tests/surveys differ drastically from agency to agency.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">Interesting for sure.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Blind-Gov <<a href="mailto:blind-gov-bounces@nfbnet.org">blind-gov-bounces@nfbnet.org</a>>
<b>On Behalf Of </b>Othman (She/her), Ronza (CMS/OEOCR) via Blind-Gov<br>
<b>Sent:</b> Friday, June 14, 2024 9:14 AM<br>
<b>To:</b> List for blind government employees <<a href="mailto:blind-gov@nfbnet.org">blind-gov@nfbnet.org</a>><br>
<b>Cc:</b> Othman (She/her), Ronza (CMS/OEOCR) <<a href="mailto:Ronza.Othman@cms.hhs.gov">Ronza.Othman@cms.hhs.gov</a>><br>
<b>Subject:</b> Re: [Blind-Gov] Action Alert: Federal Employee ViewPoint SSurvey (FEVS) Accessibility Issues<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">Hi Folks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">In addition to Nathaniel’s issues as he described them, there are also some questions whose radio buttons are not associated with the text options, having been coded as separate items. That
means it appears to a screen reader user that there are two options for each item on the Lockard scale (very good, good, etc.). In addition, several agencies have included specific questions at the end that are ranking and rating, which can only be answered
by dragging and dropping using a mouse. There is no way to answer these questions using keyboard commands.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">I am using Jaws 2024 with the latest version of Chrome. Just to be sure I wasn’t having a bad technology day, I asked OPM to reset and re-open my FEVS, and I experienced the same issues the
second time around as well. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif">Hope this helps.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Book Antiqua",serif;color:black">Ronza M. Othman (she/her/hers),
</span></b><span style="font-size:9.0pt;font-family:"Aptos",sans-serif;color:black">Director, EEO Compliance Group, Office of Equal Opportunity and Civil Rights, Centers for Medicare & Medicaid Services – 7500 Security Blvd, N3-22-16, Baltimore, MD 21244 -
410-786-3274 (o); 443-380-5044 (f)</span><span style="font-family:"Aptos",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Aptos",sans-serif">CMS aspires to create: a culture that values and recognizes our employees’ unique identities and perspectives; an environment that provides all employees with equitable
access to opportunities for growth and development; and a workforce that reflects the communities we serve.</span></i></b><span style="font-size:10.0pt;font-family:"Aptos",sans-serif"> </span><span style="font-family:"Aptos",sans-serif"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Blind-Gov <<a href="mailto:blind-gov-bounces@nfbnet.org">blind-gov-bounces@nfbnet.org</a>>
<b>On Behalf Of </b>Nathanael T. Wales via Blind-Gov<br>
<b>Sent:</b> Thursday, June 13, 2024 8:47 PM<br>
<b>To:</b> 'List for blind government employees' <<a href="mailto:blind-gov@nfbnet.org">blind-gov@nfbnet.org</a>><br>
<b>Cc:</b> Nathanael T. Wales <<a href="mailto:ntwales@omsoft.com">ntwales@omsoft.com</a>><br>
<b>Subject:</b> Re: [Blind-Gov] Action Alert: Federal Employee ViewPoint SSurvey (FEVS) Accessibility Issues<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’ve found that the most noticeable issue with this year's FEVS is the consistency of the format of the forms with the questions and the form regarding demographics. For example, on one page with several questions
a user of text-to-speech may be able to use a form control keystroke (letter "F") to move from one radial button to the next, but on another page the user must tab between questions and scroll down with the arrows to select an answer. On several of the pages
that have the format requiring tabbing from one question to the next, the question is not readily read, and the user can easily lose her or his place to read questions (first, second, and third) before then tabbing through the first, second, and third question
to select answers and remember the order of the questions. Also, on at least two pages the formatting can cause a screen reader to skip the last question unless the user goes backwards on the page to check. These were not problems in previous years.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">As data points, both this year and last year (when there were no issues), I was using a Windows PC with JAWS 2023 and Crome. To help OPM fix this problem—if it can be motivated to, would:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">--Kay: Please share which browser you used.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">--Cody: Please share what browser and screen reader you were using.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Nathanael<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Blind-Gov [<a href="mailto:blind-gov-bounces@nfbnet.org">mailto:blind-gov-bounces@nfbnet.org</a>]
<b>On Behalf Of </b>CODY GREISER via Blind-Gov<br>
<b>Sent:</b> Thursday, June 13, 2024 8:26 PM<br>
<b>To:</b> List for blind government employees<br>
<b>Cc:</b> CODY GREISER<br>
<b>Subject:</b> Re: [Blind-Gov] Action Alert: Federal Employee ViewPoint SSurvey (FEVS) Accessibility Issues<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I also have completed the FEVS recently and found no accessibility issues.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cody Greiser<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Blind-Gov <<a href="mailto:blind-gov-bounces@nfbnet.org">blind-gov-bounces@nfbnet.org</a>>
<b>On Behalf Of </b>rothmanjd--- via Blind-Gov<br>
<b>Sent:</b> Wednesday, June 12, 2024 9:02 PM<br>
<b>To:</b> <a href="mailto:blind-gov@nfbnet.org">blind-gov@nfbnet.org</a><br>
<b>Cc:</b> <a href="mailto:rothmanjd@gmail.com">rothmanjd@gmail.com</a><br>
<b>Subject:</b> [Blind-Gov] Action Alert: Federal Employee ViewPoint SSurvey (FEVS) Accessibility Issues<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Folks,<o:p></o:p></p>
<p class="MsoNormal">Several individuals have shared concerns about the 2024 Federal Employee Viewpoint Survey (FEVS) in terms of lack of accessibility and 508 compliance issues. The National Association of Blind Government Employees is asking for your help:<o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo3">Please prioritize taking the FEVS as soon as you can (we understand most agencies are now in the open period, but some may be on a later schedule);<o:p></o:p></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3">Please note any accessibility or 508 challenges you experience;<o:p></o:p></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3">Please share those challenges with me via email to
<a href="mailto:rothmanjd@gmail.com">rothmanjd@gmail.com</a>;<o:p></o:p></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3">Please consider filing a 508 complaint with OPM and your employing agency (it’s helpful to file in both places). You can file with OPM using the email address
<a href="mailto:FEVS@OPM.gov">FEVS@OPM.gov</a>.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you have questions, please don’t hesitate to reach out.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Ronza<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">Ronza Othman, </span></b><span style="font-size:12.0pt">President</span><o:p></o:p></p>
<p class="MsoNormal">National Federation of the Blind of Maryland<o:p></o:p></p>
<p class="MsoNormal">443-426-4110<o:p></o:p></p>
<p class="MsoNormal">Pronouns: she, her, hers<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The National Federation of the Blind of Maryland knows that blindness is not the characteristic that defines you or your future. Every day we raise the expectations of blind people, because low expectations create obstacles between blind
people and our dreams. You can live the life you want; blindness is not what holds you back<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>