Note: I'll try to include the most relevant metrics on the Part 4 of my Front End Developer Automation series. If you'd like to collaborate, please let me know @papaponmx.
For me the depending on the topic, some of those are:
-
<meta>tags presence and confirm that they include relevant content. - Validate all
htmltags. - First meaningful paint.
- Number, size and latency of initial requests and their relevance.
- Font sizes and images size on mobile devices.
- Color contrast ratio.
- Can I traverse the app just with the keyboard?
What are yours?
Top comments (7)
Does it work without Javascript enabled in the web browser?
Academically it should, in practice most companies will not schedule the time for the work required to make this happen. It's just a cost sink for them.
Having said that, if your app is a mithril or react app written in javascript, what exactly is supposed to happen for someone with javascript disabled?
Just a: "Please enable javascript to use this site" seems good enough for them.
If your "app" is written in Javascript and excludes many potential users without a technical advantage, you could save a lot of maintenance time and cost by just writing it as a native desktop application instead.
But that's a totally different thing.
Yup: It is much more flexible because it has full access to the operating system, you won't have to work around the limitations of a web browser, it will require no fast internet connection (but it could perfectly work with one) while hogging less RAM and blind/disabled people are able to use it.
What else?
Should it? Under which circumstances someone might disable Javascript?
Blind users with screenreaders (not sure if they are sophisticated enough already) as well as security-conscious people will have major problems using a website that requires Javascript. So yes, it absolutely must.
HTML forms are enough for most things. Please use the
<noscript>tag for more than just complaining to the user.