<html 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=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Times;
panose-1:2 0 5 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Hi Steve,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I don’t know to what degree full acceptance testing of WordPress for Section 508 compliance has been performed, and WP / Automattic doesn’t have a VPAT available, but my understanding is
that the core CMS holds up well for 508-level accessibility.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">The WordPress accessibility team recently announced that all new core code and bundled themes are required to meet the WCAG 2.0 Level AA guidelines, which are more robust than Section 508
(more modern, too — the forthcoming Section 508 refresh incorporates the WCAG 2.0 guidelines to bring the U.S. in line with many other countries’ accessibility laws):
<a href="https://make.wordpress.org/accessibility/2016/03/21/wordpress-goes-wcag/">
https://make.wordpress.org/accessibility/2016/03/21/wordpress-goes-wcag/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Granted, that’s the requirement for
<i>new</i> code. If you want to check out the open accessibility issues that remain to be fixed in core, their issue tracker might be helpful:
<a href="https://core.trac.wordpress.org/focus/accessibility">https://core.trac.wordpress.org/focus/accessibility</a> (in my experience, the editor-facing dashboard mostly has trouble with regards to color contrast and in places where JavaScript is used heavily,
like the Customizer, or where complex WAI-ARIA interactions can get muddled)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">The accessibility non-profit Knowbility has run workshops and conference talks on WordPress and accessibility (including ones focused on the admin dashboard), so they might be a good resource
to contact as far as compliance testing is concerned: <a href="http://www.knowbility.org/">
http://www.knowbility.org/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">And the WP core team’s Slack has an #accessibility channel, so you could also always ask them for more info directly!
<a href="https://make.wordpress.org/chat/">https://make.wordpress.org/chat/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Adam<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica;color:#7F7F7F">--</span><span style="font-size:13.5pt;font-family:Times;color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:Helvetica;color:#7F7F7F">Adam Norwood</span></b><span style="font-size:13.5pt;font-family:Times;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica;color:#7F7F7F">Senior Web Strategist / Developer</span><span style="font-size:13.5pt;font-family:Times;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica;color:#7F7F7F">The University of Texas School of Law</span><span style="font-size:13.5pt;font-family:Times;color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica;color:#7F7F7F">(512) 471-3040 Twitter: @anorwood</span><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">wp-edu <wp-edu-bounces@lists.automattic.com> on behalf of Steven C Burrell <Steven.Burrell@nau.edu><br>
<b>Reply-To: </b>"wp-edu@lists.automattic.com" <wp-edu@lists.automattic.com><br>
<b>Date: </b>Tuesday, August 2, 2016 at 9:24 AM<br>
<b>To: </b>"wp-edu@lists.automattic.com" <wp-edu@lists.automattic.com><br>
<b>Subject: </b>[wp-edu] Wordpress Core Accessibility from Content Editor's Perspective<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div id="divtagdefaultwrapper">
<p style="background:white"><span style="font-family:Calibri;color:black">I'm seeking insights or first-hand experiences from colleagues who can speak to the degree of accessibility compliance with Wordpress core from an administrator's or content editor's
perspective. My institution is considering adopting WPress but, by policy, assess software solutions for accessibility compliance before adopting. Most appreciatively, Steve.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>