Skip to content

Improve Accessibility of Andromeda Armada Display - #1539

Merged
pmotschmann merged 2 commits into
pmotschmann:DeadSpacefrom
AERobert:accessible_armada
Aug 8, 2026
Merged

Improve Accessibility of Andromeda Armada Display#1539
pmotschmann merged 2 commits into
pmotschmann:DeadSpacefrom
AERobert:accessible_armada

Conversation

@AERobert

Copy link
Copy Markdown
Contributor

The current controls for Andromeda ships are confusing when navigating with a screen reader, since it's supposed to visually be a grid (I believe). The changes in this PR improve things, at least during my testing. All changes only change the aria or the contents of "is-sr-only" elements, so I am pretty sure nothing changes visually.

  1. is-sr-only h4 elements are placed before the columns of each ship type with movement controls.
  2. Another is-sr-only span is added after the h4 elements to better signify that the next number represents the count of that type of ship in the Gateway System.
  3. The column consisting of available systems is now hidden using "aria-hidden", as it was simply read as a list of names and was therefore unhelpful for screen readers.
  4. Adds the target system's name to the ARIA labels for the buttons used to move ships within Andromeda. Which is to say, the labels now indicate the system a ship will be removed from or added to.
  5. The labels also now use the proper, localized names of the ships instead of their internal identifiers.

@AERobert
AERobert force-pushed the accessible_armada branch from 6d692dd to 569ec4c Compare July 7, 2026 10:01
@AERobert
AERobert changed the base branch from master to DeadSpace July 7, 2026 10:01
@AERobert
AERobert force-pushed the accessible_armada branch 2 times, most recently from aa265b9 to eefe633 Compare August 1, 2026 06:17
@AERobert

AERobert commented Aug 1, 2026

Copy link
Copy Markdown
Contributor Author

Rebased onto the latest DeadSpace code and fixed a conflict from the refactors of title and desc calls (in 9a11e52 I think),. Also moved the armada${ship} id to correctly be on the visual span again, I had accidentally moved it to the screen reader one before.

Add the target system's name to the ARIA labels for the buttons used to move ships within Andromeda. Which is to say, the labels now indicate the system a ship will be removed from or added to. For example, "Add Scout Ship to Gorddon System" or "Remove Dreadnought from Chthonian". The labels also now use the proper names of the ships instead of their internal identifiers.
The current controls for Andromeda ships are confusing when navigating with a screen reader, since it's supposed to visually be a grid (I believe). The changes in this commit improve things, at least during my testing.

1. `is-sr-only` h4 elements are placed before the columns of each ship type with movement controls.
2. Another `is-sr-only` span is added after the h4 elements to better signify that the next number represents the count of that type of ship in the Gateway System.
3. The column consisting of available systems is now hidden using "aria-hidden", as it was simply read as a list of names and was therefore unhelpful for screen readers.

2026-08-01: fixed conflicts in Dev branch dealing with refactoring "title" and desc code. Made a new variable to hold the long ternary to retrieve the ship title, `shipTitle`, used in the h4 elements and the visual ship name span. The `armada<ship>` id corrected back to the visible ship name.
2026-08-07: Wrap the `galaxyProjects.gxy_gateway.info.name` property in the new SR span with a typeof guard like the other retrievals.
@AERobert
AERobert force-pushed the accessible_armada branch from eefe633 to 12a8baa Compare August 8, 2026 01:49
@pmotschmann
pmotschmann merged commit 0b69ad2 into pmotschmann:DeadSpace Aug 8, 2026
@AERobert
AERobert deleted the accessible_armada branch August 8, 2026 18:58
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

Successfully merging this pull request may close these issues.

2 participants