QA Guideline For A Better Web Developer - Admin Section, Part - 2

From the previous post we discussed about quality measures to be taken on developing front end design. Now its time for admin side development, which is used to manage overall site functionalities and say cms sections. So this area plays a vital role. Here we are going to have a discussion about security & quality measures for administrator site development. So lets get started,

1. Password field should be masked /encrypted.
2. Admin Email address, Once the site is live please ensure the email address is of the client, if not available put the email address of the AM.
3. Should be done with sessions.
4. Last entered record should be default first position in user side unless otherwise specified in the POD
5. Navigation naming standards - Manage /module Name.
6. It would be user friendly if the navigation is categorized if too long.
7. Look and feel should be consistent.
8. Use text editor for long description.
9. Radio Button -Default should always be selected.
10. No Manage item should accept duplicate both in insert and update.
11. Drop-down data entry field (control)  - The options should sort appropriately and the field is wide enough to display all of the options.
12. Ensure that valid labels are present for each field.
13. All the field names should display outside the controls (text box, text area) on contact forms.  Only if there is a space constraint, the label text should come inside text boxes/text areas.
14. Full colon should not be used after the field names.  In case full colon is used for labels, there should not be a space before the colon, but there must be a space after the colon.
15. Also COLON should be aligned correctly.
16. Thank You page should always redirect to the form submitted page.  If it is a complete static site without ‘PHP’ support, there should be a back button using JavaScript. 
17. Password field should accept only if a minimum of 6 characters.
18. Validate the input with Data Type and Maximum Length.
19. Ensure all operations in a form such as Add, Edit, Delete, Update are performed well.
20. Ensure that the field accepts only numerical values and greater than zero where an input is designed for numerical values greater than zero. 
21.  Add the following meta tag to all landing pages that are created <meta name="robots" content="noindex, nofollow">.
22. Canonical Redirection, Index.php to domain.com/adminonline redirection.

QA Guideline For A Better Web Developer

Have anyone ever thought of building a high quality website? Its SEO? Etc. In today's competitive market one thing we cannot compromise is "quality". For any business, success depends upon the quality of product like "One who sells the better the best". This is same in the case of websites also.

There are several things to be considered in developing a high quality website. In this article we will be discussing about those points. Also this guide lines can be handy for quality analysts as well as for SEO professionals. Following this article you can build highly ranked website by search engines. Almost every web applications will have user and admin section. Quality measures for user and admin are as follows:
Wish you the best to make out of this article.

User Section (Front end)

Front end is the most attractive part of the site, part which is handed to end user. This part is to be more simple that visitors can easily navigate to inner contents. My suggestions include SEO tips also. So how to build a better front end? So, lets get started, 

1. Title – There should be meaningful title for all the pages.
2. Always use the Organization standard for Abbreviation, Eg: USA St. for Street, Rd. for Road etc.
   

   Wrong Formats
   U.S.A	U. S. A	U. S.  A.	U.S.A.	U .S .A

3. Spacing after each punctuation “  .    ,   ;  !  :  ”.  No space before punctuation!
4. Don’t put full stop after “?.” Or “!.”– “?” without full stop is correct.
   

   Sl. No.	punctuation	Correct	Wrong
   1	.	Only one. And	Only one . and
   2	,	Indent, Left	Indent , Left
   3	;	Following;	Following ;
   4	:	Indent: Left	Indent : Left
   5	!	Wow!	Wow !
   6	Do not use ‘.’ after ‘?’	Why?	Why?.
   7	Do not use ‘.’ after ‘!’	Wow!	Wow!.

5. Don’t put full stop after phrases.
6. Do not use space before or after “ – ”, when it is used for connecting two words.
7. Font Format should be readable.
8. Do not use underscore for connecting words in file names. Use hyphen (-). Eg: “about-us.php”.
9. Most of the content should be in text, Minimize image captions for articles – use H1, H2 Tags.
10. There shouldn’t be any underlining for the white space before or after the selected area. This is not correct       format.
11. All the labels having multiple words should be in Title Case. Eg: “Confirm Password” – “Confirm password” is not correct.
12. Links
    a) Check whether the links pointing are relevant.
    b) There shouldn't be any broken link.
    c) Run Xenu and find the broken links and fix it.
13. Out Going Links.
    a) Ensure all the external links from our website should have “no-follow”.
    b) Check all the external linked websites are working fine and opens in new window.
