• Use standard document classes and common packages whenever possible.
• Keep layout packages simple; visual formatting should not carry meaning.
• Use hyperref for real links, but make the visible link text descriptive.
• Avoid custom macros until the conversion workflow has been tested.

Copyable Code Snippet:

\documentclass[12pt]{article} 
 
\usepackage[utf8]{inputenc} 
\usepackage[T1]{fontenc} 
\usepackage{lmodern} 
\usepackage{amsmath, amssymb, amsfonts} 
\usepackage{graphicx} 
\usepackage{booktabs} 
\usepackage{array} 
\usepackage{hyperref} 
\usepackage{geometry} 
\geometry{margin=1in}

• Use equation environments for displayed equations.
• Use semantic math commands such as \lim, \frac, \sqrt, \int, and \sum.
• Do not replace equations with images just because they look correct visually.
• Keep explanatory sentences before or after equations so the reader has context.
• NVDA should read inline math inside the sentence flow.
• Displayed equations should be announced as math, not images.
• Cases and inequalities should be read in a logical order.
• Use ClearSpeak + Medium verbosity for a clearer demo voice when testing Math content.

Copyable Code Snippet:

\section{Calculus Examples} 
 
A derivative can be defined using a limit: 
\begin{equation} 
f'(x) = \lim_{h \to 0} \frac{f(x+h)-f(x)}{h}. 
\end{equation} 
 
An integral with an infinite limit is: 
\begin{equation} 
\int_{0}^{\infty} e^{-x^2}\,dx = \frac{\sqrt{\pi}}{2}. 
\end{equation} 
 
A summation example is: 
\begin{equation} 
\sum_{i=1}^{n} i = \frac{n(n+1)}{2}. 
\end{equation} 

• Use \section and \subsection for document organization.
• Do not create headings by manually bolding or enlarging plain text.
• Write section titles that describe the topic, such as “Vectors and Matrices.”
• Place the explanation before complex notation so users know what they are about to hear.

Copyable Code Snippet:

\section{Vectors and Matrices} 
 
A state vector for a three-dimensional system can be written as: 
\begin{equation} 
\mathbf{x} = 
\begin{bmatrix} 
p_x & p_y & p_z & v_x & v_y & v_z 
\end{bmatrix}^{\mathsf{T}}. 
\end{equation} 

• Use environments such as bmatrix for matrix notation.
• Use ampersands for columns and double backslashes for rows.
• Do not draw matrices using spaces or images.
• Define the variables around the equation so the notation has meaning.

Copyable Code Snippet:

A linear state-space model is: 
\begin{equation} 
\dot{\mathbf{x}} = A\mathbf{x} + B\mathbf{u}, 
\end{equation} 
where 
\begin{equation} 
A = 
\begin{bmatrix} 
0 & 1 \\ 
-\frac{k}{m} & -\frac{c}{m} 
\end{bmatrix}, 
\qquad 
B = 
\begin{bmatrix} 
0 \\ 
\frac{1}{m} 
\end{bmatrix}. 
\end{equation} 

• Use the cases environment for piecewise definitions.
• Write each condition explicitly, such as u > u_max.
• Keep inequalities as LaTeX symbols instead of plain visual approximations.
• Explain what the function represents before showing the equation.

Copyable Code Snippet:

\section{Piecewise Functions and Cases} 
 
Piecewise definitions are important in control, optimization, and signal processing. A saturation function can be written as: 
\begin{equation} 
\operatorname{sat}(u) = 
\begin{cases} 
u_{\max}, & u > u_{\max}, \\ 
u, & -u_{\max} \leq u \leq u_{\max}, \\ 
-u_{\max}, & u < -u_{\max}. 
\end{cases} 
\end{equation} 

• Use standard commands for Greek letters and notation.
• After an equation, define symbols such as P, Γ, and θ tilde.
• Do not rely on the reader already knowing every symbol.
• Use plain language to connect the equation to the research meaning.

Copyable Code Snippet:

\section{Greek Symbols and Control Notation} 
 
A Lyapunov candidate function for tracking error \(e\) can be written as: 
\begin{equation} 
V(e,\tilde{\theta}) = \frac{1}{2}e^{\mathsf{T}}Pe + \frac{1}{2}\tilde{\theta}^{\mathsf{T}}\Gamma^{-1}\tilde{\theta}, 
\end{equation} 
where \(P\) is positive definite, \(\Gamma\) is an adaptation gain matrix, and \(\tilde{\theta}\) is a parameter estimation error. 
 
One possible derivative condition is: 
\begin{equation} 
\dot{V} \leq -\lambda_{\min}(Q)\lVert e\rVert^2. 
\end{equation} 

• Use enumerate or itemize for real list structure.
• Keep each step as a separate item so screen readers announce list position.
• Use inline math inside list items when the equation belongs to the sentence.
• Avoid using manual numbering typed into paragraphs.

Copyable Code Snippet:

