Introduction
In an age where technology can help to remove barriers and foster inclusivity, it is still quite common for users to encounter accessibility challenges in the digital space. The ChatGPT platform, while revolutionary in its capabilities, is not exempt from such hurdles. In this article we will discuss some known accessibility issues associated with the ChatGPT tool and its associated support site, and provide suggestions for making the platform more accessible for users with disabilities.
Current Issues and Potential Workarounds
In general, both the ChatGPT tool (chatbot) and associated documentation are accessible to most users, however, the platform does present barriers to users who access digital content using a screen reader, those who navigate using only a keyboard or alternative navigation tools, and users with color related vision issues or low vision.
Note: This review lists issues observed as of December 2023. Please comment if you believe specific issues have been addressed and we will update the article as needed.
Both the Chat GPT tool and associated support website were tested against the W3C WCAG 2.0 AA standard in Windows and MacOS using NVDA and Voiceover screen readers and common browsers. The following information details which accessibility barriers were identified, how they may affect users, and some potential workarounds for helping to provide equitable access to the desired functionality.
Login Process
During the login process users are presented with the option to create an account or login using an existing Google, Microsoft, or Apple accounts. There are multiple issues with this process that may present barriers for users.
Issue:
Several elements associated with the login process do not meet minimum contrast requirements which will make the associated text difficult or impossible to read (e.g., elements using light green text on a white background and white text on a light green background).Who this may affect:
Users with low vision or color related vision issues who rely on high contrast between text and the associated background may find the associated text difficult or even impossible to read.Workaround:
Encourage users to log in using an existing Google, Microsoft, or Apple account, or consider providing written instructions detailing the login process and associated controls.Issue:
Focus indication for the login and account creation buttons is not sufficient. Some users may not be able to move past the account creation and login area without assistance.Who this may affect:
Keyboard users who rely on clear and obvious visual indicators to track which element is currently selected when navigating a webpage.Workaround:
Encourage users to log in using an existing Google, Microsoft, or Apple account, or consider providing written instructions detailing the login process and associated controls.Issue:
During the account creation process, password requirements appear after the password creation field. Instructions and requirements for a form field should be presented prior to the user accessing that field. Also, there is no error indication for assistive technology users who enter a password that does not meet minimum requirements. The cursor simply remains in the password field with no feedback for the user. This also occurs if an incorrect password is entered during login.Who this may affect:
Screen reader users may not be able to move past the account creation and/or login area without assistance.Workaround:
Encourage users to log in using an existing Google, Microsoft, or Apple account, or consider providing written instructions detailing the account creation and login process. Include password requirements and an explanation of the application’s behavior when the password either does not meet the minimum requirements or is entered incorrectly.
Chatbot User Interface
Some elements within the ChatGPT chatbot user interface make the tool difficult to use and potentially confusing for assistive technology users. Issues we experienced include portions of the screen that cannot be accessed by keyboard-only users and numerous interactive elements that do not include descriptive names/labels causing them to be unusable by screen reader users.
Issue:
Not all buttons contain descriptive labels or information about their purpose or function (e.g., send message button, clipboard, and up/down vote icons).Who this may affect:
Screen reader users who rely on clearly labelled buttons and interactive elements for navigating and interacting with an application. If a label is not provided or does not describe the purpose of the button or element, that button or element is essentially useless to screen reader users and will block their ability to effectively use the associated application. Example: the “Send Message” button is simply read as “button, group” by screen readers, giving users no indication of its purpose or functionality.Workaround:
Screen reader users may require assistance navigating the user interface to help learn the functionality of interactive elements when initially using the tool. Consider not requiring the use of unlabeled elements such as the voting buttons.Issue:
Elements of the main message and reply functionality are not presented in a logical order, a typical workflow would not have replies appearing above the message input box. This layout requires users to navigate back up the page to interact with chatbot replies/answers. There is no indication to assistive technology users that replies/answers have been generated or that they appear above the message input field.Who this may affect:
Screen reader users require notification when information on a page is changed, when that change is complete, and where the new information is located. Lack of notification about when reply generation is complete and how to access the replies will make the tool difficult to use without assistance.Workaround:
Screen reader users may require assistance navigating the user interface to help learn the main workflow and how to navigate the message and reply when initially using the tool. Consider providing documentation detailing the chatbot message and reply window to help assistive technology users more effectively use the tool.Issue:
Under user account Settings and Custom Instructions some of the associated pop-up windows are not read in a meaning sequence (e.g., the Custom Instructions pop-up opens with focus on the “Ok” button and no indication that there is text/information above that button). These windows also contain unlabeled buttons (e.g., buttons used to close the pop-up windows).Who this may affect:
Screen reader users rely on information being presented in a logical order. When a new window is opened the screen reader software should be told to start reading from the top of the new content, not set to a button or element at the bottom of the window. Also, lack of descriptive labels on buttons used to close the pop-up windows may prevent users from exiting the Settings windows.Workaround:
Screen reader users may require assistance navigating the account related tool windows. Consider providing documentation detailing the Settings and Custom Instructions windows.The Impact on Users
Barriers to access limit a platform’s usability for a wide variety of users. All students deserve equal access to information and opportunities, inaccessible technology widens the digital divide and hinders the ability of users to fully participate in online conversations and access valuable resources.
The Importance of Accessibility
Addressing accessibility concerns is not just a matter of compliance; it is a moral and ethical imperative. Inclusivity should be at the core of technological advancements. As we work to provide the best possible learning experience for our students, we must ensure that no one is excluded or left behind. By acknowledging and actively working to overcome accessibility challenges we can create a more equitable and inclusive online space and experience for all users.