14. Logo should direct to the domain. Example: http://www.website.com
15. Canonical Redirection.
    a) Non www to www redirection.
    b) Index.php to domain.com redirection.
16. Custom 404 page.
    a) This page should have link to HTML sitemap.
    b) If the error URL ends with /, it should not go to default 404 page.
17. Image Alt Tags.
    a) Alt tags should be descriptive, not just keywords.
    b) All images should have alt tags except bullet, icon images.
    Designers will provide the tag and SEO people will fill in the tags.
18. Title Attributed for text links.
    a) Be sure to use the primary keyword as title attribute for the corresponding HTML text links.
19. H1, H2 Tags.
    a) Follow hierarchy while giving H1 tags.
20. Blog  Set Up.
    a) Check all the aspects of blog working like tags, recent posts etc.
21. Blog Links - Ensure the post title should be post URL.
    a) All blogs need to have a HOME tab that links to the domain and a ‘BLOG tab’ that directs the user to the blog home.
    b) The logo in a blog needs to be directed to the domain and not the ‘blog home’.
22. Ensure that there is no broken design.
23. Check for the Alignment of contents.
24. Footer Copyright Message - Ensure the following standard message.
    a) “Copyright © 2014, Coder's Bay | Business Hotel Somerset UK”(If there is specified any place name )
    b) Copyright © 2014  Glen Pinheiro. All Rights Reserved. 
25. Contact Form - Ensure site wide form presence and functionality.
26. Form Field Validations.
    a) Mandatory for Name, Phone, Email and Comments Field. No need of space before asterisk while applying mandatory sign.
    b) Only Null field validations are required for phone number unless specified by the client otherwise.
    c) Email address with more than one period should be accepted eg:test.t.e@gmail.com.
    d) The form should not be submitted when the enter key is pressed while the cursor is in the comments text area.
27. Should be able to navigate through controls using keyboard keys.
28. Spelling - Should be checked for correctness.
29. Menu structure should be consistent.
30. Browser Compatibility - Should check in IE 6, IE 7, IE 8, Fire Fox.
                                            - Optionally - Safari, Opera and Chrome on Client’s Request.
                                            - Should check in different platform (Windows, Linux).
31. Validate HTML and XHTML using W3Cs “MarkUp Validator”.  Use the following URL http://validator.w3.org/.
32. Check anchors (hyperlinks) in a HTML/XHTML document using “The Link Checker” - Useful to find broken links, etc. Download Xenu’s Link Sleuth.
33. Validate CSS style sheets or documents using “CSS Validator”.  URL for CSS validator: http://jigsaw.w3.org/css-validator/.
34. Always use External CSS and JavaScript for performance, readability, maintainability and re-usability.
35. Use tables, only for Forms and use stylesheets for other types of positioning. Tables should be used only when it is absolutely necessary and when DIV cannot be used.
36. Ensure the presence of DOCTYPE definition in all the HTML files.
    Eg: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
37. Provide Internationalization by means of using.
    a) Unicode character set (UTF-8, UTF-16 etc.)
    b) W3C date format – “yyyy-mm-dd”
38. (1984-05-04 can only mean May 4th, 1984).
39. Always Use a Background Color - Visitors are able to change their default color preferences. If you don't specify a background color, your text might be invisible.
40. Text equivalent for all non-text elements.  Example, alt text for images. 
41. Associate labels with their controls (forms).
42. All the field names should display outside the controls (text box, text area) on contact forms.  Only if there is a space constraint, the label text should come inside text boxes/text areas.
43. Thank You page should always tempt the user to navigate through the site by providing links or options that lead to conversion friendly pages within the site.
44. Quality of information and images should not be affected even if JavaScript is turned off.  If it happens, it affects usability of the website.
45. Do not “cut & paste” from Microsoft Word into a web document as word adds lot of unwanted styles, classes etc. along with the text copied from it.
46. Use meaningful text for hyper links, rather than “click here”. 
47. Provide alternative content for video and audio contents, whenever possible.
48. Color pattern should be matching. Don’t insert much graphics. Graphics size should not affect the performance.
49. Check if the phone number (in text) is added on top of each page?
50. Check if the GA code is properly added in all pages. Ensure that the GA code is not commented for any reason. 
51. Please block Admin online folder in robot.txt.
52. Check if the conversion code is added to Thanks pages?

Hope you have found this article useful, thank you. 

In the next article we will be discussing about the security & quality measures to be taken for the administrator section.