Accessibility Evaluation
Document to analyze: Assignment 2 SUPPLEMENTAL Badly Designed Document
Report
Tester Name: Heather Michel
Name of Doc: Random Job Audit Procedure
Date Examined: August 5, 2022
Summary of Key Findings
The Random Job Audit Procedure document contains several accessibility issues. I recommend editing for problems listed in the Bugs and Usability Problems section of this document.
Bugs and Usability Problems
Document Properties and Table
- Document missing a Title in Document Properties.
- Add a Title in Document Properties.
- Content in table form instead of header/paragraph form.
- Tables are confusing for screen readers. Take the information out of the table and place the information in header & paragraph form. Include the Document Title, Department, Description, Written By, Approved By, and Effective Date at the top of the document.
- Consider moving Document No, Revision, Page No, and Title to the footer area of the document.
- Table lacks alternative text.
- If a table is included in the document, add alternative text to the table.
- A page break splits the table and column headings are not listed on each page.
- If a table is included in the document, column headings should be at the top of each column. Add column headings for each column.
- Table contains blank cells and blank rows. This can cause a confusing reading order for screen readers.
- If a table is included in the document, remove blank cells and blank rows from the table.
Images
- Images are not in line with text.
- Ensure that images are in line with the corresponding text.
- Images lack alternative text.
- Add alternative text to each image.
- Text in image of software too small to read.
- Show a smaller section of the software to ensure readability or eliminate the image.
- if the image does not add significant value consider eliminating the image.
Links & File Names
- File names are not linked.
- Link file names when possible, using descriptive text.
- File names contain a mix of all caps and sentence casing.
- Use sentence casing for links and file names.
- Use the defined “Normal” text style for links and file names.
Text
- Information is not in complete sentences.
- Use complete sentences.
- Write short, simple sentences.
- N/A vs n/a not consistent.
- Select either “N/A” or “n/a” and use consistently throughout the document.
- Document is written using passive voice.
- Use active voice.
- Lists have inconsistent punctuation.
- Correctly punctuate all list items.
- “Normal” text style is too small. Font size is 11-point.
- The “Normal” text size is 12-point minimum.
- Use the defined “Normal” style in your word processing software.
- Text in all capital letters.
- Use sentence casing.
- Text bolded
- Normal text is not bolded.
- Consider using bolded text for specific purposes. For example, a button or icon name.
- Heading styles not used.
- Use the defined “Heading” styles in your word processing software.
- Use headings in alphanumerical order. For example, H1, then H2, then H3.
Lists
- Lists are not indented correctly.
- Correctly indent sub-lists.
- Lists do not follow a logical order (1, 2, 3, a, b, c.)
- Put list and sub-lists in alphanumerical order.
Other Findings
I recommend the use of a style guide. Create and follow the style guide to increase consistency and reduce errors. For example, decide if a clickable or selectable item should be bolded or placed in quotations (“…”).