README: expanded thoughts about accessibility

feature/modern-browsers
Inga 🏳‍🌈 1 month ago
parent 67a9f6490a
commit c5eac547fb
  1. 5
      README.md

@ -327,6 +327,11 @@ None.
* Implement end-to-end tests with puppeteer / chromedriver (and run them both with JS enabled and with JS disabled).
* Implement unit tests for remaining shared code.
* Implement integration tests for backend and frontend code, maybe?
* Ensure that everything is accessible.
* For better accessibility, maybe there is also a need for a form where an user can enter row number and column number to make a move,
instead of clicking on a square (or activating it from keyboard, which works just fine now,
but idk how it is compatible with screen readers exactly).
* Should I also add row number and column number hints to squares for screen readers? idk.
* Rewrite solver so that it doesn't take a minute to compute all games on 4x4 board
(which only has under 10 millions states that can be encountered during legal play).

Loading…
Cancel
Save