You might not be aware, but when you change table elements display property, you break their semantics and break their accessibility. To retain that, you need to add in a role="..." for each table element (<table>, <tr>, <th>, <td>, etc) with the correct (default) role for each of them. It adds a little to the overall HTML markup, but it does mean that those people who rely on screen readers can still understand the table as a table.
Interesting, I didn’t know that but nice that the fix is pretty simple. Still getting to grips with stuff I’ve not had on my radar for quite some time around accessibility. Thanks for commenting 🙂
Yes, I agree, it's not something that many courses or online tutorials on languages/frameworks often give any thought to, so it's not something many developers know about. I must admit, it took me quite some years to really understand the importance of it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You might not be aware, but when you change table elements
displayproperty, you break their semantics and break their accessibility. To retain that, you need to add in arole="..."for each table element (<table>,<tr>,<th>,<td>, etc) with the correct (default) role for each of them. It adds a little to the overall HTML markup, but it does mean that those people who rely on screen readers can still understand the table as a table.Interesting, I didn’t know that but nice that the fix is pretty simple. Still getting to grips with stuff I’ve not had on my radar for quite some time around accessibility. Thanks for commenting 🙂
Yes, I agree, it's not something that many courses or online tutorials on languages/frameworks often give any thought to, so it's not something many developers know about. I must admit, it took me quite some years to really understand the importance of it.