## 6 Conclusions  
The Saudi government has recently been focusing on the usability and accessibility issues of e-government systems [40, 41]. Systems such as Noor, Faris, and iEN are some of the most rapidly developed and used e-government systems by teachers. Consequently, in this study, we investigated the degree of accessibility VI teachers had in accessing and using these systems based on a mixed-methods approach. The usability testing was done on four participants (three totally blind and one visually impaired teacher). In addition, four automated tools, namely, AChecker, HTML_CodeSniffer, SortSite, and Total Validator, were utilized in this study. Theoretically, our adopted methodology used a mixed-method approach that incorporated several methods, such as automated testing and user testing methods, which was similar to previous research, such as [24, 25, 26], which proved to be an effective methodology for highlighting the major accessibility issues faced by VI users. Practically, the obtained results from usability testing sessions showed that all systems did not support the screen readers effectively as it was the main issue reported by all participants. This issue can happen for many reasons, such as missing some HTML attributes or improper usage of some elements. Regarding automated tools, the evaluation helped us to identify the most important accessibility issues of the three systems. Therefore, we found that the perceivable principle was the most violated principle by all systems, followed by operable, and then robust. The errors corresponding to the perceivable principle alone represented around 73% of the total errors. Moreover, we observed that most of the errors violated even the lowest level of accessibility conformance, which reflected the failure of these systems to pass the accessibility evaluation. \begin{table}
\begin{tabular}{p{42.7 pt} p{113.8 pt} p{113.8 pt}} \hline \hline
**No.** & **Systems** & **Accessibility Issue** & **Correction Way** \\ \hline \multirow{3}{*}{1} & \multirow{3}{*}{All} & More than one h1 element on the page, leading to them being unreachable by the screen readers and keyboard shortcuts. & Leave the title of the main content as h1 and change other h1 elements to a lower heading level. \\ \hline \multirow{3}{*}{2} & \multirow{3}{*}{All} & Labels were missing, causing screen readers to miss content. Markup errors, like missing end tags, meant screen readers sometimes skipped important content. & Add labels to identify the contents, as well as the end tags. \\ \hline \multirow{3}{*}{3} & \multirow{3}{*}{All} & \multirow{3}{*}{Missing the ALT attribute from images.} & Add an ALT attribute describing each image, which screen readers can read aloud. Spacer images and purely decorative images should use ALT = “... \\ \cline{3-5}  & & & In the HTML, add a lang attribute to the HTML tag, and in a PDF, set the language using the document properties in Acrobat. This allows screen readers to pronounce words correctly. \\ \hline \multirow{3}{*}{5} & \multirow{3}{*}{Faris} & Many pages used nested tables, which did not make sense when reading them using a screen reader. & Add role = “presentation” if the inner table is a layout table; otherwise, modify the inner table to present the same data without nesting tables. \\ \hline \multirow{3}{*}{6} & \multirow{3}{*}{Noor} & Onfocus handlers were missing when onmousover handlers were there. & All ommousover handlers should have an equivalent onfocus handler. \\ \hline \multirow{3}{*}{7} & \multirow{3}{*}{iEN} & Some pages had the same title; therefore, the title could not be used to distinguish pages. & Use a unique title for each page. \\ \hline \multirow{3}{*}{8} & \multirow{3}{*}{iEN} & Having one meta description tag on some pages. Only the first description was displayed in search results. & The meta description tag should be one tag. \\ \hline \hline \end{tabular}
\end{table} 
Table 14: Common accessibility issues and suggested corrections.