<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:Wingdings}
@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.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{margin-right:0cm;
margin-left:0cm;
font-size:10.0pt;
font-family:"Times New Roman","serif"}
span.emailstyle17
{font-family:"Calibri","sans-serif";
color:windowtext}
span.emailstyle18
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.balloontextchar0
{font-family:"Tahoma","sans-serif"}
span.emailstyle21
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.EmailStyle24
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.EmailStyle25
{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">Ooops – cross cutting threads – sorry, my fault.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Julian, Fay, </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Maybe we should park this a week until Fay has looked at ARIA because it’s all a matter of navigational SCALES as far as I can see…</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><b><span style="color:#1F497D">Whole LO</span></b><span style="color:#1F497D"> -
<a name="_MailEndCompose">If H1 and H2 are providing a non sighted user with an instant overview of object-wide navigation we want to keep them UNLESS aria landscape markup does it better.</a></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><b><span style="color:#1F497D">Within a page</span></b><span style="color:#1F497D"> - Aria landmarks might provide a good navigation within individual LO pages but we don’t know how easy they’ll be to implement yet.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><b><span style="color:#1F497D">Within a text block</span></b><span style="color:#1F497D"> - Having a way of navigating longish text in the body of a page via a heading tag is an important accessibility feature and we should have it if we
can BUT</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">… whether the menu context tag is h1, h2 or h3 might depend on whether or not ARIA replaces h1 and h2 in current object-wide navigation.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Lets see what Fay finds out about ARIA and that will then help us know whether a menu based tag would be at level 1,2 or 3.</span></p>
<p class="MsoNormal"><span style="color:#1F497D">It’s an exciting conversation from an accessibility standpoint but can we continue it when Fay’s had a look at ARIA landscape markup?</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Alistair</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </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""> xerte-bounces@lists.nottingham.ac.uk [mailto:xerte-bounces@lists.nottingham.ac.uk]
<b>On Behalf Of </b>Fay Cross<br>
<b>Sent:</b> 03 May 2013 12:03<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">I can easily remove the h1 and h2 that are used on the interface. What’s best for accessibility? To have the main titles marked up like this or just using headings in the page contents (disregarding for the
moment the fact that people may add h1/2 to the page content manually)?</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </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" style="margin-left:36.0pt"><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> 03 May 2013 11:57<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" style="margin-left:36.0pt"> </p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D">> By the way, I’ve used H1 & H2 for the project title and page title so where ever I’ve added extra headings in the page contents I’ve only used H3 onwards</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D">That’s well worth knowing and lends strength to the argument for having a single heading level (H3) available in the right click context menu to avoid people trying to be more accessible
and accidentally being more confusing!</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D">I’d be very interested to see how the aria landmarks might work on a page level to help a blind user imagine the purpose and design of the page layout more effectively.</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D">Alistair</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><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" style="margin-left:36.0pt"><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>Fay Cross<br>
<b>Sent:</b> 02 May 2013 15:40<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" style="margin-left:36.0pt"> </p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D">Hi Alistair</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D">I’ll look in to Aria Landmarks and try adding them to define the main interface sections next week (I realise I’ve been saying for some time that I’ll look in to it but it’s now in
my calendar so I won’t forget </span><span style="font-family:Wingdings; color:#1F497D">J</span><span style="color:#1F497D"> ).</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D">By the way, I’ve used H1 & H2 for the project title and page title so where ever I’ve added extra headings in the page contents I’ve only used H3 onwards. If an author manually adds
H1/2 in the wizard the wizard then the structure might become a bit confusing.</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D">Fay</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><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" style="margin-left:72.0pt"><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" style="margin-left:72.0pt"> </p>
<div>
<p class="MsoNormal" style="margin-left:72.0pt">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" style="margin-left:72.0pt"> </p>
<p class="MsoNormal" style="margin-left:72.0pt">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" style="margin-left:72.0pt"> </p>
<p class="MsoNormal" style="margin-left:72.0pt">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" style="margin-left:72.0pt"> </p>
<p class="MsoNormal" style="margin-left:72.0pt">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" style="margin-left:72.0pt"><b>main:</b> Main content in a document.</p>
<p class="MsoNormal" style="margin-left:72.0pt"><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" style="margin-left:72.0pt"><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" style="margin-left:72.0pt"><b>navigation:</b> A collection of links suitable for use when navigating the document or related documents.</p>
<p class="MsoNormal" style="margin-left:72.0pt"> </p>
<p class="MsoNormal" style="margin-left:72.0pt">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" style="margin-left:72.0pt"> </p>
<p class="MsoNormal" style="margin-left:72.0pt">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" style="margin-left:72.0pt"> </p>
<p class="MsoNormal" style="margin-left:72.0pt">Alistair</p>
<p class="MsoNormal" style="margin-left:72.0pt"> </p>
<p class="MsoNormal" style="margin-left:72.0pt"><b><span style="color:#1F497D">Alistair McNaught</span></b></p>
<p class="MsoNormal" style="margin-left:72.0pt">Senior Advisor </p>
<p class="MsoNormal" style="margin-left:72.0pt">JISC TechDis Service</p>
<p class="MsoNormal" style="margin-left:72.0pt">Higher Education Academy | Innovation Way | York | YO10 5BR</p>
<p class="MsoNormal" style="margin-left:72.0pt"><b><span style="color:#1F497D">Mobile</span></b> - +44 (0)7870567659</p>
<p class="MsoNormal" style="margin-left:72.0pt"><b><span style="color:#1F497D">Skype</span></b> – alistair_techdis</p>
<p class="MsoNormal" style="margin-left:72.0pt"><b><span style="color:#1F497D">Twitter</span></b> - @alistairm</p>
<p class="MsoNormal" style="margin-left:72.0pt"><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" style="margin-left:72.0pt"> </p>
</div>
<p class="MsoNormal" style="margin-left:72.0pt"><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-right:0cm; margin-bottom:12.0pt; margin-left:36.0pt">
</p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><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>