Koa11y
Koa11y copied to clipboard
open-indy
Easily check for website accessibility issues
There are a lot of possible new features that could be added to Koa11y that would require us to update and change it's, currently, very simple interface. New designs for...
Likely under the `File > Export` menu. This would export out your project's `settings.json` file to your desktop, so it can be shared with someone else. During the import process,...
* https://github.com/pa11y/pa11y#actions ```js pa11y({ actions: [ 'click element #tab-1', 'wait for element #tab-1-content to be visible', 'set field #fullname to John Doe', 'check field #terms-and-conditions', 'uncheck field #subscribe-to-marketing', 'wait for...
 The guideline code shown at the top of this error message has a predictable pattern. We could grab the `G17` part...
We could improve the template used on HTML reports to include some branding, and useful information, like what version of Koa11y was used to create that report. Maybe some information...
1. Add a button (for now) to the About modal to check for updates. 2. On click make a network request to: * https://api.github.com/repos/open-indy/Koa11y/releases 3. Find the latest version number...
Requested by @rahulr892 in #19. Will need to come up with a design for how to allow for this feature in a simple to understand way.
there are some sections that can still be converted to be handled by Vue, and we can split up stuff to Vue components.
We could add some unit testing to the code, so that when updating it in the future we are less likely to break things.
NVDA is a free/open source screen reader that can be used for testing. * https://www.nvaccess.org Log any issues found to GitHub Issues page to be resolved.