Editorial: Update ATK URL

[smockle]

Initially filed as w3c/html-aam#560

https://gnome.pages.gitlab.gnome.org/atk/ (the URL currently referenced throughout html-aam) 404s, even after logging in to the GNOME GitLab instance¹.

https://docs.gtk.org/atk/ (this PR’s replacement URL) seems to be the new location. GTK’s “API Docs” page links to this URL. Update: There are 3 candidates; details in #2309 (comment).

Preview: https://deploy-preview-2309--wai-aria.netlify.app/html-aam/

❧

Test, Documentation and Implementation tracking

Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.

• "author MUST" tests:
• "user agent MUST" tests:
• Browser implementations (link to issue or commit):
  • WebKit:
  • Gecko:
  • Blink:
• Does this need AT implementations?
• Related APG Issue/PR:
• MDN Issue/PR:

Footnotes

1. That said, GNOME’s “Technologies” page still links to this URL. 🤷 ↩

[netlify]

✅ Deploy Preview for wai-aria ready!

Name	Link
🔨 Latest commit	4122754
🔍 Latest deploy log	https://app.netlify.com/sites/wai-aria/deploys/66bfa6af2747fe00084478bb
😎 Deploy Preview	https://deploy-preview-2309--wai-aria.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[scottaohara]

so.... initially i was thinking this would be good - replace all the links with the new link. but this doesn't actually fix the link in the referenced terms. that still goes to the old documentation page, and that's an issue in core aam and ARIA (all the specs i'd assume) as well.

but also, core aam doesn't link to each of the platform pages within each feature table.... and that got me wondering why this spec does/should continue to do so?

i'm thinking maybe the fix here is to fix the link in the informative references section, and instead change the atk links to use the reference link [[ATK]], as well as the platform references?

[scottaohara]

see prior comment

[smockle]

Thanks @scottaohara; that makes sense. 👍

I’ll update the PR to do what you’re suggesting:

…fix the link in the informative references section, and instead change the atk links to use the reference link [[ATK]], as well as the platform references…

❧

One question: I found https://gnome.pages.gitlab.gnome.org/at-spi2-core/atk/ today; between that and https://docs.gtk.org/atk/, which should we use?

[scottaohara]

@spectranaut do you know which we should be referring to, per @smockle's question above? seems the api version is the same in both, but the library version is different.

[smockle]

Quick updates:

• I discovered someone had already corrected the bibliographic entry:

  aria/html-aam/biblio.js

  Lines 2 to 7 in 6723ad2

  	// Correct reference for ATK
  	"ATK": {
  	"href": "https://gitlab.gnome.org/GNOME/at-spi2-core/",
  	"title": "ATK - Accessibility Toolkit",
  	"publisher": "The GNOME Project"
  	},

  However, that correction is not being loaded, so I pushed a commit to start loading it: 71891a4.

  Now, https://gitlab.gnome.org/GNOME/at-spi2-core/ is the URL used in this PR. We could keep that, since it doesn’t 404, or we could replace it with https://gnome.pages.gitlab.gnome.org/at-spi2-core/atk/ or https://docs.gtk.org/atk/.

• I replaced the hardcoded links throughout the document with [[ATK]]: 4122754. I wrapped these in class="informative" so the ATK reference wouldn’t move into “B.1 Normative references”.

[scottaohara]

looks good to me. i am thinking we leave the link that's in the biblio.js already...

we can tackle changing the other platform api links to instead link to their reference section link in a follow on PR, if we dont' want to just do those here as well.