How to make Helix Ultimate WCAG 2.0 AA compliant in 2 easy steps (time: appox. 4 minutes) - Forum | JoomShaper
Solved Helix Framework

How to make Helix Ultimate WCAG 2.0 AA compliant in 2 easy steps (time: appox. 4 minutes)

Asked by Alexander I. 5 years ago Last activity 1 year ago

1) file templates/shaper_helixultimate/features/menu.php

Change all 3 i tags (Font awesome icons) to spans, lines 37, 48 and 56.
You should also add titles to their a tags (anchor links), I suggest you just copy the existing JText::_('HELIX_ULTIMATE_NAVIGATION');

Updated lines now look like this (template version 1.1.4) https://imgur.com/zYNemYP

2) file templates/shaper_helixultimate/index.php

Add a title to the a tag (anchor link) in line 150 once again copying the already existing JText::_('HELIX_ULTIMATE_NAVIGATION');

Updated lines now look like this (template version 1.1.4) https://imgur.com/BuR2jXl

I haven't noticed any layout issues resulting from these changes (template version 1.1.4), they are pretty subtle anyway.

You can check your website's WCAG here => https://achecker.achecks.ca/checker/index.php

I'm hoping these changes will find their way to the next release of Helix Ultimate, making thousands of Joomla websites a little friendlier to people with impaired vision :)

Accepted answer

Marked as the solution
Toufiq Senior Staff
5 years ago

Hi there,

Thanks for sharing with us. I will share your forum post our developer team. I hope developer team will check & give you feedback.

-Thanks

12 more replies

Oldest first Newest first Most helpful
Alexander I. Asked this
5 years ago

Thanks Toufiq, this not only makes sense for visually impaired users but also may help improve the website's SEO since Lighthouse metrics do take these things into consideration.

I'd be happy to hear from the development team even if their answer is a negative one.

Thanks,
Alex

Paul Frankowski Senior Staff
5 years ago

Big Thanks,
have you checked also our new Helix Ultimate 2.0 (beta3 so far) we improved accessibility there.

Your steps are useful, but it's beginning of the accessibility path.

Alexander I. Asked this
5 years ago

Hi Paul, yes I'm aware of Helix Ultimate 2.0 and looking forward to the production release :)

I just made the above suggestion as an easy 4-minute improvement (these are actually the steps I take after every Helix Ultimate update to maintain the compliance of my websites using the template).

Just to be clear to all people reading: Anyone who has engaged in making a website WCAG compliant is well aware that it's a complex matter dependant on a multitude of factors, e.g. color palette, whitespace, typography, content a.o. so the website's compliance is also very much up to the web designer/developer, admin and content creator.

Paul Frankowski Senior Staff
5 years ago

As we always repeat, accessibility is a process, not only done and forget about it.

I fully agree that your suggestions may help get better score in WCAGS online tests.
So we are very happy that you shared them. Thx again.

Paul Frankowski Senior Staff
5 years ago

@Toufiq I think most of them are already included inside HU 2.0 beta, but I will check after RC publication.

‏‏‎ ‎J‏‏‎‎e‏‎‏‏‎‎n‏‏‎‎s W.‏‏‎
4 years ago · edited

ㅤ

Toufiq Senior Staff
4 years ago

@Jens Weck We just added compatible with the Joomla 4. I hope in the future update it will fix. Thanks

Paul Frankowski Senior Staff
1 year ago

WCAG update in Helix Ultimate v2.1.3:

  • We improved Mega Menu accessibility by adding keyboard (Tabs & Arrows) navigation support.
  • Accessibility was also improved in Mobile Menu - for icons [=] and [x]
Log in to reply.