Accessability

The web is a vital information tool that should be available to everyone. Web pages should be accessible to users with disabilities. Features currently implemented:

• Pictures have Alt text so their content is described
• Videos use annotations to explain the content
• Images are not the primary or unique source of text content
• All pages are titled

Future updates

• Extended descriptions of illustrations where appropriate
• CC (closed caption) scripts for the videos (W3C 2012b)
• Utilise http://wave.webaim.org/, a Web Accessibility Evaluation Tool
• Check contents to ensure a contrast ratio of 4.5:1 (W3C 2012b)
• Check that all text can be resized by 200%
• Investigate the functionality of the site when using a keyboard only interface
• Providing glossary links for technical (music theory) words
• Check that the language is at a lower secondary level(W3C 2012b)
• Identify the language of the document

Site Security

There is little site security on the current site, as it is largely informational. Upgrades will allow users to post comments, discuss issues, join a premium version of the site, and purchase products. Each of these features will require security upgrades.

Server security is in the hands of the host. As the site is remotely authored, an off-site back-up is maintained so the site can be re-launched quickly.

When comments are allowed on pages, users will be required to create a free user account. Should issues arise of abusive posts, the administrator will investigate stronger levels of authentication and use of IP tracing.

Once user information is being collected, for example user profiles, the administrator will ensure personal data is secure, encrypted and backed up securely. A site security policy will be developed and posted.

When premium access is created and products are sold, security will be taken to the next level to cover increased issues when handling credit card details. This will require use of SSL, and a reliable third party with demonstrable security capability to provide the banking facilities.

The administrator will need to have high levels of personal/physical security invoked. Security audits will be required to ensure the latest threats are evaluated and up-to-date tools used. The administrator, when all protocols are in place, will seek accreditation for the site from a trusted agency (BBB 2013).

References

Australian Federal Government (n.d.) Accessibility. Retreived from http://australia.gov.au/about/accessibility Retrieved 2/6/2013

BBB (2013) BBB Accredited Business Seal for the Web. Retrieved from http://www.bbb.org/us/bbb-online-business/ Retrieved 2/6/2013

Felke-Morris, T. (2011). Web Development and Design Foundations with XHTML. Boston: Addison-Wesley

Huckaby, J. (2012) 79 Web Server Security Tips. Retrieved from http://www.rackaid.com/resources/server-security-tips/ Retrieved 2/6/2013

Lehtinen, R., Russell, D., & Gangemi, G. T. (2006). Computer security basics (2nd ed.). Sebastopol, CA: O'Reilly & Associates

P3P (n.d.) The P3P Implementation Guide. Retrieved from http://p3ptoolbox.org/guide/ Retrieved 2/6/2013

Slatin, J., Rush, S. (2003). Maximum Accessibility, Boston: Addison-Wesley.

W3C (2012a) Web Accessibility Initiative (WAI). Retrieved from http://www.w3.org/WAI/ Retrieved 2/6/2013

W3C (2012b) How to Meet WCAG 2.0. Retrieved from http://www.w3.org/WAI/WCAG20/quickref/ Retrieved 2/6/2013