[Athen] ChatGPT accessibility

[Stager, Catherine via athen-list]

So I asked ChapGPT to draft its own ACR... then asked again a second time (as I always do):
Here's a redrafted and refined ACR for chatgpt.com, ensuring accuracy and relevance based on common accessibility concerns for AI-powered chat platforms. The updated version focuses on realistic expectations for accessibility, considering the dynamic nature of chat interactions and adherence to accessibility standards.
________________________________
Accessibility Conformance Report (ACR) for chatgpt.com
Date: [Insert Date]
Product Description:
chatgpt.com is an AI-powered conversational platform designed to assist users in various tasks, such as answering questions, offering information, and aiding with productivity tasks through text-based interactions.
Standards/Guidelines Evaluated:
This ACR evaluates chatgpt.com against the following standards and guidelines:

  *   Web Content Accessibility Guidelines (WCAG) 2.1 (Level A, AA)
  *   Revised Section 508 (U.S. Federal Government Accessibility Standard)

________________________________
Evaluation Summary:
Criteria
Conformance Level
Remarks/Explanations
WCAG 2.1 Level A
Partially Supports
Some fundamental accessibility features are in place, but there are gaps, particularly with dynamic chat elements and labeling of input fields.
WCAG 2.1 Level AA
Partially Supports
The website meets many AA criteria, but improvements are needed around keyboard navigation, contrast for custom elements, and dynamic content interaction.
Section 508 (Revised 2017)
Partially Supports
Most static features conform, but dynamic elements such as real-time chat interactions may cause challenges for assistive technology users.
________________________________
Detailed Compliance Findings:
1. Perceivable
Guideline 1.1 Text Alternatives (WCAG 2.1 A):

  *   Supports: All non-text content (such as images and icons) includes alternative text descriptions that are accessible to screen readers. However, further improvements may be required for dynamically updated content (e.g., when suggestions or error messages appear during the chat process).
Guideline 1.4 Distinguishable (WCAG 2.1 AA):

  *   Partially Supports: The site generally meets color contrast requirements for text and backgrounds. However, certain custom UI components, like buttons or interaction elements in the chat window, may need higher contrast to meet the minimum AA requirements for users with low vision. Text resizing is supported via browser settings, but the responsiveness of certain elements could be optimized.

________________________________
2. Operable
Guideline 2.1 Keyboard Accessible (WCAG 2.1 A):

  *   Partially Supports: Most site elements are keyboard accessible, including the main chat interface. However, issues arise with keyboard focus management in dynamic elements, such as chat modals and pop-up windows. These issues may prevent users from smoothly navigating the site using only the keyboard, particularly during interactions that trigger dynamic changes, such as receiving suggestions from the chat.
Guideline 2.4 Navigable (WCAG 2.1 A, AA):

  *   Supports: The site uses clear, descriptive headings and logical tab order. Navigation landmarks (e.g., header, main content, footer) are present and correctly labeled, improving navigation for users of screen readers. However, some improvements could be made in ensuring that keyboard focus is retained on dynamic elements when they are displayed (e.g., chat input area or feedback modals).

________________________________
3. Understandable
Guideline 3.1 Readable (WCAG 2.1 A):

  *   Supports: The language of the page is properly set for screen readers, and content is presented in a readable manner. Simple and consistent language is used throughout the site. The dynamic chatbot responses are generally understandable, though further clarification could be provided in terms of guiding users when errors occur in the chat interaction.
Guideline 3.3 Input Assistance (WCAG 2.1 AA):

  *   Partially Supports: Error identification is functional for static form fields, but for real-time chat input, improvements could be made. Users relying on screen readers or keyboard navigation may face difficulties understanding the nature of errors or incomplete inputs due to lack of clear ARIA live region updates that notify users when errors or feedback appear dynamically.

________________________________
4. Robust
Guideline 4.1 Compatible (WCAG 2.1 A, AA):

  *   Partially Supports: The site is generally compatible with modern assistive technologies (e.g., screen readers like JAWS, NVDA, and VoiceOver). However, dynamic content such as chatbot conversations and real-time text updates may not always be properly announced by screen readers. The chat interface does not consistently use ARIA roles or live regions, which can lead to gaps in communication for assistive technology users.

