Multiple URL issues in help section

[fstrr]

Hi

In the help section there are several issues with URLs:

1. There are six files that have URLs that use http instead of https

In the alerts page:

1. Links to ARIA authoring practices are out of date:
   a. this is the correct table link: https://www.w3.org/WAI/ARIA/apg/patterns/table/ (that page lists two different types of table)
   b. this is the correct grid link https://www.w3.org/WAI/ARIA/apg/patterns/grid/ (that page lists three different types of grid)
2. The id attribute link goes to an out of date W3C URL instead of the WHATWG spec: https://html.spec.whatwg.org/multipage/dom.html#the-id-attribute . The link text should also be updated.
3. The guidance on heading level 2 being the default ARIA level is out of date. That was the case in ARIA 1.1 but was removed in ARIA 1.2. The Editor's Draft of the Core Accessibility API Mappings 1.2 doesn't list a default heading level. (this was also raised in aria heading levels - must set #193)

[fstrr]

Update:

1. The link to "states and properties" in howtouse.html needs updating to: https://www.w3.org/TR/wai-aria/states_and_properties#introstates
2. "accessibility" is spelt incorrectly ("acessibility") in install.html

[dschaefer206]

Hello,

I would like to work on fixing this issue. I have experience with web accessibility testing and I use ANDI regularly in my own work so I am familiar with the tool

I think I should be able to:

Update the 6 HTTP URLs to HTTPS
Fix the ARIA authoring links to point to the correct W3c pages.
Update the id attribute
Update the heading level guidance to the current ARIA specs

I'll make sure to test everything I change and verify they all point to the current and correct documentation. Please let me know how you would like me to proceed or if there are any specific practices I should follow for this.

[fstrr]

I have a fix running for these issues on an internal build of ANDI. I guess I could create another fork of this repo, fix the issues on that, and create a PR. What's unclear, though, is who, if anyone, is working on ANDI now. If you look on LinkedIn, @cotter-john, who used to be the developer for ANDI changed jobs in June, so won't be working on this any more.

[dschaefer206]

Yeah I'm unsure as well. It doesn't look like it's very actively maintained.

I need to do an issue for a class I'm in so if you leave this as is I'll make the fixes and put up a pull request and maybe someone will get to it.

[fstrr]

Oh sure. If you need it for a class, then go for it :) Thanks!

[craigcecil]

I have a fix running for these issues on an internal build of ANDI. I guess I could create another fork of this repo, fix the issues on that, and create a PR. What's unclear, though, is who, if anyone, is working on ANDI now. If you look on LinkedIn, @cotter-john, who used to be the developer for ANDI changed jobs in June, so won't be working on this any more.

How about it @cotter-john? I'm suggesting you fork the SSAgov ANDI repo under your personal GitHub account and continue support for it. It's too valuable to just sit unmaintained. (Full disclosure: I'm a personal friend of John.)

[dschaefer206]

I have a fix running for these issues on an internal build of ANDI. I guess I could create another fork of this repo, fix the issues on that, and create a PR. What's unclear, though, is who, if anyone, is working on ANDI now. If you look on LinkedIn, @cotter-john, who used to be the developer for ANDI changed jobs in June, so won't be working on this any more.

How about it @cotter-john? I'm suggesting you fork the SSAgov ANDI repo under your personal GitHub account and continue support for it. It's too valuable to just sit unmaintained. (Full disclosure: I'm a personal friend of John.)

Is it likely to go on unmaintained if that didn't happen? I probably could actually help with some bigger issues if there was a better set up system for the community to contribute and maintain this. I picked this issue for the class I'm doing because it's an issue that I know I won't run into any unforeseen problems fixing but I could probably work some harder issues too.

I'll keep an eye on this thread for any updates.

[fstrr]

Is it likely to go on unmaintained if that didn't happen?

There is the possibility that the SSA has assigned someone to work on this, but with the recent government situation they've not allowed to do any government-related work so couldn't contribute to this discussion. I guess we'll have to wait a little while to see if anything surfaces.