Scribd
Upload
2 views1 page

4

The document discusses the importance of understanding the target audience's device usage for website development, emphasizing the need for compatibility with popular browsers and WCAG AA compliance. It suggests gathering data from previous research or competitor analysis to inform decisions on technology and feature sets. The development process should be modular, allowing for effective cross-browser functionality and addressing potential compatibility issues.

Uploaded by

viniciusteleco
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views1 page

4

The document discusses the importance of understanding the target audience's device usage for website development, emphasizing the need for compatibility with popular browsers and WCAG AA compliance. It suggests gathering data from previous research or competitor analysis to inform decisions on technology and feature sets. The development process should be modular, allowing for effective cross-browser functionality and addressing potential compatibility issues.

Uploaded by

viniciusteleco
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

devices, etc. will the target audience for this site be using?

The client might already have


data about this from previous research they've done, e.g. from other websites they own, or
from previous versions of the website you are now working on. If not, you will be able to
get a good idea by looking at other sources, such as usage stats for competitors, or
countries the site will be serving. You can also use a bit of intuition.
So for example, you might be building an e-commerce site that serves customers in North
America. The site should work entirely in the last few versions of the most popular desktop
and mobile browsers — this should include Chrome (and Edge, Opera as they are based on
the same rendering engine as Chrome), Firefox, and Safari. It should also be accessible with
WCAG AA compliance.
Now you know your target testing platforms, you should go back and review the required
feature set and what technologies you are going to use. For example, if the e-commerce
site owner wants a WebGL-powered 3D tour of each product built into the product pages,
they will need to accept that this just won't work all legacy browser version.
You should compile a list of the potential problem areas.

Note: You can find browser support information for technologies by looking up the
different features on MDN — the site you're on! You should also consult
caniuse.com , for some further useful details.

Once you've agreed on these details, you can go ahead and start developing the site.
Development
Now on to the development of the site. You should split the different parts of the
development into modules, for example you might split the different site areas up — home
page, product page, shopping cart, payment workflow, etc. You might then further
subdivide these — implement a common site header and footer, implement product page
detail view, implement persistent shopping cart widget, etc.
There are multiple general strategies to cross-browser development, for example:
Get all the functionality working as closely as possible in all target browsers. This may
involve writing different code paths that reproduce functionality in different ways
aimed at different browsers, or using a Polyfill to mimic any missing support using

You might also like