inga-lovinde
/
sample-tictactoe
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README: expanded thoughts about accessibility

Browse Source
main
Inga 🏳‍🌈 2 days ago
parent 67a9f6490a
commit c5eac547fb
1 changed files with 5 additions and 0 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 5
      README.md

5
README.md
Unescape View File

@ -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 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 unit tests for remaining shared code.
* Implement integration tests for backend and frontend code, maybe? * 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 * 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). (which only has under 10 millions states that can be encountered during legal play).

Write Preview
Loading…
Cancel
Save