A clear and concise description of what the bug is.
When navigating with a screen reader, the following occurs:
The main Month and Day are presented as plain text. If a user is navigating with headings or with TAB moving through interactive elements, they will encounter the name of the event and skip past the Month/Day. If they are interested in the event, they may then navigate downward using arrow keys to hear the details of the event. As they do, they will encounter the plain text for the NEXT event. There is no indication that this is not for the event the screen reader user is reading details on. The current implementation would require the SR user to navigate backwards to find the day/month for the event prior to the event name.
Recommendations
Consider a review of the layout of the calendar so that the day and month are:
1.) Part of the event title
2.) Come after the event title.
3.) Or make the day/month a heading in itself so that a user comes upon this first. The downside of this is that one may have headings with the same name if there are repeated events on the same day. An alternative would be to have a day/month heading and then list all events that occur on that day/month after that heading.
We can discuss this further, but just listing a few initial ideas for consideration.
Screenshots
If applicable, add screenshots to help explain your problem.
Source
https://airtable.com/appRFUc45sF4yWFut/tbl51inE74gEWlB0x/viwG9G4vAjsjQEh4g/recqCDJHZsgnW1YwX?blocks=hide
Describe the bug
A clear and concise description of what the bug is.
When navigating with a screen reader, the following occurs:
The main Month and Day are presented as plain text. If a user is navigating with headings or with TAB moving through interactive elements, they will encounter the name of the event and skip past the Month/Day. If they are interested in the event, they may then navigate downward using arrow keys to hear the details of the event. As they do, they will encounter the plain text for the NEXT event. There is no indication that this is not for the event the screen reader user is reading details on. The current implementation would require the SR user to navigate backwards to find the day/month for the event prior to the event name.
Recommendations
Consider a review of the layout of the calendar so that the day and month are:
1.) Part of the event title 2.) Come after the event title. 3.) Or make the day/month a heading in itself so that a user comes upon this first. The downside of this is that one may have headings with the same name if there are repeated events on the same day. An alternative would be to have a day/month heading and then list all events that occur on that day/month after that heading.
We can discuss this further, but just listing a few initial ideas for consideration.
Screenshots
If applicable, add screenshots to help explain your problem.
https://github.com/proudcity/wp-proudcity/assets/1569463/0852af15-121b-4eae-a367-1b89e42eb5dd