#Hello, author. Have there been any changes to how information is displayed in the game?
1 messages · Page 1 of 1 (latest)
@gray cypress Your report has been looked into and a related change is coming! A related change is planned for version v0.6.57. Thank you for your feedback!
Great! I had just learned about the adjustment to the Fist ability system and immediately couldn't wait to open the game. Then I found that the mouse targeting information was no longer displayed, which made me feel like the sky had collapsed. Thank you so much for promptly noticing the feedback—otherwise, I think I would have suffered for a long time.
@gray cypress Version v0.6.57 has been released with changes related to your report! Thank you for your feedback!
Thank you for your improvements. However, I'm not sure why I'm still experiencing the issue where the screen reader doesn't display detailed information after mouse targeting in version 0.6.57. I don't know why this is happening—everything was normal before version 0.6.56. But looking at the changelog for 0.6.56, it seems there were no changes related to the information display method.
ill reopen it and have a look
@gray cypress Your report has been looked into and a related change is coming! A related change is planned for version v0.6.57. Thank you for your feedback!
Sorry, I don't want to keep bothering you, but after the update, my screen reader still isn't displaying any information. 第12项,共12项
Can I confirm that you are playing in screen reader mode?
As in the option in the settings?
@gray cypress Your report has been looked into and a related change is coming! A related change is planned for version v0.6.59. Thank you for your feedback!
Here's the English translation:
Here's the situation. Before the issue occurred, the accessibility mode worked well on other pages. The problem only appeared on the technique viewing and editing page. This is because we need to use the cursor keys to view the technique icons, and then use the screen reader's built-in mouse tracking feature to move the mouse to the cursor's position. However, in screen reader mode, clicking on mouse tracking does nothing.
So I'm wondering if you could fix the issue of the intersection not being read in normal mode, rather than only fixing it in screen reader mode. Alternatively, you could define the normal mode with mouse intersection reading support as a new mode.
Thank you very much for your optimization, and I apologize for troubling you multiple times over this issue.