Accessibility Audit

[edeleastar]

Accessibility Audit

[lgriffin]

I looked at this during Hacktoberfest last year and used one of the Node.js accessibility checkers:
https://www.npmjs.com/package/accessibility-checker

A few things that are easy fixes are on the static HTML to put anchors on components etc. However the one that surprised me is the auto generated HTML that is produced is non compliant, that's going to be a very tricky fix in that it's a potential upstream patch. There may be a need to check out accessibility compliance in auto generated HTML as a research spike.

Linking this article for reference reading for whomever takes this on

https://developers.redhat.com/articles/2022/11/03/nodejs-reference-architecture-part-10-accessibility#why_node_js_developers_need_to_provide_accessibility

[edeleastar]

Thanks @lgriffin - thanks for the leads. In fact this is this is the tool to use:

• IBM Equal Accessibility Checker

Which is a Chrome plugin - to run the check on a live course. The static checker does not really make much senses in a Svelte/SvelteKit project. I ran the check on a course home page, getting this result:

The 4 violations were relatively straightforward to track down - and have been addressed in

• #699

Scan now showing:

The 24 Recommendations Issues + 4 review items will need some work, but I have corrected I think) 8 of these - but they still show up as recommendations in the scan, so will need further work.

Will leave the item "Open" and "In Development" in the project in case there are any takers!

Thanks again