Comment out instruction in A11Y tool

Author: geemanjs

chapters/3-a11y-tool.tex

@@ -194,44 +194,44 @@ \subsubsection{WCAG Checker Pack}
 import 'checkers/WCAG/TableCaptionChecker.js
 \end{lstlisting}
 
+%TODO - Complete this..
+
 \subsubsection{A11Y Browser}
 The browser component enables the tool to be ran within a web browser (Tested
 on Chrome 57). Fig.~\ref{fig:a11y_tool_browser_design} shows how this fits in
- at a high level.
+at a high level.
 
 \begin{figure}[H]
 \centering
-\includegraphics[width=0.5\textwidth]{figures/a11y_tool_browser_design}
+\includegraphics[width=0.75\textwidth]{figures/a11y_tool_browser_design}
 \captionsetup{justification=centering}
-\caption{Relationships between components and classes
+\caption{How the browser component ties everything together
 \label{fig:a11y_tool_browser_design}}
 \end{figure}
 
 
-\section{Deliverable}
-
-\newthought{Lorem ipsum dolor sit amet},
-
-This chapter should describe what was actually produced: the programs which
-were written, the hardware which was built, the theory which was developed or
-the new scientific knowledge acquired.
-
-For software projects, give a high-level overview of your realisation of the
-design. Describe the general organisation of any body of code, web pages,
-database tables, etc, that you have created. Highlight any particularly
-noteworthy aspects, e.g., specialised algorithms, but avoid excessive low-level
-detail. Diagrams and examples are usually valuable.
-
-For research projects, provide a detailed overview of how the research was
-executed (e.g., participants involved, etc). the research results and their
-analysis. Include a description of any statistical analysis methods used.
-Highlight any particularly noteworthy aspects, e.g., especially interesting
-results. Graphs/charts and examples are usually essential. When reporting
-statistical analysis, do not merely present the statistics without interpreting
-their meaning for the reader – e.g., what are the implications of the findings?
-Where applicable, based on the results and analysis, present a set of
-recommendations, guidelines, or itemised list of contributions to knowledge
-that may be derived from your work.
-
-This section should be answering the question: “What did the project actually
-produce?”
+%\newthought{Lorem ipsum dolor sit amet},
+%
+%This chapter should describe what was actually produced: the programs which
+%were written, the hardware which was built, the theory which was developed or
+%the new scientific knowledge acquired.
+%
+%For software projects, give a high-level overview of your realisation of the
+%design. Describe the general organisation of any body of code, web pages,
+%database tables, etc, that you have created. Highlight any particularly
+%noteworthy aspects, e.g., specialised algorithms, but avoid excessive low-level
+%detail. Diagrams and examples are usually valuable.
+%
+%For research projects, provide a detailed overview of how the research was
+%executed (e.g., participants involved, etc). the research results and their
+%analysis. Include a description of any statistical analysis methods used.
+%Highlight any particularly noteworthy aspects, e.g., especially interesting
+%results. Graphs/charts and examples are usually essential. When reporting
+%statistical analysis, do not merely present the statistics without interpreting
+%their meaning for the reader – e.g., what are the implications of the findings?
+%Where applicable, based on the results and analysis, present a set of
+%recommendations, guidelines, or itemised list of contributions to knowledge
+%that may be derived from your work.
+%
+%This section should be answering the question: “What did the project actually
+%produce?”