RE: Good accessibility practice for handling footnotes

Hello,

 

In our testing of EPUB reading systems, we find that many times deep linking does not always take you to the  the desired location, e.g. you get to the top of the page and not to the exact location that is referenced. For this reason, we recommend that extended descriptions should be placed in a separate file. You then always get to the extended description. The backlink to where you left off may still be a problem. We have observed this same behavior with various browsers and assistive technologies.

 

Best

George

 

 

From: Jordan Rogers <jordan.rogers@ioppublishing.org> 
Sent: Wednesday, August 4, 2021 4:55 AM
To: kerscher@montana.com; 'Peter Weil' <peter.weil@wisc.edu>; 'Bryan Garaventa' <bryan.garaventa@levelaccess.com>; 'Louise Lister' <Louise.Lister@iop.org>; w3c-wai-ig@w3.org
Subject: Re: Good accessibility practice for handling footnotes

 

Hi Everyone,

 

I have been keeping track of this email thread as I am currently investigating how to make the ‘References’ section on the digital publishing platform that I work on more accessible. The references are all grouped together at the end of each paper, and each individual reference has a backlink to the reference in the body of the article. I am struggling to figure out how to properly code a group of endnotes that each have a backlink. I have been drafting out the markup for endnotes in a Codepen <https://codepen.io/jrog/pen/gOWdMab> . 

 

In Example 5 on the notes page <https://kb.daisy.org/publishing/docs/html/notes.html> , it is recommended to include a backlink after the endnote, but this is an example of a single endnote. Is it expected to follow this setup for multiple endnotes, because I thought it was bad practice to have multiple links with the same link text, which went to different locations?

 

For more context, here is a live example of a paper with references <https://iopscience.iop.org/article/10.1088/1367-2630/ac10a6>  on the platform I work on. References are a collapsed at the end of the page.

 

Thank you 

 

Jordan Rogers
UI Developer

IOP Publishing | Institute of Physics
Temple Circus, Temple Way, Bristol 
BS1 6HG, UK

Direct line +44 (0)1179301051

ioppublishing.org |  <applewebdata://324420FD-7434-4FE5-9832-936BBA0D1D59/www.iop.org> www.iop.org

 

 

From: "kerscher@montana.com <mailto:kerscher@montana.com> " <kerscher@montana.com <mailto:kerscher@montana.com> >
Date: Monday, 2 August 2021 at 16:53
To: 'Peter Weil' <peter.weil@wisc.edu <mailto:peter.weil@wisc.edu> >, 'Bryan Garaventa' <bryan.garaventa@levelaccess.com <mailto:bryan.garaventa@levelaccess.com> >, 'Louise Lister' <Louise.Lister@iop.org <mailto:Louise.Lister@iop.org> >, "w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> " <w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> >
Subject: RE: FW: Good accessibility practice for handling footnotes
Resent from: <w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> >
Resent date: Monday, 2 August 2021 at 16:48

 

Hi,

 

In our Transition to Accessible EPUB 3 working group (not a W3C working group, we are documenting support in browsers and EPUB reading systems. We plan to publish a set of suggested voiced values that enhance semantics. For example a h2 that is a chapter title could also say “chapter. 

 

Best

George

 

 

From: Peter Weil <peter.weil@wisc.edu <mailto:peter.weil@wisc.edu> > 
Sent: Monday, August 2, 2021 6:34 AM
To: 'Bryan Garaventa' <bryan.garaventa@levelaccess.com <mailto:bryan.garaventa@levelaccess.com> >; 'Louise Lister' <Louise.Lister@iop.org <mailto:Louise.Lister@iop.org> >; w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> ; kerscher@montana.com <mailto:kerscher@montana.com> 
Subject: Re: FW: Good accessibility practice for handling footnotes

 

Thanks Bryan and Matt.

Does anyone know why are these aria-roles are documented separately from the roles developers are probably more familiar with in https://w3c.github.io/aria/ <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Faria%2F&data=04%7C01%7Cjordan.rogers%40ioppublishing.org%7C16141f33719d4fe23da808d955cdb8af%7Cf9ee42e6bad04e639115f704f9ccceed%7C0%7C0%7C637635164325985466%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yeVI3Lbt9mpga1S1RAQGEFDgP4td2HoAA5%2FNFyh3c5Y%3D&reserved=0> ? If they are usable in the web context, it seems as though they deserve some mention in the latter (unless I’ve missed something).

Also, do these roles communicate any information directly to the user, or only to the assistive technologies users might be using?

 

Peter

 

-- 

Peter Weil, Web Developer

University Marketing

University of Wisconsin–Madison

peter.weil@wisc.edu <mailto:peter.weil@wisc.edu> 

(m) 608-220-3089

 

 

  _____  


IOP Publishing email addresses have changed from @iop.org to @ioppublishing.org, except those of our legal and finance teams, which have changed to @ioplegal.org and @iopfinance.org respectively. 

This email (and attachments) are confidential and intended for the addressee(s) only. If you are not the intended recipient please immediately notify the sender, permanently and securely delete any copies and do not take action with it or in reliance on it. Any views expressed are the author's and do not represent those of IOPP, except where specifically stated. IOPP takes reasonable precautions to protect against viruses but accepts no responsibility for loss or damage arising from virus infection. For the protection of IOPP's systems and staff; emails are scanned automatically. 

IOP Publishing Limited 
Registered in England under Registration No 00467514. 
Registered Office: Temple Circus, Bristol BS1 6HG England 

Your privacy is important to us. For information about how IOPP uses your personal data, please see our Privacy Policy <http://ioppublishing.org/privacy-cookies-policy/>