-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessibility in Emails #728
Comments
I'm happy to submit a PR for this, but unsure of the best approach. |
I ran into this issue again today. Having |
I've made a PR in the Inky repo. It might take some time before it gets approved and bubbles all the way into Until then...
|
Any updates? |
No as you can see =) Any help is very welcome. |
Not sure wich one. In such cases please always link it. |
There it is: https://github.com/foundation/inky/pull/102/files |
Bump because this would be an improvement still 💯 |
+1 |
How can we reproduce this bug?
Any component that generates a
<table>
element.What did you expect to happen?
Add
role="presentation"
to the<table>
.What happened instead?
Without this ARIA Role, screen readers try to read the table as tabular data, which is incorrect.
What email clients does this happen in?
All, when a screen reader is being used.
Most of the time you can add a
role="presentation"
to the Inky component, in the case of<center>
, it does not get applied correctly. Ideally, that role would automatically get applied during the build system to keep the working markup cleaner. I don't think there are any drawbacks to this because if you really wanted to display a<table>
as tabular data, you would just build the table using the<table>
element, not<container>
.Further Reading: http://blog.rebelmail.com/accessibility-in-email-part-ii/
The text was updated successfully, but these errors were encountered: