- From: Lucy GRECO <lgreco@berkeley.edu>
- Date: Thu, 22 Sep 2022 10:44:02 -0700
- To: Kiran <kiranph@gmail.com>
- Cc: w3c WAI List <w3c-wai-ig@w3.org>
- Message-ID: <CAESOp7pb+q9jrhxm+CuBO3=t56AXDc6v_=S+Va=9R57ZrKPJiw@mail.gmail.com>
this is the first time i have ever herd of some one want to not get more hits on a hedding not less Berkeley IT <https://technology.berkeley.edu/home> Lucy Greco, Web Accessibility Evangelist Campus IT Experience Phone: (510) 289-6008 | Email: lgreco@berkeley.edu | https://webaccess.berkeley.edu Follow me on twitter @accessaces We champion diversity. We act with integrity. We deliver. We innovate. On Thu, Sep 22, 2022 at 10:41 AM Kiran <kiranph@gmail.com> wrote: > Hey you all! > > I am here again with some guidance needed from you all. > > While reviewing for accessibility-related issues, I raised my concern > about not having some heading attributes to some of the section headings > which is a must for accessibility. To that- the other team replied that > it is removed intentionally for SEO reasons. They are looking for a > solution where even less important heading attributes like h3, and h4 can > be avoided while still meeting the accessibility compliance requirements. > > 1. Per my understanding, heading attributes -specifying in HTML formats > like H1, and H2 is a must and we should implement it that way only. am I > correct here? > > 2. What other solution can be implemented which will make both WCAG 2.1 AA > and SEO happy? > > Please guide. > > And thank you as always for the support this group provides. > > Regards > ~ Kiran > > > > > > >
Received on Thursday, 22 September 2022 17:44:54 UTC