- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 16 Jun 2020 13:39:36 +0000
- To: Andrew Kirkpatrick <akirkpat@adobe.com>
- CC: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <AM7PR09MB4167518653515882842957ABB99D0@AM7PR09MB4167.eurprd09.prod.outlook.com>
Hi Andrew, 1. The 4th bullet seems incomplete… Indeed, we caught that at the last minute, if you look at the preview it should say: “A fully automated contact mechanism" https://raw.githack.com/w3c/wcag/wcag22-findable-help/understanding/22/findable-help.html I think you must have loaded the previous version, possibly cached. 1. I agree with Wilco’s point about SPA’s but more to the point, are we finding SPA’s that have help and that move it around to different locations? It was raised by the COGA TF as something to include, I don’t know the examples off hand, we can ask. It does occur to me it might be easier to consider an SPA as a ‘set of web pages’ than define something new. 1. I don’t understand (or have forgotten) why we are concerned with the blocks of repeated content in a set of web pages. I think this was to avoid things like PDFs needing to include help, it was a proxy for ‘more than a one page site or PDF’. However, perhaps that was from before the switch to using [if it has / then locate it], so it might not be needed. 1. For the location, why not use the “same relative order” as this worked for 3.2.3 Consistent Navigation? It would need to be relative to something. The other SC is relative to navigation mechanisms, I assume this would be relative to other page content. Otherwise it reads as relative to each mechanism. E.g. “For any set of web pages<https://www.w3.org/TR/WCAG21/#dfn-set-of-web-pages>, if one of the following is available, then at least one of the following is provided in the same relative order on each page:…” I don’t think it reads as well, but if that helps… -Alastair
Received on Tuesday, 16 June 2020 13:39:51 UTC