Open scottsb opened 5 years ago
Hi @scottsb. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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?
@magento-engcom-team give me 2.3-develop instance
Hi @Jitheesh. Thank you for your request. I'm working on Magento 2.3-develop instance for you
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.
@magento-engcom-team give me 2.3.0 instance
Hi @adarshkhatri. Thank you for your request. I'm working on Magento 2.3.0 instance for you
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 give me 2.3.0 instance
Hi @adarshkhatri. Thank you for your request. I'm working on Magento 2.3.0 instance for you
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.
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: :point_down:
[ ] 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
branchDetails
- 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
Hi @engcom-backlog-nazar. Thank you for your request. I'm working on Magento 2.3-develop instance for you
Hi @engcom-backlog-nazar, 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.
:white_check_mark: Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98480
, MAGETWO-98481
were created
Issue Available: @engcom-backlog-nazar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
I do not have time to verify at the moment that this is still valid in 2.4; however, this is an important issue for WCAG compliance, so I don't want it to be closed automatically.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
Posting a comment. Issues should not be automatically closed.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 28 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
Hi @engcom-Delta. 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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.
Preconditions (*)
All versions from 2.0.0 to 2.3.0
Steps to reproduce (*)
Expected result (*)
VoiceOver navigates through each cell in sequence.
Actual result (*)
Diagnosis
These have two separate causes:
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 arole="gridcell"
to the first<td>
where the CSS rule is applied.<caption>
is being hidden. This seems like it may be a bug in VoiceOver itself, but by virtue of theposition: absolute
being applied through thelib-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