<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
span.emailstyle17
{font-family:"Calibri","sans-serif";
color:windowtext}
span.EmailStyle18
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
span.EmailStyle21
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
div.WordSection1
{}
-->
</style>
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">I agree the right click menu could go on forever but given the fact that XOT templates are designed to minimise long pages of text I don’t think we’d need more than H1 and H2. Even H1 alone would improve the
navigability of the body text on pages.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">I totally agree that this is a sticking plaster – the real benefits will come with a new editor but that’s a BIG job and could take a long time. If there are simple ways we could ramp up the navigability of text
for screenreader users we would significantly enhance usability for some of the audience.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">A</span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D"> </span></a></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> xerte-bounces@lists.nottingham.ac.uk [mailto:xerte-bounces@lists.nottingham.ac.uk]
<b>On Behalf Of </b>Julian Tenney<br>
<b>Sent:</b> 02 May 2013 15:34<br>
<b>To:</b> Xerte discussion list<br>
<b>Subject:</b> [Xerte] Re: Playing around with XerteToolkits - heading levels on right click menu?</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:#1F497D">The problem is, where does it end? The right click menu is OK for simple formatting, but if you add all the different headings H1 – H6 and if they need configuring differently in different context etc, then the
right click menu is going to be a right mess.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">This might be something better looked at as we think more about redeveloping the wizard, and we get an opportunity to add a ‘proper’ html editor.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">
<a href="mailto:xerte-bounces@lists.nottingham.ac.uk">xerte-bounces@lists.nottingham.ac.uk</a> [<a href="mailto:xerte-bounces@lists.nottingham.ac.uk">mailto:xerte-bounces@lists.nottingham.ac.uk</a>]
<b>On Behalf Of </b>Alistair McNaught<br>
<b>Sent:</b> 02 May 2013 15:10<br>
<b>To:</b> <a href="mailto:xerte@lists.nottingham.ac.uk">xerte@lists.nottingham.ac.uk</a><br>
<b>Subject:</b> [Xerte] Playing around with XerteToolkits - heading levels on right click menu?</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">If you’ve been listening to any TechDis mantra over recent years you’ll realise that adding heading levels to documents is really important for accessibility for all sorts of reasons, but especially for blind people.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Yesterday I was working with some publishing colleagues on accessibility guidance for publishers and we were playing with toolkits to see how much html we could add in the editor and have it carry through to the html5 output. I was excited
to find we could embed heading levels, tables and even inline styling – (for colour coding ONIX accessibility metadata if you really want to know!).</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Of all these things the most genuinely useful for non-technical users would be to have a rightclick option in the editor to be able to apply a heading level in the same way it currently applies bold, italic and hyperlinking etc.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Could Aria Landmarks be added in a similar way? Or can they be built in automatically (since most page types have clearly identifiable areas that relate to Aria definitions like
</p>
<p class="MsoNormal"><b>main:</b> Main content in a document.</p>
<p class="MsoNormal"><b>complementary:</b> Any section of the document that supports but is separable from the main content, but is meaningful on its own even when separated from it. (Nested pages?)</p>
<p class="MsoNormal"><b>form</b>: A region of the document that represents a collection of form-associated elements, some of which can represent editable values that can be submitted to a server for processing. (Gap fill and hangman?)</p>
<p class="MsoNormal"><b>navigation:</b> A collection of links suitable for use when navigating the document or related documents.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">More questions than answers but you have to realise the flack I get from accessibility militants that Toolkits “doesn’t do semantic structure” etc. Now that I’ve realised it CAN I’d love to be able to find away of making it easy for non
coders to do it.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">How feasible is tweaking of the right click Editor menu? How long would it take? Where in the scale of costs or favours does this lie? A pint at the local? a meal at the Indian restaurant? A day out at Thorpe Park or a new house?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Alistair</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><b><span style="color:#1F497D">Alistair McNaught</span></b></p>
<p class="MsoNormal">Senior Advisor </p>
<p class="MsoNormal">JISC TechDis Service</p>
<p class="MsoNormal">Higher Education Academy | Innovation Way | York | YO10 5BR</p>
<p class="MsoNormal"><b><span style="color:#1F497D">Mobile</span></b> - +44 (0)7870567659</p>
<p class="MsoNormal"><b><span style="color:#1F497D">Skype</span></b> – alistair_techdis</p>
<p class="MsoNormal"><b><span style="color:#1F497D">Twitter</span></b> - @alistairm</p>
<p class="MsoNormal"><b><span style="color:#1F497D">Web</span></b> – <a href="http://www.jisctechdis.ac.uk/">
www.jisctechdis.ac.uk</a> | <a href="http://www.scoop.it/t/inclusive-teaching-and-learning">
www.scoop.it/t/inclusive-teaching-and-learning</a> </p>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"">This email is confidential and may be privileged. If you are not the intended recipient please accept our apologies. Please do not disclose, copy, or distribute information
in this email nor take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it. Please note that views expressed in this email are those of the author
and do not necessarily represent those of the Higher Education Academy. Please note that this e-mail has been created in the knowledge that Internet e-mail is not a secure communications medium. We advise that you understand and observe this lack of security
when e-mailing us. Although we have taken steps to ensure this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. The Higher Education Academy Registered
No 4930131 </span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt; font-family:"Times New Roman","serif""><br>
<br>
</span></p>
</div>
This email is confidential and may be privileged. If you are not the intended recipient please accept our apologies. Please do not disclose, copy, or distribute information in this email nor take any action in reliance on its contents: to do so is strictly
prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it. Please note that views expressed in this email are those of the author and do not necessarily represent those of the Higher Education Academy. Please note
that this e-mail has been created in the knowledge that Internet e-mail is not a secure communications medium. We advise that you understand and observe this lack of security when e-mailing us. Although we have taken steps to ensure this e-mail and attachments
are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. The Higher Education Academy Registered No 4930131
</body>
</html>