rvantonisse/accessibility-evaluation-tool

Evaluate and report accessibility issues

Hi there 👋

accessibility-evaluation-tool's Issues

Chore: Style and refactor components

Styles and add consistency in file markup and code practices.

Add usecases with storybook.

Limit markdown support

...or remove support for markdown.

Observation descriptions should be short texts.

Chore: remove redundant packages and other rollup workflow

Cleanup after vite migration

Feature: Add a wcag scraper tooling

In a previous report tool version there was a translation scraper available for WCAG 2.0.

add this feature with e.g. cypress.io. Then we can start making some e2e tests as well.

Chore: Refactor App logic

Contexts, stores and other logic is set at multiple places, making the app code non understandable. Refactor that removes duplicate and redundant logic. Add jsdoc comments for documentation.

Tests: Add integration tests for data in and output

Adding a test framework to test the data in and output of the tool.

Feature: Migrate to SvelteKit

Less code overhead...

Use vite's glob import to make new translations without touching js files

Currently translators need to touch the file scripts/i18n.js to add a new registration.

Replacing the registering with some vite import.meta.glob functionality would greatly improve development. It would also make the rollup plugin workflow redundant, since all json would be globbed together in one object.

Like Vite docs :

// Import
const localeModules = import.meta.glob('./path/to/locales/**/*.json')

// Walk localeModules
for (const path in localeModules) {
  localeModules[path]().then((localeModule) => {
    // Register locales 
  })
}

Chore: Remove or move deployment setup options

Make it applicable to new setups. Create production- branches for deployment environments.

Add lint enforcement

E.g.
Eslint
Stylelint
Prettier

Enforcing on commit with husky/lint-staged.