It is not enough to just have a visually appealing or aesthetically pleasing website. If users find it difficult to navigate your page, It is a fa...
For further actions, you may consider blocking this person and/or reporting abuse
I'm glad you mentioned "description" -- the conventional wisdom around SEO is that Google doesn't care about it, so no point in bothering with it. It's so easy to forget that accessibility is a goal entirely of its own, and that "description" is useful for something even if that something isn't SEO.
Thank you for reading and I hope you got value for your time. Follow me on twitter @Frontend_Jedi to connect and learn more about web development and ocassional sarcasm. Follow me here on dev.to @frontend_jedi for more contents like this. Remember to leave a comment.
I never knew that the tag can make code more accessible. I thought it was just protocol for setting up the HTML document. Thanks for the great post @frontend_jedi! π
my pleasure Christine and thanks for reading!
nice tips! you could also mention the
og:title
andog:description
tags for embedding.Hello Medea, thanks for your suggestion
Although content on the internet is typically created for the purpose of sharing and open graph simplifies this, I do not believe it neccesary in respect to accessibility
Please do not read this as me shrugging off your suggestion, I would love to know how og would help in accessibility, so please do well to elaborate your point. I would love to hear from you and thanks for reading my content.
Hey, I completely understand your point, and agree that embeds arenβt that important as the ones you have listed, but they can still play a part in accessibility.
For example, if someone sends you a link, thereβs a big chance you might miss it if there is no context with it. However if it has an embed, thereβs a bigger chance it will catch your eye and you will want to view it.
Mehn... I never thought about it this way, clever! and thanks for your explanation, because personally I love to see a preview of any link i'm being sent π
great to know you agree! keep posting because your posts are always pretty interesting
Thanks for your kind words, what's your twitter handle, I'd love to connect
hey, sorry I donβt have Twitter, but if you ever need to email me: vulcanwmemail@gmail.com
Hi Excel Bill, my understanding of accessibility differs from yours.
I would strongly advise against disabling user zooming, accessibility is about user choice to cater for the needs of the individual, although itβs mostly about allowing all content to be viewed by as many people as possible (those with poor vision who may require zoom to extremes) it is as much about UX because a well designed experience tends to lend itself to accessibility.
The description meta tag, this is another that falls under good experience and doesnβt immediately fall under accessibility it is just content that happens to be enriching a website that the Search Engine will also fallback for if none is provided, itβs UX because it doesnβt loose context if not provided due to that fallback.
Title, yes agreed itβs a really important one but again could that be UX, idea or no idea does not translate to some people understanding and others not due to the use of AT
You see my points and I hope that the least this comment will count towards your posts rankingπ
Hi Adam, thank you so much for your observations
Firstly, this is going to be a series and in one of the series, I was going to talk about enabling font size increment and decrement, the reason I support disabling user zooming is mostly ui, because it can lead to content and UI breaking, so to preserve the UI and still have the option of zooming, things like lightbox for images and optional font zoom for text should be put in place, it also helps for users who don't have fingers to zoom and also need the option of bigger text.
For the description meta tag, I'm probably wrong but I read somewhere that screen readers can give a brief description of the site on hover of the link shown in a search engine, which means you don't have to visit the site to know if it is what you're looking for, for me that screams accessibility for visually impaired users, please correct me if I'm wrong.
Lastly, I think the title tag speaks for itself in terms of screen readers aiding the visually impaired users understand or know what the site title is, for example, say a blind user prompts google to search for "How to make tofu" and the first link is an ad about the most famous tofu place in china, the title tag doesn't lie and the user will definitely know it's not the tutorial he or she was looking for.
Finally, thank you so much for taking out the time to read through and give me these educating feedback, I really appreciate and would still love to hear from you. Thanks.
Love how you focus on the HTML, we've had discussions internally at my company where Aria has come up and basically we were told don't as about everything you need can be done in HTML so long as you do it correctly so the tools work with it.