- This topic has 12 replies, 4 voices, and was last updated 5 months ago by
Tom.
-
AuthorPosts
-
March 9, 2022 at 2:41 pm #2148786
Maria
Axe Dev Tools is giving me this error on my page titles. Any idea why? See screenshots: https://www.screencast.com/t/71lytO7ofV7
March 9, 2022 at 7:33 pm #2148941Elvin
StaffCustomer SupportHi Maria,
Can you try setting up a Block Element – Page hero containing this setup?
https://share.getcloudapp.com/5zuLpP1qAnd then try checking with axe-core dev tools if it still gets flagged.
A wise man once said:
"Have you cleared your cache?"March 10, 2022 at 10:07 am #2149834Maria
Will do. What should I set the Element Type and Hook Name to?
March 10, 2022 at 10:57 am #2149872Ying
StaffCustomer SupportThe type would be
page hero
, you don’t need to selecthook name
whenpage hero
is selected as the element type.March 10, 2022 at 11:36 am #2149926Maria
Thanks for the clarification. I’m not sure why I should be doing this. When creating a page, I should just be able to enter the title and not get any accessibility errors.
March 10, 2022 at 11:54 am #2149959Ying
StaffCustomer SupportYou should not π
As accessibility rules are changing rapidly, we might not be able to keep up with it with our updates.
I would mention this to Tom see what he thinks.
March 10, 2022 at 11:56 am #2149961Maria
If you could pass this on to him, that would be great. I appreciate your help.
March 10, 2022 at 12:06 pm #2149974Ying
StaffCustomer SupportYou are welcome π
March 10, 2022 at 7:51 pm #2150254Tom
Lead DeveloperLead DeveloperHi there,
Any chance you can link me to that page so I can take a closer look?
Let me know π
Documentation: http://docs.generatepress.com/
Adding CSS: http://docs.generatepress.com/article/adding-css/
Ongoing Development: https://generatepress.com/ongoing-developmentMarch 11, 2022 at 5:47 am #2150684Maria
I get the error on all pages except the Home page. Here’s one of the pages: https://a6awareness.org/testing-centers/
March 11, 2022 at 8:58 pm #2151561Tom
Lead DeveloperLead DeveloperThe
aria-label
is required on theheader
element, but arole
should not be required asheader
already implies the role (the header of the content).Have you checked the page using a different accessibility tool? It’s possible that the one you’re using is wanting a
role
attribute even though it shouldn’t be necessary.We can remove the
aria-label
with a filter very simply, but doing so will cause more accessibility errors for you. We can also add arole
attribute very easily with a filter if you’d like us to provide it.Let me know π
Documentation: http://docs.generatepress.com/
Adding CSS: http://docs.generatepress.com/article/adding-css/
Ongoing Development: https://generatepress.com/ongoing-developmentMarch 11, 2022 at 9:50 pm #2151586Maria
I’m going to leave it alone. I did check it with other accessibility tools and didn’t get any errors so I’m good. Thanks for looking into it for me.
March 12, 2022 at 8:18 pm #2152534Tom
Lead DeveloperLead DeveloperNo problem!
Documentation: http://docs.generatepress.com/
Adding CSS: http://docs.generatepress.com/article/adding-css/
Ongoing Development: https://generatepress.com/ongoing-development -
AuthorPosts
- You must be logged in to reply to this topic.