Skip to content
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

Open
SpacyRicochet opened this issue Oct 11, 2020 · 3 comments
Open

Further improvement in CombatantRow's accessibility label. #7

SpacyRicochet opened this issue Oct 11, 2020 · 3 comments

Comments

@SpacyRicochet
Copy link
Contributor

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;

"Mummy, HP: 64 of 58 including 8 temporary, AC: 11, Initiative modifier: -1"

I agree with this advice, though it has some implications;

  • We should move the accessibility texts from the individual components to CombatantRow.
  • Since the entire row would be one sentence, it can be considered to move the additional actions (update HP and roll initiative to the row's accessibilityActions.

That would be a bit of a change, so discussing this here first.

@Thomvis
Copy link
Owner

Thomvis commented Oct 11, 2020

Thanks for looking into this; I agree the advice makes sense. That would lead to quite a few actions on the row:

  • update hp
  • roll initiative
  • open combatant details screen
  • open context menu for more/"secondary" actions (remove, duplicate, eliminate, etc.)

Is that a problem, should this be structured differently?

@SpacyRicochet
Copy link
Contributor Author

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;

  • Base action; Open stat block.
  • Additional actions;
    • Update HP
    • Roll initiative
    • Open context menu

So the default activate would open the stat block, and swiping up or down would rotate between that and the additional actions.

@Thomvis
Copy link
Owner

Thomvis commented Oct 11, 2020

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 .accessibilityElement(children: .combine)

SpacyRicochet added a commit to SpacyRicochet/Construct that referenced this issue Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants