Re: Seeking *opinions* as part of a larger research issue.

Hi Leonard,

Thanks. The actual source is ePub (i.e. xhtml markup), which like PDF does
support inline hyperlinks. Currently the client is ensuring that all of
their ePub documents are GCA Certified (by Benetech. See here:
https://bornaccessible.benetech.org/global-certified-accessible/)

The content owners have a broad policy that active URLs should be linked
from the ePub books, but I am asking about non-active or
deliberately 'fake' URLs.

Our current workflow system *CAN* make all URLs (or text strings that look
like URLs) hyperlinks (in essentially the same way that my typing www.w3.org
into my GMail client will automagically turn that text string into a URL),
but I am seeking to argue that doing so is actually making some content
*less* accessible (if the text that looks like a link really isn't a link),
but because WCAG says nothing, I am doing the research and hoping to build
some form of consensus or "group thinking" around these use cases. (Current
industry practice seemingly goes counter to my argument, with tools like
JIRA & github and social media sites like LinkedIn and Facebook also do the
'automagic' thing that Gmail just did above)

Hope that the explanation helps.

JF



On Mon, Jan 16, 2023 at 2:28 PM Leonard Rosenthol <lrosenth@adobe.com>
wrote:

> Why is the “print” version, which I take to be a PDF, using active styling
> and/or making the links active?   There is no requirement to do so either
> from most authoring solutions and certainly not from PDF.
>
>
>
> I run into this frequently when describing things like XML namespaces or
> JSON-LD contexts, which are URIs but not active (and in most cases don’t
> even represent a real thing).  I have to manually disable the link in the
> authoring tool to make it remain as standard content.
>
>
>
> Leonard
>
>
>
> *From: *John Foliot <john@foliot.ca>
> *Date: *Tuesday, January 17, 2023 at 5:10 AM
> *To: *public-epub3@w3.org <public-epub3@w3.org>,
> public-publishingcg@w3.org <public-publishingcg@w3.org>,
> epub-higher-education@lists.daisy.org <
> epub-higher-education@lists.daisy.org>
> *Subject: *Seeking *opinions* as part of a larger research issue.
>
> *EXTERNAL: Use caution when clicking on links or opening attachments.*
>
>
>
> The use-cases are pretty simple:
> 1) an ePub book has text content on the page that is a URL (i.e. it quite
> literally reads "www.examplesite.com
> <https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.examplesite.com%2F&data=05%7C01%7Clrosenth%40adobe.com%7Ce52e5b6d7c044002261508daf7ecf790%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638094894392371578%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ncF14tzY8p6TrGYCq0MAzFdLY0HZud7w1riTww1y3bQ%3D&reserved=0>").
> The URL does not (and is not expected to) actually resolve anywhere, it's
> just an example or placeholder text.
> 2) an ePub book has content on the page that was once an active hyperlink,
> but the link no longer exists.
>
> The question is: for both of those use-cases (where the "print" is
> offering up a text string formatted as an URL, but there is no actual URL
> to resolve to), should those text strings STILL be marked up as hyperlinks?
>
> From a strict conformance to WCAG perspective… well, WCAG is silent on
> this specific topic (and so it seems is ePub Accessibility 1.1).
> I strongly suspect that there are arguments for both sides of the
> discussion (“should all printed URL’s be active links”?), but I am
> currently backing the perspective that having users (readers) follow
> inactive links (or presenting users with inactive links to follow),
> a) potentially places negative cognitive strain and confusion on some
> users,
> b) potentially demands unnecessary interactions (clicking a useless link)
> that could be problematic for mobility impaired users, and
> c) delivers zero quality for any effort invested by the user.
>
> My questions are:
> 1) do you agree or disagree with my reasoning? (If you disagree, might I
> ask for your counter-argument please?)
>
> 2) have you encountered this before? If you have, can you tell me what you
> ended up doing? In particular, if you work in EDU (office of accommodation,
> etc.) where ePub remediation is part of your work/tasks, do you have a
> 'standard' policy or solution to either of these use cases?
>
> 3) any other thoughts or comments? (Note: we're looking for a solution
> that is also scalable, FWIW)
>
> Thanks in advance for any feedback!
>
>
> JF
>
> --
>
> *John Foliot* |
> Senior Industry Specialist, Digital Accessibility |
> W3C Accessibility Standards Contributor |
>
> "I made this so long because I did not have time to make it shorter." -
> Pascal "links go places, buttons do things"
>


-- 
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"