The following list tests math embedded in list items: 
\begin{enumerate} 
\item Choose a sampling period \(T_s = 0.01\) seconds. 
\item Estimate the state error \(e_k = x_k - \hat{x}_k\). 
\item Apply the control law \(u_k = -Kx_k + r_k\). 
\item Verify that \(\lVert e_k \rVert\) decreases over time. 
\end{enumerate} 

• Use a tabular environment for data with consistent rows and columns.
• Include a caption that explains the table purpose.
• Use a clear header row: Parameter, Symbol, Value, Meaning.
• Avoid merged, nested, or layout-only tables when possible.
• Do not rely on visual spacing to communicate relationships.
• Test table navigation with T and Ctrl + Alt + arrow keys in NVDA.

Copyable Code Snippet:

\section{A Data Table Containing Math} 
 
The next table is a true data table. It uses a header row and avoids using a table only for visual layout. 
 
\begin{table}[h] 
\centering 
\caption{System parameters for a second-order example.} 
\begin{tabular}{llll} 
\toprule 
Parameter & Symbol & Value & Meaning \\ 
\midrule 
Mass & \(m\) & \(1.0\,\mathrm{kg}\) & Object inertia \\ 
Damping coefficient & \(c\) & \(0.4\,\mathrm{N\,s/m}\) & Velocity resistance \\ 
Spring constant & \(k\) & \(2.0\,\mathrm{N/m}\) & Position restoring force \\ 
Natural frequency & \(\omega_n\) & \(\sqrt{k/m}\) & Undamped oscillation rate \\ 
Damping ratio & \(\zeta\) & \(c/(2\sqrt{mk})\) & Normalized damping \\ 
\bottomrule 
\end{tabular} 
\end{table} 

• Use a figure caption for the visible chart.
• Provide a long description that states the trend and main takeaway.
• Add a data table when exact values are important.
• Do not expect alt text alone to explain a complex chart.
• Text equivalents for charts and diagrams – when to use what:
  • Use alt text for the short identification of the image.
  • Use a figure caption for visible and structural context.
  • Use a long description when the image contains important data or relationships.
  • For charts, also provide the key data or a linked data table when needed.

The examples below include a chart and a diagram, which should include a figure caption and a long description as the text equivalents, respectively.

Copyable Code Snippet:

\section{A Chart With a Text Equivalent} 
 
The next figure is a chart. A screen reader cannot infer the trend from the image alone, so the chart is followed by a text description and a small data table. 
 
\begin{figure}[h] 
\centering 
\includegraphics[width=0.82\textwidth]{figures/stability_plot.png} 
\caption{Tracking error decreases over time in a stable system.} 
\end{figure} 
 
\textbf{Long description of the stability chart.} The line chart shows tracking error magnitude from 0 to 10 seconds. The error starts at 1.00, oscillates slightly, and decays toward zero. The main takeaway is that the controller reduces tracking error over time. 

• Use the figure for sighted users and a text equivalent for screen reader users.
• Describe the flow: input, summing junction, controller, plant, output, feedback.
• Keep the long description close to the figure in the source file.
• Avoid relying only on arrows or spatial position to communicate meaning.

Copyable Code Snippet:

\section{A Block Diagram With a Text Equivalent} 
 
The next figure is a block diagram. The visible diagram is useful for sighted users, but the text description is necessary for screen reader users. 
 
\begin{figure}[h] 
\centering 
\includegraphics[width=0.90\textwidth]{figures/control_loop_diagram.png} 
\caption{Closed-loop control diagram with reference input, controller, plant, output, and feedback.} 
\end{figure} 
 
\textbf{Long description of the control-loop diagram.} The reference signal enters a summing junction. The error signal goes into the controller. The controller output goes into the plant. The plant produces the output. The output is measured and sent back through a feedback path to the summing junction, where it is compared with the reference. 

Accept license

Install progress

Finish setup

• Open a new Command Prompt window after installation.
• Run: pandoc --version
• A version number confirms Pandoc is installed and available on the system path.
• If the command is not found, reopen Command Prompt or restart the computer.

• -s creates a full standalone HTML document.
• --toc creates a linked document index/table of contents.
• --mathml converts LaTeX equations into MathML.
• --embed-resources embeds images into the HTML file.
• -o names the output file.

• -s creates a full standalone HTML document.
• --toc creates a linked document index/table of contents.
• --mathml converts LaTeX equations into MathML.
• --embed-resources embeds images into the HTML file for Pandoc versions 2.19+.
• --self-contained embeds images into the HTML file for Pandoc versions older than 2.19.
• -o names the output file.

• Select from: LaTeX and to: HTML5.
• Check Standalone and TOC.
• Choose MathML for math output.
• Paste LaTeX or upload a simple .tex file.
• If figures do not load, the uploaded file names and image paths likely do not match.

Document structure

• NVDA + Down Arrow: continuous reading
• H / Shift + H: next or previous heading
• Tab / Shift + Tab: index links
• NVDA + F7: list headings and links
• G: graphics/images

Math and tables

• T / Shift + T: next or previous table
• Ctrl + Alt + Arrow keys: table cells
• NVDA + Alt + M: math navigation
• Arrow keys: move inside math
• Escape: leave math navigation