Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Front-End Checklist

github.com

Post reply on HN
Print view View original

61–70 of 82 posts

Re: Front-End Checklist

#63

Post by laktek »

mycentstoo wrote: post #62

What would be a great idea is an app that scans for the presence of these conditions.

If anyone wants to have a crack at it, you can use Page.REST to build it. If not I might be able to get to it towards next week :)

Re: Front-End Checklist

#64

Post by miguelrochefort »

zeronight wrote: post #22
miguelrochefort wrote: post #2

It's already missing iPhone X support.

It will be interesting to find what the visitor percentages are for iPhone x. Even though its Apple, at some point its not worth spending the time and money.

The iPhone X will be sold out everywhere until 2018.

Re: Front-End Checklist

#65

Post by gspetr »

corymayfield wrote: post #45
rimliu wrote: post #14

Earlier quoted context omitted.

This recommendation would be fine 20 years ago. You should not have any decorative images in your markup, they belong to CSS.

Some people like myself work in places where there are still some clients that ask for IE6 compatibility and have to comply with WCAG 2.0 accessibility standards.

What makes it worth it for you to keep working there?

Re: Front-End Checklist

#68

Post by groby_b »

chrismorgan wrote: post #56
groby_b wrote: post #54

Earlier quoted context omitted.

No. But e.g. automated translation now needs to guess your language, and that's... not always successful. Screenreaders will need to guess the language to pronounce properly. Search engines will have to infer the language. And so on. Your site isn't "broken", per se, but it's not as high quality as it could be.

I wonder how much lang=en can actually be trusted—enough things put it in by default that I can easily imagine its presence on non-English pages. Update: from elsewhere on this thread, Google ignores : > But the language attribute within the HTML markup is something we don't use at all. We've found that this language markup is something that is almost always wrong. So we tend to ignore that. https://www.seroundtable.…

It tends to be more reliable if it's not lang=en. The cargo culting nature of web development makes some things a bit painful.

FWIW, Chrome's translate feature does care about lang=. Or at least it did last time I checked.

It's one of the things that has no downside, and a small upside. If you leave it out, your site isn't horribly broken. People will always get the content, but tools that process the content might be wrong.

Re: Front-End Checklist

#70

Post by fold_left »

drusepth wrote: post #58
robin_reala wrote: post #17

Earlier quoted context omitted.

Exactly. Every img element should have an alt attribute; those with visual content should have explanatory text in it.

What is the value of having an alt attribute if its value is blank? Just to tell someone poking at the source code that, "yeah, I know I'm supposed to have this, and it's intentionally left blank"?

No, the reason given was

> 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

Post reply on HN