Assignment 02, Website Development, CCV Spring 2017


Question 1:
I use google search for all my research needs.

Question 2:

Question 3:
Term 1: custom 404 page
When browsing on websites, it is possible that a viewer will try to go to a webpage that isn't in the right location, or hasn't been created.
If this happens, the viewer will be sent to a page that tells them the webpage they were looking for does not exist.
It's a very dry boring page, and it's possible to customize it, so that a viewer sees a custom error message instead.
First, you need to create a file named .htaccess, and inside it put the line "ErrorDocument 404 /notfound.html".
Next, create a webpage named notfound.html and customize it to your liking.
Upload the notfound.html webpage to your main directory.
Upload the .htaccess file to your main directory.

Term 2: meta refresh redirect
A meta redirect is added to the head tag in a webpage to redirect the page viewer to another webpage.
It is often used to redirect a viewer to a page that has been moved, however, my use for it is to add a redirect to my custom 404: Page Not Found page.
When someone navigates to a page that doesn't exists on my website, they land on a customized error page and are then redirected to the front page of my website.

Term 3: <main> tag
The main tag is a new element for me and I wanted to know the reasoning behind using one. It doesn't really seem necessary.
It seemed to me that it would be something you would use mostly if you got lost inside your own code in a particularly busy page, as a placemarker. explained the system and now I understand it advances assessibility for assistive technology software.
I did some digging, and it appears that while the specifications clearly say that it is not a styling element, it is being used as one by some web designers, for example, this guy:
LINK who is clearly upset that his page is not displaying properly because of a specific browser not understanding the implied style in this element's specification.
In conclusion, the main tag does indeed impart a style element to a page:
main { unicode-bidi: isolate; display: block; }
This is automatically rendered in all modern browsers, and only absent in older versions of IE, which incorrectly renders it as an inline block element.
Still, I bristle that webdesigners are using it as a styling element, when the specifications clearly state it is not intended for that purpose. has a list of ways to implement, and not to implement the ARIA tags,
and since the example they give goes in direct opposition to the instruction example in the textbook, I think I will just NOT USE IT AT ALL. goes on to say this:
5.3.4. Landmark Roles

The following roles are regions of the page intended as navigational landmarks. All of these roles inherit from the landmark base type and, with the exception of application, all are imported from the Role Attribute [ROLE]. 
The roles are included here in order to make them clearly part of the WAI-ARIA Role taxonomy.

If and when I create a website that is complex enough to require navigational landmarks, I will consider delving into the complexities of ARIA, until then, I'll pass on implementing it on my websites.