act-rules / act-implementor Goto Github PK

I personally much prefer sites with dark themes. This one was built in such a way that that would be fairly easy to do. The dark theme should:

1. Be enabled by default if the user has the dark them set in their operating system
2. Have a toggle to override
3. Once toggled, the setting should persist

Add linting, code formatting, and github hooks to make sure these run before every commit

On an approved rule, an example can appear more than once. That happens when there is an update for that example in the proposed rule. It should be clear when filling out an approved rule, which example is proposed and which is not.

• Persist import options in local storage
• Warn when leaving the page with unsaved content

A variety of buttons and links in the app use standard functionality. Adding an icon to those, and personalization semantics will make those a little easier to use.

Currently there is a one-to-many relationship between ACT rules and implementation procedures. This works most of the time since ACT rules are fairly atomic. Especially manual evaluators tend not to break procedures down to a highly granular level. However it is a use case that the tool should support.

Implementors should be able to indicate the name of the implementation, version, vendor, that kind of thing.

The overview page is currently just a long list of rules, along with the number of test cases implemented. That's workable, but not idea for finding rules that need to be updated. Perhaps the implementation could be grouped by "incomplete", "complete", and "untested".

• Add an option to download the file
• Provide a quick link to github, if github was used to import

On the rule implementation pages, the mapping key is used when the there is no title. Those work as a short hand, but are not particularly user friendly. Instead the full title of an accessibility requirement, and a link to that requirement should be used.

Add better documentation, both in the site on how to use it, and in the repo on how to build with it.

In selecting which rules to evaluate first it would be useful for the tool to indicate which rules are approved. I don't think that information is directly available so we'll have to infer that based on whether there are approved test cases.