-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Further improvement in CombatantRow's accessibility label. #7
Comments
Thanks for looking into this; I agree the advice makes sense. That would lead to quite a few actions on the row:
Is that a problem, should this be structured differently? |
I don't think that looks like too much… it seems like four actions is the current maximum, so that is feasible. We could structure it as follows;
So the default activate would open the stat block, and swiping up or down would rotate between that and the additional actions. |
Sounds good. I wonder if we need to manually combine all into a single element/sentence or if that is handled by the system if we use |
After asking some advice in a Slack channel on using the legend, the expert advice was to attempt to ensure that the entire row is read as one sentence. For example;
I agree with this advice, though it has some implications;
update HP
androll initiative
to the row's accessibilityActions.That would be a bit of a change, so discussing this here first.
The text was updated successfully, but these errors were encountered: