Cart is not accessible to VoiceOver in base styles

[scottsb]

Preconditions (*)

All versions from 2.0.0 to 2.3.0

Steps to reproduce (*)

1. Add two items to cart.
2. Use VoiceOver on Mac to navigate through cart using "next item" keyboard shortcut or gesture.

Expected result (*)

VoiceOver navigates through each cell in sequence.

Actual result (*)

1. VoiceOver skips the first cell containing the item name, meaning that a visually impaired user cannot understand what is actually in their cart.
2. VoiceOver skips the last row in the cart (containing action buttons), meaning they cannot remove or edit the last item from their cart.

Diagnosis

These have two separate causes:

1. VoiceOver skips the first table cell because it is marked with display: block, which VoiceOver interprets as meaning the cell is only presentational. Anytime CSS changes the display property on a table element, it effectively changes the implicit role as well. This can be fixed by either getting rid of the CSS rule, which doesn't seem necessary in the first place, or by explicitly adding a role="gridcell" to the first <td> where the CSS rule is applied.
2. VoiceOver skips the last row due to how the <caption> is being hidden. This seems like it may be a bug in VoiceOver itself, but by virtue of the position: absolute being applied through the lib-visually-hidden mixin, it seems to remove it from the table (for a similar reason as the prior point), yet fail to internally account for this properly when determining how many rows to read through.

I may submit a PR for this, but I'm waiting for feedback on the best way to resolve the second issue. Glad to hear any suggestions here, and I've also posted on Stack Overflow:
https://stackoverflow.com/questions/54876969/how-to-accessibly-hide-table-caption-element

[magento-engcom-team]

Hi @scottsb. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@scottsb do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[Jitheesh]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @Jitheesh. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @Jitheesh, here is your Magento instance.
Admin access: https://i-21447-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[adarshkhatri]

@magento-engcom-team give me 2.3.0 instance

[magento-engcom-team]

Hi @adarshkhatri. Thank you for your request. I'm working on Magento 2.3.0 instance for you

[magento-engcom-team]

Hi @adarshkhatri, here is your Magento instance.
Admin access: https://i-21447-2-3-0.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[adarshkhatri]

@magento-engcom-team give me 2.3.0 instance

[magento-engcom-team]

Hi @adarshkhatri. Thank you for your request. I'm working on Magento 2.3.0 instance for you

[magento-engcom-team]

Hi @adarshkhatri, here is your Magento instance.
Admin access: https://i-21447-2-3-0.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• Next steps are available in case you are a member of Community Maintainers.

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @engcom-backlog-nazar. Thank you for your request. I'm working on Magento 2.3-develop instance for you