Install demo data. In the frontend, select the item to create an article. Notice the AUTHOR (a custom field that is created with demo data), Publish, Metadata tabs. One tab has a legend, others don't. Out of sync.
Now, for example, create a CREATE CONTACT menu item in the control panel. Go to the front again and try to make contact. Now check out the tabbed legends here.
One thing is clear - there is no single solution. I think similar places can be found 50/50 in other extensions. I am ready to review all such pages and report them if a clear decision is made whether the legends on the tabs are needed or not.
My opinion is that duplication of the tab title is absolutely useless. Correct me if I do not understand why this is.
Labels |
Added:
?
|
We are doing all for disabled users and sometimes this results in bad UX for sighted users. Less noise would be appreciated.
Sorry, it is so hot today.
Accessibility requires that fields are grouped into fieldsets and fieldsets need a legend. But I also feel, as sighted user, that there is information noise when the same information appears several times. I feel it "too much" if the tab and the legend show the same information.
. I feel it "too much" if the tab and the legend show the same information.
I understand what you are saying (and while I personally dont see a problem) I know that if some tabs have visible fieldset legends and others do not then people will report that as a bug.
I have a PR for the missing character count, very attentive :) please test #34563
Your remarks concerning the fieldset and legend are answered by @brianteeman, so maybe this issue can be closed?
Closing this for now as the bug is resolved and the question is answered.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-06-22 21:17:04 |
Closed_By | ⇒ | chmst |
A fieldset must have a legend.
In some tabs there are multiple fieldsets but in others there is only one hence the apparent useless duplication. However it is a requirement to have a legend