Front-End Checklist
github.com
Front-End Checklist
1–10 of 82 posts
Re: Front-End Checklist
#2It's already missing iPhone X support.
Re: Front-End Checklist
#3Are sitemaps still a thing that really matters?
Re: Front-End Checklist
#4Are sitemaps still a thing that really matters?
Don't you wanna get crawled?
Re: Front-End Checklist
#5 - High?
why?
Re: Front-End Checklist
#6- High? why?
I'd have thought things like that were better handled as a response header (same for the charset).
Re: Front-End Checklist
#7> Alternative text: High All have an alternative text which describe the image visually.
Please don't do that. Don't put an alt on ALL images. Screen readers will read all of them. Skin and flavour images don't deserve to be read outloud. Nobody wants to hear "bottom left corner of logo" or "rounded corner".
Re: Front-End Checklist
#8- High? why?
I also found that odd. I've always placed mine in the HTML tag.
Re: Front-End Checklist
#9Are sitemaps still a thing that really matters?
If you're coding it from scratch, don't bother.
If you're using wordpress or another pre-baked system, then it's worth having a sitemap plugin (example: Yoast SEO) or the built-in sitemap (like for Shopify).
Submit it to Google Search Console, Bing, and you're done (essentially).
Re: Front-End Checklist
#10> Alternative text: High All have an alternative text which describe the image visually. Please don't do that. Don't put an alt on ALL images. Screen readers will read all of them. Skin and flavour images don't deserve to be read outloud. Nobody wants to hear "bottom left corner of logo" or "rounded corner".
Typically you’d use background images for something like that. Regardless, if you do have an image that doesn’t add anything to the information on the page give it an empty alt attribute to indicate to the screen reader that it shouldn’t try to read out the file name or something.