legal requirement for websites to be accessible to individuals with disabilities.
y
yazan abuzeed
The Service Accessibility Regulations concern the removing of barriers so that people with disabilities will be able to receive services with the same level of comfort and quality as the general public, and lead an independent and full life. The Service Accessibility Regulations deal with a wide range of issues including: physical accessibility of the places where the service is provided, accommodations of the ways and means in which it is provided, ways of providing accessible information and making the different services accessible.
Many service providers use the web to provide services to the public (for example, sales and commerce). Websites are also often used to provide information about services. In order to provide equal service to people with disabilities via the internet, accommodations in websites or applications providing service, or information about a service. are mandated, in accordance with the provisions of Article C of the Equal Rights for People with Disabilities (Service Accessibility Accommodations) Regulations, 5773-2013 (hereinafter: the 'Service Accessibility Regulations').
those pictures are for example!@!
it's really important, This accessibility menu ensures that users with visual impairments or other accessibility needs can adjust the website to their preferences.
Photo Viewer
View photos in a modal
Log In
C
Chris Stamler
I would like to add my support to Julie White’s April 13, 2026 request for the Website/Funnel Builder to use native semantic HTML elements, including <header>, <nav>, <main>, and <footer>.
I have completed accessibility training and have tested my publicly discoverable GHL webpages with WAVE, alongside manual keyboard testing. My pages currently return 0 WAVE errors and 0 contrast errors, and keyboard focus is visible and functional on interactive controls. However, every page returns the same page-regions/landmarks alert.
My pages already have the intended visual structure: a top logo/site-identity area, a primary navigation menu on the homepage, main page content, and a footer. The issue is that the Website/Funnel Builder does not currently appear to provide an author-facing way to identify the corresponding top-level sections as semantic landmarks in the generated HTML.
Please add a page-builder setting that lets an author designate a selected top-level section or container as one of the following:
● Header / banner
● Navigation
● Main content
● Footer / content information
Where multiple navigation areas exist, please provide an accessible label field, for example, “Primary navigation” or “Footer navigation.”
Native semantic output would be substantially more robust than requiring users to add JavaScript workarounds based on generated CSS selectors. It would help screen-reader users navigate efficiently between major areas of a page, improve semantic structure for accessibility, and support SEO and machine-readable page understanding.
As a secondary advanced option, it would also be helpful if authors could assign a stable, unique HTML ID to a selected top-level section or container. This would support reliable integrations and advanced accessibility use cases without depending on automatically generated class names or page position.
S
Sales & Marketing
Merged in a post:
aria-label NEEDED
S
Susan Winters
aria-label needed on BUTTONS and IMAGES in order to pass Accessibility checks on these Websites using the GHL Builder.
S
Sales & Marketing
Merged in a post:
Website / Funnel builder should use semantic html elements such as <header><footer>
J
Julie White
For SEO and accessibility the back end code of the website and funnel builder should use HTML semantic elements. This is becoming even more important as generative search develops more and more.
"HTML semantic elements are HTML tags that define the meaning or purpose of the content they contain, rather than just the appearance. Some examples of semantic elements include:
<header>: Defines the header section of a document or a section
<nav>: Defines a set of navigation links
<article>: Defines an independent, self-contained piece of content
<section>: Defines a section in a document
<aside>: Defines some content loosely related to the page content
<footer>: Defines the footer section of a document or a section
<time>: Defines a date/time
<figure>: Defines self-contained content, like illustrations, diagrams, photos, etc.
The use of semantic elements helps provide more meaning and structure to web pages, making the content more understandable for both humans and machines (such as search engines). This improves accessibility, SEO, and overall code readability."
At the moment, everything appears to be contained within an <aside> (<aside>: Defines some content loosely related to the page content) tag which is really not good!
Photo Viewer
View photos in a modal
E
Elsie Silva Kniff
This is very important in Canada as there are some deadlines this year legally that we are supposed to have this done on our websites.