From c5eac547fbaea3345fa500f159fbb1516861d7b9 Mon Sep 17 00:00:00 2001 From: Inga Date: Wed, 20 Nov 2024 03:47:10 +0000 Subject: [PATCH] README: expanded thoughts about accessibility --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 8720dd2..0318b13 100644 --- a/README.md +++ b/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).