-
iCagenda
-
iCagenda - English
-
WCAG 2.0 Compliance error - Check 185 - ID attribute is not unique
WCAG 2.0 Compliance error - Check 185 - ID attribute is not unique
-
4samuels
-
Topic Author
-
New Member
-
Less
More
-
Posts: 6
-
Thank you received: 0
-
-
4 years 1 week ago #17226
by 4samuels
Hello, I have a WCAG 2.0 compliance error. It is check 185 - "ID attribute is not unique".
Can you please advise how I can make the ID unique so that it passes accessibility compliance? I'm using this same ID attribute with the T3 framework. Where is the file located? What could I change the ID attribute to?
Thank you in advance for your help,
Please Log in or Create an account to join the conversation.
-
4samuels
-
Topic Author
-
New Member
-
Less
More
-
Posts: 6
-
Thank you received: 0
-
-
4 years 1 week ago #17227
by 4samuels
Although I haven't yet solved my issue after further investigation it does not appear to be an issue with iCagenda itself.
I am using Components Anywhere that displays iCagenda events. Components Anywhere and the T3 framework are using the same ID attribute which is causing the WCAG error.
Please Log in or Create an account to join the conversation.
-
Lyr!C
-
-
Administrator
-
-
Lead Developer
Less
More
-
Posts: 6777
-
Thank you received: 606
-
-
-
-
3 years 11 months ago #17236
by Lyr!C
Hello,
At ready first message, i was wondering what was this ID issue, but reading the second message, i understand better!
Seems more a conflict of ID between component Anywhere and T3 framework. Did you contact one of them?
Best regards,
Cyril
Latest version : iCagenda 3.9.7
We recommend every user to keep iCagenda updated.
Don't forget to have your Joomla!™ up-to-date!
Do you like iCagenda?
I would appreciate if you could take 5 minutes to post a review on
JED (Joomla Extensions Directory)
.
Please Log in or Create an account to join the conversation.
-
iCagenda
-
iCagenda - English
-
WCAG 2.0 Compliance error - Check 185 - ID attribute is not unique
Time to create page: 0.069 seconds