Web

Development Standards

Development standards for websites.

Responsive

A responsive website can be rendered, navigated and utilized on many different combinations of devices and browsers.

Browser compatibility – the website should be accessible by different versions of the most common web browsers (e.g. Internet Explorer, Firefox, Safari, Chrome, etc.)

Accessible

An Accessible website can support browsers outfitted with functionality that allows users with disabilities to use your website and allows all users to load, view, understand and use the site with ease.
Web accessibility encompasses all disabilities that affect access to the Web, including:

Web accessibility also benefits people without disabilities, for example:

people using mobile phones, smart watches, smart TVs, and other devices with small screens, different input modes, etc.
older people with changing abilities due to ageing
people with “temporary disabilities” such as a broken arm or lost glasses
people with “situational limitations” such as in bright sunlight or in an environment where they cannot listen to audio
people using a slow Internet connection, or who have limited or expensive bandwidth

Navigation

A navigable website should allow a user to browse to, bookmark and exit from any page or exhibit on the website.

Recoverability

Websites, related databases and media should be backed up regularly.

Relevancy

Content

Standards

Design

The website should utilize a consistent design for navigation/layout.
The website should be user friendly with a clear and simple interface.
The website should make it easy for a user to quickly find the information that they need.
The website should have a high level of visual appeal.
Graphics should be used to complement the website.
The website should not contain inappropriate graphics.
The chapter’s name should be in the title of each page for bookmarking purposes.
The website should not auto-play sound or video.
he use of horizontal scrolling should be minimized.
Overall page lengths should be reasonable. Website pages greater than four “page downs” in length should be avoided. Long pages should have “Return to top” links.
There should be an organized structure for links to other Kappa Alpha Psi websites (chapters, provinces, national).
The website should be laid out in an organized manner with content appropriately divided.
Flash introductions should have the option to be skipped.
Improper use of the Kappa Alpha Psi Coat of Arms or improper display of the Kappa Diamond is prohibited.

Innovation & Technology

The website improves the province/chapter’s operational effectiveness and/or productivity of its members (e.g. use of integrated group collaboration tools – email, calendar, file sharing, etc.)
The website makes effective use of tools and technologies (e.g. content management systems, HTML5, CSS, JavaScript, etc.).
The website leverages social network integration to assist with distribution of chapterrelated public information, increase traffic, and present/promote a positive image of the chapter and fraternity.
The website makes creative use of relevant content syndication via RSS (blogs, audio podcasts, video podcasts, etc.).
Turnkey tools should be used to audit the accessability, best practices, performance, page speed and SEO
The website has high search engine rankings.
The website employs other innovative uses of technology.
The platform, software and host used to serve the site should be able to be updated and improved

Originality

Does the website stand out from other province or alumni/undergraduate chapter websites? If the answer is yes then the site is original.

Legality

Supportable

A supportable website can be maintained and upgraded to protect user data and secure the site from malicious intent.

Chapter & Related Entity Websites

Chapter Certification Procedure

The Chapter must submit its Website Link and the names, emails and phone numbers of the primary and secondary web masters. If there is a third party vendor responsible for the website and its content, the same contact information for the vendor should be submitted as well. If the chapter has a Kappa League with its own website, the same contact information must be submitted for the person and/or company responsible for its contents. Documentation must be included, signed by the Polemarch, Vice Polemarch, KOR, KOE of the Chapter, all Webmasters and where applicable, the Advisor, stating that each member of the Chapter understands that:

Web

Web