Update A11Y Tool section

Author: geemanjs

Dissertate.cls

@@ -29,6 +29,7 @@
 }
 \DeclareOption{ddouble}{\togglefalse{DissertateSingleSpace}}
 
+
 \ProcessOptions\relax
 
 % Line Spacing
@@ -82,6 +83,7 @@
 \RequirePackage{color}
 \RequirePackage{xcolor}
 \usepackage{hyperref}
+\usepackage{makecell}
 \RequirePackage{url}
 \RequirePackage{amssymb}
 \RequirePackage{mathspec}

chapters/0-introduction.tex

@@ -1,8 +1,49 @@
 %!TEX root = ../dissertation.tex
 \chapter{Introduction}
 \label{introduction}
+20\% of the UK population reported they have a disability
+\citep{UkGovFamilySurvey}.
+That is approximately 13.3 million people. In the physical world,
+companies are by law
+bound \citep{DDA} to ensure that this minority are able to access their services; be it by
+leaving enough room to accomodate wheel chairs; or offering large text prints
+of their products. In the digital world there are no such laws and thus the web can be a
+difficult place for these users to consume services and content.
 
-The Introduction should clearly lay out the principal motivation for the project
-and briefly outline how the work fits into the broad area of surrounding
-Computer Science. The Introduction should outline the remaining structure of
-the report.
+A range of assistive
+tools aim to improve the experience by targeting a selection of
+disabilities and offering other means to consume the content. For example,
+JAWS \citep{JAWS} targets visually impaired users; reading the content,
+labelling actions and offering keyboard shortcuts to navigate. The
+problem
+with all these tools is that they rely upon Software Engineers to produce
+content semantically (using HTML, CSS and Javascript) and add metadata using,
+until recently,
+very loose specifications \citep{WCAG} to enable the tools to better process
+the content.
+
+Although difficult to assess some companies believe \textasciitilde70\% of all
+websites are inaccessible to all users \citep{Slate} \citep{SightAndSound}.
+This identifies a clear gap in knowledge within the design/development community
+when it comes to producing accessible web applications.
+
+This project aims to to reduce the size of the gap by enabling the development
+community through education and `easy to use' tools to think about and
+implement accessibility whilst coding.
+
+This report begins with a background chapter to discuss the topic, the business
+requirement, this projects goals and the methodology that will be used to
+compelete it. Chapter 2 will discuss the first deliverable an
+accessibility guide. It will document the preparation that was undertaken and
+then then how the deliverable was designed and implemented. Chapter 3 will be
+of similar structure, using the knowledge learned building the guide it will
+discuss the creation of a tool for assessing accessibilty issues. A
+critical evaluation of the project will follow discussing the successes
+and shortcomings as well as personal reflections on the journey. Followed by
+of course a concluding paragraph, references and appendecies.
+
+% The Introduction should clearly lay out the principal motivation for the
+% project
+% and briefly outline how the work fits into the broad area of surrounding
+% Computer Science. The Introduction should outline the remaining structure of
+% the report.

chapters/1-background.tex

@@ -6,34 +6,6 @@
 \end{savequote}
 
 \chapter{Background}
-\newthought{20\% of the UK population reported they have a disability
-\citep{UkGovFamilySurvey}.}
-That is approximately 13.3 million people. In the physical world,
-companies are by law
-bound \citep{DDA} to ensure that this minority are able to access their services; be it by
-leaving enough room to accomodate wheel chairs; or offering large text prints
-of their products. In the digital world there are no such laws and thus the web can be a
-difficult place for these users to consume services and content.
-
-A range of assistive
-tools aim to improve the experience by targeting a selection of
-disabilities and offering other means to consume the content. For example,
-JAWS \citep{JAWS} targets visually impaired users; reading the content,
-labelling actions and offering keyboard shortcuts to navigate. The
-problem
-with all these tools is that they rely upon Software Engineers to produce
-content semantically (using HTML) and add metadata using, until recently,
-very loose specifications \citep{WCAG} to enable the tools to better process
-the content.
-
-Although difficult to assess some companies \citep{Slate}
-\citep{SightAndSound} believe \textasciitilde70\% of all websites are
-inaccessible to all users. This identifies a clear gap in knowledge within
-the development community when it comes to producing accessible web
-applications. Thus, the purpose of this project is to enable the development
-community through education and `easy to use' tools to think about and
-implement accessibility during development.
-
 \section{What is accessibility?}
 "Accessibility" is a subjective term which offers many opinionated
 definitions. The \cite*{OxDict} defines accessiblity as:
@@ -105,15 +77,16 @@ \section{Business Context \& Requirement}
 experience to users of assistive tools can be achieved.
 
 
- By building a tool that can be used during
- the development process the feedback loop on issues will be much
- shorter and as described in agile 'cost of change' the cost of remediation
- much lower. The tool will be supported by an accessibility guide which can
- be used either to teach or to reference when trying to understand.
+By building a tool that can be used during
+the development process the feedback loop on issues will be much
+shorter and as described in agile 'cost of change' the cost of remediation
+much lower. The tool will be supported by an accessibility guide which can
+be used either to teach or to reference when trying to understand.
 
 John Clifford a Senior Software Engineer at Capgemini has written a short
 paragraph about Capgemini's need for a project in this area:
 \begin{center}
+\label{quote:john}
 \textit{
 ``Front end development is known by many, but mastered by few. Software
 engineers tend to have a good grasp of the basics, producing screens to meet

chapters/2-a11y-guide.tex

@@ -14,8 +14,6 @@ \chapter{A11Y Guide}
 
 \section{Preparation}
 \subsection{Planning}
-% TODO - Reference curve: http://www.wranx.com/ebbinghaus-and-the-forgetting-curve/
-
 As researched by \citep{Ebbinghaus} in 1885 the forgetting curve demonstrates the
 amount of knowledge remembered after a period of time. See Fig.~\ref{fig:ebbinghaus}
 Repeating or revising the learning unsuprisingly results in the knowledge
@@ -317,8 +315,6 @@ \subsubsection{Defining Requirements}
 \end{center}
 
 \section{Deliverable}
-% TODO -
-% Reference Github - https://github.com/open-source
 \subsection{Iteration 1 - Create content using markdown}
 The first iteration of developing content was targetted the broader aspects
 which affect every part of the users experience. This covered page structure,