You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm just wondering if there's anything I'm missing about how to make sure that TinaCMS' UI is accessible. I've followed the quick setup guide for using Tina CMS with 11ty and I've noticed that the field labels and fields in the example configuration don't have a programmatic relationship. Specifically, the Title field has a label:
<labelfor="title">Title</label>
But the title input itself has no ID, so the for attribute on the label doesn't properly link the label to the input. This is flagged in the Chrome developer tools:
I'm wondering if this is a known issue or an easily-resolved configuration issue. I'm trying to evaluate TinaCMS as an appropriate tool for use by content managers who may rely on screen readers or other assistive technologies. Thanks in advance.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I'm just wondering if there's anything I'm missing about how to make sure that TinaCMS' UI is accessible. I've followed the quick setup guide for using Tina CMS with 11ty and I've noticed that the field labels and fields in the example configuration don't have a programmatic relationship. Specifically, the
Title
field has a label:But the title input itself has no ID, so the
for
attribute on the label doesn't properly link the label to the input. This is flagged in the Chrome developer tools:I'm wondering if this is a known issue or an easily-resolved configuration issue. I'm trying to evaluate TinaCMS as an appropriate tool for use by content managers who may rely on screen readers or other assistive technologies. Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions