Until these issues/questions are resolved, I would not consider DanaSwap beta-ready. However, they can be a bit of a time sink preventing alpha testing.
ARIA for everything (especially comboboxes)
Keyboard support for literally everything, onclick doesn’t cut it and we need tabindex in many cases. This definitely includes the table columns.
Devise a way to shave down the icons from importing 1000s to importing just what we need. (In other projects, I’ve just followed the CC BY attribution and manually built my own file with <symbol> elements because automating it would be more trouble than it’s worth for the 6 icons we were using). Closed #40
Make sure unsafe-eval isn't in the production CSP
Evaluate if Bulma really is the way. I don’t think we want to introduce and maintain the complexity of Sass unless absolutely necessary. Also, some of the naming conventions are misleading (e.g. "is-mobile" should be something like "viewport-small"). There are a few viable CSS-variable forward options that I think would better suit this project. Everything we need from CSS in 2022 is support in the CSS spec now meaning we could go from needing a tool/compiler to no tool/compiler--just text and a minifier/autoprefixer like lightningcss.
After #22
Until these issues/questions are resolved, I would not consider DanaSwap beta-ready. However, they can be a bit of a time sink preventing alpha testing.
onclickdoesn’t cut it and we needtabindexin many cases. This definitely includes the table columns.Devise a way to shave down the icons from importing 1000s to importing just what we need. (In other projects, I’ve just followed the CC BY attribution and manually built my own file withClosed #40<symbol>elements because automating it would be more trouble than it’s worth for the 6 icons we were using).unsafe-evalisn't in the production CSP