By Paul Bradley on Monday, 08 January 2018
Posted in Technical Issues
Replies 3
Likes 0
Views 651
Votes 0
We have noticed that EB (5.1.15) generates HTML content with repeated HTML ID attribute values of "eb". Although, standard browsers display this pretty much as intended, the issue comes for HTML validation, which tends to cause issues for accessibility and "browsers" (user agents) that are more strict about HTML conformance - as is the case for screen readers and similar accessibility aids. It is my understanding that IDs are to be unique to the whole document (see https://stackoverflow.com/questions/9454645/does-id-have-to-be-unique-in-the-whole-page - it has handy references to the relevant HTML 4 and HTML 5 sections)

At present, EB generates a wrapping DIV with id="eb" and then within that DIV, the wireframe template generates a image popup DIV also with id="eb" (and class="eb-image-popup"). I can, of course, change the wireframe code to use a different ID value, but at the next update this will be overwritten.

I haven't checked exhaustively, but the theme CSS file does reference #eb over 3000 times, and #eb.eb-image-popup 8 times - the latter one could relatively safely be rewritten as either #<newid>.eb-image-popup or #eb .eb-image-popup - but, as I say, I haven't exhaustively checked other EB CSS files.

This does seem rather "trivial" by most measures, but, unfortunately, it makes the task of improving accessibility much harder, and as that is gradually becoming a source of litigation in many jurisdictions (US, CA and the EU to name a few), it should be addressed by all of us.
Unfortunately currently we didn't have a quickly way to remove those same #id in Easyblog HTML structure.

The reason why we added these same #id name in different DIV wrapping area like module, image pop up and etc is because most of these items are needed to avoid conflicts with 3rd party templates / extensions styling.
·
Tuesday, 09 January 2018 15:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Alex,

I accept changing the ID might be non-trivial. I think the point is acceptance that it does need to be changed as surely StackIdeas would wish to generate HTML that validates? I also accept that a huge number of templates, extension and so on (from third parties) may not validate, but that's not a reason for "us" not to try to generate validating HTML.

Thanks
·
Tuesday, 09 January 2018 17:07
·
0 Likes
·
0 Votes
·
0 Comments
·
To be honestly, currently we didn't plan for this yet because this required all the existing theme HTML structure have to follow validator standard and it have to revamp all the current Easyblog Javascript and CSS as well.
·
Wednesday, 10 January 2018 12:07
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post