Street fields in checkout don't have a label that's readable by a screenreader

[TomFranssen]

Preconditions

1. Standard Magento ver. 2.1.7 installation

Steps to reproduce

1. Add a product to your cart
2. Go to checkout

Expected result

1. The labels should have a valid <label> element that is linked to the <input> field with a for attribute. My advice is to add linked elements to all the address line fields so that screen readers can know what kind of fields the address fields are and thus increasing accessibility.

Actual result

The address lines input fields don't have a <label> element with a valid value. There is a <span> infront of it with the text 'Address'. This text however doesn't get recognised by screen readers.

If I test this on the default MAC screenreader (activated by CMD + F5) I get the feedback of: 'edit text blank'. In this situation the visually impaired user doesn't get feedback on what type of field it is.

[patrikpihlstrom]

I can take a look at this later today if nobody else has claimed it.

[mzeis]

@patrikpihlstrom Looks like the issue is yours!
[Update] Sorry, can't assign you to the issue, your name is not available in the selection.

[okorshenko]

Hi @patrikpihlstrom could you please accept the invitation on GitHub?

[bluemwhitew]

Possibly related to #7428?

[magento-engcom-team]

Hi @scottsb. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. 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

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[scottsb]

@patrikpihlstrom Since this hasn't been touched in two years, I'm assuming you didn't reach a solution. 😆Taking this to work on.

[patrikpihlstrom]

@scottsb Go nuts!

[magento-engcom-team]

Hi @TomFranssen. Thank you for your report.
The issue has been fixed in #21484 by @scottsb in 2.3-develop branch
Related commit(s):

• e1fa2898da686fcad88d0478f0f7e610cc0c6ce6

The fix will be available with the upcoming 2.3.2 release.

[magento-engcom-team]

Hi @TomFranssen. Thank you for your report.
The issue has been fixed in #22070 by @amol2jcommerce in 2.2-develop branch
Related commit(s):

• 3e37244e8d1c6c529cfa5132b848b01fab6faf91

The fix will be available with the upcoming 2.2.9 release.