nikiforosk
nikiforosk
@Adedoyinebi to check if these are still valid after implementing the changes in #1946
@bhushan-ebi Please close this tasks when the subtasks are completed.
So vf-section headers are currently treated as h2 semantically but as h3 visually (with 24px font instead of 30px). I'd recommend against treating them as h3 semantically because this will...
Also just to remind you that a vf-section-header with a link is still not a h2, at least according to WAVE. An example is the "Recruitment" link in this report:...
>> Also just to remind you that a vf-section-header with a link is still not a h2, at least according to WAVE. An example is the "Recruitment" link in this...
> As you can tell this is a pretty broad change, so it would be best until the new product designer joins and came make new reference designs. I agree...
This issue came up again in our review of [the accessibility of the EMBL-EBI site](https://docs.google.com/presentation/d/13QfRjFJtjRkaXVXrlfKPafrjhLvH7-lNgM7EF02VxMc/edit#slide=id.gffa5e227f5_1_69) with @sandykadam (see slides 23-24, 32 and 36: viewing the presentation may require access). We...
Related to #1926
Thank you @biomadeira for suggesting this. @MGS-sails has added an autocomplete feature to the drop-down of [vf-form](https://stable.visual-framework.dev/components/vf-form/) for [the Registration page of the EMBL-EBI Training site](https://www.ebi.ac.uk/training/user/register):  This looks more like an acknowledgement of partnerships. Also, would [the elixir-banner](https://stable.visual-framework.dev/components/vf-banner-elixir/) fall into this category? I feel that...