iansan5653 / github-markdown-a11y-extension Goto Github PK

When an image is uploaded (ie, via the file upload button in the editor toolbar), linting is not refreshed. This means that the ALT text error does not appear until the user starts typing.

This is a challenge to solve because the editor is setting the value property of the HTMLTextareaElement instance, so no events are emitted. There's nothing to listen for in this case.

This is a challenging one... how can we do end-to-end testing on an extension that depends on an external website? Maybe a mock website?

All GitHub pages already have level 1 headings, so these should be avoided in user-generated content.

We should possibly consider the same for level 2 since most pages already have level 2 headings, restricting headings to level 3 and higher.

The tooltip is appearing too far to the left, outside the bounds of the editor:

Looks like maybe we aren't adjusting for the editor x-position?

After using the extension for a while, I think I should remove the unordered list style rule that enforces the use of asterisks instead of hyphens. This does make the Markdown code itself more readable with a screen reader, but it doesn't affect the rendered output and it's a lot of noise for little gain. I think I want this extension to focus on the high-impact rules so that we can maximize the 'signal-to-noise' ratio. In other words, I want to minimize lint errors to focus on the important ones.