________________________________
Potential Accessibility Improvements:

  1.  ARIA Labeling for Dynamic Content: Implement better ARIA roles and live region labeling for dynamic content updates, such as chat responses or error messages, to ensure screen readers can effectively announce changes.
  2.  Keyboard Navigation for Dynamic Elements: Ensure that all dynamic elements, including modals and chat interactions, maintain appropriate keyboard focus. Users should be able to smoothly navigate through dynamic content without losing focus on important elements.
  3.  Contrast and Custom Interactive Elements: Review all interactive elements, particularly custom buttons and input fields, to ensure they meet WCAG 2.1 AA contrast requirements. Text within dynamic components, such as chat modals, should be easily adjustable for users with low vision.
  4.  Improved Error Identification and Feedback: Ensure error messages and other system feedback are accessible for users of screen readers or other assistive technology. Clear labeling and ARIA announcements can help users understand the status of their input or errors that need correction.

________________________________
Conformance Statement:
chatgpt.com partially conforms to WCAG 2.1 Level A and AA, as well as the Section 508 accessibility standards. While the site implements many accessibility features, particularly for static content, further improvements are necessary to ensure that dynamic content, such as chatbot interactions, fully meet the needs of users with disabilities.
________________________________
Accessibility Contact Information:
If you experience any accessibility issues or have suggestions for improving the accessibility of chatgpt.com, please contact us at:
Email: [Insert Accessibility Contact Email]
Phone: [Insert Phone Number]
Accessibility Support Page: [Insert URL]
________________________________
Conclusion:
This ACR report outlines areas where chatgpt.com complies with WCAG 2.1 and Section 508 standards, as well as areas that require further improvement. While static content on the site largely adheres to accessibility standards, dynamic interactions, particularly within the chat interface, present challenges for full accessibility and require additional attention to enhance the experience for all users.



From: athen-list <athen-list-bounces at mailman12.u.washington.edu> On Behalf Of Gian Wild via athen-list
Sent: Sunday, October 13, 2024 10:18 PM
To: athen-list at u.washington.edu
Subject: [Athen] ChatGPT accessibility


EXTERNAL MAIL: athen-list-bounces at mailman12.u.washington.edu<mailto:athen-list-bounces at mailman12.u.washington.edu>: Do not click links or open attachments unless you recognize the sender and know the content is safe. Please contact your college IT Help Desk if you have any questions
Thanks everyone for your comments and information! It was great to know that they haven't just been ignoring only us! It is a bit of a problem though.

I did ask ChatGPT but it was quite evasive (or maybe not believable?)! Here are some questions and answers:

Does OpenAI have a Voluntary Product Assessment Template or Accessibility Conformance Report for you, ChatGPT?
ChatGPT said:
OpenAI does provide information on accessibility and product features, but specific documents like a Voluntary Product Assessment Template (VPAT) or an Accessibility Conformance Report (ACR) might not be publicly available. For detailed information on accessibility, it's best to refer to OpenAI's official resources or reach out to their support for specific requests.
You said:
Can you please provide links to these official resources
ChatGPT said:
I can't browse the internet to provide current links, but you can find official resources about OpenAI's products, including accessibility information, on the OpenAI website. Typically, sections like "Documentation," "Support," or "Accessibility" would have relevant information. If you're looking for specific reports like a VPAT, contacting OpenAI directly through their support channels would be the best approach.
You said:
Is chatgpt accessible?
ChatGPT said:
Yes, ChatGPT is designed with accessibility in mind. OpenAI aims to ensure that the platform is usable by a wide range of users, including those with disabilities. This includes considerations for screen readers, keyboard navigation, and other assistive technologies. If you have specific accessibility concerns or needs, please let me know, and I can provide more detailed information!
You said:
Please provide more detailed information
ChatGPT said:
ChatGPT
Here are some key aspects of accessibility in ChatGPT:

  1.  Keyboard Navigation: The interface is designed to be navigable using a keyboard, allowing users to access features without relying on a mouse.
  2.  Screen Reader Compatibility: ChatGPT is built to be compatible with popular screen readers, which can help visually impaired users interact with the content.
  3.  Clear Language: Efforts are made to use clear and straightforward language to accommodate users with different reading levels.
  4.  Responsive Design: The interface adjusts to various screen sizes and resolutions, making it usable on both desktop and mobile devices.
  5.  Customizable Display: Some features allow users to adjust text size and contrast to improve readability.
For the most accurate and up-to-date information, including specific accessibility features and guidelines, visiting OpenAI's official website or accessibility section is recommended. If you have particular needs or suggestions, OpenAI encourages feedback to improve accessibility further.

Cheers
Gian

Gian Wild, CEO
AccessibilityOz
Company Twitter: @accessibilityoz

Email: gian at accessibilityoz.com<mailto:gian at accessibilityoz.com>
United States: (917) 764 5452
Australia: 0408 223 391 - Mobile: 042 442 6262
Twitter: @gian - LinkedIn: https://www.linkedin.com/in/gianwild/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20241014/901e7f8a/attachment.html>