Correct spelling and finish conclusion

chapters/0-introduction.tex

@@ -6,18 +6,18 @@ \chapter{Introduction}
 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
+leaving enough room to accommodate 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
+labeling 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,
+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.
@@ -27,20 +27,20 @@ \chapter{Introduction}
 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
+This project aims 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
+complete 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
+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
+discuss the creation of a tool for assessing accessibility 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.
+and shortcomings as well as personal reflections on the journey. Finally, a
+concluding paragraph, references, and appendices will end the report.
 
 % The Introduction should clearly lay out the principal motivation for the
 % project

chapters/1-background.tex

@@ -8,7 +8,7 @@
 \chapter{Background}
 \section{What is accessibility?}
 "Accessibility" is a subjective term which offers many opinionated
-definitions. The \cite*{OxDict} defines accessiblity as:
+definitions. The \cite*{OxDict} defines accessibility as:
 \begin{quote}
 "The quality of being able to be reached or entered"
 \end{quote}
@@ -31,10 +31,10 @@ \section{What is accessibility?}
 used by individuals with disabilities"
 \end{quote}
 
-Finally \cite*{JimByrne} founder of Guild of Web Designers offers an interesting
+Finally, \cite*{JimByrne} founder of Guild of Web Designers offers an interesting
 insight. He refers to Google as a blind visitor which is technically correct
 as google will never be able to see all the `pretty' pictures on your website.
-It can however understand text and markup. This hints at the fact that
+It can however, understand text and markup. This hints at the fact that
 improving the markup will improve the experience for not just users of
 assistive tools, but machines too.
 
@@ -43,14 +43,13 @@ \section{What is accessibility?}
 \end{quote}
 
 To me, accessibility is a way of thinking. It requires a range of disciplines
-and should start with what the users goal is. If any type of user is unable to
-acheive the goal they came to acheive then the web page is inaccessible. It
-is unfortunately entirely possible to have the most semantic well
-structured web page yet it is still totally inaccessible.
+and should start with what the users' goal is. If any type of user is unable to
+achieve the goal they came to achieve then the web page is inaccessible. It
+is unfortunately entirely possible to have the most semantic well-structured web page yet it still be totally inaccessible.
 
 \section{Business Context \& Requirement}
 Capgemini undertakes a range of projects across both public and private
-sector. In the current digital climate most projects involve the
+sector. In the current digital climate, most projects involve the
 development of some form of web frontend. As a Professional Services supplier it
 is quite common for Software Engineers to be multi-skilled and thus web
 development may not be a ``core skill". A common problem is that developers
@@ -61,7 +60,7 @@ \section{Business Context \& Requirement}
 These mistakes are only identified later in the project when
 'assistive tool' testing is performed at which point repetitive and sometimes
 significant rework may be necessary. The agile 'Cost of Change' \citep{CostOfChange} curve
-shown in Fig.~\ref{fig:costOfChange} demonstrates this.
+shown in Fig.~\ref{fig:costOfChange} demonstrates the cost of a change as the time moves on in a project.
 
 \begin{figure}[H]
 \centering
@@ -71,14 +70,14 @@ \section{Business Context \& Requirement}
 \label{fig:costOfChange}}
 \end{figure}
 
-With this in mind this project aims to enable developers with limited
+With this in mind, this project aims to enable developers with limited
 experience in web development to write cleaner, more semantic code. It is
-through educating developers that the primary goal of offering a better
+through educating developers that offering a better
 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
+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.
@@ -113,7 +112,7 @@ \section{Business Context \& Requirement}
 importance to those that use rely on it would be a great benefit to Capgemini’s
 developers and the developer community as a whole. If these guidelines could
 be distilled into the kind of language that has become commonplace for
-explaining other areas of front end development, it would help to dispel
+explaining other areas of front-end development, it would help to dispel
 myths of complexity and allow projects to implement WCAG in a meaningful way.
 This would save on project costs by removing pitfalls of “adding it later”; but
 importantly, it would help to keep the web a diverse and inclusive place."}
@@ -126,7 +125,7 @@ \section{Project Goals}
 the project deliverables will be relevant, useful and fill the described
 business need. The deliverables are:
 \begin{enumerate}
-  \item A tool for software engineers which will bootstrap itself into a web
+  \item A tool for software engineers which will bootstrap itself into the web
 browser, assess and report possible accessibility issues
   \item A suite of documentation which will collate and demonstrate best
 practices. It will show what 'assistive tools' output based upon different
@@ -141,7 +140,7 @@ \section{Project Stakeholders}
   \item My two supervisors — Academic and Company, these are the people whom
   the deliverables will be presented too.
   \item Software Engineers at Capgemini — To improve the experience for the
-  users web developers \& designers are those who need to produce a better
+  user's web developers \& designers are those who need to produce a better
   product.
   \item Software Engineers within the wider community - Similar to above
   \item Users of assistive technologies. This whole project would be
@@ -165,7 +164,7 @@ \section{Methodology}
    the project. 'Medium' \citep{Medium} a blogging platform will instead be
    used to
    capture key events and entries. At the end of the project this will be
-   supplemented with notes from meetings between myself and my acadamic
+   supplemented with notes from meetings between myself and my academic
    supervisor.
    %TODO - Check with HARRY if the below statement is correct. This is
    %TODO   currently an assumption and may be totally incorrect.
@@ -177,7 +176,7 @@ \section{Methodology}
   feedback' from stakeholders and produce a higher quality product
   \item Open Source Everything - Capgemini consumes and
   produces a lot of open source software! With myself sitting within a team
-  that are leading this drive, all code produced will be available under a MIT
+  that are leading this drive, all code produced will be available under an MIT
   Licence \citep{MITLicence} on Github.
   \item Share Everything - The JVM team has its own 'ethos'
   \citep{JVMHowWeWork} that sits on top
@@ -190,15 +189,14 @@ \section{Methodology}
    things
    tackled on
    each deliverable. This will allow its process to be tested and validated
-   for every change made thereafter; reducing risk of failure later in the
+   for every change made thereafter; reducing the risk of failure later in the
    project. Travis CI \citep{TravisCi} and Github Pages \citep{Ghpages} will
    enable
    this.
  \end{itemize}
 
 \subsection{Making Better Decisions}
 \label{sec:manifesto}
-% TODO * reference Agile Manifesto
 Coming from a background in Agile projects, the ``Agile Manifesto" \citep{AgileManifesto} has
 enabled
 me to make and justify difficult decisions under pressure. For example deciding
@@ -226,30 +224,30 @@ \subsection{A Process}
 
 This project is no exception and will follow the Unified Process. This gives
 a structure to different phases throughout the lifecycle of
-the project Inception, Elaboration, Construction and Transition. It enables
+the project Inception, Elaboration, Construction, and Transition. It enables
 iterations to occur within each of these phases but focuses the iteration
 towards the goal of the phase you are currently in.
 
 \subsubsection{Why the Unified Process?}
 
 Agile is a poor fit for me as a distant learner with a
-full time job. Each iteration requires a small amount of every aspect of the
+full-time job. Each iteration requires a small amount of every aspect of the
 development lifecycle (analysis, design, implementation and test). This would
 make it difficult to understand and report progress to myself and the
-stakeholders. Given the projects deliverables are well known from
-the outset Agile would only add unneccesary ceremonies.
+stakeholders. Given the deliverables are well known from
+the outset Agile would only add unnecessary ceremonies.
 
 Using the manifesto above, the sprial model would satisfy ``Start simple with
 many organic iterations", due to each turn of the spiral gaining user feedback
 and then using that feedback to direct new requirements. It's flexible enough
  and well structured for this project. What steered the project towards Unified
  Process over Spiral was the amount of risk
 collection and analysis required. Due to being an individual project, most
-risks fall into the low probability, low impact category, and with one quater of
-each spiral dedicated to risk analysis .
+risks fall into the low probability, low impact category, and with one quarter of
+each spiral dedicated to risk analysis.
 
-\subsection{High Level Planning}
-At a high level I was aiming for the following to be acheived:
+\subsection{High-Level Planning}
+At a high level I was aiming for the following to be achieved:
 \begin{enumerate}
   \item {Inception - February}
     \begin{itemize}
@@ -286,7 +284,7 @@ \subsection{High Level Planning}
 \end {enumerate}
 
 \section{A Major Issue}
-Due to unforseen circumstances \textasciitilde6 weeks of time was lost;
+Due to unforeseen circumstances \textasciitilde6 weeks of time was lost;
 Mid-March through to the start of May. This covered the Elaboration, and
 Construction phase of the project. So it was clear a change in process would be
 necessary.
@@ -295,7 +293,7 @@ \subsection{Change of process}
 I chose to change from the 'Unified Process' towards a more
 prototypical/iterative process; 'Evolutionary Prototyping'. This is a form of
 the prototyping model which often suits tight time scales and fast development
-lifecycles \citep{EvoProto}. The 'Evoloutionary' aspect means rather than the
+lifecycles \citep{EvoProto}. The 'Evolutionary' aspect means rather than the
 prototype being thrown away and rebuilt at the end, it will instead be
 iteratively enhanced until a final product is produced. Fig.~\ref{fig:proto}
 from \citep{EvoProto2} displays the process.