Replies: 3 comments 2 replies
-
|
Another issue I just realized is that the subtitle of the process is presented as
There are two problems with this:
I propose that we would fix this for the time being by removing the If the proposed change is done, it will affect also some other views, such as the component index views which list the items in that component as they have the listing title marked as |
Beta Was this translation helpful? Give feedback.
-
|
About the h2 subtitle, I agree. I've just mentioned the same change after doing a really small research:
|
Beta Was this translation helpful? Give feedback.
-
|
Great, there is now a PR for this building at #8901. |
Beta Was this translation helpful? Give feedback.
-
|
Totally agree. We'll take this into account for the redesign. |
Beta Was this translation helpful? Give feedback.
-
|
We have took a look on the accessibility issues on the platform that we are running. We can share some of the findings, but I am not sure that all are applicable to Decidim Core. cc @roxanaopr . |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently Decidim duplicates H1-level headings on many pages. For instance, take these pages at MetaDecidim:
Propose new functionalities for Decidim software"
Semantically this is a problem because these pages indicate the same content at the highest heading level. Generally websites should have individual and unique H1 headings on all pages which indicate the content on that unique page. For example, in the example page, the H1 headings should be as follows in the perfect world:
<h3>actually but about to be fixed as<h2>)A good general advice is also that the first "section" of the page's
<title>element should match the page's H1 element. The<title>elements on these pages are already in line with the suggested approach above, but the H1 elements are duplicated right now as described above. From SEO perspective, having semantically correct content on all web pages would also make the structure easier to understand for search spiders and also make the content to be more easily discoverable through search engines.Additionally to being semantically correct, the duplicated H1 headings on multiple pages also causes an issue for the users of assistive technologies who have been reported to glance through the page headings when they first arrive on a page to get a sense about the content on that page. If the same H1 heading is duplicated on multiple pages, it makes the structure harder to understand for users of such assistive technologies.
I am well aware of the current ongoing redesign process with Decidim but since I have not seen all the plans, I also don't know if this problem is being addressed during this process. I think this is quite a fundamental issue in the current design that should be addressed during the redesign process. As I have understood, the redesign will introduce a breadcrumbs element on all pages, which should make it unnecessary to display e.g. the process name on all pages as
<h1>as it would be already in the breadcrumbs element, leaving the<h1>element "free" for the actual content on each page.This is also related to the larger structural complexity issue in Decidim which has been raised as a discussion point in the redesign meetings. But I just wanted to make sure this point of view would be also considered during the redesign process by opening this discussion thread and bringing some attention to this problem through this.
Beta Was this translation helpful? Give feedback.
All reactions