Accessibility for Desktop Apps: macOS TextEdit Audit

This is in continuation to my series of accessibility audits for built-in macOS apps. In the last article I audited Calculator app, and in this article, I am auditing TextEdit app.

The built-in TextEdit app on macOS needs no introduction. It acts as a lifesaver for anyone needing to take quick notes, create simple documents, or even edit plain text code. It is an excellent example of ‘minimalism’ when it comes to text handling.

While TextEdit excels in simplicity and convenience for many users, it’s also important to note that it lacks accessibility support, which deprives a significant number of users from using this valuable tool.

When it comes accessibility compliance, it primarily falls short of expectations in these two critical areas:

• Color Contrast &
• Keyboard Operability

Color Contrast

Sufficient color contrast must be provided between text and its background so that text can be seen by people of all abilities. It should be at least 3:1 for larger text (i.e. 18+ points; or 14+ points if bold) and for sizes smaller than that, it should be at least 4.5:1.

Now look at the toolbar, where the status is reflected if the document is edited. The background color is #F1F0EE and the foreground color is #B1B0AE. This makes the contrast ratio as 1.9:1 which is inadequate for both: large and small text.

This makes the app non-compliant as per WCAG Success Criteria 1.4.3, which is of Level-AA category.

Keyboard Operability

While not adhering to color-contrast impacts disabilities segments like color blindness and low vision, the impact of not adhering to keyboard operability is even huge and that’s the reason it is categorized as Level-A as per WCAG. Keyboard accessibility is super-critical for:

• People who are partially or completely blind, as we’ll not be able to use the mouse.
• People with low vision, as they’ll find it difficult to track the pointer
• People with mobility, flexibility and body structure disabilities

Over and above these permanent disabilities – there are situation disabilities like a non-functional mouse; or a temporary disability like recovering from a broken arm. Keyboard accessibility is equally critical for them as well.

Therefore, as a part of this audit I tried accomplishing below tasks using keyboard-only and wasn’t quite successful.

Note: While recording the screen, I have opened Virtual Keyboard so that the viewers can track my keystrokes: like when I am pressing Tab / Shift+Tab, or Up / Down Arrow keys while trying to achieve the desired task.

Task 1 — Close the file without saving

Task 2 — Save the file in a different location

Task 3 — Change the Font style

Task 4 — Change any setting that requires using a Radio-button or a Checkbox; or going to different Tab

This makes the app non-compliant as per WCAG Success Criteria 2.1.1 & 2.1.2. Both of them are of Level-A category.

Conclusion

While TextEdit offers a convenient option for basic text editing on macOS, its lack of accessibility support creates barriers for users with visual impairments and those who rely completely on keyboard navigation. By prioritizing accessibility features like sufficient color-contrast and robust keyboard controls, Apple can ensure TextEdit remains a truly inclusive tool for everyone.